Re: Walnut 405GP and a 3com 905 (PCI slot0 J31)

Well switching the card to J25 PCI Slot 3 seems to solve
the problem.

I was using J31 Slot 0. The docs on the board say that this
slot can be used with a 3.3v card at 66MHz if the connector
is reversed.

Since the connector on my board is in the 5v config, I
would hope the programming resistors were shipped in
the correct config, but I did not check.

So I don't know what the problem was and I don't really
care, but I will just stay away from using J31 for now.

On Wed, Mar 14, 2001 at 02:53:58PM -0800, andrew may wrote:

Anyone try to use a 3com NIC card on the Walnut board?

I can load the module but when I try to bring up the
interface I get a stream of bus errors.

eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
eth1: PCI bus error, bus status 80000020
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.
eth1: PCI bus error, bus status 80000020
eth1: using NWAY autonegotiation
eth1: Host error, FIFO diagnostic register 0000.

I am using the 2.4.2 version of the Walnut kernel dated
Mar 1 on the ftp site.

There are changes to the 3com driver in the pre patches
but I have not tried it yet.

Most docs say this is a hardware failure so I might want
to change the PCI slot I am using.

Has anyone successfully used a PCI network card in the
Walnut board.

If it is just a driver bug I do not want to spend time
fixing it, I would just want to get a card that works.

I just want to do some perf testing on board itself.

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