Recent content by peterb

Photolibrary process eating up all CPU time in the 'Setting up your MAC' window when losing in after the upgrade process. Its been in there for more then an hr now

Adding the patched AppleRTC.kext to the system via mutibeast (7.0.1) causes system to hang at the end of boot, White screen, no curser. last messages with -v geforcesensors: Still waiting ..... Copied the original AppleRTC.kext from other system back via USB (boot) and shell. System is...

I am having problems with the USB mouse. I have a USB mouse hooked up and a magic mouse via a BT adapter. Both work in ML. After the boot from the USB stick the initial installation screen come up. Keyboard works, mouse not. Removed all other USB connections from PC. No luck. Move USB mouse...

I'll try it on my macbook first...

System refuses to boot after using multi beast 5.2.1 after 10.8.3 upgrade. Offending item, fakesmc.kext System P55MU2 with GT 640 graphics card. Recovered by booting from USB stick 10.8.2 and removing FakeSMC.kext from /System/Library/Extensions. Reboot via usb cimera, HD version did not...

Do the Nvidia GTX updates also apply to the GT keplar based cards?

Own a macbook pro 2009. Would never go back to a wintel environment. Each time I try to help someone out with a wintel PC I end up spending hrs to get things sorted. And with a MAC (OSX) , no issues, you get things changed/configured in minutes!

Article: MultiBeast 5.0 for Mountain Lion MB 5 does not cleanup stuff from older versions MB, so be careful. You manually have to remove old stuff, especially if names of kext files have changed. I don't think updates of same kext is a problem.

The problems brought up in this thread are caused by a couple of issues, all to do with the fact that when upgrading OSX and then subsequently using a new version of MB, MB does not clean up old versions or obsolete kext from previous installs. There is a post by rabbit74 describing the...

Do not use the FakeSMC Nvidia plugins, when using native supported Nvidia cards, NVClockX.kext will cause system panic during boot in such situations.

Remove fakesmc.kext, rebuild the cache, reinstall fakesmc.kext from mb 4.6 That will get you back to being able to install things. I downloaded the latest fakesmc package from projectx website, installed those by hand (plugins in /s/l/e ) , removed all old plugins and fakesmc, copied new...

MB 5.0 FAkeSMC.kext clash with MB 4.6 FakeSMC plugins? Reading the following in MB 5 release notes: - Update all FakeSMC Plugins to install in the Plugins directory inside of FakeSMC.kext Does this mean that the old FakeSMC plugins that were installed by MB 4.6 before upgrading to ML have to...

Multibeast 5.0.1 support questions, FakeSMC causing installation failed messages. Reading the following in MB 5 release notes: - Update all FakeSMC Plugins to install in the Plugins directory inside of FakeSMC.kext Does this mean that the old FakeSMC plugins that were installed by MB 4.6...

I'm seeing installation failed after using FakeSMC.kext from MB 5.0.1 Instalation of other packages also give failed error messages. Culprit seems to be FakeSMC.kext from 5.0.1, From Install.log: Aug 14 11:41:18 pbmac.local installd[5028]: PackageKit: kextcache -system-caches Aug 14...

Had the same issue, install of other packages fail too, had a look at install.log, kextcache: //System/Library/Extensions/FakeSMC.kext is not authentic; omitting from prelinked kernel. Looks like cache rebuild fails on FakeSMC.kext. Can someone make this kext appear as an authentic...