Patrick Welche <prlw1@newn.cam.ac.uk> writes:

> According to our vr driver and pcidevs,

> vendor VIATECH      0x1106  VIA Technologies
> product VIATECH VT3043          0x3043  VT3043 (Rhine) 10/100 Ethernet
> product VIATECH VT6102          0x3065  VT6102 (Rhine II) 10/100
Ethernet
> product VIATECH VT86C100A       0x6100  VT86C100A (Rhine-II) 10/100
> Ethernet

> I just got an Asus P4XP-X, which has a

> VIA Technologies product 0x3106

> The driver CD includes a driver for FreeBSD (if_fet rather than if_vr)
> which has

> DEVICEID_3043   VIA VT86C100A Rhine Fast Ethernet Adapter
> DEVICEID_3065   VIA Rhine II Fast Ethernet Adapter
> DEVICEID_3106   VIA VT6105 Rhine III Fast Ethernet Adapter
> DEVICEID_3053   VIA VT6105M Rhine III Management Adapter

> If that is to be believed, then our current pcidevs should be (and vr(4)
fixed)

> product VIATECH VT86C100A       0x3043  VT86C100A (Rhine) 10/100
Ethernet
> product VIATECH VT6102          0x3065  VT6102 (Rhine II) 10/100
Ethernet

> which begs the question, has anyone ever seen VT86C100A in their dmesg?

in NetBSD-1-6-1-stable /usr/src/sys/dev/pci/pcidevs, these changes:

#product VIATECH VT3043         0x3043  VT3043 (Rhine) 10/100 Ethernet
#product VIATECH VT86C100A      0x6100  VT86C100A (Rhine-II) 10/100  Ethernet
product VIATECH VT86C100A       0x3043  VT86C100A (Rhine) 10/100 Ethernet

yield:

vr0 at pci0 dev 8 function 0: VIA VT3043 (Rhine) 10/100 Ethernet
vr0: interrupting at irq 10
vr0: Ethernet address: 00:0b:6a:06:60:eb
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface

for my ASRock M810LMR Socket A MB.

Before I was getting:

/netbsd: VIA Technologies VT82C686A SMBus Controller (miscellaneous
bridge, revision 0x40) at pci0 dev 7 function 4 not configured
/netbsd: VIA Technologies product 0x3106 (ethernet network, revision
0x8b) at pci0 dev 8 func tion 0 not configured

Sam.
sthigpen@freeshell.org

-----------------------------
SA Thigpen
KL1FE
http://sthigpen.freeshell.org
-----------------------------