Hi, I have severe problems with my D-Link 530TX (not plus) cards. The driver initializes correctly: Mar 27 22:35:43 cosmo kernel: via-rhine.c:v1.10-LK1.1.13 Nov-17-2001 Written by Donald Becker Mar 27 22:35:43 cosmo kernel: http://www.scyld.com/network/via-rhine.html Mar 27 22:35:43 cosmo kernel: via-rhine: reset finished after 5 microseconds. Mar 27 22:35:43 cosmo kernel: eth0: VIA VT6102 Rhine-II at 0xd000, 00:05:5d:a3:dd:5e, IRQ 10. Mar 27 22:35:43 cosmo kernel: eth0: MII PHY found at address 8, status 0x782d advertising 01e1 Link 0021. Mar 27 22:35:43 cosmo kernel: via-rhine: reset finished after 5 microseconds. Mar 27 22:35:43 cosmo kernel: eth1: VIA VT6102 Rhine-II at 0xd400, 00:05:5d:a1:f1:16, IRQ 12. Mar 27 22:35:43 cosmo kernel: eth1: MII PHY found at address 8, status 0x782d advertising 01e1 Link 45e1. Mar 27 22:35:43 cosmo kernel: eth0: via_rhine_open() irq 10. Mar 27 22:35:43 cosmo kernel: eth0: reset finished after 5 microseconds. Mar 27 22:35:43 cosmo kernel: eth0: Done via_rhine_open(), status 081a MII status: 782d. Mar 27 22:35:43 cosmo kernel: eth1: via_rhine_open() irq 12. Mar 27 22:35:43 cosmo kernel: eth1: reset finished after 5 microseconds. Mar 27 22:35:43 cosmo kernel: eth1: Setting full-duplex based on MII #8 link partner capability of 45e1. Mar 27 22:35:43 cosmo kernel: eth1: Done via_rhine_open(), status 0c1a MII status: 782d. The driver comes from the original Kernel 2.4.18 source at kernel.org. The cards work fine with low traffic. But when the traffic gets higher, I get lots of transmission errors: Mar 27 22:53:58 cosmo kernel: eth0: Transmit error, Tx status 00008100. Mar 27 22:54:01 cosmo kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 27 22:54:01 cosmo kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting... Mar 27 22:54:01 cosmo kernel: eth0: reset finished after 225 microseconds. Mar 27 22:54:07 cosmo kernel: eth0: Transmit error, Tx status 00008100. Mar 27 22:54:09 cosmo kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 27 22:54:09 cosmo kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting... Mar 27 22:54:09 cosmo kernel: eth0: reset finished after 5 microseconds. Mar 27 22:54:52 cosmo kernel: eth0: Transmit error, Tx status 00008100. Mar 27 22:54:55 cosmo kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 27 22:54:55 cosmo kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting... Mar 27 22:54:55 cosmo kernel: eth0: reset finished after 200 microseconds. Mar 27 22:54:58 cosmo kernel: eth0: Transmit error, Tx status 00008100. Now, if the traffic gets even higher, the NIC will hang after about half an hour. You have to make a cold reboot of the system to get the NIC working again: Mar 27 22:07:07 cosmo kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 27 22:07:07 cosmo kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting... Mar 27 22:07:07 cosmo kernel: eth0: reset did not complete in 10 ms. Mar 27 22:07:07 cosmo kernel: eth0: reset finished after 10005 microseconds. Mar 27 22:07:07 cosmo kernel: eth0: Promiscuous mode enabled. Mar 27 22:07:19 cosmo kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 27 22:07:19 cosmo kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting... Mar 27 22:07:19 cosmo kernel: eth0: reset did not complete in 10 ms. Mar 27 22:07:19 cosmo kernel: eth0: reset finished after 10005 microseconds. Mar 27 22:07:19 cosmo kernel: eth0: Promiscuous mode enabled. Mar 27 22:07:45 cosmo kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 27 22:07:45 cosmo kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting... Mar 27 22:07:45 cosmo kernel: eth0: reset did not complete in 10 ms. Mar 27 22:07:45 cosmo kernel: eth0: reset finished after 10005 microseconds. Mar 27 22:07:45 cosmo kernel: eth0: Promiscuous mode enabled. Mar 27 22:07:59 cosmo kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 27 22:07:59 cosmo kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting... Mar 27 22:07:59 cosmo kernel: eth0: reset did not complete in 10 ms. Mar 27 22:07:59 cosmo kernel: eth0: reset finished after 10005 microseconds. Mar 27 22:07:59 cosmo kernel: eth0: Promiscuous mode enabled. After this last message the NIC (just the NIC, everything else is fine) was dead. I had to reboot the system. The same thing happens with eth1, but the traffic is not that high on that device so the problem rarely occurs there. I look around the internet and found others with the same problem: http://lhd.zdnet.com/db/dispproduct.php3?DISP?296 Their suggestion, just not to buy the card is not really a solution. What do you think about the strange repeating reset times of exactly 10005 microseconds? There seems to be a driver version 1.11 at Donald Becker's page. Should I try this one? I hope you can help me here, otherwise I will have to exchange both NICs. Thanks, Marc - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
