serial ports on the Ultra 5

John Baldwin jhb at
Mon Dec 5 21:23:55 GMT 2005

On Monday 05 December 2005 02:28 pm, Aaron Glenn wrote:
> On 12/5/05, John Baldwin <jhb at> wrote:
> > You don't use sab(4) anymore, but uart(4).
> I had a suspicion that was the case, but couldn't confirm it.
> > Here are your SAB ports.  /dev/ttyu0 and /dev/ttyu1
> Then something more sinister is at work here. A 'cu -l /dev/ttyu0'
> will "connect" me, however I get no prompt, and not input or output
> seems to be passed to the console port. All input gets dumped to the
> shell I executed the cu command from, *after* I kill the first (lowest
> pid) cu process.
> Example:
> yang# ps -ax | grep ttyu
>   687  ??  I      0:00.01 /usr/libexec/getty std.9600 ttyu1
>   688  u0  Is+    0:00.01 /usr/libexec/getty std.9600 ttyu0
>   741  p0  R+     0:00.01 grep ttyu
> yang# cu -l /dev/ttyu1 -s 9600
> Connected
> *hit enter a few times, type hello john, then kill the first cu
> process from another shell*
> yang#
> yang#
> yang#
> yang#
> yang#
> yang#
> yang# hello john
> hello: Command not found.
>                          yang#
> Reading the handbook section on serial communications again, I don't
> see anything wrong. I'll be the first to admit this type of stuff is
> uncharted territory for me. If I skipped some required reading on the 
> subject, please don't hesitate to point me to it.

Try using /dev/cuau0 instead.  /dev/ttyu0 will wait for CD (carrier detect) 
before it opens.

John Baldwin <jhb at>  <><
"Power Users Use the Power to Serve"  =

More information about the freebsd-sparc64 mailing list