mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Lamarque <eric.lamarque@col.bsf.alcatel.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: serial console and kernel 2.4
Date: Wed, 16 Jan 2002 15:29:53 +0100	[thread overview]
Message-ID: <3C458E61.DE349425@col.bsf.alcatel.fr> (raw)

From: christophe barbé (christophe.barbe@lineo.fr)
Date: Mon Jul 30 2001 - 09:54:53 EST 
> I recently upgraded a linux box to the kernel 2.4.4 .
> Since the upgrade I can see the boot output on the remote console
> but I can't use the keyboard

It seems that I experiment the same problem: I've some Compaq machine
that I control remotely with the serial console.

It always runs 2.4.x kernel and all runs fine.

I just replace the machine by a newer one and experiment the same problem
as you. It seems to me that Linux send CTRL-S on the serial line.

To check that this is the real problem, I use rlogin to access the machine
and send CTRL-Q to the Linux console: it does the trick.
( # echo -e "\021" > /dev/console )

I trace the problem to be the arch/i386/kernel/dmi_scan.c function:
DMI is a set of structures to get information about the machine.
It is the one that print "Board Version:.." at boot time.

I'll check at http://www.ibm.com/products/surepath/other/smbios.html to
know the type of such data. "Board Version" must be a string (I assume with
printable character).

My problem is that "Board Version" is printed as "Board Version: 0x14 0x13 *."
where 0x13 is CTRL-S.

Does the kernel contains a mechanism to avoid console printing of DMI information?
(If not, we could maybe add it in function dmi_scan.c:dmi_save_ident()).

Eric.

             reply	other threads:[~2002-01-16 14:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16 14:29 Eric Lamarque [this message]
  -- 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é
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=3C458E61.DE349425@col.bsf.alcatel.fr \
    --to=eric.lamarque@col.bsf.alcatel.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

all inboxes | Powered by JetHome®