On Mon, Feb 16, 2015 at 10:50:35AM +0100, Radek wrote:
> I'm trying to setup a serial console. My RS-232 is an old PCIcard.
>
> I tried this way:
> boot> set tty com4
>
> /etc/ttys:
> tty00 "/usr/libexec/getty std.9600" vt220 on secure
> tty04 "/usr/libexec/getty std.9600" vt220 on secure
>
> but can't connect to console and the system doesn't boot.
> What am I doing wrong?
The boot loader is a simplistic program making use of basic CPU
features and BIOS services. It can't access every device like a
fully initialized kernel can.
At startup, the boot loader will probe the available device it can
make use of. It will look like this:
probing: pc0 com0 apm pci mem[640K 990M a20=on]
disk: hd0+ hd1+*
>> OpenBSD/i386 BOOT 3.26
On this computer, I can use "com0" or "pc0" (display) as a console.
"com0" is a standard traditionnal motherboard serial port.
Look at what your boot loader tell you. Very likely, only tradionnal
serial port can be use, not something attached to a "puc" card.
[Note that boot loader names can be different that kernel device
names.]
Beside that, if you just want a login console on tty04, add the
"local" flag to the /etc/ttys file.
The truth is that there is very few DTE-to-DTE serial cable that
provide the correct signaling to support open on DCD only.
like:
tty04 "/usr/libexec/getty std.9600" vt220 on secure local
>
> # dmesg
> OpenBSD 5.6 (GENERIC.MP) #1: Wed Feb 11 11:23:16 CET 2015
> [email protected]:/usr/src/sys/arch/i386/compile/GENERIC.MP
...
> puc0 at pci4 dev 0 function 0 "Sunix 40XX" rev 0x01: ports: 1 com
> com4 at puc0 port 0 apic 2 int 16: ti16750, 64 byte fifo
> com4: probed fifo depth: 32 bytes
Your dmesg didn't show traditionnal serial ports.
Good luck.
