- Joined
- Aug 20, 2012
- Messages
- 48
- Motherboard
- Gigabyte GA-Z77X-UD5H
- CPU
- Intel Core i5 3.4Ghz
- Graphics
- Gigabyte GeForce GTX 670 OC edition
- Mac
- Classic Mac
- Mobile Phone
Article: MultiBeast 5.2 Update
I tried this, but after removing FakeSMC.kext from my Mountain Lion drive, I was unable to boot to it from Chimera on my USB. I got stuck at the grey apple logo screen, and a verbose boot stopped at the following:
After that I tried booting from my backup (which has the old FakeSMC) and reinstalling FakeSMC & plugins onto my Mountain Lion drive from there, but this resulted in the same kernel panic/freeze up that I was getting before.
The two of us who seem to be having this issue both have factory overclocked editions of the 670, do you think that might be part of the issue?
Edit: I'm going to go ahead and try a complete reinstall of OSX on my Mountain Lion drive using the new MultiBeast. Will report back with results.
Edit 2: After a regular reinstall, I get a KP on boot. Looks like this:
I'm now attempting a complete erase and install to see if a completely fresh installation will work on my system with the new FakeSMC.
Edit 3: Yep, I did a complete erase and install and installed the latest FakeSMC and plugins, (didn't even install iStat, just HWMonitor) and the issue still persists. If I boot up with the HWMonitor menubar plugin disabled it's fine, and I can even turn it on once I'm booted, but if I have it enabled at boot time it freezes my whole system as soon as it loads in the menubar. There is definitely some kind of bug here, it can't be a conflict with any other software. Please let me know if I can help track it down; I don't know what else to try.
I'm rolling back to my MultiBeast 5.1.1 backup for now.
I am running the latest FakeSMC, HWMonitor app and iStat Menu 4 on my GA-Z77X-UP5 TH / GTX 670 on 10.8.2.
For those having issues here is what I recommend you do to fix it:
1) Boot from your UniBeast USB volume and select the OS X Installer volume.
2) Once you are in the installer, select Terminal and the delete the FakeSMC.kext on the volume you are having issues with. The command will like look something like this:
rm -rf /Volumes/ML/System/Library/Extensions/FakeSMC.kext
Replace ML with your volume name. Remember if it has spaces in it surround the name with "".
3) Reboot using your UniBeast USB but this time select the Mountain Lion volume you deleted FakeSMC from.
4) Run MultiBeast and reinstall FakeSMC, Plugins and HWMonitor.app
5) Reboot your system normally.
I tried this, but after removing FakeSMC.kext from my Mountain Lion drive, I was unable to boot to it from Chimera on my USB. I got stuck at the grey apple logo screen, and a verbose boot stopped at the following:
Code:
ACPI_SMC_PlatformPlugin::registerLPCDriver - failed to locate SMC driver
After that I tried booting from my backup (which has the old FakeSMC) and reinstalling FakeSMC & plugins onto my Mountain Lion drive from there, but this resulted in the same kernel panic/freeze up that I was getting before.
The two of us who seem to be having this issue both have factory overclocked editions of the 670, do you think that might be part of the issue?
Edit: I'm going to go ahead and try a complete reinstall of OSX on my Mountain Lion drive using the new MultiBeast. Will report back with results.
Edit 2: After a regular reinstall, I get a KP on boot. Looks like this:
I'm now attempting a complete erase and install to see if a completely fresh installation will work on my system with the new FakeSMC.
Edit 3: Yep, I did a complete erase and install and installed the latest FakeSMC and plugins, (didn't even install iStat, just HWMonitor) and the issue still persists. If I boot up with the HWMonitor menubar plugin disabled it's fine, and I can even turn it on once I'm booted, but if I have it enabled at boot time it freezes my whole system as soon as it loads in the menubar. There is definitely some kind of bug here, it can't be a conflict with any other software. Please let me know if I can help track it down; I don't know what else to try.
I'm rolling back to my MultiBeast 5.1.1 backup for now.