LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices


Reply
  Search this Thread
Old 09-08-2009, 10:06 AM   #1
aunola
LQ Newbie
 
Registered: Jul 2008
Posts: 3

Rep: Reputation: 0
X-server fails to start on Fedora 11 box w/o mouse,kbd and monitor


I recently upgraded a cluster from Fedora 7 and 9 to all Fedora 11. I then noticed that all the cluster nodes that have no mouse, keyboard and monitor connected to them fail to start the X-server. This problem did not exists in the previous distro's mentioned above.

Here is a part of what /var/log/Xorg.o.log says:

(II) NOUVEAU(0): Bios version 05.67.32.22
(WW) NOUVEAU(0): TMDS table script pointers not stubbed
(II) NOUVEAU(0): Found Display Configuration Block version 3.0
(!!) NOUVEAU(0): Raw DCB entry 0: 02000310 00000023
(!!) NOUVEAU(0): Raw DCB entry 1: 04031322 00000080
(--) NOUVEAU(0): Parsing VBIOS init table 0 at offset 0xD877
(EE) NOUVEAU(0): ========== misaligned reg 0x001020FB ==========
(EE) NOUVEAU(0): ========== misaligned reg 0x001020FB ==========
(--) NOUVEAU(0): Parsing VBIOS init table 1 at offset 0xD9D5
(--) NOUVEAU(0): Parsing VBIOS init table 2 at offset 0xD9D6
(EE) NOUVEAU(0): ========== unknown reg 0x0077FFF4 ==========
(EE) NOUVEAU(0): ========== unknown reg 0x0077FFF8 ==========
(EE) NOUVEAU(0): ========== unknown reg 0x0077FFFC ==========
(--) NOUVEAU(0): Parsing VBIOS init table 3 at offset 0xDB58
(--) NOUVEAU(0): Parsing VBIOS init table 4 at offset 0xDBD8
(EE) NOUVEAU(0): Pointer to flat panel table invalid
(II) NOUVEAU(0): Output VGA-0 using monitor section Monitor0
(II) NOUVEAU(0): I2C bus "VGA-0" initialized.
(II) NOUVEAU(0): Output DVI-D-0 has no monitor section
(II) NOUVEAU(0): I2C bus "DVI-D-0" initialized.
(II) NOUVEAU(0): I2C device "VGA-0:E-EDID segment register" registered at address 0x60.
(II) NOUVEAU(0): I2C device "VGA-0:ddc2" registered at address 0xA0.
(II) NOUVEAU(0): EDID for output VGA-0
(II) NOUVEAU(0): I2C device "DVI-D-0:E-EDID segment register" registered at address 0x60.
(II) NOUVEAU(0): I2C device "DVI-D-0:ddc2" registered at address 0xA0.
(II) NOUVEAU(0): EDID for output DVI-D-0
(II) NOUVEAU(0): Output VGA-0 disconnected
(II) NOUVEAU(0): Output DVI-D-0 disconnected
(WW) NOUVEAU(0): No outputs definitely connected, trying again...
(II) NOUVEAU(0): Output VGA-0 disconnected
(II) NOUVEAU(0): Output DVI-D-0 disconnected
(WW) NOUVEAU(0): Unable to find initial modes
(EE) NOUVEAU(0): 1526: No valid modes.
(II) UnloadModule: "nouveau"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib64/xorg/modules//libvgahw.so
(II) UnloadModule: "dri"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib64/xorg/modules//libint10.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found


The problem with this is that now the cluster software cannot run, because all the nodes must execute a program that attempts to connect to the local X-server. Since that never starts, this program will no longer run.

I have tried to add the Option

Option "AutoAddDevices" "off"

to the ServerLayout section of xorg.conf thinking if I disbaled the HAL probing it might help. It does not. I have seen some other threads in this forum about this, but none with a resolution.

I guess the problem is how to make sure X-server starts even if no monitor is connected.

Any ideas ?
 
Old 09-09-2009, 06:29 AM   #2
cardy
Member
 
Registered: Jan 2005
Location: Shropshire, England, UK
Distribution: RedHat, Fedora, CentOS..........
Posts: 121

Rep: Reputation: 19
The problem here appears to be the driver detecting the no attached screen.

(II) NOUVEAU(0): Output VGA-0 disconnected
(II) NOUVEAU(0): Output DVI-D-0 disconnected
(WW) NOUVEAU(0): No outputs definitely connected, trying again...
(II) NOUVEAU(0): Output VGA-0 disconnected
(II) NOUVEAU(0): Output DVI-D-0 disconnected
(WW) NOUVEAU(0): Unable to find initial modes
(EE) NOUVEAU(0): 1526: No valid modes.

Because no screen is attached then no modes can be determined thus the drivers for x are unloaded and the server shuts down.

You can look at the following

man intel

which will show the options for the intel card drivers, in particular the

Option "DDC" "0"

May be of use to stop the card trying to use ddc to determine the monitor attached. More information about DDC is available here http://en.wikipedia.org/wiki/Display_Data_Channel.

I have not tried it but it may stop the server testing for a monitor, if not some of the other information in there may be of use.
 
Old 09-09-2009, 08:28 AM   #3
aunola
LQ Newbie
 
Registered: Jul 2008
Posts: 3

Original Poster
Rep: Reputation: 0
Thank you for your reply.

The nouveau driver is an nVidia one and it does not appear to have the DDC option according to man nouveau. However, I created another xorg.conf file using simply vesa, which seems to be more forgiving.

After that, the X-server starts fine even with no monitor attached.

However, when I do a remote login from the head node (here: wulf00) to a monitor-less node (here wulf01), I get the following:

wulf00 : ssh wulf01
wulf01 : export DISPLAY=localhost:0
wulf01 : glxgears
wulf01 : Error: couldn't open display localhost:0

Note that I do not want to use X11 forwarding (ssh -X|-Y). wulf01 must be capable of running a program that connects to its local X-server. That program, by the way, is a parallel rendering program that is capable of doing rendering of partitioned data locally before shipping back the resulting images to the head node.

Initially, I thought the reason could be that the X-server on wulf01 is started with the -nolisten option. This is not the case.

Any hints on what causes this error ?
 
Old 09-09-2009, 08:38 AM   #4
cardy
Member
 
Registered: Jan 2005
Location: Shropshire, England, UK
Distribution: RedHat, Fedora, CentOS..........
Posts: 121

Rep: Reputation: 19
The problem is the xauthentication is refusing the connection.

Quote:
xauth can be used to manipulate the authentication you could try


The most common use for xauth is to extract the entry for the current
display, copy it to another machine, and merge it into the user’s
authority file on the remote machine:

% xauth extract - $DISPLAY | rsh otherhost xauth merge -
the manual page

Quote:
man xauth
lists the available options and some examples.


You could login to the remote host and run

Quote:
xhost +
this will allow ANY host to connect but would prove its an X authentication issue as xhost + turns off x authentication, however it must be run on the remote host by a user with access to the x session and I would not recommend this as a perm solution for that look at xauth.

see

man xhost

Last edited by cardy; 09-09-2009 at 08:40 AM.
 
Old 09-09-2009, 09:12 AM   #5
fpmurphy
Member
 
Registered: Jan 2009
Location: /dev/ph
Distribution: Fedora, Ubuntu, Redhat, Centos
Posts: 299

Rep: Reputation: 62
If the nv driver worked for you on the older versions of Fedora, you could swich back to using it instead of the nouveau or vesa drivers.
 
Old 09-09-2009, 10:07 AM   #6
aunola
LQ Newbie
 
Registered: Jul 2008
Posts: 3

Original Poster
Rep: Reputation: 0
Thanks.

Regarding the driver. I had thought about reverting to the old one if all else would fail. Since I seem to have some progress with the vesa driver I decided to put it on hold for a while and see if I could get everything working with vesa.

As to the authentification, I had tried to do execute xhost + as a very temporary solution, but even when I try that I get the same error message:

[mar@wulf00 ~]$ ssh wulf01 'export DISPLAY=localhost:0; xhost'
xhost: unable to open display "localhost:0"

I then did a physical (non-remote) login on wulf01 and xhost +. No change. I also did the xauth merge as suggested. No change. I still get this

wulf00 : ssh wulf01
wulf01 : export DISPLAY=localhost:0
wulf01 : glxgears
wulf01 : Error: couldn't open display localhost:0
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora server fails to start perfectpol7 Linux - Server 2 05-25-2009 04:48 AM
the device cannot be managed via the video/kbd/mouse interface on snap server 4500 lv112 Linux - Newbie 1 02-14-2009 01:41 AM
fc10 x fails to start when monitor turned off gfem Fedora 1 02-12-2009 05:53 PM
Virtual Box Fails to start iro_number1 Linux - Software 10 12-31-2007 03:00 PM
Gentoo box fails to start after 'emerge -u world' satimis Linux - Distributions 0 02-10-2004 02:08 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora

All times are GMT -5. The time now is 07:15 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration