Jump to content

Snow Leopard booting slow, What is with my Bootmessages ?


6 posts in this topic

Recommended Posts

Hello,

 

my SL booting 30s.

 

Can anywhere take a look on my 2 Bootscreens and say me, if all correct ? Or gives Errors ?

 

cimg5300rh8p.jpg

 

cimg5301qgce.jpg

 

And an other Question. I use Apple Speedstep with my C2D. Must I have the Voodoopstate kext or it this kext only for P State check ?

 

Thanks

Link to comment
Share on other sites

Try unplugging and/or disabling all devices that aren't essential to get the system booting.

 

To begin with try unplugging all other hard drives (see NTFS error message in second screenshot) and disable Bluetooth as well.

Link to comment
Share on other sites

What do you mean SLOW BOOT?

 

you clearly say "my SL booting 30s."

 

that is not bad at all... mine is 24s from turning on computer to the desktop load

 

or am I confused somewhere?

Link to comment
Share on other sites

@Beerkex'd: Thanks but I'am need Bluetooth and NTFS Drive ^^.

 

@sendblink23: Thanks, OK when 30s is good then I want to use this Setting ^^

But the messages: "not found and kext not ..." isthis an Error?

Or fakesmc: key not found :thumbsup_anim:

Link to comment
Share on other sites

But the messages: "not found and kext not ..." isthis an Error?

Or fakesmc: key not found :wacko:

 

Are you using an extensions.mkext in /extra? I get those messages as well for some of the extensions on my EFI partition.

OS X boots fast enough for me so I haven't tried to find out if there's a way to get rid of those messages.

 

I know there are some extensions that must be inside the mkext for them to load but I haven't done any experiments with that either, I use extra/extensions and extra/extensions.mkext at the same time, with the same contents in both.

 

Try without an extensions.mkext and see if those messages go away. Or try only with an mkext.

 

The fakesmc messages you can fix by adding the missing key to the plist inside fakesmc.kext (search for a how-to, I think there's one on Prasys' blog) - or you can disable the messages altogether, there's a debug messages flag in the plist you can toggle.

 

But IMO none of those messages slow down the boot process enough to worry about. You should probably be investigating that NTFS error message instead.

 

Run Console.app and check the kernel log. You can look at the time stamps and see exactly where in the boot process there is a slowdown.

Link to comment
Share on other sites

 Share

×
×
  • Create New...