All of lore.kernel.org
 help / color / mirror / Atom feed
From: Armin <akuster@pacbell.net>
To: "Wright, David" <dwright@infiniswitch.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Anyone got eepro100 working on Walnut?
Date: Wed, 17 Apr 2002 08:42:52 -0700	[thread overview]
Message-ID: <3CBD97FC.1060503@pacbell.net> (raw)
In-Reply-To: FF6CF34C346E724596A2FB5CAAB2C4978844FF@voyager.ops.infiniswitch.com


Wright, David wrote:
> I've been trying to get an Intel eepro100 card working on a
> Walnut board.  I've tried both the 1.09 and 1.19 versions of
> the driver (eepro100.c).  Initially, both failed the self-
> test step.  I was able to get past that one by invalidating
> the dcache after issuing the self-test directive.  However,
> I now find that the card is neither transmitting nor receiving
> reliably.  I get messages like:
>
>    eth1: Unknown receiver error, status=0x5048.  [lots of these]
>
> and
>
> eth1: Transmit timed out: status 0050  0000 at 2/8 commands 00a00300 00a003000.
> eth1: Restarting the chip...
> eth1: Command unit failed to mark command 00030000 as complete at 6.
>
>
> Any suggestions (other than junking this card, which is not an option
> for me) most welcome.
>
>   -- David Wright, InfiniSwitch Corp.
>
>
>
>

Yes,

What kernel version are you using? and what is the openbios version ?

armin


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

  parent reply	other threads:[~2002-04-17 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17  1:08 Anyone got eepro100 working on Walnut? Wright, David
2002-04-17 15:36 ` Matt Porter
2002-04-17 15:42 ` Armin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-17 19:22 Wright, David

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=3CBD97FC.1060503@pacbell.net \
    --to=akuster@pacbell.net \
    --cc=dwright@infiniswitch.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.