[gentoo-user] boot log

[gentoo-user] boot log

[Bill Kenworthy]

Is there a way to log the boot messages - dmesg after booting up doesnt
show module load failures and they scroll off the screen and I can find
what they are.

BillK

Re: [gentoo-user] boot log

[Dakota]

[-- Attachment #1: Type: text/plain, Size: 388 bytes --]

 On 8/4/2010 8:19 PM, Bill Kenworthy wrote:
> Is there a way to log the boot messages - dmesg after booting up doesnt
> show module load failures and they scroll off the screen and I can find
> what they are.
>
> BillK
>
>
>
>
/var/log/messages doesn't contain anything relevant? I thought that's
where stuff like that got logged.
Also, have you checked /var/log/kern.log?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]

Re: [gentoo-user] boot log

[Bill Kenworthy]

On Wed, 2010-08-04 at 21:10 -0400, Dakota wrote:
> On 8/4/2010 8:19 PM, Bill Kenworthy wrote:
> > Is there a way to log the boot messages - dmesg after booting up doesnt
> > show module load failures and they scroll off the screen and I can find
> > what they are.
> >
> > BillK
> >
> >
> >
> >
> /var/log/messages doesn't contain anything relevant? I thought that's
> where stuff like that got logged.
> Also, have you checked /var/log/kern.log?
> 

messages has nothing but messages printed by modules after they
successfully loaded - no failures.

kern.log doesnt exist - there is a /var/log/kernel directory, but stuff
in there is dated 2005 (!)

Probably I need to turn on debug in the kernel somewhere - but what?

BillK

Re: [gentoo-user] boot log

[Rod]

On 5/08/2010 11:10 AM, Dakota wrote:
>   On 8/4/2010 8:19 PM, Bill Kenworthy wrote:
>    
>> Is there a way to log the boot messages - dmesg after booting up doesnt
>> show module load failures and they scroll off the screen and I can find
>> what they are.
>>
>> BillK
>>
>>
>>
>>
>>      
> /var/log/messages doesn't contain anything relevant? I thought that's
> where stuff like that got logged.
> Also, have you checked /var/log/kern.log?
>
>    

     You'd possibly find that /var/log/everything/current is the Gentoo 
logging location I have a symlink from there to /var/log/messages

     There is a backup of dmesg stored in /var/log/dmesg

     I use a combination of dmesg | less and /var/log/everything/current 
and lsmod for module testing (if they load and don't load)

Re: [gentoo-user] boot log

[Bill Kenworthy]

On Thu, 2010-08-05 at 12:47 +1000, Rod wrote:
> On 5/08/2010 11:10 AM, Dakota wrote:
> >   On 8/4/2010 8:19 PM, Bill Kenworthy wrote:
> >    
> >> Is there a way to log the boot messages - dmesg after booting up doesnt
> >> show module load failures and they scroll off the screen and I can find
> >> what they are.
> >>
> >> BillK
> >>
> >>
> >>
> >>
> >>      
> > /var/log/messages doesn't contain anything relevant? I thought that's
> > where stuff like that got logged.
> > Also, have you checked /var/log/kern.log?
> >
> >    
> 
>      You'd possibly find that /var/log/everything/current is the Gentoo 
> logging location I have a symlink from there to /var/log/messages
> 
>      There is a backup of dmesg stored in /var/log/dmesg
> 
>      I use a combination of dmesg | less and /var/log/everything/current 
> and lsmod for module testing (if they load and don't load)
> 

/var/log/everything was replaced by /var/log/messages in 2005 (and this
system dates from ~2001 and was dd'd from a dell to the sony - dont you
luv linux!) so I have the directory but nothing actually "current" in
there.

There is a dmesg file, same content as given by the dmesg command

I think most (or all) the modules that errored were not found (I do load
most modules manually) as over the years there have been problems with
both order and loading when needed.  Maybe time to clear them out and
see if autoloading actually works now ... it doesnt on my mythbox but
this system is a lot simpler.

BillK

Re: [gentoo-user] boot log

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

On Thu, 05 Aug 2010 08:19:29 +0800, Bill Kenworthy wrote:

> Is there a way to log the boot messages - dmesg after booting up doesnt
> show module load failures and they scroll off the screen and I can find
> what they are.

Set rc_logger="YES" in /etc/rc.conf to have the boot sequence logged
to /var/log/rc.log. This is for BL2, BL1 has a similar setting.

It gives this output here

rc boot logging started at Tue Aug  3 17:39:35 2010

 * Setting system clock using the hardware clock [UTC] ...
 [ ok ]
 * Loading module fuse ...
 [ ok ]
 * Loading module rfcomm ...
 [ ok ]
 * Loading module kvm-intel ...
 [ ok ]
 * Autoloaded 3 module(s)
...

You can also increase the size of the dmesg ring buffer, which was
discussed on this list last month.


-- 
Neil Bothwick

If at first you don't succeed, call in an airstrike.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] boot log

[dhk]

On 08/05/2010 03:54 AM, Neil Bothwick wrote:
> On Thu, 05 Aug 2010 08:19:29 +0800, Bill Kenworthy wrote:
> 
>> Is there a way to log the boot messages - dmesg after booting up doesnt
>> show module load failures and they scroll off the screen and I can find
>> what they are.
> 
> Set rc_logger="YES" in /etc/rc.conf to have the boot sequence logged
> to /var/log/rc.log. This is for BL2, BL1 has a similar setting.
> 
> It gives this output here
> 
> rc boot logging started at Tue Aug  3 17:39:35 2010
> 
>  * Setting system clock using the hardware clock [UTC] ...
>  [ ok ]
>  * Loading module fuse ...
>  [ ok ]
>  * Loading module rfcomm ...
>  [ ok ]
>  * Loading module kvm-intel ...
>  [ ok ]
>  * Autoloaded 3 module(s)
> ...
> 
> You can also increase the size of the dmesg ring buffer, which was
> discussed on this list last month.
> 
> 

After booting try Shift-PageUp.  Hopefully your not booting to run level
5, if you are you need to get to the alternate terminal with all the
messages on it.  Try Shift-PageUp before and after logging in.  The
buffer isn't that big and I'd like to know how it can be increased so I
can go back to earlier messages, but I haven't found that out yet.

The Shift-PageUp may get you back far enough to see the message that
scrolled by.

Re: [gentoo-user] boot log

[William Kenworthy]

On Thu, 2010-08-05 at 06:55 -0400, dhk wrote:
> On 08/05/2010 03:54 AM, Neil Bothwick wrote:
> > On Thu, 05 Aug 2010 08:19:29 +0800, Bill Kenworthy wrote:
> > 
> >> Is there a way to log the boot messages - dmesg after booting up doesnt
> >> show module load failures and they scroll off the screen and I can find
> >> what they are.
> > 
> > Set rc_logger="YES" in /etc/rc.conf to have the boot sequence logged
> > to /var/log/rc.log. This is for BL2, BL1 has a similar setting.
> > 
> > It gives this output here
> > 
> > rc boot logging started at Tue Aug  3 17:39:35 2010
> > 
> >  * Setting system clock using the hardware clock [UTC] ...
> >  [ ok ]
> >  * Loading module fuse ...
> >  [ ok ]
> >  * Loading module rfcomm ...
> >  [ ok ]
> >  * Loading module kvm-intel ...
> >  [ ok ]
> >  * Autoloaded 3 module(s)
> > ...
> > 
> > You can also increase the size of the dmesg ring buffer, which was
> > discussed on this list last month.
> > 
> > 
> 
> After booting try Shift-PageUp.  Hopefully your not booting to run level
> 5, if you are you need to get to the alternate terminal with all the
> messages on it.  Try Shift-PageUp before and after logging in.  The
> buffer isn't that big and I'd like to know how it can be increased so I
> can go back to earlier messages, but I haven't found that out yet.
> 
> The Shift-PageUp may get you back far enough to see the message that
> scrolled by.

I didnt think gentoo uses runlevel 5 - you mean into X I think

I'll try that next time (not booting into X) and see what happens - but
I think it resets itself somewhere in the middle of the text as well as
scrolling off the top of the buffer - can be increased I think and
booting into single might stop the graphics reset.

thanks for the hint.
BillK

[gentoo-user] Re: boot log

[James]

Bill Kenworthy <billk <at> iinet.net.au> writes:


> Is there a way to log the boot messages - dmesg after booting up doesnt
> show module load failures and they scroll off the screen and I can find
> what they are.

app-admin/showconsole
"small daemon for logging console output during boot"

I have not tried this yet, but it looks promising....

post back your experience.

hth,
James