linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Guillaume Laurès" <guillaume.laures@noos.fr>
To: Jure Menart <jure@kom.org>
Cc: linuxppc dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: linux + serial console
Date: 09 Oct 2001 21:58:03 -0400	[thread overview]
Message-ID: <1002679084.773.5.camel@pmg4> (raw)
In-Reply-To: <20011009203308.B28132@hannanges.teden-mladih.com>


le mar 09-10-2001 at 14:33 Jure Menart a écrit :
>
> Hello,
> I'm trying to have Linux box (custom made board, IBM 405gp), which would
> 'work' only through serial console (ttyS0).
> I try many things but I just couldn't keep my 'console' on ttyS0.
> I change everything in main.c to open only /dev/ttyS0, not the usual
> /dev/console. I made /dev/std[io,out,err] links which pointed to /dev/ttyS0
> (although it isn't important I think), but my console 'dissapears' anyway.
> Did I forget something... or better - what did I forget?


I run "root=/dev/hda14 console=ttyS0,38400 console=tty0" as a boot
comand line.
Both console declaration enable output of startup messages on the serial
port as well as on the console, you may only use "console=ttyS0,9600" or
so.

Interesting too, if you happen to have getty installed (getty_ps rpm)
you can set in your /etc/inittab:
s1:2345:respawn:/sbin/getty ttyS0 DT38400
so that you can login on the serial port with a utility like cu or
minicom.

Adding :
ttyS0
in /etc/securetty helps also, to log in as root directly

Enjoy,

--
GoM


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

      reply	other threads:[~2001-10-10  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 18:33 linux + serial console Jure Menart
2001-10-10  1:58 ` Guillaume Laurès [this message]

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=1002679084.773.5.camel@pmg4 \
    --to=guillaume.laures@noos.fr \
    --cc=jure@kom.org \
    --cc=linuxppc-dev@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 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).