Hi, You can redirect kernel output to the serial port. hook another machine up to the serial port and run your favourite tool to catch all the text/info..
Then, you can get all kernel messages generated, up to and including the dump info. Particularly useful for debugging drivers. Trouble is, it slows down the whole machine. You see, the machine waits until all messages are sent out of the port before continuing. Particularly noticeable duing bootup. Derek. ====================================================== On Mon, 9 Aug 2004, Carl Cerecke wrote: > Matthew Gregan wrote: > > At 2004-08-09T13:29:26+1200, Warwick Hay wrote: > > > >> Moving to Linux (Kiss the Blue Screen of Death Goodbye!) by Marcel > >>Gagne > > > > > > Heh, sometimes I wish Linux had something similar to the blue screen of > > death. It's frustrating when the kernel panics and all you see is a > > hung X session. It makes it rather difficult to record the panic message > > for fault finding. > > > > There are patches around to provide this (I can't find the link right > > now), but it's not in the standard kernel and probably never will be. I > > guess I should be content with the having the panic output as morse > > code... > > I vaguely remember a patch that would write the panic message to a > floppy if the kernel got its knickers in a knot. Saves copying hex from > the screen by hand. Course, that assumes the floppy code didn't get munted. > > Cheers, > Carl. > > > -- Derek Smithies Ph.D. This PC runs pine on linux for email IndraNet Technologies Ltd. If you find a virus apparently from me, it has Email: [EMAIL PROTECTED] forged the e-mail headers on someone else's machine ph +64 3 365 6485 Please do not notify me when (apparently) receiving a Web: http://www.indranet-technologies.com/ windows virus from me......
