Kent, It appears that X itself is the culprit. I disabled gdm as you suggested, and was able to scroll backward through the history. I didn't even know that you could do that, so I won in two ways. However, once I launched X using "startx", I could no longer scroll back.
Thanks for your help > Kent West wrote: > I've found that if you have xdm/gdm/kdm/wdm (I'm not sure > which one(s) > cause the problem) starting X automatically, about the only > way to find > these module errors is to look in the log files for the > individual modules. > > A better way, is to disable xdm/gdm/kdm/wdm, then reboot. > When you get > logged in, you can then Shift-PgUp through the error > messages. (For some > reason, xdm/gdm/kdm/wdm seems to clear out the Shift-PgUp history, so > this method doesn't work if one of them is installed. Again, I'm not > sure which one(s) cause this behaviour; I'm currently using > wdm at home, > nothing at work, but I used to and don't remember which, and > it's been > so long since I've had to reboot, I've forgotten even which machine I > needed to look at these errors on.) > > > Trandahl, Steve wrote: > > >I am having trouble with some of my modules at during > boot-up. I can see > >the error messages fly by, but when I use dmesg, I don't see > the errors. > >How can I find out what these errors and/or warning messages > are once Debian > >has booted? > > > >Thanks in advance! > > > >Steve Trandahl > >Cotelligent, Inc > >[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > > >
