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

[Anton Yurchenko]

Donald Becker wrote:

>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?
>
in dmesg I get bunch of wait_for_cmd timeout.
I also was not able to get this card to work under win2000 server.

>
>I'm guessing that the chip now completes the self-check.
>
>  
>
>>eepro100-diag.c:v2.08 4/17/2002 Donald Becker (becker@scyld.com)
>> 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.
>  
>
yes the first one seems to work OK.

>  
>
>> 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.
>
>  
>


-- 

Anton Yurchenko<phila@dg.net.ua>
Digital Generation