Casey, thanks for the reply. I've only recently switched to Debian and I don't recall either RedHat or Mandrake logging all of this info (or more likely, I never checked for it). Nonetheless, the error I'm looking for didn't show up.
I've recompiled the kernel again. Why ?? ;-) The console has started getting flakey... no characters show up when I type. Or the characters that do show up are missing "pixels" in the horizontal plane (hard to describe) and they're also about 1/4 the size of my monitor !! I did enable framebuffer for my Matrox card, but this has worked fine with 2.2.17 and .18. This time though, I enabled some additional fonts. Have to assume that's the problem, so I've removed them and will try again. Is this a known problem ... anyone ?? Regards, Hall Stevenson * Casey Webster ([EMAIL PROTECTED]) [010113 09:52]: > dmesg is just the kernel bootstrap messages and will catch all of that, > once init is spawned, the kernel is done, and you should check syslog for > further messages. > > -Casey > > On Sat, 13 Jan 2001, Hall Stevenson wrote: > > > > > I just upgraded my kernel to 2.4.0 with no apparent problems... I did > > notice on bootup some messages that scroll by far too quickly to read that > > I wanted to take another look at. I think they just have something to do > > with my CD-ROM drives (possibly because there's no discs in them). > > > > How can I log *all* of the kernel's boot messages ?? "dmesg" doesn't show > > everything. > > > > Thanks in advance > > Hall > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > >
