Date: Mon, 16 Dec 2024 13:01:38 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: Freebsd-stable List <stable@freebsd.org>, Warner Losh <imp@bsdimp.com>, Kurt Jaeger <pi@freebsd.org> Subject: Re: not working /dev/console Message-ID: <501640865.7444.1734350498438@localhost> In-Reply-To: <044EAFE1-DCB8-439C-A422-4B5F8CD4C37C@cs.huji.ac.il> References: <DBE9ABDF-092F-4198-9E14-DF2E0AAB3638@cs.huji.ac.il> <Z0bcQvu36o-rqsJn@fc.opsec.eu> <CAA78225-E266-4CBE-807D-B72D9BCE58E8@cs.huji.ac.il> <CANCZdfoQtYLP62rWO6oTHg4ajbV7SK=ehq2jkv1o0ZX8_im0jw@mail.gmail.com> <365D866D-F7D2-4DB6-AFFB-B4C3829D8467@cs.huji.ac.il> <CANCZdfoiJE6-aKKFhafXPMY8FOg4nEBmhf2hN%2BcJXzMVrkyiqg@mail.gmail.com> <Z1Wb6vdZ8V6Pmf4J@fc.opsec.eu> <ED9E83DE-FA40-4685-B073-E5BF5A29B1CB@cs.huji.ac.il> <Z1XbDqEzeI_Qvf8I@fc.opsec.eu> <CANCZdfrrpdaR_4Zyj3WgZTj7EcXT-YzdaeD%2BM-0ucUTDs9Aucg@mail.gmail.com> <Z1Xk_SpEZL4XVm2S@fc.opsec.eu> <3F04B2DC-1AA9-4663-BCDE-3EFD0B01527E@cs.huji.ac.il> <044EAFE1-DCB8-439C-A422-4B5F8CD4C37C@cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_7443_110460761.1734350498418 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Daniel Braniss <danny@cs.huji.ac.il> Datum: maandag, 16 december 2024 09:23 Aan: Kurt Jaeger <pi@freebsd.org> CC: Warner Losh <imp@bsdimp.com>, Freebsd-stable List <stable@freebsd.org> Onderwerp: Re: not working /dev/console > > > > On 9 Dec 2024, at 10:35, Daniel Braniss <danny@cs.huji.ac.il> wrote: > > > > hi Kurt & Warner: > > im trying on a PCengines apu2 fbsd 14.2, but have the same symptoms, no console. > > dmesg|grep uart -> nothing. > > after some trials the best i have is: > > the bsd-menu showing > > 5. Cons: Serial > > and only the kernel messages. > > > > no /dev/console, no /dev/ttyu0, but can remote login. > > > > btw, all works fine with a 13.1 kernel > > > >> On 8 Dec 2024, at 20:27, Kurt Jaeger <pi@freebsd.org> wrote: > >> > >> Hi! > >> > >>> So, there should be a line like > >>> > >>> uart0: console (115200,n,8,1) > >>> > >>> if not, then hw.uart.console isn't making it through. > >> > >> So somehow the uarts are not found during initialization ? > >> > >>> If you are using a custom kernel, > >> > >> It's the generic kernel. > >> > >>> you can add that to a file and add 'env > >>> /path/to/file/on/build/host' to the kernel config to wire that into the > >>> kernel, should the boot path make it hard to set an initial environment > >>> otherwise. Also, DHCP should still try to grab /boot/loader.conf from the > >>> tftp/http server as well. That might also be something that needs debugging > >>> (or hopefully just correct config). > >> > >> I'll investigate further. > > > I made a diff from booting 13.1 and 14.2 with boot_verbose, and this stands out: > (only in the 13.1) > > -pcib0: allocated type 4 (0x3f8-0x3f8) for rid 0 of uart0 > -pcib0: allocated type 4 (0x3f8-0x3f8) for rid 0 of uart0 > -uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0 > -pcib0: allocated type 4 (0x3f8-0x3f8) for rid 0 of uart0 > -uart0: console (115200,n,8,1) > -ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 2 vector 53 > -uart0: fast interrupt > -uart0: PPS capture mode: DCD > -pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1 > -pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1 > -uart1: <16550 or compatible> at port 0x2f8 irq 3 on isa0 > -pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1 > -ioapic0: routing intpin 3 (ISA IRQ 3) to lapic 3 vector 53 > -uart1: fast interrupt > -uart1: PPS capture mode: DCD > > does this help? > cheers, > danny > > > >> > >> -- > >> pi@FreeBSD.org +49 171 3101372 Now what ? > > > > > > > Hi, A change was made that uart does not attach on isa anymore. I think this was the commit about it: https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=74b9fc7adcf4afb1c3039267e338c3cfdf022957 I don't know much about the details. Somebody else can tell more. Regards, Ronald. ------=_Part_7443_110460761.1734350498418 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body><br> <p><strong>Van:</strong> Daniel Braniss <danny@cs.huji.ac.il><br> <strong>Datum:</strong> maandag, 16 december 2024 09:23<br> <strong>Aan:</strong> Kurt Jaeger <pi@freebsd.org><br> <strong>CC:</strong> Warner Losh <imp@bsdimp.com>, Freebsd-stable List <stable@freebsd.org><br> <strong>Onderwerp:</strong> Re: not working /dev/console</p> <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"> <div class="MessageRFC822Viewer" id="P"> <div class="TextPlainViewer" id="P.P"><br> <br> > On 9 Dec 2024, at 10:35, Daniel Braniss <danny@cs.huji.ac.il> wrote:<br> ><br> > hi Kurt & Warner:<br> > im trying on a PCengines apu2 fbsd 14.2, but have the same symptoms, no console.<br> > dmesg|grep uart -> nothing.<br> > after some trials the best i have is:<br> > the bsd-menu showing<br> > 5. Cons: Serial<br> > and only the kernel messages.<br> ><br> > no /dev/console, no /dev/ttyu0, but can remote login.<br> ><br> > btw, all works fine with a 13.1 kernel<br> ><br> >> On 8 Dec 2024, at 20:27, Kurt Jaeger <pi@freebsd.org> wrote:<br> >><br> >> Hi!<br> >><br> >>> So, there should be a line like<br> >>><br> >>> uart0: console (115200,n,8,1)<br> >>><br> >>> if not, then hw.uart.console isn't making it through.<br> >><br> >> So somehow the uarts are not found during initialization ?<br> >><br> >>> If you are using a custom kernel,<br> >><br> >> It's the generic kernel.<br> >><br> >>> you can add that to a file and add 'env<br> >>> /path/to/file/on/build/host' to the kernel config to wire that into the<br> >>> kernel, should the boot path make it hard to set an initial environment<br> >>> otherwise. Also, DHCP should still try to grab /boot/loader.conf from the<br> >>> tftp/http server as well. That might also be something that needs debugging<br> >>> (or hopefully just correct config).<br> >><br> >> I'll investigate further.<br> <br> <br> I made a diff from booting 13.1 and 14.2 with boot_verbose, and this stands out:<br> (only in the 13.1)<br> <br> -pcib0: allocated type 4 (0x3f8-0x3f8) for rid 0 of uart0<br> -pcib0: allocated type 4 (0x3f8-0x3f8) for rid 0 of uart0<br> -uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0<br> -pcib0: allocated type 4 (0x3f8-0x3f8) for rid 0 of uart0<br> -uart0: console (115200,n,8,1)<br> -ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 2 vector 53<br> -uart0: fast interrupt<br> -uart0: PPS capture mode: DCD<br> -pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1<br> -pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1<br> -uart1: <16550 or compatible> at port 0x2f8 irq 3 on isa0<br> -pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1<br> -ioapic0: routing intpin 3 (ISA IRQ 3) to lapic 3 vector 53<br> -uart1: fast interrupt<br> -uart1: PPS capture mode: DCD<br> <br> does this help?<br> cheers,<br> danny<br> <br> <br> >><br> >> --<br> >> pi@FreeBSD.org +49 171 3101372 Now what ?<br> ><br> <br> </div> <hr></div> </blockquote> <br> <br> Hi,<br> <br> A change was made that uart does not attach on isa anymore.<br> I think this was the commit about it:<br> <a href="https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=74b9fc7adcf4afb1c3039267e338c3cfdf022957">https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=74b9fc7adcf4afb1c3039267e338c3cfdf022957</a><br>; <br> I don't know much about the details. Somebody else can tell more.<br> <br> Regards,<br> Ronald.<br> </body></html> ------=_Part_7443_110460761.1734350498418--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?501640865.7444.1734350498438>