Jump to content

Succesful installation but OSX86 doesnt boot


9 posts in this topic

Recommended Posts

The installation went perfctly well but after the machine restarted it went to the grey screen with the apple logo then ten seconds later it went to a blue screen.

 

This is a single boot installation thus I have a whole HDD dedicated to OS X. I am running it on a Core 2 Duo E6600, Asus P5W DH Deluxe and Sapphire ATI X1900XT, also I installed OS X on a SATA hard-drive not an IDE one. All the hardware is said to be compatible.

 

I suppose this might kick me in the arse but I didnt follow any of the installation guides because they only had details of what to do with partitions on a HDD and how to dual boot. Dont flame me, I did read them just I thought I didnt need to do anything to/in XP to make OS X work.

 

Please help: what do I do next?

 

Thanks in advance.

 

EDIT: -spelling correction-

 

EDIT: The packages I chose were: Intel Combo update 10.4.7, SSE3 and ATI X1600/X1800/X1900 drivers. Imight also be in the wrong subforum! :P

Edited by PurpleObscurity
Link to comment
Share on other sites

"Posting #3 takes you to an installer": I tried this one first because I was lazy and after downloading the older one (3.2 - which in the read me did not mention the X1900), running it and restarting my machine it returned me to the blue screen (which proceeds the grey screen w/ Apple logo). So I will try the manual method by Boris, unless you can suggest something else.

 

BTW, I had to reinstall the OS to revert to the original. Is their a way to boot in 'safe mode', to prevent having to reinstall every time I {censored} up?

Link to comment
Share on other sites

When OSX starts to boot, first the screen turns black and then goes to grey with the spinning gear icon. Just as soon as the screen turns black, press and hold the F8 key until a command prompt appears. If the grey screen shows up, you were too late, try again. At the prompt, type one or more of the following:

 

-v for verbose mode to read boot messages for troubleshooting

-x for safe mode to troubleshoot in a GUI environment

-s for single user mode, a command line environment for troubleshooting when you can't boot

-f to bypass reading the cache of kexts, overcomes some booting problems.

 

You can combine all of them except only choose one of -x or -s since they do different, not complementary things.

Link to comment
Share on other sites

Thanks for that last tip. I tried Boris method and that after rebooting resulted in a screen which was darker grey with a message in multiple languages telling me to rebbot. tried that and then again in single user mode (thanks again) but no luck (it said there was a panic: presumably a kernel panic something to do with one of the modified kexts.

 

Now Im stuck. It could be have been an error in my typing but I doubt it. Is it possible that in the system profiler when it gives the device ID should it be in hexadecimal or decimal? (My id contained no letters so a n uneducated guess would be its decimal but Boris' example contained a letter as well as the content of the kext files).

 

I will try the installer method again.

Link to comment
Share on other sites

 Share

×
×
  • Create New...