Tracking boot messages
Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. Furthermore, it appears that the font change done by console-setup kills my scrollback; so that Shift+PageUp and Shift+PageDown don't work. That is, I can't scroll back prior to the font change. On some hardware platforms, such as s390, when running in a virtual machine under z/VM, I can capture the console boot messages by spooling the virtual console. But on other platforms, such as i386, I do not know of a way to capture all the boot messages. Does anybody know of a way? (I am running Debian Squeeze.) -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1458241328.162591.1295279631499.javamail.r...@md01.wow.synacor.com
Re: Tracking boot messages
On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote: Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. Furthermore, it appears that the font change done by console-setup kills my scrollback; so that Shift+PageUp and Shift+PageDown don't work. That is, I can't scroll back prior to the font change. On some hardware platforms, such as s390, when running in a virtual machine under z/VM, I can capture the console boot messages by spooling the virtual console. But on other platforms, such as i386, I do not know of a way to capture all the boot messages. Does anybody know of a way? (I am running Debian Squeeze.) /etc/default/bootlogd Set BOOTLOGD_ENABLE=YES and examine /var/log/boot or dmesg after rebooting. Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1295280135.12602.4059.ca...@nero.internal.friendscout24.de
Re: Tracking boot messages
Hello, Stephen Powell a écrit : Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. Try to enable bootlogd in /etc/default/bootlogd. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3468b0.4040...@plouf.fr.eu.org
Re: Tracking boot messages
On Mon, 17 Jan 2011 10:53:51 -0500, Stephen Powell wrote: Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. (...) (see the responses in the other user's e-mails, you have to manually enable this) What I can't see is why this logging facility is not enabled by default. I also think it should be kept in a unique file, instead to be split in / var/log/dmesg and /var/log/boot, IMO it would be easier to read, interpret and debug... Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.17.16.34...@gmail.com
Re: Tracking boot messages
On Mon, Jan 17, 2011 at 10:53 AM, Stephen Powell zlinux...@wowway.com wrote: Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. Furthermore, it appears that the font change done by console-setup kills my scrollback; so that Shift+PageUp and Shift+PageDown don't work. That is, I can't scroll back prior to the font change. Edit /etc/default/bootlogd. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=Oe7uje=M9F8Q2=1pwsoltuhjxhtlfzkjp7...@mail.gmail.com
Re: Tracking boot messages
On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote: On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote: Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. Furthermore, it appears that the font change done by console-setup kills my scrollback; so that Shift+PageUp and Shift+PageDown don't work. That is, I can't scroll back prior to the font change. On some hardware platforms, such as s390, when running in a virtual machine under z/VM, I can capture the console boot messages by spooling the virtual console. But on other platforms, such as i386, I do not know of a way to capture all the boot messages. Does anybody know of a way? (I am running Debian Squeeze.) /etc/default/bootlogd Set BOOTLOGD_ENABLE=YES and examine /var/log/boot or dmesg after rebooting. Hmm. Well, that helps. dmesg still does not contain the message from console-setup, but /var/log/boot now does. I'm not sure if I needed to rebuild my initial RAM file system image after making the above change, but I did anyway for good measure. Still, I was hoping for all boot messages in a single file somewhere. /var/log/boot starts with Setting parameters of disc: (none). This is about three lines prior to Checking root file system...fsck from util-linux-ng 2.17.2 All boot messages prior to this point are not included in /var/log/boot. Is there any way to get *all* messages actually written to the console during boot in a single file somewhere? -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/361746793.164047.1295282620128.javamail.r...@md01.wow.synacor.com
Re: Tracking boot messages
Connect a serial cable to your console port and use minicom on you laptop to save the output ;) Frank Von meinem iPhone gesendet Am 17.01.2011 um 17:43 schrieb Stephen Powell zlinux...@wowway.com: On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote: On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote: Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. Furthermore, it appears that the font change done by console-setup kills my scrollback; so that Shift+PageUp and Shift+PageDown don't work. That is, I can't scroll back prior to the font change. On some hardware platforms, such as s390, when running in a virtual machine under z/VM, I can capture the console boot messages by spooling the virtual console. But on other platforms, such as i386, I do not know of a way to capture all the boot messages. Does anybody know of a way? (I am running Debian Squeeze.) /etc/default/bootlogd Set BOOTLOGD_ENABLE=YES and examine /var/log/boot or dmesg after rebooting. Hmm. Well, that helps. dmesg still does not contain the message from console-setup, but /var/log/boot now does. I'm not sure if I needed to rebuild my initial RAM file system image after making the above change, but I did anyway for good measure. Still, I was hoping for all boot messages in a single file somewhere. /var/log/boot starts with Setting parameters of disc: (none). This is about three lines prior to Checking root file system...fsck from util-linux-ng 2.17.2 All boot messages prior to this point are not included in /var/log/boot. Is there any way to get *all* messages actually written to the console during boot in a single file somewhere? -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/361746793.164047.1295282620128.javamail.r...@md01.wow.synacor.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca2e52e4-7bd9-4520-9d83-d193f451d...@anotheria.net
Re: Tracking boot messages
On Mon, 17 Jan 2011 16:34:21 +, Camaleón wrote: What I can't see is why this logging facility is not enabled by default. I also think it should be kept in a unique file, instead to be split in / var/log/dmesg and /var/log/boot, IMO it would be easier to read, interpret and debug... Strongly agree. -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ih1u3b$fih$4...@dough.gmane.org
Re: Tracking boot messages
Stephen Powell a écrit : Set BOOTLOGD_ENABLE=YES and examine /var/log/boot or dmesg after rebooting. Hmm. Well, that helps. dmesg still does not contain the message from console-setup Of course not. dmesg displays only kernel messages. This is completely different from messages displayed on the console by any process. You could even set /proc/sys/kernel/printk to not display kernel messages on the console. Still, I was hoping for all boot messages in a single file somewhere. /var/log/boot starts with Setting parameters of disc: (none). This is about three lines prior to Checking root file system...fsck from util-linux-ng 2.17.2 All boot messages prior to this point are not included in /var/log/boot. Obviously bootlogd can record only messages which are displayed while it is running. See /etc/rcS.d/ for the initscripts order. Specifically, it won't record messages displayed in the initramfs, before initscripts are started. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d348c93.3010...@plouf.fr.eu.org
Re: Tracking boot messages
T o n g wrote: Camaleón wrote: What I can't see is why this logging facility is not enabled by default. I also think it should be kept in a unique file, instead to be split in / var/log/dmesg and /var/log/boot, IMO it would be easier to read, interpret and debug... Strongly agree. There is a wishlist bug in the BTS for this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=232569 Miquel van Smoorenburg wrote: Date: Tue, 17 Feb 2004 16:43:44 +0100 The reason bootlogd is off, is that it is buggy and doesn't work on all systems. So, it will remain off for the foreseeable future. It will likely even be replaced by another solution entirely. After the Squeeze release seems like a good time to visit that issue again. It would be useful. Bob signature.asc Description: Digital signature
Re: Tracking boot messages
On Mon, 17 Jan 2011 13:03:27 -0700, Bob Proulx wrote: T o n g wrote: Camaleón wrote: What I can't see is why this logging facility is not enabled by default. I also think it should be kept in a unique file, instead to be split in / var/log/dmesg and /var/log/boot, IMO it would be easier to read, interpret and debug... Strongly agree. There is a wishlist bug in the BTS for this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=232569 Thanks for the link. I know the bug is very old but anyway, I've added my comments there. Miquel van Smoorenburg wrote: Date: Tue, 17 Feb 2004 16:43:44 +0100 The reason bootlogd is off, is that it is buggy and doesn't work on all systems. So, it will remain off for the foreseeable future. It will likely even be replaced by another solution entirely. After the Squeeze release seems like a good time to visit that issue again. It would be useful. Yes, and I hope bootlogd is nowadays (7 years later) working okay. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.17.20.57...@gmail.com
Re: Tracking boot messages
On Mon, Jan 17, 2011 at 11:43 AM, Stephen Powell zlinux...@wowway.com wrote: On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote: On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote: Hello, list. I am trying to find a way to track boot messages. I know about things like dmesg|less and less /var/log/syslog but they don't cover everything. For example, /etc/init.d/console-setup issues a message during boot that goes something like this: Setting up console font and keymap and this does not appear in either dmesg output or in /var/log/syslog. Furthermore, it appears that the font change done by console-setup kills my scrollback; so that Shift+PageUp and Shift+PageDown don't work. That is, I can't scroll back prior to the font change. On some hardware platforms, such as s390, when running in a virtual machine under z/VM, I can capture the console boot messages by spooling the virtual console. But on other platforms, such as i386, I do not know of a way to capture all the boot messages. Does anybody know of a way? (I am running Debian Squeeze.) /etc/default/bootlogd Set BOOTLOGD_ENABLE=YES and examine /var/log/boot or dmesg after rebooting. Hmm. Well, that helps. dmesg still does not contain the message from console-setup, but /var/log/boot now does. I'm not sure if I needed to rebuild my initial RAM file system image after making the above change, but I did anyway for good measure. Still, I was hoping for all boot messages in a single file somewhere. /var/log/boot starts with Setting parameters of disc: (none). This is about three lines prior to Checking root file system...fsck from util-linux-ng 2.17.2 All boot messages prior to this point are not included in /var/log/boot. Is there any way to get *all* messages actually written to the console during boot in a single file somewhere? The closest to what you're looking for is to add debug to the boot command line to have your initrd's /init run with set -x and have its output saved to /dev/.initramfs/initramfs.debug. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTinXCJycZrzPuFwpE-62=D-CTZQ0KoW=al7fd...@mail.gmail.com
