I got myself two FTDI based USB adapters with a zero cable; direct cu confirmed that hardware is in working order.
Now, on host A I edited /boot/loader.conf to enable serial console, /etc/ttys to enable a login on /dev/cuaU0 and I do receive a login prompt on host B.
I can even successfully enter my login on the remote side B and receive the motd but after that, nothing happens. And there's nothing in the logs that indicates why the shell isn't getting started.
EDIT: I should probably add, that I can press Ctrl+C at that point, which returns me back to the login prompt. No amount of waiting spawns the shell, unfortunately.
My entry in host A's /etc/ttys:
EDIT2: I set the speed in /boot/loader.conf, that's why I modified it here as well for 115200.
What could possibly block the shell from getting started? I even tried binding to ttyU0 on host A, but that didn't produce any login on host B.
Now, on host A I edited /boot/loader.conf to enable serial console, /etc/ttys to enable a login on /dev/cuaU0 and I do receive a login prompt on host B.
I can even successfully enter my login on the remote side B and receive the motd but after that, nothing happens. And there's nothing in the logs that indicates why the shell isn't getting started.
EDIT: I should probably add, that I can press Ctrl+C at that point, which returns me back to the login prompt. No amount of waiting spawns the shell, unfortunately.
My entry in host A's /etc/ttys:
Code:
cuaU0 "/usr/libexec/getty std.115200" vt100 on secure
What could possibly block the shell from getting started? I even tried binding to ttyU0 on host A, but that didn't produce any login on host B.