Computer boots up fine, but drops to commandline as it tries to go to the desktop. Just logging in and issuing “startx” brings up the desktop and all is well.
The Xorg logfile gives no fatals or clues (at least to me), but the “warn” file in /var/log gives the following at the end:
Mar 13 13:25:43 xxxxxxxx kdm[2328]: X server startup timeout, terminating
Mar 13 13:25:43 xxxxxxxx kdm[2328]: X server for display :0 can’t be started, session disabled
Yesterday was fine, and never had it before; no harware changes (still same ATI 4770 and ATI 11.2 driver), nor BIOS changes/updates, for ages. First boot today this started. Does it continuously.
Any insight into how I might slightly increase X’s timeout parameter a bit, if this is the problem?
Got the same exact message in logs with 11.4, it began few days ago after some online updates. Every time I have to login as root into console, do init 3 than init 5 and KDM starts normally.
Tried timeouts of 200, 500 and 800, no success.
CPU is AMD 64 dual core.
Is there any way to make KDM start absolutely last, after all other services started? I know it will slow down boot time up to 5 seconds, but I do not care about boot time any way. I’ve seen symlinks in /etc/init.d/rc5.d, but XDM is already K01. Will it help to make it 00 or 10?
Also listing my /etc/init.d/rc5.d/ folder, maybe it will help to determine problem. I have SSHD and NTP enabled, plus VirtualBox from it’s official site, maybe it causes troubles with timeouts…
Made all timeouts 1000, including OpenTimeout, and changed to ServerAttempts=3, it starts with second attempt. Still, I’d like to make KDM the very last service to start, after everything else was started…
On 2011-04-05 07:06, nrickert wrote:
>
> Aekold;2317540 Wrote:
>> I’ve seen symlinks in /etc/init.d/rc5.d, but XDM is already K01. Will it
>> help to make it 00 or 10?
>
> It should be the “S” numbers that start the service and the “K” numbers
> for stopping (killing) it.
>
> I see S11earlyxdm and S12xdm
Don’t try to change the numbers there. You have to edit the requires inthe
scripts instead.
You could try parallel boot no. Just a wild guess, but it is affecting some
people.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)