Jump to content
5 posts in this topic

Recommended Posts

My system was running well until yesterday when it started hanging at a blue screen with a movable cursor just after the gray apple screen. If I press f8 and supply a -f boot flag it boots to a login screen and runs correctly after that.

 

I know I can add a -f kernel flag to the com.apple.Boot.plist file to get past the problem, but I would rather solve the problem. I have tried using disk utility to correct permissions but that didn't resolve the problem. I think I saw a topic relating to this same problem a few days ago, but now I can't locate it.

 

If anyone has seen this problem and has any suggestions about how to resolve it I would greatly appreciate the help.

 

Resolved: I had an incorrect user ID on one of the kext and repair permissions did not correct or flag it. I found it by doing a terminal - command-line "ls -ald Extensions/*"

  • 3 weeks later...

This is probably what you saw. I have the same problem after upgrading to Leopard. Unfortunately I don't know squat about Unix commands and can't seem to implement this fix. I tried your -f flag but no luck either.

 

Great workaround

1. Reboot into single-user mode (hold Cmd-S while booting machine)

2. Follow the directions OSX gives you when you get to the prompt (I think these were them - just type the two commands it tells you to):

fsck -fy /

/sbin/mount -uw /

3. Remove the following files:

rm -rf /Library/Preference Panes/Application Enhancer.prefpane

rm -rf /Library/Frameworks/Application Enhancer.framework

rm -rf /System/Library/SystemConfiguration/Application Enhancer.bundle

rm -rf /Library/Preferences/com.unsanity.ape.plist

4. Exit, to continue booting normally

exit

 

It did work for several people on that post so good luck.

actually what you should be doing is booting w/ "-v" (after a successful "-f" boot) to determine what kext is crapping out (before you start deleting kexts since there's many different root causes for the scenario you've described).

 

I appreciate both replies. I have resolved the problem today. One of the things I did was to get the latest copy of enhancer. I also found that even though I had run repair permissions on the drive more than once - there was still a problem. I had missed the ownership on one of the kext. It still had my user ID as owner. I corrected that and repaired permissions again. I think that may have been the problem.

 

Anyway, now it is resolved - mo more -f to boot the system.

  • 5 months later...
×
×
  • Create New...