Mine is almost the same:
NETGEAR
NGMC1698
9831
AN3125.1
::
:: > which is described in hinv (on the server, which I'll describe
:: > exclusively, because it's been running longest and has the most
:: > to lose if the card turns out to be icky) as
:: >
:: > eth0: Lite-On 82c168 PNIC
:: > eth0: MII transceiver found
::
:: My logs are long since rotated, but that looks familiar.
::
dmesg gives me the following:
tulip.c:v0.89F 5/12/98 becker@cesdis.gsfc.nasa.gov
eth0: NETGEAR NGMC169 MAC at 0xb800, <hardware address>, IRQ 5.
eth0: MII transceiver found at MDIO address 1, config 1000 status 782d.
eth0: Advertising 01e1 on PHY 1, previously advertising 01e1.
That's with the tulip.c that came on the NetGear drivers floppy, from
their Linux directory. I've been careful to use that tulip.c, but then
tulip.c in the kernel hasn't been updated or included in patch in the
2.2.x series (perhaps because it hasn't needed to be, likely).
I've had nary a problem with the NG on my Linux box. Had to get the
latest drivers for the on in my NT box, though; it kept crashing with
the distributed drivers. Damn MS, always changing stuff! :/
Also, afaik, I don't have a VIA chipset. I've the Asus P5A mobo, and
don't think that has that particular chipset. My Linux box is all
SCSI, anyhow, though. My NT box is running a BH6, which uses an Intel
chip, so no way to test the implications there with a VIA/NG clash.
:: > And the VIA chipset I've got on the motherboards (FIC PA2013)
:: > is Vendor id 1106, Device id 586, which dmesg reports as
:: >
:: > ide: VT82C586 VXPRO+ (Apollo) on PCI bus 0 function 57
:: > ide0: BM-DMA at 0x6400-0x6407
:: > ide1: BM-DMA at 0x6408-0x640f
:: > hda: IBM-DTTA-351350, 8063MB w/464kB Cache, CHS=1644/255/63, DMA
:: > hdc: IBM-DTTA-351350, 8063MB w/464kB Cache, CHS=16383/16/63, DMA
:: >
:: >
Of course, Via has this to say about their 586 chip:
The VIA Apollo VPX/97 features the VIA
VT82C586B PCI-IDE south bridge controller chip.
Highly integrated, this chip complies with the
Microsoft® PC97industry standard by supporting
ACPI/OnNow, Ultra DMA/33 and USB technologies.
Would compliance with MS's industry standard (now wait a sec, isn't
that an oxymoron??) cause you guys any problems?
Just food to chew on. I'll be quiet now and listen to my betters. ;)
::
:: Hmmm, it most definitely didn't function, as evidenced by the mark in the
:: wall the airborne card caused. :-)
::
:: dave
::
Damn cards just won't stop growing wings, will they? :)
-- Matthew Vanecek Studies in Business Computers at the University of North Texas http://www.unt.edu/bcis Visit my Website at http://people.unt.edu/~mev0003 ***************************************************************** For 93 million miles, there is nothing between the sun and my shadow except me. I'm always getting in the way of something...
- 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/