Kernal Panic and Clover not working after El Capitan install reboot

SOLVED: Kernal Panic and Clover not working after El Capitan install reboot

SOLVED in Post #9.....

--------

I followed the guide for a direct update. I copied the kext's from the 10.10 folder into the 10.11 folder in the EFI.
I modified the config.plist with the suggested RT varibles.

I ran the installer and rebooted, selected the OS X installer disk and then the installation ran. When it finished, the computer rebooted, got to clover and selected the Boot OS X disk. Then it kernal panicked and rebooted.

When I get to the clover screen, the left plain disk (boot clover from EFI) does not do anything. If I click it, it just blacks the screen and brings me back to the main clover menu. It worked with mavericks.

If i click below on options to run change config parameters or anything, when I select an option the mouse freezes.

The only thing that works is the Boot Recovery from Recovery HD option on the right, which will get me to disk utilities and a reinstall option.

If I hit the spacebar and select verbose, single user, safemode, or any of the options to boot with out kexts or caches, etc, still get a kernal panic.

I feel like Clover got nuked somehow.

Here is a pic of the kernel panic....



Any suggestions would be much appreciated.

Appears to be panicking at ACPI: S3 S4 S5

I can get to the Terminal, any thoughts what i can do in there?

What is the "Emergency partition"

Meant the Boot Recovery on the right.

Read the rules, http://www.tonymacx86.com/faq.php and put your system specs in your profile...

Sorry, can't get all the specs with the thing down.

Do you have a backup of your config.plist? Maybe when you made the change you introduced some bad formatting or something. If you have a backup you can mount the EFI partition from Terminal and replace the current config.plist with the backup.

Worst case, you should be able to get a Clover USB stick working and boot from that, which will avoid any problems with the Clover on your hard drive, at least long enough to fix up the hard drive Clover install/config.

If its anything, I have this exact same issue on a GA-Z97 board with 4690K and 580GTX

I have this same issue as well. I can boot to recovery and run a terminal, disk util etc, but when it comes to booting into the OS, I get the Apple screen loading bar for about a second before the machine reboots.

I have tried (via terminal) replacing my config.plist with a backup that worked flawlessly with Yosemite, but still no dice. In fact, the backup was so unusable that I could no longer boot to recovery! I had to use the UEFI shell to get my installer config.plist back into place. I also attempted to reinstall the OS (via backup), but Apple will not allow it. I get an error that says something about unable to verify...blah blah contact AppleCare. My lovely machine is now stuck using Windows 10 instead of 10.11

I found a work around!!

As it turns out, the kernel panic we are experiencing is KEXT related. I didn't know what kext was causing the problems, so I went with the nuclear option of replacing ALL of my kexts. Since our machines are capable of booting into System recovery, we can fix this problem by doing a good old S/L/E swap. This gets pretty Terminal heavy, so be warned!

Boot into OS X Recovery. Once there, open a terminal from the menu at the top of the screen.

First, enter the following two commands:
This will list all of your machine's partitions. The two that we are interested in are your Mac's hard drive, and the one called Mac OS X Base System. In the following commands, make sure where I write "Macintosh\ HD" that you replace it with whatever your system's hard drive is called. For example, my machine is actually called Mac HD, so I would have wrote "Mac\ HD" in the commands.

Enter this command:
This will backup your current extensions so we can make sure we don't do something irreversible.

Next, enter this command:
This will copy the S/L/E from your working recovery system to your El Capitan install. After doing this, reboot your machine and you should be able to boot your system like you did on Yosemite (it will, however, have to finish installing).

stevereno30... .You da man!

It worked.. Make sure to make "Extensions" at the end of the final step with an uppercase "E".... Did lower case the first time and it didn't work.

Also, since it needs to finish installing, it might take a while before you see something happen on screen, or get a spinning beach ball. BUT, as long as the disk is thrashing, then it's making progress.

Thanks
RCK