Richard Oldham wrote: > Shutdown from KDM often provided no visual display of what was going on so > when the hard drive had ceased operating for a short while I would key in > "shutdown -h now" and press enter (just in case....), all blind, and switch > off after a further period of apparent inactivity. This behaviour was not > cured by manually configuring "XF86Config" or "drakeres" (by rejecting the > probed settings) for 8MByte of Videoram or by following a recommendation to > set the Option "sw_cursor" in "XF86Config". The "sw_cursor" option did give > me xxxx's for password input in KDM login screen for the very first time and > did seem to reduce the occurrences of the blind shutdown problem but it's not > fixed yet. > This is by no means a "correct" solution or anything, but . . . You might try some of the following to see what happens: a) CTL-ALT-F2 to get a console window, then log in as root and do a shutdown -h now. b) When confronted with the blank screen from the KDM shutdown, type CTL-ALT-F1 and/or CTL-ALT-F2 to get the/a console window. c) Rather than using the KDM shutdown, issue the shutdown command from a shell. d) Try running X 3.3.6 rather than X 4.0. Personally, I did a chmod +s /sbin/shutdown and just shutdown myself (with "halt" and "reboot" aliases; it saves the spurious extra step of logging off from KDE. Either way, however, X does successfully switch back into console mode for the shutdown). If this approach works for you, then you can probably make a script to shut down in a way that works for you by having a "halt" script like this: chvt 1 shutdown -h now (chvt changes to a virtual terminal; it's like CTL-ALT-1 in a script.) -- "Brian, the man from babble-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
