Multibeast Install Failed (5.2.1) - Chimera 2.0 related?

[adrianjgsmith]

I couldn't wait for the newest version of Multibeast to fix my iMessage issues, so I went ahead last night and updated Chimera 2.0 via the standalone installer.

Today I wanted to add in the FakeSMC plugins from Multibeast 5.2.1, but every time I try to install it fails: the kexts never show up in /System/Library/Extensions. I also tried reinstalling AHCI_3rdParty_eSATA, which I already have, as a test, but same error there, too.

Could this be related to having gone on to Chimera 2.0, or am I barking up the wrong tree?

 

[Say Heading]

(...)or am I barking up the wrong tree?

Probably, as long as you mean the plugins only.
They should be in System>Library>Extensions>FakeSMC.kext>Contents>PlugIns.

Edit: Can´t get rid of that empty space in Pl ugIns?! WTF?

 

[adrianjgsmith]

The kexts are there, even though Multibeast reported an installation failure. But HWMonitor still doesn't show any data from the CPU/GPU/motherboard etc.

Tried using Kext Utility to repair permission, but no joy so far...

 

[Say Heading]

Hm, strange...
Have you tried installing from a user account or logged in as administrator or root? I remember that helped me in a similar situation with other software.

 

[adrianjgsmith]

My main user account is the admin account, so don't think it's that. It's definitely not Chameleon 2.0, as I've since rolled my system back and still have the problem. Reading around, I might have let a dodgy legacy kext creep in there, so will have a look into that over the weekend. Thanks for your help so far.

 

[adrianjgsmith]

Well here's my console log from a failed install attempt I just made:


15/03/2013 13:29:09.942 coreservicesd[68]: Application App:"Installer" [ 0x0/0x152152] @ 0x0x7ff983e36bf0 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x154154 ), so denying.
15/03/2013 13:29:09.942 WindowServer[106]: [cps/setfront] Failed setting the front application to Installer, psn 0x0-0x152152, securitySessionID=0x186a5, err=-13066
15/03/2013 13:29:20.372 com.apple.kextd[16]: kextcache error while updating / (error count: 29)
15/03/2013 13:29:21.071 Installer[15627]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
15/03/2013 13:29:21.223 Installer[15627]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
15/03/2013 13:29:25.384 com.apple.kextd[16]: /: kextcache has had enough tries; not launching any more

 

[RehabMan]

Well here's my console log from a failed install attempt I just made:


15/03/2013 13:29:09.942 coreservicesd[68]: Application App:"Installer" [ 0x0/0x152152] @ 0x0x7ff983e36bf0 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x154154 ), so denying.
15/03/2013 13:29:09.942 WindowServer[106]: [cps/setfront] Failed setting the front application to Installer, psn 0x0-0x152152, securitySessionID=0x186a5, err=-13066
15/03/2013 13:29:20.372 com.apple.kextd[16]: kextcache error while updating / (error count: 29)
15/03/2013 13:29:21.071 Installer[15627]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
15/03/2013 13:29:21.223 Installer[15627]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
15/03/2013 13:29:25.384 com.apple.kextd[16]: /: kextcache has had enough tries; not launching any more

You have an issue with installed kexts preventing your kernel cache from being created.

Try to determine the cause:
- reboot (this resets kextcache's error count)
- run Console.app
- run Kext Wizard and rebuild cache, keeping an eye on system.log

You should see errors from kextcache in system.log which should give you an idea of the kext(s) causing the issue.

 

[adrianjgsmith]

Thanks RehabMan, looking in the system.log there were a ton of errors about dependencies in FakeSMC for the plugins I'd tried to add. Reinstalling FakeSMC with Multibeast seems to have fixed it for me.