Re: Capturing Boot Messages?

Am 21.09.23 um 10:53 schrieb Ian Smith:
> On 21 September 2023 5:53:55 am AEST, Ede Wolf <listac@nebelschwaden.de> wrote:
>   > Am 20.09.23 um 20:44 schrieb Yuri:
>   > > Ede Wolf wrote:
>   > >> Hello,
>   > >>
>   > >> I am seeing boot messages on screen, errors from rc.conf, that I have
>   > >> yet to find in any log. Neither dmesg, nor /var/run/dmesg.boot nor
>   > >> in /var/log/messages.
>   > >>
>   > >> Any chance to reread the full boot process somewhere or to set up
>   > >> full boot logging?
> 
>   > > Tried `dmesg -a`?
> 
>   > No, shame on me, did not remotely think about dmesg may having any
>   > options - therefore never been diving into the manpage. That's the
>   > solution, I've found my messages!
>   >
>   > Thanks very much
> 
> Further ... log hoarders can add to /boot/loader.conf:
> 
> boot_verbose="YES"         # always boot -v from loader
> verbose_loading="YES"    # detailed module loading
> kern.msgbufsize=98304   # X200 @ 9.3S
> 
> /var/run/dmesg.boot can be >4 times its non-verbose size, so you might need to enlarge the buffer to keep it all ... check size of (verbose) dmesg.boot after boot and allow maybe +20%. Perhaps ~150kB by now?
> 
> Apart from dmesg, it all (and more) goes into /var/log/messages, so newsyslog.conf needs tweaking if you always boot verbosely, where a boot might use ~200kiB in messages.
> 
> cheers, Ian

Hello Ian,

thanks very much, those are further excellent suggestions! Highly 
appreciated.
Quite a lot of useful basic, but rather new stuff for me, I've learned. 
Thanks to all again.

Ede