Not all boot msgs in dmesg

[balanga]

I see numerous msgs come up during boot which dmesg does not record. Can I get a complete report of any errors?

 

[YYY__]

Debugging the boot process

Is there any way to trace what is going on whilst booting if the process suddenly hangs? ie like a 'safe mode'... I don't suppose there is anything like single step booting....

forums.freebsd.org

/etc/rc.conf:
rc_debug="YES" rc_info="YES"

Debugging the boot process

Is there any way to trace what is going on whilst booting if the process suddenly hangs? ie like a 'safe mode'... I don't suppose there is anything like single step booting....

forums.freebsd.org

type boot -v at the loader prompt

 

[yuripv79]

dmesg -a

 

[Ron_H]

Also have a look in

/var/run/dmesg.boot

which contains a snapshot of the boot dmesg output. The system message buffer is a ring buffer and over time the contents thereof changes.

 

[smithi]

CuatroTorres said, in an unlabeled box that won't quote (?):

"type boot -v at the loader prompt"

Or as I do to always have access to all boot messages, add to /boot/loader.conf:

kern.msgbufsize=98304
verbose_loading="YES"
boot_verbose="YES"

boot_verbose does what boot -v does without having to pause in loader, or setting verbose in boot options.

verbose_loading also shows more detail as each kernel module is loaded.

Increasing kern.msgbufsize makes room for the extra messages. You may need (possibly much) more than 96kiB on later systems.

Only after verbose booting will looking at dmesg -a or /var/run/dmesg.boot show all boot messages.