missing log messages

[Bill-75]

Hi folks,

I'm tweaking a new kernel for my old laptop to install a new module.

At boot I see a number of 'fail' messages scroll past on the
screen, but they don't show up in dmesg /var/log/dmesg
/var/log/syslog /var/log/messages etc. These files are
practically devoid of error messages.

Where can I find the 'complete' output of my boot process?

        b.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sven Joachim]

On 2008-05-16 14:48 +0200, Bill wrote:

> I'm tweaking a new kernel for my old laptop to install a new module.
>
> At boot I see a number of 'fail' messages scroll past on the
> screen, but they don't show up in dmesg /var/log/dmesg
> /var/log/syslog /var/log/messages etc. These files are
> practically devoid of error messages.
>
> Where can I find the 'complete' output of my boot process?

In Debian's default boot configuration: nowhere.  You need to edit
/etc/default/bootlogd and change BOOTLOGD_ENABLE=No to Yes.  After a
reboot, you will find the log in /var/log/boot.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Johannes Wiedersich]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2008-05-16 15:09, Sven Joachim wrote:

> On 2008-05-16 14:48 +0200, Bill wrote:
>
>> I'm tweaking a new kernel for my old laptop to install a new module.
>>
>> At boot I see a number of 'fail' messages scroll past on the
>> screen, but they don't show up in dmesg /var/log/dmesg
>> /var/log/syslog /var/log/messages etc. These files are
>> practically devoid of error messages.
>>
>> Where can I find the 'complete' output of my boot process?
>
> In Debian's default boot configuration: nowhere.  You need to edit
> /etc/default/bootlogd and change BOOTLOGD_ENABLE=No to Yes.  After a
> reboot, you will find the log in /var/log/boot.

You could also just press the 'scroll button' on your keyboard, while
the interesting output floats by. This would stop any further output
until you press it again, so you have more time to view/read it.

(While this is quick, it does not actually save the output to a log).

HTH,
Johannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILY4RC1NzPRl9qEURAtU/AJ44una3RvzOs6RfwBXt3fYUX00l/ACeLPQi
KxKAq18HqBq04toM4oSYpoQ=
=LHO6
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Bill-75]

On Fri, 2008-16-05 at 15:09 +0200, Sven Joachim wrote:
> In Debian's default boot configuration: nowhere.  You need to edit
> /etc/default/bootlogd and change BOOTLOGD_ENABLE=No to Yes.  After a
> reboot, you will find the log in /var/log/boot.

This is good yes I'm getting some additional messages but
the total output is quite short only a few screens long
and there are no references for example to problems with
pcmcia/cardbus modules which I can see fail during boot.

Does bootlogd log via levels? How would I set that?

        b.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Chris Bannister-4]

On Fri, May 16, 2008 at 03:37:22PM +0200, Johannes Wiedersich wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2008-05-16 15:09, Sven Joachim wrote:
> > On 2008-05-16 14:48 +0200, Bill wrote:
> >
> >> I'm tweaking a new kernel for my old laptop to install a new module.
> >>
> >> At boot I see a number of 'fail' messages scroll past on the
> >> screen, but they don't show up in dmesg /var/log/dmesg
> >> /var/log/syslog /var/log/messages etc. These files are
> >> practically devoid of error messages.
> >>
> >> Where can I find the 'complete' output of my boot process?
> >
> > In Debian's default boot configuration: nowhere.  You need to edit
> > /etc/default/bootlogd and change BOOTLOGD_ENABLE=No to Yes.  After a
> > reboot, you will find the log in /var/log/boot.
>
> You could also just press the 'scroll button' on your keyboard, while
> the interesting output floats by. This would stop any further output
> until you press it again, so you have more time to view/read it.
>
> (While this is quick, it does not actually save the output to a log).

Also <SHIFT>-<PAGE_UP> will scroll up a few screens. I don't know what
determines the value of few, but being able to increase it could be
handy.

--
Chris.
======
"One, with God, is always a majority, but many a martyr has been burned
   at the stake while the votes were being counted."  -- Thomas B. Reed


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Douglas A. Tutty]

On Fri, May 16, 2008 at 05:48:59AM -0700, Bill wrote:
> I'm tweaking a new kernel for my old laptop to install a new module.
>
> At boot I see a number of 'fail' messages scroll past on the
> screen, but they don't show up in dmesg /var/log/dmesg
> /var/log/syslog /var/log/messages etc. These files are
> practically devoid of error messages.
>
> Where can I find the 'complete' output of my boot process?

"complete"?  The only way to get everything that goes to the screen is
to connect up a serial port as a serial console and log it on another
box.  bootlogd doesn't get everything.  dmesg doesn't get everything,
and neither do the logs.

If you install the doc-linux-HOWTO package in whatever format, you'll
find the serial-console HOWTO.  That and the other serial- related
howtos will allow you to connect a serial cable from the target box to a
logging box.

If you have a paralell printer, you can also have the printer act as a
console and print all messages.  I don't know if it will work with a
USB printer.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...