Disabled Dual Head and now No GUI on boot - Suse 10.2, Intel 855 GM, Latitude D505

unassassinalbe · 08-28-2007, 01:04 PM

Hey guys,

I'm fairly new to the Linux world, I am a network and systems administrator but up until about 6 months ago I have been primarily involved in windows based servers. I was asked by my employer to configure Nagios to run on our network and have been since actively involved in Linux and love it!

I have a laptop that I have docked with which I have been running Suse 10.2 on for some time. Yesterday I added a second monitor and setup Dual Head Mode. When leaving the office I disabled dual head mode and got the message "you must restart X for the settings to take effect". I logged out, hit Ctrl+Alt+Backspace and it brought me to a command prompt. I restarted the computer and it also brought me to a command prompt. No X. I logged in as root, ran the "startx" command and got error:

Fatal server error:
no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

I tried running "sax2" got the following message:

Sax: no X server is running
Sax: will start own server if needed

The screen then went totally blank. I could not do anything to get back to the command line. Ctrl+Alt+Del restarted the computer, I ran sax2 -p and it outputs the following:

Chip: 0 is -> Intel 855 GM 00:02:0 0x8086 0x3582 PCI i810

The laptop is a Dell Latitude D505. If you need any other info, please ask. Thanks in advance,
Rich

unassassinalbe · 08-29-2007, 10:58 PM

Nevermind, I found the problem in the logs.

If your curious as to a fix, reply and id be glad to post it.

Rich

Kenn McHugh · 10-03-2007, 08:59 AM

Hi,

I've run into the same problem on my IBM X41 laptop. I'm not sure where or what logs to check. Can you tell me what you had to do to fix it?

Kenn

Kenn McHugh · 10-04-2007, 09:18 AM

After using SaX2 to disable Dual Head monitors, the X server would no longer start. This included SaX2 no longer starting.

I found in the /etc/X11/xorg.conf file that SaX2 had not removed all necessary settings.

Under the the device section for the monitor, there were still two lines for dual head 'Options'listed. One indicated a merged screen. The second indicated the relative position of the monitors. It seems that because of this, the X server was looking for a second monitor device definition.

Removing these lines from the file seemed to correct the problem and allowed X server adn KDE to function normally.

unassassinalbe · 10-04-2007, 12:06 PM

Quote:

Originally Posted by Kenn McHugh

After using SaX2 to disable Dual Head monitors, the X server would no longer start. This included SaX2 no longer starting.

I found in the /etc/X11/xorg.conf file that SaX2 had not removed all necessary settings.

Under the the device section for the monitor, there were still two lines for dual head 'Options'listed. One indicated a merged screen. The second indicated the relative position of the monitors. It seems that because of this, the X server was looking for a second monitor device definition.

Removing these lines from the file seemed to correct the problem and allowed X server adn KDE to function normally.

Thats exactly what I found as well. Sorry I didnt get back to you after your first post, but thats cool you found the solution as well. It's too bad also that this has to be a problem. Youd think if you removed one monitor it would be able to re-configure the x.org file automaticly...

Rich

Kenn McHugh · 10-05-2007, 07:23 AM

Thanks, Rich. At least we know how to correct that one in the future.

Kenn