Moritz Schulte wrote: > > Kent West <[EMAIL PROTECTED]> writes: > > > I know "dmesg" will show the boot-up messages generated (by the > > kernel?); however, this apparently doesn't show the errors generated by > > modules being loaded. These messages go by too fast to catch, and then I > > haven't been able to find a way to read them again. > > ehm, you can scroll on the linux console with shift+page_down/page_up.
Normally; except that after the login prompt appears, shift-pageUp only works for about half a screen instead of the several screens it seems to recall at other times. > you can also use "flow control". with Ctrl+s you "freeze" your terminal, This works, but is somewhat inconvenient. However, it'll do. Thanks! The errors are being generated by depmod, complaining about unresolved symbols. Hmm. At least now I have a clue. > wake it up again with Ctrl+q. (BTW: with cat and flow control you really > have a nice pager ;) ) > also, check the log files under /var/log/. The errors don't show up in /var/log/syslog, or anywhere else I've looked. > moritz > -- > /* Moritz Schulte <[EMAIL PROTECTED]> > * http://hp9001.fh-bielefeld.de/~moritz/ > * PGP-Key available, encrypted Mail is welcome. > */ > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Kent West [EMAIL PROTECTED]
