linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Milan P. Stanic" <mps@rns-nis.co.yu>
To: linux-admin@vger.kernel.org
Subject: Re: console parameter ignored
Date: Tue, 4 May 2004 01:02:14 +0200	[thread overview]
Message-ID: <20040503230214.GA4980@rns-nis.co.yu> (raw)
In-Reply-To: <20040503173049.B23868@cougar.aero-vision.com>

On Mon, May 03, 2004 at 05:30:49PM -0400, A. R. Vener wrote:
> 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.

Does it have compiled in support for serial console?
 
> Once the boot process reaches run level 3 however,  the getty process on ttyS0 
> works and I can login, assuming all goes well.

That convince me that the your kernel image doesn't have support for
serial console, but I can be wrong.
 
> 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.

Se above.

  reply	other threads:[~2004-05-03 23:02 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
2004-05-03 23:02               ` Milan P. Stanic [this message]
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=20040503230214.GA4980@rns-nis.co.yu \
    --to=mps@rns-nis.co.yu \
    --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).