> On 27 Nov 2024, at 12:59, Robert Schulze <r...@bytecamp.net> wrote:
>
> Hello,
>
> Am 27.11.24 um 09:34 schrieb Daniel Braniss:
>> Hi,
>> when the console is not uart0, init’s output, which I assume uses
>> /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="yes"
> comconsole_port="0x2f8"
>
> hint.uart.0.flags="0x0"
> hint.uart.1.flags="0x10"
> hint.uart.1.baud="115200"
> --
>
> hint.uart.N.flags="0x10" means: this is a potential system console.
> See uart(4) manpage for this.
>
> regards,
> Robert Schulze
>
Do you also get the output from init(8)?, does date > /dev/console work?
That is what I do, so most of the outputs go to uart1,
The only missing is /dev/console. IMHO it’s the one used by init(8)
Messages from the boot/kernel are redirected fine, the missing stuff is from
init(8)
There is also a login, and so I can login to the’console’.
Cheers,
Danny
