Many thanks.
I had noticed the puc entries in dmesg, and I tried using cua03, but my
problem came from using an inadequate serial connector [1].
I was not suspecting the connector because I was convinced I was using
one coming from Soekris.
It would have helped if Soekris was selling it's serial connectors with
some identification on it. A simple label with the Soekris brand and a
model/part number would be great.
[1]
http://soekris.com/products/accessories/serial-connector-2nd-port-pci-bracket.html
--
Laurent Salle
On 06/07/13 01:02, Christian Weisgerber wrote:
Laurent Salle <lsa...@taciturne.net> wrote:
I'm unsuccessful trying to use the second serial port on a Soekris Net
6501 with OpenBSD 5.3.
$ cu -s 9600 -l cua01
/dev/cua01: Device not configured
link down
$
Anyone has been able to use this port ? With which command ?
It's cua03.
See below dmesg output:
Exactly!
com3 at puc0 port 0 apic 0 int 19: ti16750, 64 byte fifo
com4 at puc1 port 0 apic 0 int 19: ti16750, 64 byte fifo
com5 at puc2 port 0 apic 0 int 19: ti16750, 64 byte fifo
com6 at puc3 port 0 apic 0 int 19: ti16750, 64 byte fifo
com0 at isa0 port 0x3f8/8 irq 4: ti16750, 64 byte fifo
com0: console
Note that it's com2 if you run amd64 and this has changed yet again
in OpenBSD -current. In short, it's the port at puc0, and dmesg
will tell you as which com(4) device it shows up. For com4 and
higher, you'll need to create the corresponding /dev entries with
MAKDEV tty04 etc. first.
_______________________________________________
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech
