Date: Wed, 27 Nov 2024 09:44:43 -0700 From: Warner Losh <imp@bsdimp.com> To: Robert Schulze <rs@bytecamp.net> Cc: stable@freebsd.org Subject: Re: not working /dev/console Message-ID: <CANCZdfrs=2mw3pcqG_is8zeLZ07cPropcVab96tGU1Y%2BgycjqQ@mail.gmail.com> In-Reply-To: <27224122-3f36-4e88-87b4-c4cfc0a6b7d8@bytecamp.net> References: <DBE9ABDF-092F-4198-9E14-DF2E0AAB3638@cs.huji.ac.il> <27224122-3f36-4e88-87b4-c4cfc0a6b7d8@bytecamp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000007014570627e7af42 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 27, 2024 at 3:59=E2=80=AFAM Robert Schulze <rs@bytecamp.net> wr= ote: > Hello, > > Am 27.11.24 um 09:34 schrieb Daniel Braniss: > > Hi, > > when the console is not uart0, init=E2=80=99s output, which I assume us= es > /dev/console > > is lost. Boot, kernel and login work ok, also debugger. > > you can give the loader a hint, which uart is considered a console. > In my case, any IPMI-console on uart1 works with the following settings > in /boot/loader.conf: > > -- > boot_multicons=3D"yes" > comconsole_port=3D"0x2f8" > > hint.uart.0.flags=3D"0x0" > hint.uart.1.flags=3D"0x10" > hint.uart.1.baud=3D"115200" > -- > > hint.uart.N.flags=3D"0x10" means: this is a potential system console. > See uart(4) manpage for this. > hw.uart.console is preferred over the flags. In fact, nobody should be setting the flags at all. I should remove them from the man page, or burry them in a footnote somewhere. So boot_mulitcons w/o boot_serial=3Dyes will mean that video is the primary console and serial the secondary, and /etc/rc only runs on the primary console. Warner > regards, > Robert Schulze > > --0000000000007014570627e7af42 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 27, 2024 at 3:59=E2=80=AF= AM Robert Schulze <<a href=3D"mailto:rs@bytecamp.net">rs@bytecamp.net</a= >> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px= 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hel= lo,<br> <br> Am 27.11.24 um 09:34 schrieb Daniel Braniss:<br> > Hi,<br> > when the console is not uart0, init=E2=80=99s output, which I assume u= ses /dev/console<br> > is lost. Boot, kernel and login work ok, also debugger.<br> <br> you can give the loader a hint, which uart is considered a console.<br> In my case, any IPMI-console on uart1 works with the following settings <br= > in /boot/loader.conf:<br> <br> --<br> boot_multicons=3D"yes"<br> comconsole_port=3D"0x2f8"<br> <br> hint.uart.0.flags=3D"0x0"<br> hint.uart.1.flags=3D"0x10"<br> hint.uart.1.baud=3D"115200"<br> --<br> <br> hint.uart.N.flags=3D"0x10" means: this is a potential system cons= ole.<br> See uart(4) manpage for this.<br></blockquote><div><br></div><div>hw.uart.c= onsole is preferred over the flags. In fact, nobody should be setting</div>= <div>the flags at all. I should remove them from the man page, or burry the= m</div><div>in a footnote somewhere.</div><div><br></div><div>So boot_mulit= cons w/o boot_serial=3Dyes will mean that video is the</div><div>primary co= nsole and serial the secondary, and /etc/rc only runs on</div><div>the prim= ary console.</div><div><br></div><div>Warner</div><div><br></div><div>=C2= =A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e= x;border-left:1px solid rgb(204,204,204);padding-left:1ex"> regards,<br> Robert Schulze<br> <br> </blockquote></div></div> --0000000000007014570627e7af42--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrs=2mw3pcqG_is8zeLZ07cPropcVab96tGU1Y%2BgycjqQ>