Hi,
IIRC, the /var/log/dmesg file is empty when booting into grml.
Can anyone confirm this? How can I fix it so that my device info is retained?
Thanks
* T o n g mlist4suntong@yahoo.com [Tue Jul 13, 2010 at 04:16:29PM +0000]:
IIRC, the /var/log/dmesg file is empty when booting into grml.
Can anyone confirm this? How can I fix it so that my device info is retained?
That's because we don't invoke /etc/init.d/bootlogs in live mode. Why would you need that? Doesn't invoking dmesg(1) provide what you'd need?
regards, -mika-
On Wed, 14 Jul 2010 10:56:34 +0200, Michael Prokop wrote:
Why would you need that? Doesn't invoking dmesg(1) provide what you'd need?
I was trying to use dmesg to see what kind of peripheral does the booted machine has. IIRC, dmesg yielded empty output as well.
A better alternative to see all peripheral info for the box?
Thanks
* T o n g mlist4suntong@yahoo.com [Wed Jul 14, 2010 at 03:43:22PM +0000]:
On Wed, 14 Jul 2010 10:56:34 +0200, Michael Prokop wrote:
Why would you need that? Doesn't invoking dmesg(1) provide what you'd need?
I was trying to use dmesg to see what kind of peripheral does the booted machine has. IIRC, dmesg yielded empty output as well.
Basically /var/log/dmesg provides the same as running dmesg.
A better alternative to see all peripheral info for the box?
Invoking dmesg, lspci, lshw, hwinfo --all,... Check out what grml-hwinfo does.
regards, -mika-
On Wed, 14 Jul 2010 15:43:22 +0000, T o n g wrote:
. . . Doesn't invoking dmesg(1) provide what you'd need?
. . . IIRC, dmesg yielded empty output as well.
Nope, incorrect -- invoking dmesg(1) right after boot can get boot up peripheral info.
Thanks
Teilnehmer (2)
-
Michael Prokop -
T o n g