On Tuesday 30 March 2004 12:31, Brockamp@tlt.ilt.fhg.de wrote:
Hi!
OK, here's my test results:
Leendert Meyer <leen.meyer@home.nl> schrieb am 26.03.2004 20:43:05:
Did you try <Ctrl>+<Alt>-<Backspace> to kill X?
Nope, but tried now. Doesn't work though.
What's in the logs?
Sorry, I'm not that firm in Linux yet ;-( What are the relevant logs for a berserking X?
/var/log/XFree86*.lo If there are more then one, check the date. Lines starting with "(EE)" indicate an error (grep "^(EE)" XFree86*.log). Maybe there's also something in /var/log/messages. Each log entry has a timestamp, so errors should be easy to locate. Don't post the whole files, only those lines that contain errors, and perhaps a some lines of relevant context.
Can you login remotely with another PC? If you can, run 'top' prior to testing to see if there is a process going mad (using 100% CPU or memory).
Not that easy, as the other machine is Bill OS only (I admit, sigh! Shame on me!) and with my fli4l-router I haven't got the neccessary software on this machine. Is there an easy way to log into a Unix machine from Bill OS?
Yes! :) PuTTY. Very small, quite easy. Get it here: http://www.chiark.greenend.org.uk/~sgtatham/putty/ It's an exe program, you could run it even strait from there. If you want to check the MD5sums: copy putty.exe and md5sums to the same directory /on a Linux machine/, and issue "md5sum -c md5sums". There should be a message indicating putty.exe is OK. Before trying a screensaver, login with putty and start 'top'. [...]
Press these sequences in the same order:
<Alt>+<SysRq>-<S> ==> S)yncs the disks <Alt>+<SysRq>-<U> ==> U)nmounts the disks <Alt>+<SysRq>-<B> ==> reB)oots
(release all keys between sequences)
Tried it. Doesn't work either :-(
You could try it once to see if it works. The safest way to try is boot the machine in runlevel S: At the boot prompt (the first prompt after passing the BIOS screens) just type an 'S' (no quotes) and hit enter. The system boots in a special maintenance mode. Only / (and perhaps /boot) is/are mounted. Nice is they're mounted read only, meaning you can't damage the file system! :) Now try the SysRq sequences as indicated above: while holding down <Alt>+<SysRq> press the 'S' key, etc. Doesn't work? Just reboot normaly. If the SysRq sequences don't work during the screensaver crash, It's probably best to just leave those alone. An unclean reboot (when disks are not unmounted prior to halting/booting) could damage the file system, with even a (very small) risk to be forced to re-install Linux, but a bit more likely resulting in damaged files. You're a bit better off if you use reiserfs or ext3. A simple 'mount' command will tell you that. Decide if you want to continue. ;) BTW, YaST should indicate if there are missing/conflicting packages. If so, try to solve them, or post the missing/conflicting packages here. Cheers, Leen