Error Message...

[Leo Hourvitz]

I'm in about the same boat as Angel -- I went looking for an eepro100 but all
I could find was this new inBusiness 10/100 card.  I've had the same symptoms
as Angel reports; I'm on RedHat 6.2 (kernel 2.2.12-20)...  From looking
around on the Intel website at
http://support.intel.com/support/network/adapter/pro100/21397.htm it looks
like the inBusiness uses the 82559 chipset, but doesn't have the management
features of the higher-end cards.  Of course, there's no information anywhere
about how it's different...  I'm wondering the same thing as Angel, whether I
should give up and look for another NIC.

The t version of the driver won't find the card by default, but I'm running a
dual-boot system and Windows is working fine with the hardware, so if I get
the i/o address from there and specify it to eediag, it seems to see the card
(at least the eerom):

[root@minmay eepro]# ./eepro-diag -p da00 -a -ee
eepro100-diag.c:v1.01 7/8/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Assuming a Intel 82557 EtherExpressPro100B adapter at 0xda00.
i82557 chip registers at 0xda00:
  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.
EEPROM contents:
    00: 9000 d127 d97d 0203 0000 0201 4701 0000
  0x08: 7422 5201 6082 1030 8086 0000 0000 0000
      ...
  0x38: 0000 0000 0000 0000 0000 0000 0000 7db6
 The EEPROM checksum is correct.
Intel EtherExpress Pro 10/100 EEPROM contents:
  Station address 00:90:27:D1:7D:D9.
  Board assembly 742252-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.




Leo


Leo Hourvitz
leo@stoneschool.com


Angel Hernandez wrote:

> Angel Hernandez wrote:
>
> > Thanks for the quick response. This time, though, the result was worse.
> > Before, the error message didn't appear until a few minutes after I
> > booted up. This time the message appeared immediately after eth1 was
> > initialized, before startup was even complete. The message was also a
> > little longer this time:
> >
> > "eth1: Transmit timed out: status 0050 0000 at 0/12 commands 0001a000
> > 0002a000 0003a000"
> > "eth1: Trying to restart the transmitter"
> >
> > The first version of eepro100 I tried was v1.09l. Also, I'm on kernel
> > 2.2.9 - RedHat 6.
> >
> > Any ideas?
> >
>
> So is there another eepro100 driver I should be using? Or is this whole
> ordeal not worth the trouble...meaning it would be better to just go buy
> another NIC card that uses the DEC tulip. Let me know what you think!
>
> - Angel
> -------------------------------------------------------------------
> To unsubscribe send a message body containing "unsubscribe"
> to linux-eepro100-request@beowulf.org

-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-eepro100-request@beowulf.org