From: Wolfgang Denk <wd@denx.de>
To: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: LXT972 FEC problem on MPC855
Date: Mon, 26 Aug 2002 20:27:02 +0200 [thread overview]
Message-ID: <20020826182707.BA14B11829@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 26 Aug 2002 11:04:13 PDT." <3D6A6D9D.20404@redswitch.com>
In message <3D6A6D9D.20404@redswitch.com> you wrote:
>
> > After running ppcboot on our board successfully (including the fast
> > ethernet LXT972), we have trouble on enabling FEC on linux kernel. The
> > problem is that we cannot send any packets through the network after the
> > kernel is booted. The ethernet looks OK during initialization according
> > to the printed messages. We are trying to locate the problem but haven't
> > found yet so far. Any hints on what caused such problem?
...
> eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
> IP-Config: Incomplete network configuration information.
You are passing bad/insufficient boot arguments to the Linux kernel;
unfortunaltely you don;t show us this part of the boot messages, so I
cannot even guess what you're doing wrong.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Do not underestimate the value of print statements for debugging.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-26 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 1:20 LXT972 FEC problem on MPC855 Xiaogeng (Shawn) Jin
2002-08-26 18:04 ` Xiaogeng (Shawn) Jin
2002-08-26 18:27 ` Wolfgang Denk [this message]
2002-08-26 19:17 ` Xiaogeng (Shawn) Jin
[not found] ` <3D6A9E57.1060308@redswitch.com>
2002-08-26 22:34 ` Ricardo Scop
2002-08-28 0:19 ` Xiaogeng (Shawn) Jin
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=20020826182707.BA14B11829@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=xjin@redswitch.com \
/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).