[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can't read bootup message



Thanx guys,

	Ctrl-S stuff works well (so does scroll lock) the SHIFT-PgUp is cool

Edwin Lau

On Mon, Jun 25, 2001 at 09:04:28AM -0600, Jimmy Richards wrote:
> On Mon, Jun 25, 2001 at 11:40:14AM +0200, Matthias Fechner wrote:
> > Hi,
> > 
> > On Sun, 24 Jun 2001, Chun Kit Edwin Lau wrote:
> > 
> > > 	I noticed that when I booted up Linux, I saw some error message.  But the message just when very fast that I couldn't really read it. dmesg and the message file didn't have that error. I think it was some shell script error. Can anyone show me a way to show all the message in some kind of log file for the bootup process.
> > 
> 
> 	Hi Mattias,
> 
> 	The best way to examine init errors that aren't logged to 'dmesg' is
> to use the 'Suspend' control key. Suspend can be used once the kernel
> has booted up enough that kernel has enabled it. It is not long into the
> boot sequence before it is enabled. When the boot sequence comes to the
> point where you start receiving the error messages, press CTRL-S. This
> suspends processing of the bootup sequence temporarily. If the message
> you want see has scrolled off the screen, use SHIFT+PAGE_UP to scroll up
> a page at a time. SHIFT+PAGE_DOWN can be used to scroll back down. To
> Start the boot sequence back up from it's suspended state, hit CTRL+Q.
> You can see the CTRL-S and CTRL-Q keyboard bindings in the command 'stty
> -a' if you wanna a look.
> 
> 	HTH,
> 
> 	Jim Richards
> 
> 
> > Gruss
> > Matthias
> > 
> > 
> > -- 
> > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Content-Description: PGP Key 0x0062D7A7.




-- 
Edwin Lau (lauedw@waves.utoronto.ca)



Reply to: