I'm guessing that you haven't loaded Chimera or Chameleon on the system yet and your having an issue when you boot with your OSX drive as your primary boot device?
When it stops on the Bluetooth stuff, it's almost ALWAYS Graphics related. As for the crash, I'm not sure. It might have something to do with the PowerManagement stuff? maybe? I'm glad you've been able to boot into the system, but sorry to hear your having more/different issues. Now that it's...
It's the GenericUSBXHCI.kext. I wanna say it's already there? I temperately remove it and reload it after with kextbeast. I'll attach it just in case.
It works, it took me two weeks of loading and reloading making small tweaks before I landed on something that worked.
My process was ( not 100% if it'll work for because you're not flashing the BIOS ):
Flash to modified 2.7 Bios
Install Mavericks
boot into mavericks from USB with -v -x
Install Ethernet KEXT
reboot, -v -x
use Multibeast
reboot, -v -x
adjust boot.plist:
GraphicsEnabler=Yes
PCIRootUID=0...
I was having an issue like this, sort of? If you have GenericUSB drivers loaded, try deleting the Kext files. I've gotten my system working, also w/o pwrmgmt, and waited until I had the system running before installing the USB kext files.
Ok, so I just got home from work. Took a look as saw that the FakeSMC is there. Maybe it's the wrong version? Also, I can't get the system to boot into Safe Mode either, it does the same thing as a normal boot, so I'm not sure how I would run KextBeast anyway. Any other thoughts?
Not really sure what's up. There aren't any errors. The boot just hangs at the same spot (see image of verbose boot). Same spot in both normal as well as safe mode.
It sees my RAM, Video Cards, CPU, all at the beginning of the load before the KEXTs start to load.
Here's my Boot.plist. I don't...
Yea, flashed from 2.2 to 2.9.
I've removed the AppleIntelCPUPowerManagement && AppleIntelCPUPowerManagementClient KEXT files. It made the Kernel panic stop, and I'm on to a new issue. It might have something do to with MOBO, or its with the Graphics cards I have? Not 100% sure what's causing...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.