- Joined
- May 30, 2012
- Messages
- 108
- Motherboard
- ASUS P8Z77-I (patched ROM)
- CPU
- i7 3770k
- Graphics
- Gigabyte GTX 670 2GB OC edition
- Mac
- Classic Mac
- Mobile Phone
This is weird. I have successfully installed El Capitan 10.11.2 with these small issues, and I HAD it working up until about an hour ago when it started KP'ing.
Firstly, I had it working BUT:
So today I have the following issue:
I backed up my config.plist file to my desktop just in case, then I opened Clover Configurator. I loaded the theme I wanted (bootcamp) and changed it. Noticed that if I opened config.plist, no "theme" was evident at all, and the file as a whole was a whole lot shorter than it used to be... a bit of a worry but let's continue. Noticed that my new theme has been downloaded to it's new folder on the EFI drive, so that part appeared to have worked... maybe it doesn't need to be listed in config.plist any more?
I added the nvda_drv=1 flag to the boot flags, since the big El Cap installation guide says very clearly that you should do that after installing the web drivers from nvidia. I have a GeForce 680 btw.
I didn't change anything else in Clover Configurator, thinking I would reboot to check before adding more stuff.
Rebooted - immediate KP in AppleIntelCPUPowerManagement.
I read the Big List Of Problems and it says that if you get that you should set cpus=1. Tried that but it still KP's. I also tried removing the nvda_drv=1 flag from within clover, but it pops back up as soon as I go back a menu. I cannot find a way to delete any of the hardcoded flags at all (i.e. the ones that are in config.plist) - no matter what I do (tried nv_disable=1 nvd_drv=0 -s -v -x...etc but whatever I type, nvda_drv=1 pops up at the end when I actually boot). I don't get it. See this screenshot - I also note that it has inexplicitly changed my system definition from the (working) MacPro3,1 to an iMac13,2 which I think was my system definition under Yosemite and earlier. When I had El Capitan working it was always as a MacPro3,1.
And to top it all off, I still can't use clover's Shell - it won't let me type more than 2-4 characters before the cursor goes back to the beginning of the line again, making whatever I type garbage.
I also noted in the Big List Of Solutions this tid-bit:
If I can just get into my system once I can put the old, working config.plist back into place and delete CloverConfigurator forever... but I can't even do that.
Any ideas?
Firstly, I had it working BUT:
- I noticed that when I started up the screen was very yellow, but then it corrects itself. May be something to do with f.lux but when I quit that app, it goes yellow again - it's like yellow is the default state but f.lux starts up and is correcting it again... not sure what's happening here.
- Before or after installation and even now, whenever I tried to go into Clover's shell prompt, I could never type. I would get a few characters (1-4 usually) but the cursor would jump back to the beginning of the line, and I could not type any coherent lines at all.
- USB 3 seemed to work fine
- I could never get the clover theme to change. other boot flags seemed to make it into clover upon boot, but not the theme. I definitely had it set correctly in the config.plist file. And I was definitely typing in the correct file as evidenced by the fact that my boot flags made it there. The theme that seems very persistent is the new year's one, very annoying.
- That's all the weird stuff I can remember, everything else seemed to work fine (hey I even had sound working off the board, which I've never had before!
So today I have the following issue:
I backed up my config.plist file to my desktop just in case, then I opened Clover Configurator. I loaded the theme I wanted (bootcamp) and changed it. Noticed that if I opened config.plist, no "theme" was evident at all, and the file as a whole was a whole lot shorter than it used to be... a bit of a worry but let's continue. Noticed that my new theme has been downloaded to it's new folder on the EFI drive, so that part appeared to have worked... maybe it doesn't need to be listed in config.plist any more?
I added the nvda_drv=1 flag to the boot flags, since the big El Cap installation guide says very clearly that you should do that after installing the web drivers from nvidia. I have a GeForce 680 btw.
I didn't change anything else in Clover Configurator, thinking I would reboot to check before adding more stuff.
Rebooted - immediate KP in AppleIntelCPUPowerManagement.
I read the Big List Of Problems and it says that if you get that you should set cpus=1. Tried that but it still KP's. I also tried removing the nvda_drv=1 flag from within clover, but it pops back up as soon as I go back a menu. I cannot find a way to delete any of the hardcoded flags at all (i.e. the ones that are in config.plist) - no matter what I do (tried nv_disable=1 nvd_drv=0 -s -v -x...etc but whatever I type, nvda_drv=1 pops up at the end when I actually boot). I don't get it. See this screenshot - I also note that it has inexplicitly changed my system definition from the (working) MacPro3,1 to an iMac13,2 which I think was my system definition under Yosemite and earlier. When I had El Capitan working it was always as a MacPro3,1.
And to top it all off, I still can't use clover's Shell - it won't let me type more than 2-4 characters before the cursor goes back to the beginning of the line again, making whatever I type garbage.
I also noted in the Big List Of Solutions this tid-bit:
- Another option that might work is to set KernelAndKextPatches/AsusAICPUPM to true in config.plist
If I can just get into my system once I can put the old, working config.plist back into place and delete CloverConfigurator forever... but I can't even do that.
Any ideas?
Last edited:
