logging during loader

[Polytropon]

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, ...