From: "christophe barbé" <christophe.barbe@lineo.fr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: serial console and kernel 2.4
Date: Mon, 30 Jul 2001 16:54:53 +0200 [thread overview]
Message-ID: <20010730165453.A19255@pc8.lineo.fr> (raw)
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 ?)
Is sombody else experienciong the same problem ?
Christophe
--
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 reply other threads:[~2001-07-30 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 14:54 christophe barbé [this message]
2001-07-30 15:18 ` serial console and kernel 2.4 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
-- strict thread matches above, loose matches on Subject: below --
2001-07-30 15:20 James Bottomley
2001-07-30 15:37 ` christophe barbé
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é
2002-01-16 14:29 Eric Lamarque
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=20010730165453.A19255@pc8.lineo.fr \
--to=christophe.barbe@lineo.fr \
--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