[opensuse-kde3] Possible Problem with KDM in KDE3 and 11.3/11.4 re: Booting to GUI?
Started my computer this a.m. and it booted my 11.3/kde3 partition as it should, but dropped to the commandline rather than go through to the desktop. Logging in and "startx" worked right off. Problem is repeatable, and booting will not go through to the GUI without dropping to the commandline. Tried it on the 11.4/kde3 that I had created a week ago (pure icewm install for 11.4, then add kde3 repo), and the same thing happened. Yesterday both were working fine. Here are the pertinent lines in /var/log/warn's from these two systems (Xorg.0.log is useless): Mar 13 15:37:18 s113kde3 kdm[2373]: X server startup timeout, terminating Mar 13 15:37:18 s113kde3 kdm[2373]: X server for display :0 can't be started, session disabled Mar 13 15:19:05 s114kde3 kdm[1904]: X server startup timeout, terminating Mar 13 15:19:05 s114kde3 kdm[1904]: X server for display :0 can't be started, session disabled Two other opensuse partitions I have, with 11.4/kde4 (stock install from final DVD), and 11.4/kde3 (this is the one I set up as a test yesterday, putting on 11.3/kde3 first, then upgrading to 11.4/kde3), go straight through to the GUI as they should. BUT, they have the stock X video drivers. The two non-performing partitions/systems have the ATI 11.2 proprietary driver. As I said, everything was fine yesterday when I powered down, and I haven't had a problem with the 11.3/kde3 partition that I use every day. I'm tempted to put the ATI driver on the 11.4/kde3 system (the one I set up as a test yesterday, since krandr doesn't retain settings) and see if it craps out on boot too. Would a recent (up to yesterday) KDE3 update(s) have affected this? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde3+help@opensuse.org
On Sunday 13 March 2011 4:00:51 pm Erik Sorenson wrote:
Started my computer this a.m. and it booted my 11.3/kde3 partition as it should, but dropped to the commandline rather than go through to the desktop. Logging in and "startx" worked right off. Problem is repeatable, and booting will not go through to the GUI without dropping to the commandline.
Update after some additional testing: 1. Uninstalled/installed ATI drivers on my 11.3/kde3 production partition right back to 10.9 (current is 11.2). Installs go swiftly, no errors. No difference in booting problem 2. Boot to "init 3", login, "init 5" and up comes KDE login screen without delay, thence to desktop and regular operation. 3. Installed ATI 11.2 driver on fresh 11.4/kde4 (genned yesterday), and it works fine, as it should, without droppoing to commandline. 4. Everytime it boots to commandline, there's no usual X-chatter (EE's and stuff), nothing, just the prompt. The only indication of the problem is in /var/log/warn, and it always says what I pasted in my initial post ... timeout. Any ideas? I'm out of them. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde3+help@opensuse.org
What's the output of 'cat /proc/cmdline'? What if anything does xorg.conf contain? Has anything been added by you or proprietary driver installation to /etc/X11/xorg.conf.d/'s files? -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde3+help@opensuse.org
On Monday 14 March 2011 12:52:28 am Felix Miata wrote:
What's the output of 'cat /proc/cmdline'?
root=/dev/disk/by-path/pci-0000:00:11.0-scsi-0:0:0:0-part1 resume=/dev/disk/by-path/pci-0000:00:11.0-scsi-0:0:0:0-part6 splash=silent nomodeset quiet vga=0x375 For the ATI prop drivers, I nomodeset'd as you can see and, for drm incompat, "no_kms_in_initrd" is set to yes (obviously recreated the initrd since it was done in Yast). It has been running fine since (at least) Feb 24th, booting multiple times/day without issue. Same with another partition, which only crapped out this morning (in the same way) also.
What if anything does xorg.conf contain
At end of ATI install, I run "aticonf --initial" before rebooting. ATI's install routine puts in this standard xorg.conf each time: Section "ServerLayout" Identifier "aticonfig Layout" Screen 0 "aticonfig-Screen[0]-0" 0 0 EndSection Section "Module" EndSection Section "Monitor" Identifier "aticonfig-Monitor[0]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Monitor" Identifier "0-DFP1" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" Option "PreferredMode" "1024x768" Option "TargetRefresh" "75" Option "Position" "0 0" Option "Rotate" "normal" Option "Disable" "false" EndSection Section "Device" Identifier "aticonfig-Device[0]-0" Driver "fglrx" Option "Monitor-DFP1" "0-DFP1" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "aticonfig-Screen[0]-0" Device "aticonfig-Device[0]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection
Has anything been added by you or proprietary driver installation to /etc/X11/xorg.conf.d/'s files?
No -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde3+help@opensuse.org
On Sun, Mar 13, 2011 at 10:00 PM, Erik Sorenson
Started my computer this a.m. and it booted my 11.3/kde3 partition as it should, but dropped to the commandline rather than go through to the desktop. Logging in and "startx" worked right off. Problem is repeatable, and booting will not go through to the GUI without dropping to the commandline.
Tried it on the 11.4/kde3 that I had created a week ago (pure icewm install for 11.4, then add kde3 repo), and the same thing happened. Yesterday both were working fine.
Here are the pertinent lines in /var/log/warn's from these two systems (Xorg.0.log is useless):
Mar 13 15:37:18 s113kde3 kdm[2373]: X server startup timeout, terminating Mar 13 15:37:18 s113kde3 kdm[2373]: X server for display :0 can't be started, session disabled
Mar 13 15:19:05 s114kde3 kdm[1904]: X server startup timeout, terminating Mar 13 15:19:05 s114kde3 kdm[1904]: X server for display :0 can't be started, session disabled
Eric, It might be the same issue I've seen before with oS 11.1 and newer kernels (from Evergeen repository). Somehow the KDM is started early and X later and KDM times out before X is ready. The simple workaround was to change KDM timeout in /opt/kde3/share/config/kdm/kdmrc The default was 15 seconds. I set it to 100 and it solved the issue. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde3+help@opensuse.org
On Monday 14 March 2011 1:38:11 am Mark Goldstein wrote:
It might be the same issue I've seen before with oS 11.1 and newer kernels (from Evergeen repository). Somehow the KDM is started early and X later and KDM times out before X is ready. The simple workaround was to change KDM timeout in /opt/kde3/share/config/kdm/kdmrc The default was 15 seconds. I set it to 100 and it solved the issue.
Thanks, Mark. Although it didn't directly fix the problem, it enabled me to stumble opon the solution! There were so many timeout parms there, that I decided to change the Local Displays section and, while I was there, Server Attempts (from 1 to 2). A reboot produced the same commandline though, and while I was sitting there pondering the issue, without logging in, (after 15 seconds, I guess) it automatically retried and went straight to the KDM login screen! So I started looking at all the logs (warn, X, messages, etc) and came across this (just a snippet from "/var/log/messages"): ++++++++++++++++++++++++++++++++++++++++++++++ Mar 14 08:48:24 s113kde3 kdm_config[2370]: Multiple occurrences of key 'AutoLoginEnable' in section [X-:0-Core] of /opt/kde3/share/config/kdm/kdmrc Mar 14 08:48:24 s113kde3 acpid: 1 client rule loaded Mar 14 09:48:23 s113kde3 ntpd[2417]: ntpd 4.2.4p8@1.1612-o Mon Jul 5 13:44:05 UTC 2010 (1) Mar 14 09:48:23 s113kde3 ntpd[2418]: precision = 1.000 usec Mar 14 09:48:23 s113kde3 ntpd[2418]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Mar 14 09:48:23 s113kde3 ntpd[2418]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled .. .. Mar 14 09:48:25 s113kde3 kdm[2369]: X server startup timeout, terminating +++++++++++++++++++++++++++++++++++++++++++++ See the one hour upshift? At that point some process must think there's a one-hour gap since the Xserver was asked to fire up ... perhaps this is the issue? Bug?? Dunno, beyond me. That got me thinking ... this had all started Sunday morning (DST commencement), and I was on this 11.3 system from about 11 pm till 1:30 am, pre-DST. So I rebooted, checked the BIOS and, sure enough, the BIOS clock was still at 8:57, one hour behind actual DST (9:57 actual). Is this normal? I advanced the clock one hour manually, rebooted, and everything was back to normal, inluding the other openSuse partition that was displaying the same problem. I've now reset kdmrc back to it's original state and all is still well/normal. The two other gens/partitions that were NOT displaying the same problem were 11.4 gens, one a KDE3 and the other a KDE4, They still boot fine. Obviously the 11.4 ones seem to have handled the problem more gracefully than 11.3, but if all have NTP running, why did none of them not adjust the clock? Anyway, I'll look into it further but, in the meantime, many thanks to all for the assistance. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde3+help@opensuse.org
participants (3)
-
Erik Sorenson -
Felix Miata -
Mark Goldstein