Looks like I didn't search hard enough. There is a post from yesterday by
Andrey Savochkin (saw@saw.sw.com.sg) answering this question. I look
forward to using the new driver with the next kernel version.
BTW, the output of the driver (for 2.3.51) is:
eepro100.c:v1.09j+LK1.0 Feb 13, 2000 Linux Kernel
Team http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eth0: Intel PCI EtherExpress Pro100 at 0xc6817000, 00:A0:C9:5C:37:E5, IRQ 9.
Board assembly 667280-003, Physical connectors present: RJ45
Primary interface chip i82555 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.
> I'm on a Debian woody system using an EtherExpress Pro100. libc version
is 2.1.3. The system is an HP Vectra Pentium 166 with 96MB RAM.
> If I boot with any of the 2.3.99-pre kernels, I cannot access the
network (pings fail, nfs don't mount) , even though an ifconfig shows the
interface (eth0) as RUNNING. Booting with a 2.3.51 kernel works fine.
> Any help would be appreciated. I've not found any reference to this
problem in the mailing list archives.
> Please cc me on any responses as I'm not on the mailing list.
> Thanks for your help.
> Kamlesh Bans
> kbans@corsair.com
> Corsair Communications
-
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 : Mon May 15 2000 - 21:00:27 EST