Re: logging during loader
On Wed, 26 Jun 2013 23:40:07 -0400, Robert Huff wrote: > > Polytropon writes: > > > > During the processing of loader.conf, something gets printed > > > that suggests all is not right. However, this is a sufficiently > > > modern machine it goes by too fast to read exactly what. > > > It is my understanding that file gets read before the system > > > logging facilities are operational, and possibly before things like > > > ^S/^Q work on the terminal. > > > Is there a way to store the results of that phase of boot-up? > > > > Being on the 1st virtual terminal in text mode (ttyv0) which > > also acts as the console device, press the "Scroll Lock" > > key and use the vertical arrow keys and page scrolling keys > > to get to the top of the log. > > This does not work for me. Specifically, pushing [Scroll Lock] > causes the appropriate light to go on, but output continues to flow. This doesn't look normal. Maybe kernel messages have "precedence" and can appear while regular output is halted? The cursor block should disappear (and the LED should light up). When the console TTY (ttyv0) does not show "any more action", is scrolling back possible then? I've tried it on my home 8.2 system. Normal output is halted. I seem to remember that kernel messages "unlock" Scroll Lock... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: logging during loader
Polytropon writes: > >During the processing of loader.conf, something gets printed > > that suggests all is not right. However, this is a sufficiently > > modern machine it goes by too fast to read exactly what. > >It is my understanding that file gets read before the system > > logging facilities are operational, and possibly before things like > > ^S/^Q work on the terminal. > >Is there a way to store the results of that phase of boot-up? > > Being on the 1st virtual terminal in text mode (ttyv0) which > also acts as the console device, press the "Scroll Lock" > key and use the vertical arrow keys and page scrolling keys > to get to the top of the log. This does not work for me. Specifically, pushing [Scroll Lock] causes the appropriate light to go on, but output continues to flow. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: logging during loader
On Mon, 24 Jun 2013 09:23:10 -0400, Robert Huff wrote: > > During the processing of loader.conf, something gets printed > that suggests all is not right. However, this is a sufficiently > modern machine it goes by too fast to read exactly what. > It is my understanding that file gets read before the system > logging facilities are operational, and possibly before things like > ^S/^Q work on the terminal. > Is there a way to store the results of that phase of boot-up? Being on the 1st virtual terminal in text mode (ttyv0) which also acts as the console device, press the "Scroll Lock" key and use the vertical arrow keys and page scrolling keys to get to the top of the log. It should start with the last BIOS POST messages (if any), and then continue with the loader messages, the kernel messages, and the system startup messages. You can copy them via mouse left/middle to another tty with an editor for future use. This is what Scroll Lock is inteded for. :-) Example: BIOS 637kB/2094976kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (???@?..???, Sun Aug 21 03:33:08 CEST 2011) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x600ebf data=0x68ab4+0x84a44 syms=[0x4+0x75f50+0x4+0xa 27db] /boot/kernel/bktr.ko text=0xfe20 data=0xc08+0x10 syms=[0x4+0xd80+0x4+0xcd6] loading required module 'bktr_mem' /boot/kernel/bktr_mem.ko text=0x8f4 data=0xe0+0xec syms=[0x4+0x2a0+0x4+0x2b3] /boot/kernel/drm.ko text=0x10e2c data=0x11cc+0x10 syms=[0x4+0x1c20+0x4+0x22b1] /boot/modules/nvidia.ko text=0x71c060 data=0x1f7f9c+0x7900 syms=[0x4+0x82510+0x4 +0x59a76] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... And here the kernel messages start, and they will be logged in /var/log/messages anyway. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: logging during loader
Bernt Hansson writes: > Try "start freebsd with verbose logging" then check dmesg. Doesn't that only apply to stuff generated by the hardware enumeration/drivar attach phase? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: logging during loader
On 2013-06-24 15:23, Robert Huff wrote: During the processing of loader.conf, something gets printed that suggests all is not right. However, this is a sufficiently modern machine it goes by too fast to read exactly what. It is my understanding that file gets read before the system logging facilities are operational, and possibly before things like ^S/^Q work on the terminal. Is there a way to store the results of that phase of boot-up? Have you checked dmsg? Try "start freebsd with verbose logging" then check dmesg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: logging during loader
On 6/24/2013 at 4:05 PM Arthur Chance wrote: |On 06/24/13 14:23, Robert Huff wrote: |> |> During the processing of loader.conf, something gets printed |> that suggests all is not right. However, this is a sufficiently |> modern machine it goes by too fast to read exactly what. |> It is my understanding that file gets read before the system |> logging facilities are operational, and possibly before things like |> ^S/^Q work on the terminal. |> Is there a way to store the results of that phase of boot-up? = This has worked well for me, logging the early boot process that usually scrolls by on the screen. I use it on 8.3 and 9.1. I was surprised that it managed to log console stuff that occurred before syslogd was loaded... from syslog.conf # uncomment this to log all writes to /dev/console to # /var/log/console.log # touch /var/log/console.log and chmod it to mode 600 # before it will work console.info/var/log/console.log ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: logging during loader
On 06/24/13 14:23, Robert Huff wrote: During the processing of loader.conf, something gets printed that suggests all is not right. However, this is a sufficiently modern machine it goes by too fast to read exactly what. It is my understanding that file gets read before the system logging facilities are operational, and possibly before things like ^S/^Q work on the terminal. Is there a way to store the results of that phase of boot-up? Does ScrollLock and repeated PageUp get you back far enough? -- In the dungeons of Mordor, Sauron bred Orcs with LOLcats to create a new race of servants. Called Uruk-Oh-Hai in the Black Speech, they were cruel and delighted in torturing spelling and grammar. _Lord of the Rings 2.0, the Web Edition_ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: logging during loader
On Mon, 24 Jun 2013 09:23:10 -0400 Robert Huff wrote: > > During the processing of loader.conf, something gets printed > that suggests all is not right. However, this is a sufficiently > modern machine it goes by too fast to read exactly what. > It is my understanding that file gets read before the system > logging facilities are operational, and possibly before things like > ^S/^Q work on the terminal. > Is there a way to store the results of that phase of boot-up? > > Respectfully, > > > Robert Huff > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I am sure there is a 'right' way to do it, but I had success reading a transitory BIOS message by photographing the screen with a 2-second exposure, in a fairly dark room. This will only work for white-on-black text, of course. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
logging during loader
During the processing of loader.conf, something gets printed that suggests all is not right. However, this is a sufficiently modern machine it goes by too fast to read exactly what. It is my understanding that file gets read before the system logging facilities are operational, and possibly before things like ^S/^Q work on the terminal. Is there a way to store the results of that phase of boot-up? Respectfully, Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
