All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@bork.org>
To: Aman <aman@mistralsoftware.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Serial Console Login Fails
Date: Wed, 23 Apr 2003 08:30:15 -0400	[thread overview]
Message-ID: <20030423123015.GI553@bork.org> (raw)
In-Reply-To: <001301c3093d$ad9c69f0$370da8c0@aman>


On Wed, Apr 23, 2003 at 07:41:40AM +0530, Aman wrote:
>
> Hi All
>
> I am using IBM PPC 440 processor on custom board , which has no network
> support. I am using Monta Vista Linux with ramdisk enabled. In the ramdisk ,
> I have very less files. Since there is no network on the board , I am trying
> to enable the serial console login. To achieve this, I disabled serial
> console logging by saying "console=NULL " in the cmdline and in the
> /etc/inittab file added this line

If the kernel is compiled with CONFIG_SERIAL_CONSOLE then you can
do  "console=ttyS0", which will give you a 9600bps 8n1 serial console to
see the kernel boot messages.

> "T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100"
> Bcos of which during the linux bootup , there wont be console message on the
> screen , after some time , there is a login prompt
> <none>login:
> If I try login then it waits for some seconds and then display the same i.e
> <none>login:

You don't have "ttyS0" in /etc/securetty

mh

--
Martin Hicks  ||  mort@bork.org  || PGP/GnuPG: 0x4C7F2BEE
plato up 5 days, 21:20, 12 users,  load average: 0.49, 0.50, 0.46
Beer: So much more than just a breakfast drink.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-04-23 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23  2:11 Serial Console Login Fails Aman
2003-04-23 12:30 ` Martin Hicks [this message]
2003-04-23 12:59   ` Mark Hatle
2003-04-23 13:46     ` Aman
2003-04-23 13:59       ` Martin Hicks
2003-04-23 14:13       ` Mark Hatle

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=20030423123015.GI553@bork.org \
    --to=mort@bork.org \
    --cc=aman@mistralsoftware.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.