From: Jim Dennis <jimd@starshine.org>
To: "Green" <greeen@iii.org.tw>
Cc: "LinuxKernelMailList" <linux-kernel@vger.kernel.org>,
"MipsMailList" <linux-mips@fnet.fr>,
"LinuxEmbeddedMailList" <linux-embedded@waste.org>
Subject: Re: Serial Console!!
Date: Mon, 02 Apr 2001 19:57:38 -0700 [thread overview]
Message-ID: <200104030257.TAA20765@mars.starshine.org> (raw)
In-Reply-To: <001201c0bb3f$4dd65600$4c0c5c8c@trd.iii.org.tw> Message Apparently From "Green" <greeen@iii.org.tw> Dated Mon, 02 Apr 2001 14:36:50 +0800.
Apparently "Green" <greeen@iii.org.tw> wrote:
> Hi all,
> I want to login to my MIPS box through serial port.
> I execute 'make menuconfig' and select the 'serial console'.
> But I can't see the login prompt in my window(I use netterm).
> May I ask how serial console work?
> Or I forget something?
> P.S I skip /sbin/init program.
In order for you to have full serial console port you
must do more than simply enable the option in your kernel.
Your BIOS/firmware should have serial console support of
its own (most PCs don't, most other systems, even most
PowerPC based Macs and workstations do, in the form of
OpenFirmware --- formerly known as Sun's FCODE).
Your MIPS box might have a firmware with serial console
support, or it might not.
That should allow you to access any pre-boot configuration
options or diagnostics (including providing some mechanism
to reset the NVRAM and to set the boot device or sequence)
Your bootloader would have to support serial console
to allow you to select which kernel you want to load
and/or to pass kernel command line options and set
initial environment variable/value pairs (a feature
that seems unique to Linux).
Of course, the Linux kernel support must be enabled,
though that *only* applies to whether the kernel messages
are copied to that device. If you would see it from
dmesg, then it won't get copied to the console.
To enable logins on a serial device you must spawn
some form of getty process (normally done by init). That
will listen for connections (normallly by taking login names)
and exec() your login program (usually with the login name passed
on its argument list).
Since you specify that you're not running init, it's obvious
why you can't "login."
So, please tell me that you didn't actually think that
logins and shells were handled directly by UNIX and Linux
kernels!
--
Jim Dennis
Software Analyst
Axis Personal Trainers http://www.axispt.com
next parent reply other threads:[~2001-04-03 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001201c0bb3f$4dd65600$4c0c5c8c@trd.iii.org.tw>
2001-04-03 2:57 ` Jim Dennis [this message]
2005-11-18 1:31 Serial console?? Nicholas Lee
-- strict thread matches above, loose matches on Subject: below --
1998-06-25 16:55 Serial console? Craig Metz
1998-06-25 21:28 ` djb
1998-06-26 6:49 ` David S. Miller
1998-06-26 6:50 ` Jakub Jelinek
1998-06-26 10:41 ` Marc Duponcheel
1998-06-26 22:26 ` Jakub Jelinek
1998-06-27 6:40 ` Ward Deng
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=200104030257.TAA20765@mars.starshine.org \
--to=jimd@starshine.org \
--cc=greeen@iii.org.tw \
--cc=linux-embedded@waste.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@fnet.fr \
/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.