From: "christophe barbé" <christophe.barbe@lineo.fr>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: "christophe barbé" <christophe.barbe@lineo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: serial console and kernel 2.4
Date: Mon, 30 Jul 2001 17:37:02 +0200 [thread overview]
Message-ID: <20010730173702.C19605@pc8.lineo.fr> (raw)
In-Reply-To: <200107301520.f6UFKtT06867@localhost.localdomain>
In-Reply-To: <200107301520.f6UFKtT06867@localhost.localdomain>; from James.Bottomley@SteelEye.com on lun, jui 30, 2001 at 17:20:55 +0200
"it works for me" is better that no answer for me. So Thank you for your
answer.
Reto give me a solution : because of a flag all incomming char are ignored.
So now I need to find why this flag is ok for you and not for me.
Christophe
Le lun, 30 jui 2001 17:20:55, James Bottomley a écrit :
> > I recently upgraded a linux box to the kernel 2.4.4 (from 2.2.18).
> > This box has no display and use the serial console. Since the upgrade
> > I can see the boot output on the remote console but I can't use the
> > keyboard. Each time I press a key, an interrupt is seen by the
> > no-display machine but no char appears in the console. Today I've
> > upgraded an another box to 2.4.7 with a similar setup and I've the
> > same problem.
>
> > Is there something that I'm missing ? (something new with the kernel
> > 2.4 that is required for a serial console that was not required with
> > the 2.2 ?)
>
> I hate to send an email which says "it works for me", but it does (all
> the way
> up to 2.4.7).
>
> However, one of the things to remember about the serial console is that
> it is
> primarily designed for *output*. If you see the boot messages, then it's
>
> doing its job correctly. Things like kdb and sysrq can accept input from
> the
> serial console, but usually only if something else (like getty) has
> opened it
> first.
>
> My setup (on RedHat 7.1) looks like this
>
> In /etc/lilo.conf
>
> # make lilo output to serial console
> serial=0,9600n8
>
> # for each kernel add this line
> append="console=ttyS0,9600n8 console=tty0"
>
> Note, the above append causes /dev/console to be /dev/tty0 (the virtual
> console). If you want to see all the boot messages you need /dev/ttyS0
> to be
> /dev/console and you should reverse the two console statements in this
> line.
>
> In /etc/inittab:
>
> S:0123456:respawn:/sbin/mingetty --noclear ttyS0
>
> With this setup I can activate sysrq and kdb from the serial console.
>
> Note also that different distributions have different ways of handling
> the
> system console; you might also have to disable the special distribution
> handling on a non-RedHat system.
>
> James Bottomley
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Christophe Barbé
Software Engineer - christophe.barbe@lineo.fr
Lineo France - Lineo High Availability Group
42-46, rue Médéric - 92110 Clichy - France
phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01
http://www.lineo.com
next prev parent reply other threads:[~2001-07-30 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 15:20 James Bottomley
2001-07-30 15:37 ` christophe barbé [this message]
2001-07-30 15:53 ` Stuart MacDonald
2001-07-30 16:21 ` christophe barbé
2001-07-30 16:55 ` Chris Wedgwood
2001-07-30 20:36 ` Thomas Duffy
2001-07-30 21:41 ` Chris Wedgwood
2001-07-30 22:24 ` Miquel van Smoorenburg
2001-07-31 7:51 ` christophe barbé
-- strict thread matches above, loose matches on Subject: below --
2002-01-16 14:29 Eric Lamarque
2001-07-30 14:54 christophe barbé
2001-07-30 15:18 ` baettig
2001-07-30 15:33 ` christophe barbé
2001-07-30 15:19 ` Steve Hill
2001-07-30 20:43 ` Fabrice Gautier
2001-07-30 20:59 ` Miquel van Smoorenburg
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=20010730173702.C19605@pc8.lineo.fr \
--to=christophe.barbe@lineo.fr \
--cc=James.Bottomley@steeleye.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®