On Wed, May 17, 2000, Kamlesh Bans <kbans@corsair.com> wrote:
; Thanks for the help. I made the following change to eepro100.c (both the
; 2.2.14/1.18 and 2.2.15/1.20.2.3 versions) plus I modified the version
; string (forgetting a newline):
;
; // #define eeprom_delay() inw(ee_addr)
; #define eeprom_delay() udelay(100)
;
; Unfortunately, this did not help. Both are built in to the 2.2.15 kernel.
;
; May 8 10:47:28 newton kernel: SCSI device sdg: hdwr sector= 512 bytes.
; Sectors= 17689267 [8637 MB] [8.6 GB]
; May 8 10:47:28 newton kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
; http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
; May 8 10:47:28 newton kernel: eepro100.c: $Revision: 1.18 $ 1999/12/29
; Modified by Andrey V. Savochkin <saw@msu.ru>
; May 8 10:47:28 newton kernel: 1.18kb 2000/05/17 Kamlesh Bans
; workaround<4>eth0: Invalid EEPROM checksum 0x0000, check settings before
; activating this device!
; May 8 10:47:28 newton kernel: eth0: Intel PCI EtherExpress Pro100 at
; 0xc8808000, 00:00:00:00:00:00, IRQ 11.
; May 8 10:47:28 newton kernel: Board assembly 000000-000, Physical
; connectors present:
; May 8 10:47:28 newton kernel: Primary interface chip None PHY #0.
; May 8 10:47:28 newton kernel: General self-test: passed.
; May 8 10:47:28 newton kernel: Serial sub-system self-test: passed.
; May 8 10:47:28 newton kernel: Internal registers self-test: passed.
; May 8 10:47:28 newton kernel: ROM checksum self-test: passed (0x49caa8d6).
; May 8 10:47:28 newton kernel: Receiver lock-up workaround activated.
; May 8 10:47:28 newton kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
; http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
; May 8 10:47:28 newton kernel: eepro100.c: $Revision: 1.18 $ 1999/12/29
; Modified by Andrey V. Savochkin <saw@msu.ru>
; May 8 10:47:28 newton kernel: 1.18kb 2000/05/17 Kamlesh Bans
; workaroundPartition check:
; May 8 10:47:28 newton kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
;
; May 8 10:47:28 newton kernel: mdio_read() timed out with val = 08040000.
>From looking at the error messages that you are getting I second Andrey's
mail, this is happening because the driver is experiencing problems when
reading the eeprom and fails to detect you PHY. Unless you have no PHY :^)
The driver has issues with reading the eeprom, it doesn't drive the
eeprom serial clock correctly. By not following clock frequency
specification it clocks data "into/out of" epprom incorrectly.
Can you please mail me in your lspci output I want to see which revision
of the eepro you have, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:16 EST