1.20.2.5 eepro100.c bug?

[Brian Leeper]

This is what I'm getting with the new driver--note the "Invalid EEPROM" 
error 5 lines down. The driver (an older EEPRO 10/100, at least 2.5 years
old) seems to work enough to let me telnet into the box, but the ethernet
address is quite wrong. Also, it's getting a totally different hardware
address compared to the stock driver.

New driver output:

eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/driv ers/eepro100.html eepro100.c:
$Revision: 1.20.2.5 $ 2000/03/28 Modified by Andrey V. Savochkin <sa
w@saw.sw.com.sg> and others 
eth0: Invalid EEPROM checksum 0x818c, check
settings before activating this device!  eth0: Intel PCI EtherExpress
Pro100 at 0xcc804000, 00:F0:ED:3E:7B:FF, IRQ 19. 
  Board assembly 771d6d-134, Physical connectors present: RJ45
  Primary interface chip unknown-15 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x49caa8d6).
  Receiver lock-up workaround activated.
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/driv
ers/eepro100.html
eepro100.c: $Revision: 1.20.2.5 $ 2000/03/28 Modified by Andrey V. Savochkin <sa
w@saw.sw.com.sg> and others

<->

Below is the output from the original driver, as included with stock
2.2.14:

eth0: Intel EtherExpress Pro 10/100 at 0x6400, 00:A0:C9:3C:73:FA, IRQ 19.
  Board assembly 661949-004, Physical connectors present: RJ45
  Primary interface chip DP83840A PHY #1.
  DP83840 specific setup, setting register 23 to 8462.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x49caa8d6).
  Receiver lock-up workaround activated.

Brian

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