Contribute
Register

MultiBeast 5.0 for Mountain Lion

Status
Not open for further replies.
Do not use the FakeSMC Nvidia plugins, when using native supported Nvidia cards, NVClockX.kext will cause system panic during boot in such situations.
 
thanks forever
 
Hi, from Australia

I am experiencing slow boot up times with Mountain Lion compared with Lion.
When I Boot Verbose mode I can see that it takes a long time to find "Got boot device =".

Is there any way of reducing this time delay?


CPU: Intel i7-2600K
Graphics: PowerColor ATI Radeon HD 5770
Motherboard: Gigabyte Z68XP-D3, BIOS ver. F3
 
it's no good for my after install of MultiBeast 5.2 ! Mail Quit Unexpectedly

asus p8z68-v pro
GeForce GTX 560 1024 MB
I did something wrong?
 
Article: MultiBeast 5.0 for Mountain Lion

Thanks- we've already identified the issue, and 5.0.1 is on the way.

I'm getting a CPU unknown error. Any chance you could update the archives with newer versions of multibeast eg 5.0.1? (-I posted my issue in the lab.)
The last mbeast listed there is 4.5.2, and that didn't help. The multibeast listed a week ago worked fine -no luck with 5.0.2, now I'm stuck! (please and thank you)
 
Article: MultiBeast 5.0 for Mountain Lion

I'm getting a CPU unknown error. Any chance you could update the archives with newer versions of multibeast eg 5.0.1? (-I posted my issue in the lab.)
The last mbeast listed there is 4.5.2, and that didn't help. The multibeast listed a week ago worked fine -no luck with 5.0.2, now I'm stuck! (please and thank you)

You're talking about the following error during verbose boot? (taken from Console.app)
Code:
15.08.12 17:17:36,000 kernel[0]: WARNING: IOPlatformPluginUtil : getCPUIDInfo: this is an unknown CPU model 0x3a
I keep getting this error since my first install with Lion and Bridge Helper. It keeps showing up even on ML but I suspect it do be irrelevant since everything works fine.
 
Among changes in MB 5: "Removed System Utilities" ... did I miss the memo as to why? Someone please enlighten me!

I'm puzzled! Can't find any explanation as to why it's been removed... We were supposed to basically ALWAYS do Repair Permissions, and now it's not there any more... what are we supposed to do?

Is MB now doing Permission repairs systematically without asking? Or are we supposed to do it manually in Disk Utilities???

Nobody seem to be bothered by this, I guess if your Hackintosh runs fine, then you don't worry, but if you have issues you start wondering whether the lack of Repair Permissions is the cause...
 
Status
Not open for further replies.
Back
Top