Re: boot messages too fast to read.
Subject: boot messages too fast to read. Date: Thu, Aug 19, 1999 at 06:14:02PM +1000 In reply to:Alexander Jankowsky Quoting Alexander Jankowsky([EMAIL PROTECTED]): > > > How do you look at all the start up information that scrolls past > too quickly to read when the computer is first booted. > I do dmesg | less or dmesg > startup.msg right after I log in. HTH -- Crashing is the only thing windows does quickly. ___ Wayne T. Topa <[EMAIL PROTECTED]>
Re: boot messages too fast to read.
In article <[EMAIL PROTECTED]>, Hwei Sheng TEOH <[EMAIL PROTECTED]> wrote: >It seems that certain messages are not recorded by dmesg: such as isapnp >messages. (I've never been able to see the board ID and "activated OK" message >in dmesg -- only on the console.) Anybody can explain why?? Yes. There are 2 kind of messages: the ones originating from the kernel, and the ones printed by applications to /dev/console. Only the first kind is stored in a ring buffer by the kernel. >I'd like to have >dmesg record *every* bootup message, so that I don't have to avoid switching >VC's right after bootup in order not to erase important messages that may not >appear in dmesg. Dmesg doesn't record anything. It's just a tool that reads /proc/kmsg (which is an interface to the ring buffer of kernel messages). Mike. -- ... somehow I have a feeling the hurting hasn't even begun yet -- Bill, "The Terrible Thunderlizards"
Re: boot messages too fast to read.
On Tue, Aug 24, 1999 at 12:40:19AM -0400, Hwei Sheng TEOH wrote: > It seems that certain messages are not recorded by dmesg: such as isapnp > messages. (I've never been able to see the board ID and "activated OK" message > in dmesg -- only on the console.) Anybody can explain why?? I'd like to have > dmesg record *every* bootup message, so that I don't have to avoid switching > VC's right after bootup in order not to erase important messages that may not > appear in dmesg. dmesg only records output produced by the kernel. Since isapnp is a userland program it gets ignored. Failing other solutions (make your console a paper tty? :-) ), you could modify the init scripts to send output wherever you like. -- Mark Brown mailto:[EMAIL PROTECTED] (Trying to avoid grumpiness) http://www.tardis.ed.ac.uk/~broonie/ EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/ pgpJN8pJbYFK2.pgp Description: PGP signature
Re: boot messages too fast to read.
On Tue, 24 Aug 1999, Mark Wagnon wrote: > On Mon 08/23/99 11:31PM, David Teague wrote: > > > After boot, dmesg will give a good bit of the boot messages, but > > sometimes it fails to give parts of the boot message that I want :( > > I have this problem, and it drives me crazy. Sometimes I want to cut > and paste the info into my pleas for help, but end up resorting to > using a pencil and paper and retyping the message. > > The man page for dmesg says something about increasing the ring > buffer size, but does anyone know how to do this? > > inquiring minds want to know. It seems that certain messages are not recorded by dmesg: such as isapnp messages. (I've never been able to see the board ID and "activated OK" message in dmesg -- only on the console.) Anybody can explain why?? I'd like to have dmesg record *every* bootup message, so that I don't have to avoid switching VC's right after bootup in order not to erase important messages that may not appear in dmesg. T
Re: boot messages too fast to read.
On Mon 08/23/99 11:31PM, David Teague wrote: > After boot, dmesg will give a good bit of the boot messages, but > sometimes it fails to give parts of the boot message that I want :( I have this problem, and it drives me crazy. Sometimes I want to cut and paste the info into my pleas for help, but end up resorting to using a pencil and paper and retyping the message. The man page for dmesg says something about increasing the ring buffer size, but does anyone know how to do this? inquiring minds want to know. -- ( __ _ Mark Wagnon ) Debian GNU/ -o) / / (_)__ __ __ Chula Vista, CA ( /\\/ /__/ / _ \/ // /\ \/ / [EMAIL PROTECTED] ) www.debian.org _\_v/_/_//_/\_,_/ /_/\_\
Re: boot messages too fast to read.
On Mon, 23 Aug 1999, Patrick Ouellette wrote: > You shouldn't need to do anything special to enable this, but if > you switch virtual consoles the buffer that Shift-PGUP/PGDN > scrolls through is reset. Pat Don't switch consoles. That does indeed reset the scrollback buffer. Wait until the login message. Then scroll back with shift-PgUp back to the start of boot. This loses the beginnning of the boot messages if there is more to display than the scroll back (ring?) buffer can handle. In that event, stop the scrolling with Control-S in the middle and use shift-PgUp/PgDn to look at the boot messages. After boot, dmesg will give a good bit of the boot messages, but sometimes it fails to give parts of the boot message that I want :( --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I'm hoping this is all of the above!)
Re: boot messages too fast to read.
You shouldn't need to do anything special to enable this, but if you switch virtual consoles the buffer that Shift-PGUP/PGDN scrolls through is reset. Pat
Re: boot messages too fast to read.
On Thu, Aug 19, 1999 at 01:16:48AM -0700, Steve Lamb wrote: > Thursday, August 19, 1999, 1:14:02 AM, Alexander wrote: > > How do you look at all the start up information that scrolls past > > too quickly to read when the computer is first booted. > > dmesg from the command prompt. > > Shift-PGUP/PGDN for console scrolling. This is the second time I've read this. Do I need to activate this somewhere? -- Jim Foltz <[EMAIL PROTECTED]>
Re: [boot messages too fast to read.]
Alexander Jankowsky <[EMAIL PROTECTED]> wrote: >How do you look at all the start up information that scrolls past >too quickly to read when the computer is first booted. > > Use Shift + pgup/pgdown before you logon to see the messages. Henning Olsen ___ DO YOU YAHOO!? Get your free @yahoo.com.au address at http://mail.yahoo.com.au -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
RE: boot messages too fast to read.
Alexander Jankowsky wrote on Thursday, August 19, 1999 10:14 AM: -- snip -- > How do you look at all the start up information that scrolls past > too quickly to read when the computer is first booted. -- snip -- Try SHIFT and UP-ARROW after boot has finished! HTH Bernd -- , }\ o ) _.-` `-. Thanx ( ( \`'./ (o)\ O for () ) ) ) > )))} the) ( ( ( /_.'\ / \/ Fish ) ) `'---'=` ( ) [EMAIL PROTECTED]
Re: boot messages too fast to read.
Thursday, August 19, 1999, 1:14:02 AM, Alexander wrote: > How do you look at all the start up information that scrolls past > too quickly to read when the computer is first booted. dmesg from the command prompt. Shift-PGUP/PGDN for console scrolling. -- Steve C. Lamb | I'm your priest, I'm your shrink, I'm your ICQ: 5107343 | main connection to the switchboard of souls. ---+-
boot messages too fast to read.
How do you look at all the start up information that scrolls past too quickly to read when the computer is first booted. Please send your reply to the senders email address, otherwise I'll miss it. ___ DO YOU YAHOO!? Get your free @yahoo.com.au address at http://mail.yahoo.com.au
