Gentlebeings, I'm not sure if this question is a "user" or "developer" question. I recently got a D-link DGE500T gigabit NIC for use with one of my Linux systems, which runs on a Tyan 1590 (Via MVP3 chipset with AMD K6/2-500). This machine is fairly modern: it has an 80GB UDMA disk, an ISA and two PCI NICs, and even a FireWire attached IDE disk and CD-RW. It runs all of *them* quite nicely. Unfortunately, I can't get the DGE500T to work. Using the 2.4.19 kernel with the 2.4.20 version of ns83820.c (which had some significant-looking fixes from 2.4.19), I could get the DGE500T to work on a ASUS K7M motherboard (AMD 751 / Via 686 chipset with Slot-1 Athlon 650) but not on the older Tyan 1590. More specifically, on the Tyan 1590, the driver seemed to recognize the NIC and ifconfig reports it, but ping wouldn't work, and tracing with tethereal produced only random-looking frames. There were no kernel error messages when operating. (Also, when I previously tried the 2.4.19 driver on the Tyan 1590; ping didn't work either.) Furthermore, the DOS diagnostic program that came with the DGE500T behaved rather strangely (internal loopback failure) on the Tyan 1590, but since the diag had no significant documentation, I can't be sure what the implications are. With the exact same DGE500T on the Asus K7M, on the other hand, ping worked fine as did ftp. (I didn't try the 2.4.19 driver, nor the DOS diag.) So I no longer think that my DGE500T is defective. Various Google searches didn't turn up anything on the hardware compatibility of the DGE500T, and of course D-Link's WIndows-oriented manual was useless, but National's data sheet on the DP83820 refers to PCI V2.2 compliance. Could that mean it won't work on any PCI V2.1 motherboard? (The Tyan 1590 is PCI V2.1, the Asus K7M is PCI V2.2. Does anyone know of a BIOS tweak that might get the DP83820 chipset to work with PCI V2.1? Or perhaps a driver modification might help? Or is it something else? Thanks, Paul Kosinski Paul Kosinski InterMedia Enterprises prk@iment.com - : 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
