Re: [eepro100-bug] two i82559 on board do not work

On Tue, 1 Oct 2002, Anton Yurchenko wrote:
> >On Tue, 1 Oct 2002, Anton Yurchenko wrote:
> >>Donald Becker wrote:
> >>>On Wed, 25 Sep 2002, Anton Yurchenko wrote:
> >>>OK, you have a failure of some sort.
> >>>You can read the configuration EEPROM, but the chip can't operate on the bus.
> >>>It appears that the card isn't enabled as a bus master, or the modified
> >>>driver you are using isn't initializing the chip correctly.
...
> I`m sorry, I was under the impression that 2.4.19 had you latest driver 
> in it. I rechecked your web page and compiled it. It doesnt work still, 
> but the eepro100-diag output is a bit different here it is:

What is the detection message?
Are there any error messages?

I'm guessing that the chip now completes the self-check.

> eepro100-diag.c:v2.08 4/17/2002 Donald Becker ([email protected])
>  http://www.scyld.com/diag/index.html
> Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xd400.
> i82557 chip registers at 0xd400:
>   0c000050 367f2000 00000000 00080002 182540a1 00000600
>   No interrupt sources are pending.
>    The transmit unit state is 'Suspended'.
>    The receive unit state is 'Ready'.
>   This status is normal for an activated but idle interface.

This indicates that this NIC chip is operating normally.

>  The Command register has an unprocessed command 0c00(?!).

This is a little curious -- these are mask bits that my driver doesn't set.

> Index #2: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xd000.
> i82557 chip registers at 0xd000:
>   00000000 00000000 00000000 00080002 10000000 00000000
>   No interrupt sources are pending.
>    The transmit unit state is 'Idle'.
>    The receive unit state is 'Idle'.
>   This status is unusual for an activated interface.

This NIC hasn't been started.

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993