From: ebiederm@xmission.com (Eric W. Biederman)
To: Fabrice Gautier <gautier@email.enst.fr>
Cc: Reto Baettig <baettig@scs.ch>,
Linux Alpha mailing list <linux-alpha@vger.rutgers.edu>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: serial console problems with 2.4.4
Date: 02 May 2001 10:37:21 -0600 [thread overview]
Message-ID: <m1elu7pv0e.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3AEFD943.8FE23199@scs.ch> <20010502130958.38BB.GAUTIER@email.enst.fr>
In-Reply-To: Fabrice Gautier's message of "Wed, 02 May 2001 13:15:05 +0200"
Fabrice Gautier <gautier@email.enst.fr> writes:
> On Wed, 02 May 2001 11:54:11 +0200
> Reto Baettig <baettig@scs.ch> wrote:
>
> > Hi
> >
> > I just installed 2.4.4 on our alpha SMP boxes (ES40) and now I have
> > problems with the serial console:
>
> I get same kind of problem when upgrading from 2.4.2 to 2.4.3 and using
> busybox as init/getty
>
> The problem was a bug in busybox. The console initialisation code was
> not correct.
> >
> > sulogin does not accept input from the serial line
> > mingetty does not accept input from the serial line
> > agetty works fine
>
> So this this probably a sulogin/mingetty problem. They should set the
> CREAD flag in your tty c_cflag.
>
> the patch for busybox repalced the line
> tty.c_cflag |= HUPCL|CLOCAL
> by
> tty.c_cflag |= CREAD|HUPCL|CLOCAL
>
> Hope this help.
This part is correct.
However the kernel sets CREAD by default.
sysvinit (and possibly other inits) clears CREAD.
I wish I knew where the breakage actually occured.
And then sulogin/mingetty need to reenable it.
It's not too big of a deal except the serial code doesn't accept SAK's
when CREAD is clear.
Eric
next prev parent reply other threads:[~2001-05-02 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 9:54 serial console problems with 2.4.4 Reto Baettig
2001-05-02 11:15 ` Fabrice Gautier
2001-05-02 16:37 ` Eric W. Biederman [this message]
2001-05-02 18:52 ` Fabrice Gautier
2001-05-03 8:15 ` Eric W. Biederman
2001-05-03 12:30 ` Fabrice Gautier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1elu7pv0e.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=baettig@scs.ch \
--cc=gautier@email.enst.fr \
--cc=linux-alpha@vger.rutgers.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.