On Thu, Nov 14, 2002 at 04:52:21PM +1100, Rob Weir wrote: > On Wed, Nov 13, 2002 at 10:13:10PM -0500, Seneca wrote: > > On Thu, Nov 14, 2002 at 12:08:08AM +0100, Michael Naumann wrote: > > > Last day I had a heavy crash of my woody box. > > > I suspect some misbehaviour of xmms here. > > > The whole display was very flickery and no > > > application responded any more, though I saw, that > > > gkrellm was still working. Even switching to a console (ALT-F1) > > > did not succeed. I had the the X-screen still visible, jumping > > > half a page to the left each time I hit a key. > > > Had no luck in rebooting blindly. > > > > I've had that happen with X on my laptop. My standard method to attempt > > to get out of that state is to return to X (I tend to have num lock on > > in X, a useful indicator to show that I am at the right screen), wait > > until the load on the system is lower, change to console. If the screen > > looks either grey or normal, it worked (although grey needs the "reset" > > command) > > I've had this happen a few times too. Once you get to the > 'screen-out-of-phase-by-half' stage, even the kernel is b0rked. Magic > sysrq doesn't work, so you're left with a hardware reset.
I haven't had problems with a borked kernel with that happening, with my laptop, I can connect a serial terminal to it and change to the appropriate runlevel, and login on it and do my work from there, while the laptop's console cannot be seen properly. I just have to becareful not to typo while entering "telinit 3", and to type it at the appropriate console (when having X problems, I label them in binary using num lock and caps lock). -- Seneca [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
