Re: How to see module errors on bootup?
Quoting Robb Kidd ([EMAIL PROTECTED]): Bernd Worsch wrote: In case your feeling lonely your quite right, the messages seem to be nowhere in the logs. Which is quite unsatisfactory. It's to do with what goes on in /etc/init.d/modutils. I'm not savvy enough to tell you where to do it, but if you've a mind to, start figuring out that script and add 2 /var/log/syslog where appropriate. But do bear in mind that you *might* not have any /var yet. Modutils runs before mountall.sh, so /root might be a better place. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: How to see module errors on bootup?
Brent Buchholz wrote: On Tue, 26 Sep 2000, Kent West wrote: 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. Can anyone clue me in as to how I can get to these messages? Thanks! They should be in /var/log/syslog. Well, you'd think so. There are some error messages in there, but not the ones that are generated by modules being loaded (at least not the ones I see during bootup). Just as a test, I rebooted just now and checked /var/log/syslog; nope, the errors are not there. Thanks anyway! Brent -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Kent West [EMAIL PROTECTED]
Re: How to see module errors on bootup?
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]
Re: How to see module errors on bootup?
In case your feeling lonely your quite right, the messages seem to be nowhere in the logs. Which is quite unsatisfactory. Thanx for posting this, i wondered where to find them quite a while already. How about filing this as a bug :) Cheers Bernd -- [EMAIL PROTECTED] -email-preferred
Re: How to see module errors on bootup?
Quoting Kent West ([EMAIL PROTECTED]): 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. Have you got something clearing the screen, e.g. does SVGA do this? (I know xdm does.) There's nothing special about the login prompt. I can see back to the BIOS screen of some of my machines: BIOS Version 1.00.05.CV2 0032768 KB Please Wait... Keyboard.Detected MouseDetected Hard Disk 0 Installed Maxtor 51024U2 Floppy A: Installed ... pasted with gpm. The errors don't show up in /var/log/syslog, or anywhere else I've looked. As well as dmesg, have you checked /var/log/kern.log? I think you may be asking a bit much for /var/log/syslog to contain these errors as they occur before syslogd starts (entering runlevel 2). The kernel messages get logged because the kernel maintains a ring buffer from time zero. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: How to see module errors on bootup?
%% Moritz Schulte [EMAIL PROTECTED] writes: ms ehm, you can scroll on the linux console with shift+page_down/page_up. You can only do this up until you switch to a different console, for any reason. Once that happens, all history on the first one is gone. For example, if you use XDM or GDM you're pretty much out of luck. You'll have to disable them while you debug the problem. Also, if you try to jump to a different terminal to look at or fix problems you find, you'll lose all your history. In short, this works to some extent but is not convenient. Now, logging _all_ the boot message somewhere _would_ be extremely convenient. -- --- Paul D. Smith [EMAIL PROTECTED] Network Management Development Please remain calm...I may be mad, but I am a professional. --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them.
Re: How to see module errors on bootup?
Bernd Worsch wrote: In case your feeling lonely your quite right, the messages seem to be nowhere in the logs. Which is quite unsatisfactory. It's to do with what goes on in /etc/init.d/modutils. I'm not savvy enough to tell you where to do it, but if you've a mind to, start figuring out that script and add 2 /var/log/syslog where appropriate.
Re: How to see module errors on bootup?
They don't show up in my syslog. On Tue, 26 Sep 2000 15:44:03 -0500 (CDT), Brent Buchholz wrote: On Tue, 26 Sep 2000, Kent West wrote: 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. Can anyone clue me in as to how I can get to these messages? Thanks! They should be in /var/log/syslog. Brent -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Cam Ellison, Ph.D., R.Psych. [EMAIL PROTECTED] or [EMAIL PROTECTED] From the lovely Sunshine Coast, where it only SEEMS to rain.
How to see module errors on bootup?
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. Can anyone clue me in as to how I can get to these messages? Thanks!
Re: How to see module errors on bootup?
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. you can also use flow control. with Ctrl+s you freeze your terminal, 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/. moritz -- /* Moritz Schulte [EMAIL PROTECTED] * http://hp9001.fh-bielefeld.de/~moritz/ * PGP-Key available, encrypted Mail is welcome. */
Re: How to see module errors on bootup?
On Tue, 26 Sep 2000, Kent West wrote: 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. Can anyone clue me in as to how I can get to these messages? Thanks! They should be in /var/log/syslog. Brent
