tsoome, I have mailed you loader's ok prompt lsefi command , as requested. Here for the continuing of debugging it.

I'd also like to see prtconf -vD | grep -w asy

from lsefi, you should have 3 serial ports; PciRoot(0x0)/Pci(0x16,0x3)/Uart(115200,8,N,1) -- I think, its UART on PCI (to be confirmed from prtconf -vD), and PciRoot(0x0)/Pci(0x1F,0x0)/Acpi(PNP0303,0x0) and PciRoot(0x0)/Pci(0x1F,0x0)/Acpi(PNP0303,0x1) (ttya and ttyb on ISA, that is serial ports "onboard").

ah, silly me, PNP0303 should be ps/2 keyboard and mouse, not serial port...

so its down to one serial port;)

Also, if you have chance to get on OK prompt: efi-show -g global, But, I wonder if your loader is thinking it has ttya, but kernel is thinking it has term/0 -- check with ls /dev/term. Only "onboard" ports are named ttya-ttyd

# prtconf -vD | grep -w asy gives pci103c,8299, instance #0 (driver name: asy)

and ls /dev/term ?

tsoome, ls /dev/term gives : 0 ; ls -l /term gives : 0 -> ../../devices/pci@0,0/pci103c,8299@16,3:0

let me send you another listing of efi-show -g global on mail

sent

yes, so it has no ttya, but term/0. You can try boot -B os_console=term/0 but Im not quite sure if it will do any good... early boot can not access it and kernel startup, Im not really sure if it will agree to attach console on term/0.

its all built assuming ttya-ttyd.

no surprses from efi-show --ConIn and ConOut values are as expected.

surprises*

putting term/0 in loader boot does not change it.

yea, was pretty sure it does not.

So there could be some settings in SmartOS to point to right terminal then

Also it is hard to even get Serial console runnin in Mesh Commander, I restart it few times and get it if Remote desktop/console is not active/connected ..

basically thats the bad boy there: src.illumos.org/source/xref/illumos…/i86pc/io/consplat.c?r=82bb7c22#451

but its not all of it (as one might suspect).

I plan to use serial console for Intel AMT or USB connected serial port plus some MCU as a cheapo replacement for full KVM, where not available for remote access. And Serial seems more useful because on SmartOS I am basically always in terminal, anyway.

Maybe if I put something in my SmartOS post booting script that's started by service? So It activates serial console post boot