linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "A. R. Vener" <salt@aero-vision.com>
To: linux-admin@vger.kernel.org
Subject: Re: console parameter ignored
Date: Mon, 3 May 2004 17:30:49 -0400	[thread overview]
Message-ID: <20040503173049.B23868@cougar.aero-vision.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405031548540.5382-100000@marcus.rome.vh.org>; from wcarlson@vh.org on Mon, May 03, 2004 at 03:51:52PM -0500

Grub supports the serial console just fine. I can use it during the GRUB boot 
process to select   the linux image and command line options I want.

The problem happens when the kernel takes over and begins  printing 
messages to the console or waiting for input from the console in case of fsck 
failure.  

The /proc/cmdline file shows:
ro root=/dev/hda1 console=tty0 console=ttyS0,38400n8

So apparently the kernel is reading the command line arguments correctly.

For some reason, the kernel is  not using  ttyS0 for its console.  The kernel 
boot messages go to the video screen and  input is read from the keyboard.

Once the boot process reaches run level 3 however,  the getty process on ttyS0 
works and I can login, assuming all goes well.

Since GRUB and getty  both work with the ttyS0 serial port, there
is obviously nothing wrong with it per se. So I am left with the 
conclusion that for some reason the kernel is refusing to use the ttyS0 port 
as its console.

On Mon, May 03, 2004 at 03:51:52PM -0500, Bill Carlson wrote:
> No, look at serial-console.txt in the kernel Documentation, the above 
> syntax is correct for the kernel.
> 
> Rudy, you'll need to tell grub to support serial; I prefer lilo and one 
> has to tell lilo specifically to support serial as well as add the kernel 
> parameters. You'll have to figure out what to tell grub.
> 
> Also, double check your kernel parameters are being read correctly by 
> checking /proc/cmdline.
> 
> Bill Carlson

Rudy Vener

  reply	other threads:[~2004-05-03 21:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 15:31 Kernel panic: VFS: unable to mount fs on 09:00 Ralica Kirilova
2004-04-28 18:37 ` Kevin J. Cummings
2004-04-29  7:24   ` Ralica Kirilova
2004-04-29 15:20     ` Glynn Clements
2004-04-29 16:26       ` console parameter ignored A. R. Vener
2004-04-30  6:34         ` terry white
2004-05-03 20:51           ` Bill Carlson
2004-05-03 21:30             ` A. R. Vener [this message]
2004-05-03 23:02               ` Milan P. Stanic
2004-04-29 20:50     ` Kernel panic: VFS: unable to mount fs on 09:00 Kevin J. Cummings
2004-05-04  7:32 ` Ralica Kirilova
  -- strict thread matches above, loose matches on Subject: below --
2004-05-04  2:52 console parameter ignored Jim C. Brown

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=20040503173049.B23868@cougar.aero-vision.com \
    --to=salt@aero-vision.com \
    --cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).