Console Access/Protectli V1211/USB-C

Started by dgrns, December 30, 2025, 02:43:06 PM

Previous topic - Next topic
I'm having a strange issue when trying to access the console on a protecli V1211 (2 port firewall with corebios) running Opnsense 25.7.10

I'm able to connect from a linux host using `screen /dev/tty<name> 115200` However characters are randomly dropped from the output and many times not echoed when typed. Boot messages are garbled and only parts of the opnsense-shell are shown.  I am able to type `8` to get to the shell and run commands (with the same dropped character issues).

My current console settings are in the screencap.  An example of the corrupted output is:

```
# ls -al
30 08:08 .history
-rw-------   1 root wheel   20 Dec 29 03:03 .wheel 1174 Dec 17 02:56 .shrc
drwx------   3 root wheel    4 De
```

and partial/truncated opnsense-shell default menu

```
FreeBSD/amd64 (fw) (ttyu0)
 :::        :::
|  Code:        https://github.com/opnsense    root@fw:~ #
```

I've tried the sc console driver, tried the usb setting, etc. Nothing seems to change the behavior.

Any ideas/thoughts on next steps to troubleshoot this?

Observations:
- I don't remember seeing the dropped character issues on the factory installed 25.7 version. I booted, confirmed connectivity, then applied 25.7.10. My next console access had the issue.
- I also had this on the VP6650 with ami bios. I never was able to get usb-c console working. I was able to use the rj45 console instead, but the V1211 does not have one.


- I've also opened a ticket with Protectli. Will update here if any progress on that front.

December 30, 2025, 03:09:45 PM #1 Last Edit: December 30, 2025, 03:35:40 PM by OPNenthu
I have the V1410 (same family) but no current issues with serial console.  In earlier releases (24.7 or early 25.1) there was an issue with a FreeBSD update that broke serial on these devices and a tunable was needed, but that was reverted I think.  I'm not using any tunable work-around currently.  Protectli also recently released a coreboot v0.9.4 update that addresses it.

For me, enabling the VGA Console caused failure to boot.  Maybe I would need to reinstall OPNsense from the VGA image for that, but in any case I have it off.  The other relevant settings look the same.

FWIW, I use PuTTY but screen also works.

EDIT: the tunable that needed to be set then was hint.uart.0.at="isa"