> Hello!
>
> > I've eepro100 card and when I try to use IPv6 I'm getting
> > following messages:
> >
> > eth0: Transmit timed out: status 0050 command 0000.
> ....
> > What is going on ?
> > With IPv4 this card works good on 2.1.120...
>
> It does not work with IPv4 too, only you still did not stepped
> into this hole. This drivers dies, when it is loaded with more
> than two multicast addresses.
>
> Try to get newer driver from Donald Becker site.
> If it is still not fixed there, then ...
The newer one doesn't work at all with some of eepro100's even without
multicast addresses...
The card does simply turn all the LED's off and doesn't work. Ifconfig does
happily report that the card is up and running ....
This is the card which do work:
=== Cut ===
/proc/pci:
Bus 0, device 9, function 0:
Ethernet controller: Intel 82557 (rev 4).
Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable.
Latency=32. Min Gnt=8.Max Lat=56.
Prefetchable 32 bit memory at 0xe7800000 [0xe7800008].
I/O at 0xe000 [0xe001].
Non-prefetchable 32 bit memory at 0xe6800000 [0xe6800000].
dmesg log:
Sep 14 16:17:17 tigra kernel: eepro100.c:v1.03 8/11/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
Sep 14 16:17:17 tigra kernel: eepro100.c:v1.03 8/11/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
Sep 14 16:17:17 tigra kernel: eth0: Intel EtherExpress Pro 10/100 at 0xe000,
00:A0:C9:B2:0F:E5, IRQ 9.
Sep 14 16:17:17 tigra kernel: Board assembly 668081-004, Physical
connectors present: RJ45
Sep 14 16:17:17 tigra kernel: Primary interface chip i82555 PHY #1.
Sep 14 16:17:17 tigra kernel: General self-test: passed.
Sep 14 16:17:17 tigra kernel: Serial sub-system self-test: passed.
Sep 14 16:17:17 tigra kernel: Internal registers self-test: passed.
Sep 14 16:17:17 tigra kernel: ROM checksum self-test: passed (0x3c15c8f1).
Sep 14 16:17:17 tigra kernel: Receiver lock-up workaround activated.
=== Cut ===
And this is the one which doesn't work:
=== Cut ===
/proc/pci:
Bus 0, device 9, function 0:
Ethernet controller: Intel 82557 (rev 1).
Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable.
Latency=32. Min Gnt=8.Max Lat=56.
Prefetchable 32 bit memory at 0xe7800000 [0xe7800008].
I/O at 0xe000 [0xe001].
Non-prefetchable 32 bit memory at 0xe6800000 [0xe6800000].
dmesg log:
eepro100.c:v1.03 8/11/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c:v1.03 8/11/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eth0: OEM i82557/i82558 10/100 Ethernet at 0xe000, 00:00:F4:A4:06:2E, IRQ
9.
Board assembly 650466-002, Physical connectors present: RJ45
Primary interface chip DP83840 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.
=== Cut ===
Both cards do work like a charm under 2.0.34. The second one is totally
unusable under 2.1.xxx - the old driver included into the kernel tree
doesn't work with multicast (namely gated is killing network), the newer
ones don't work at all.
Can anybody drop some light - will eepro100 EVER work with 2.1/2.2 kernels
or should we look for another NICs? If so which ones DO really work?
Frankly, I'm extremely bored by this infinite eepro100/2.1.xxx war... It
seems the driver will never get working. Does anybody care?
=======================================================================
Serguei Koubouchine aka the Tamer < > The impossible we do immediately.
e-mail: ksi@gu.net SK320-RIPE < > Miracles require 24-hour notice.
=======================================================================
-
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/