Date: Thu, 21 Sep 2023 18:53:22 +1000 From: Ian Smith <smithi@nimnet.asn.au> To: Ede Wolf <listac@nebelschwaden.de>,Yuri <yuri@aetern.org> Cc: questions@freebsd.org Subject: Re: Capturing Boot Messages? Message-ID: <2FF738A7-8F20-469B-92BE-65525C95D770@nimnet.asn.au> In-Reply-To: <0b80148a-3feb-43b8-8358-cc048be8f32e@nebelschwaden.de> References: <26de1d95-abff-465d-b25c-1b2465e80342@nebelschwaden.de> <f4bea8f9-da21-4e54-9974-aebc01367dbe@aetern.org> <0b80148a-3feb-43b8-8358-cc048be8f32e@nebelschwaden.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 September 2023 5:53:55 am AEST, Ede Wolf <listac@nebelschwaden=2Ede> = wrote: > Am 20=2E09=2E23 um 20:44 schrieb Yuri: > > Ede Wolf wrote: > >> Hello, > >> > >> I am seeing boot messages on screen, errors from rc=2Econf, that I h= ave > >> yet to find in any log=2E Neither dmesg, nor /var/run/dmesg=2Eboot n= or > >> in /var/log/messages=2E > >> > >> 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=20 > options - therefore never been diving into the manpage=2E That's the=20 > solution, I've found my messages! >=20 > Thanks very much Further =2E=2E=2E log hoarders can add to /boot/loader=2Econf: boot_verbose=3D"YES" # always boot -v from loader verbose_loading=3D"YES" # detailed module loading kern=2Emsgbufsize=3D98304 # X200 @ 9=2E3S /var/run/dmesg=2Eboot can be >4 times its non-verbose size, so you might n= eed to enlarge the buffer to keep it all =2E=2E=2E check size of (verbose) = dmesg=2Eboot after boot and allow maybe +20%=2E Perhaps ~150kB by now? Apart from dmesg, it all (and more) goes into /var/log/messages, so newsys= log=2Econf needs tweaking if you always boot verbosely, where a boot might = use ~200kiB in messages=2E cheers, Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2FF738A7-8F20-469B-92BE-65525C95D770>