Blank screen lockup with both xdm and kdm in runlevel 5

From: Lucius Chiaraviglio (luciusone_at_chapter.net)
Date: 07/29/03 

Date: Tue, 29 Jul 2003 11:06:36 GMT

When I put the system into runlevel 5 (telinit 5 or start with linux 5;
doesn't seem to make any difference) and use the graphical login, and then
try to log out (or in the case of xdm also do some other things that I haven't
figured out yet), the screen goes blank and the system freezes hard, with no
keyboard LED response and no network access either (and no error messages).
In the case of using kdm, the lockup occurs just after playing the KDE exit
sound, but I doubt that sound has anything to do with it, because XFree86
running xdm does not use sound. The strange thing is that no lockup occurs
if I start X (with or without KDE) in runlevel 3 using "startx". Anyone know
what could cause this problem?

The relevant /etc/inittab lines for runlevel 5 are (one or the other of the
following, not both):

x:5:respawn:/opt/kde/bin/kdm
x:5:respawn:/usr/X11R6/bin/xdm -nodaemon

System configuration, hardware
------------------------------

Athlon XP 2000+ (1.67 GHz) (no overclocking)
Soyo SY-KT333 Dragon Plus mainboard (VIA KT333 chip set)
        Network chip is integrated VT6102 Rhine II, according to /proc/pci
        Sound chip is integrated CMI8738, according to /proc/pci
LNE100TX 4.1 PCI ethernet card (in case of problems with onboard chip)
256 Mibytes of RAM
80 Gbyte hard drive (ATA-133)
Sapphire Atlantis (OEM ATI Radeon) 9100 video card (AGP 4X)
(Misc. peripherals such as CD-R and floppy omitted)

System configuration, software
------------------------------

Kernel 2.4.21 from kernel.org (compiled with -O2 -march=athlon)
XFree86 4.3.0, including DRI radeon.o module (compiled with -O3 -mcpu=athlon)
Lesstif 0.93.36 (compiled with -O3 -mcpu=athlon)
aRts 1.1 (compiled with -O3 -mcpu=athlon)
qt-x11-free 3.1.2 (compiled with -O3 -mcpu=athlon)
kdelibs 3.1 (compiled with -O3 -mcpu=athlon, but seemed to use -O2 anyway)
kdebase 3.1 (compiled with -O3 -mcpu=athlon, but seemed to use -O2 anyway)
Modutils 2.4.22 (compiled with -O3 -mcpu=athlon)
glibc 2.3.1 (compiled with -O2 -g)
GCC 3.2.1 (compiled with -O2 -g)
(Other Linux From Scratch system software compiled with -O3 -mcpu=athlon)
GCC 2.95.3 (compiled with -O2 -g, available as alternative GCC version)
alsa-driver 0.9.4 (compiled with -O2 -g)
alsa-lib 0.9.4 (compiled with -O2 -g)
alsa-utils 0.9.4 (compiled with -O2 -g)
alsa-tools 0.9.4 (compiled with -O2 -g)
alsa-oss 0.9.4 (compiled with -O2 -g)
(Various other Linux From Scratch and Beyond Linux From Scratch packages
compiled mostly with -O3 -mcpu=athlon)
(All packages compiled with GCC 3.2.1 unless otherwise stated) 

-- 
Lucius Chiaraviglio
Approximate E-mail address:  luciusone@chapter.net
To get the exact address:          ^^^    ^replace this with 'r'
                                   |||
    replace this with single digit meaning the same thing
(Spambots of Doom, take that!).

Relevant Pages

  • Blank screen lockup with both xdm and kdm in runlevel 5
    ... running xdm does not use sound. ... System configuration, hardware ... (Various other Linux From Scratch and Beyond Linux From Scratch packages ...
    (comp.os.linux.x)
  • Re: Ranting about JVMs default memory limits...
    ... reference is five years old, and maybe Linux has been fixed by now). ... That is, it is likely to be particular applications, not particular Linux installations, that need the system configuration changed. ... I wonder how many Linux users, even experienced ones, have random processes just die because of this and don't know why. ...
    (comp.lang.java.programmer)
  • Using network routers with Linux
    ... I am using a cable modem with DHCP under Linux and there is another computer ... running Windows in the house and i want to use a router to supply the cable ... changes in my system configuration? ...
    (comp.os.linux)