Date: Mon, 16 Dec 2024 10:23:21 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: Kurt Jaeger <pi@freebsd.org> Cc: Warner Losh <imp@bsdimp.com>, Freebsd-stable List <stable@freebsd.org> Subject: Re: not working /dev/console Message-ID: <044EAFE1-DCB8-439C-A422-4B5F8CD4C37C@cs.huji.ac.il> In-Reply-To: <3F04B2DC-1AA9-4663-BCDE-3EFD0B01527E@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>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 9 Dec 2024, at 10:35, Daniel Braniss <danny@cs.huji.ac.il> wrote: >=20 > 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=20 > 5. Cons: Serial > and only the kernel messages. >=20 > no /dev/console, no /dev/ttyu0, but can remote login. >=20 > btw, all works fine with a 13.1 kernel >=20 >> On 8 Dec 2024, at 20:27, Kurt Jaeger <pi@freebsd.org> wrote: >>=20 >> Hi! >>=20 >>> So, there should be a line like >>>=20 >>> uart0: console (115200,n,8,1) >>>=20 >>> if not, then hw.uart.console isn't making it through. >>=20 >> So somehow the uarts are not found during initialization ? >>=20 >>> If you are using a custom kernel, >>=20 >> It's the generic kernel. >>=20 >>> 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). >>=20 >> 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 >>=20 >> --=20 >> pi@FreeBSD.org +49 171 3101372 Now what ? >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?044EAFE1-DCB8-439C-A422-4B5F8CD4C37C>