From: Michael Pruznick <michael_pruznick@mvista.com>
To: clark@esteem.com
Cc: Wolfgang Denk <wd@denx.de>,
ppcboot-users@lists.sourceforge.net,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ethernet Trouble
Date: Mon, 09 Oct 2000 18:03:18 -0700 [thread overview]
Message-ID: <39E26AD6.1933322F@mvista.com> (raw)
In-Reply-To: 1.5.4.32.20001010000239.006b54d8@pop.esteem.com
> Right now I think that it can't talk to the console or init uses a
> function in ld.so.1 to spit a message to the console and is failing to load
> the library correctly. Does PPCBOOT tell the kernel to use its console or do
> I need to do that somehow? I have tried to stick "console=/dev/ttyS00" in
> the bootargs but then I don't get any messages after the uncompresssing
> kernel message.
Unless its a typo, try "console=/dev/ttyS0" (1 zero, not 2).
Also, if its just a console print problem, you should still be able to
telnet into the box and do things like "cat <file> > /dev/ttyS0" and
"od -x /dev/ttyS0", just to show that the serial device is good and
the problem is with the console device attached to the serial port.
Your console,tty should look something like this:
> ls -l console ttyS0
crw------- 1 root root 5, 1 Aug 4 10:34 console
crw------- 1 root tty 4, 64 Aug 4 10:34 ttyS0
I also like to use the following inttab file, instead of
default we ship. It means there are more places for problems
to exist, but I've seen direct bash drop errors that getty
picks up, like "serial input buffer overrun".
> cat etc/inittab
id:3:initdefault:
# System initialization.
si::sysinit:/etc/rc.sysinit
# Single user shell
1:2345:respawn:/sbin/getty console DT9600 linux
l0:0:wait:/sbin/halt -dip
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/sbin/reboot -dip
> cat etc/default/getty
CLEAR=NO
--
Michael Pruznick, michael_pruznick@mvista.com, 408-328-9215
MontaVista Software, 490 Potrero Ave, Sunnyvale, CA 94085
http://www.hardhatlinux.com, V:408-328-9200, F:408-328-9204
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-10 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-10 0:02 Re: Ethernet Trouble clark
2000-10-10 0:43 ` Wolfgang Denk
2000-10-10 1:03 ` Michael Pruznick [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-06 15:56 clark
2000-10-06 17:18 ` Matthew Locke
2000-10-06 17:59 ` Jerry Van Baren
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=39E26AD6.1933322F@mvista.com \
--to=michael_pruznick@mvista.com \
--cc=clark@esteem.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ppcboot-users@lists.sourceforge.net \
--cc=wd@denx.de \
/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.