Hello, For some time I have been trying to track down why I cannot get XDM to start correctly at boot [1] under Sarge, where the system was working properly under Woody. I believe XDM is giving up waiting for the X server to start. Measuring the X server start time with "time X" and closing the resulting display as soon as it comes up gives a real elapsed time of 3 minutes 4 seconds.
So X does work, StartX does work also, And XDM does work, because I can drive my external X termial with it. Examining the output of "strace &>X.log -ff X" [2] indicates that it takes over a minute for the X server to determine that it should use the clgen driver (measuered from the start to when that selection is written to the XFree86.0.log file). Searching the XDM man page, I found the config DisplayManager.DISPLAY.openTimeout which is the amount of time for the XDM to wait for the display to be available. I am going to see if that fixes this problem. If so, this might be a FAQ item? According to the man page, the openTimeout value is 30 seconds. I am going to increase this to 255 and see if it makes a difference. It is interesting that X takes so much longer to start under Sarge than it had under Woody, as least on my Amiga 2000 with 030 at 40MHz and 16M RAM with an EGS Spectrum (clgen) video card. My kernel is a 2.4.30 compiled off current CVS sources with the clgen support compiled in. Once running, though, I have no issues with the response time. I seem to recall that X under Woody went to 4.3.0 of the X Window System. [1] http://lists.debian.org/debian-68k/2005/08/msg00046.html [2] http://www.luminet.net/~lancetag/debian/sarge/X.log Thanks, --Lance -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
