altares Posted October 22, 2014 Share Posted October 22, 2014 I had a working Yosemite + Chameleon setup and I migrated to Clover. Everything's working fine except that, every-time I log into my session, I get a "Problem Report for OS X" asking me to send to Apple along with the usual message "Your computer did not shut down properly... Do you wish to reopen you apps...". This is getting annoying as I can't grasp where that came from. I didn't have these messages before Clover. I use Nvidia's web driver because I own a 970 GTX. This is part of the backtrace: Kernel Extensions in backtrace: com.apple.iokit.IOGraphicsFamily(2.4.1) dependency: com.apple.iokit.IOPCIFamily(2.9) com.apple.nvidia.driver.NVDAResman(10.0) dependency: com.apple.iokit.IOPCIFamily(2.9) dependency: com.apple.iokit.IONDRVSupport(2.4.1) dependency: com.apple.iokit.IOGraphicsFamily(2.4.1) dependency: com.apple.AppleGraphicsDeviceControl(3.7.2) BSD process name corresponding to current thread: WindowServer What do you think? UPDATE: I installed Clover fron scratch, without the Nvidia driver (software mode), and the KP report still is here on every reboot. Even the very 1st one after Yosemite's installation. Installing Nvidia's web driver after that didn't change a thing. Seems like Clover has an issue with Nvidia. How to stop this? Link to comment Share on other sites More sharing options...
jamiethemorris Posted October 22, 2014 Share Posted October 22, 2014 do shutdown and restart work correctly? Link to comment Share on other sites More sharing options...
ADHDMedia Posted October 23, 2014 Share Posted October 23, 2014 I am also experiencing this same issue. Also, when I install the nVidia Web Driver, I can't boot at all with Clover UEFI. I have to use Legacy to even get into my system. Not sure what's going on… Note: I've been using Clover through the entire Yosemite beta process, and everything was fine until I updated to the official version via the MAS. Link to comment Share on other sites More sharing options...
jamiethemorris Posted October 23, 2014 Share Posted October 23, 2014 What version of Clover are you guys using, and what does nvram -p give you? Link to comment Share on other sites More sharing options...
altares Posted October 23, 2014 Author Share Posted October 23, 2014 What version of Clover are you guys using, and what does nvram -p give you? Using the latest version to date: r2953. NVRAM works correctly on my part and gives the correct vars between reboots along with the very very long: aapl,panic-info %f0%b0;=F%8d%.... Shutdown and boot "looks" to precede normally, except that KP report at login time. Oh, and it may be because of this, but login time (after entering my password) is very very long compared to what it used to be on my system before Clover. Link to comment Share on other sites More sharing options...
jamiethemorris Posted October 23, 2014 Share Posted October 23, 2014 Try enabling haltenabler, slpsmiatwake, and shutdownfix. I had this problem before a while back, unfortunately I don't remember what fixed it... See if that helps. Otherwise I don't know, it could be stuck in nvram so you could try clearing it with nvram -c. Link to comment Share on other sites More sharing options...
altares Posted October 23, 2014 Author Share Posted October 23, 2014 Try enabling haltenabler, slpsmiatwake, and shutdownfix. I had this problem before a while back, unfortunately I don't remember what fixed it... See if that helps. Otherwise I don't know, it could be stuck in nvram so you could try clearing it with nvram -c. Man, you're a genius. When I read your post it jumped at me instantly: this HAD to do with the NVRAM variable that was stuck in there. So I finally cleared that memory and the issue was gone! It was not obvious tho, my NVRAM has some kind of bug that I just discovered. It wouldn't delete variables when I asked it to, nor be cleared by the -c command argument (in sudo mode). I tried multiple times with my own variables and it was resisting all along. Then, out of the blue, it cleared that aapl-report variable and still wouldn't let me clear my own test variable... Seriously, something's wrong with that NVRAM emulator EFI - I can't use my native NVRAM because of it being modified on every reboot. Thank you again JamieTheMorris, you're a true life saviour!!! Sheers! Link to comment Share on other sites More sharing options...
jamiethemorris Posted October 23, 2014 Share Posted October 23, 2014 Man, you're a genius. When I read your post it jumped at me instantly: this HAD to do with the NVRAM variable that was stuck in there. So I finally cleared that memory and the issue was gone! It was not obvious tho, my NVRAM has some kind of bug that I just discovered. It wouldn't delete variables when I asked it to, nor be cleared by the -c command argument (in sudo mode). I tried multiple times with my own variables and it was resisting all along. Then, out of the blue, it cleared that aapl-report variable and still wouldn't let me clear my own test variable... Seriously, something's wrong with that NVRAM emulator EFI - I can't use my native NVRAM because of it being modified on every reboot. Thank you again JamieTheMorris, you're a true life saviour!!! Sheers! No worries, I'm glad that worked out for you. I believe NVRAM is being worked on right now. It's not working too well for me either (with or without EmuVariable). Link to comment Share on other sites More sharing options...
Recommended Posts