Re: serial ttys broken?

From: Ruslan Ermilov <ru_at_FreeBSD.org>
Date: Wed, 21 Sep 2005 16:51:37 +0300
On Tue, Sep 20, 2005 at 02:13:59PM -0700, Marcel Moolenaar wrote:
> On Tue, Sep 20, 2005 at 08:26:36PM +0300, Ruslan Ermilov wrote:
> > > 
> > > In my experience, you need to use:
> > > 
> > > cuad0   "/usr/libexec/getty std.9600"   dialup  on secure
> > > and not
> > > ttyd0   "/usr/libexec/getty std.9600"   dialup  on secure
> > > 
> > > in /etc/ttys to get a console on the serial port if you are not using -h
> > > in /boot.config.  I'm pretty sure it's been like this for a long time.
> > > 
> > > What line have you got in /etc/ttys?
> > > 
> > I've come to the same conclusion after also trying uart(4) instead
> > of sio(4).
> 
> Don't forget that DCD does not have to be asserted when the
> serial line is used as serial console. When the serial line
> is not used as serial console, DCD must be asserted. This
> is not always the case with null-modem cables.
> Change std.9600 to 3wire.9600 and don't use cua*. Use tty*.
> 
Thanks a lot!  This has fixed all issues I had, now everything
works as advertised, including being able to use conscontrol(8)
to add serial console, and set/reset console via TIOCSTTY.

Perhaps it would be a good idea to add entries with 3wire
to /etc/ttys?


Cheers,
-- 
Ruslan Ermilov
ru_at_FreeBSD.org
FreeBSD committer

Received on Wed Sep 21 2005 - 11:51:26 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:43 UTC