Fine install on 8550 - now no video in OS X |
September, 28, 2002 11:50 AM |
winkie |
I completed the install of OS X Server 10.1 on my 8550 Server box and everything was running fine until I looked at the System Preference 'Displays' in OS X. I clicked on the 'Colors' button, saw that only 'Thousands' was available and immediately the screen went black. Quit and shutdown by using Power Button and hitting return. Shut down ok. Here is what I have done since: Restarted in OS X - grey screen with Apple comes up, momentary blue screen pops up and then screen goes black but startup continues and seems to be ok. I did not bother to check this fact with the Server Admin client. Whe I restart in OS 9.1 and everything is fine. Tried resetting Open Firmware with Cmd, Opt O+F and typed reset-all, reset the motherboard rerset button for 15 seconds. Same OS X black screen but OS 9.1 is fine. I'm lost now. Any suggestions? |
. |
RE: Fine install on 8550 - now no video in OS X |
September, 29, 2002 1:17 PM |
winkie |
. |
I had suspected that a preference file was at fault but had no idea what it might be called or where it was located. This solution worked fine. This advise was well worth the $10 . to me. Cheers |
. |
RE: Fine install on 8550 - now no video in OS X |
September, 28, 2002 3:38 PM |
OSXGuru |
. |
What you'll probably need to do is delete a preferences file at the following path (it will be recreated with default settings). It is at: /Library/Preferences/com.apple.windowserver.plist You may also need to delete a preference file in your home directory, if it exists. It would be located in this directory: /Users/[your user name]/Library/Preferences/ByHost And the name of the file would start with "com.apple.windowserver". I get the same thing on occasion with my monitor, though usually after changing a Display setting, rather than just looking at it. It appears that the Display preferences don't always correct understand what resolution / frequency combinations the monitor supports. Presumably this is a bug that could be fixed, but I haven't spent much time trying to figure it out. |