Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

com(4) dialout device behavior change?

On a netbsd-8/amd64 system I have no problem using 'cu' to connect to
the serial console of another system (sparc, netbsd-8.99.37) with a
"three-wire" serial cable:

Excerpt from "dmesg.boot":

  com0 at acpi0 (UAR1, PNP0501-1): io 0x3f8-0x3ff irq 4
  com0: ns16550a, working fifo

  $ cu -9600 -l dty00

When I boot the same amd64 host with -current, the same command reports
"connected", but I have no evidence of characters being transmitted.
(Subsequently connecting to the remote with SSH shows 'sudo' waiting
for authentication on the serial console port.  It should have aborted
after all the newlines I sent to it.)

I seem to recall a change with some of the signals now required before
dialout devices work.  I'll need to check my adapter to make sure
everything that I need to loop back is correct.

|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

Home | Main Index | Thread Index | Old Index