Subject: Re: Via VT6103 Ethernet supported?
To: None <current-users@netbsd.org>
From: Michael van Elst <mlelstv@serpens.de>
List: current-users
Date: 03/16/2004 12:45:36
tron@zhadum.de (Matthias Scheler) writes:

>Via Rhine network chips are - please execuse the rude word - crap.

Hi Tron,

pussyfoot# dmesg | fgrep vr0
vr0 at pci0 dev 18 function 0: VIA VT6102 (Rhine II) 10/100 Ethernet
vr0: interrupting at irq 11
vr0: Ethernet address: 00:40:63:ca:8d:9b
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface
pussyfoot% ifconfig vr0
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:40:63:ca:8d:9b
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 10.28.5.6 netmask 0xffffff00 broadcast 10.28.5.255
        inet6 fe80::240:63ff:feca:8d9b%vr0 prefixlen 64 scopeid 0x1
pussyfoot# netstat -I vr0
Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs Colls
vr0   1500  <Link>        00:40:63:ca:8d:9b  1395198     0  1922446     0     0
vr0   1500  fe80::        fe80::240:63ff:fe  1395198     0  1922446     0     0
vr0   1500  10.28.5/24    pussyfoot.local    1395198     0  1922446     0     0
pussyfoot# ping -f pepew
PING pepew.local (10.28.5.3): 56 data bytes
^C

----pepew.local PING Statistics----
36826 packets transmitted, 36826 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.150/0.164/10.566/0.116 ms
  5886.2 packets/sec sent,  5886.5 packets/sec received


pepew# dmesg | fgrep fxp0
fxp0 at pci3 dev 4 function 0: i82559 Ethernet, rev 8
fxp0: interrupting at irq 11
fxp0: Ethernet address 00:20:e0:68:5b:cd
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
pepew# ifconfig fxp0
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:20:e0:68:5b:cd
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 10.28.5.3 netmask 0xffffff00 broadcast 10.28.5.255
        inet6 fe80::220:e0ff:fe68:5bcd%fxp0 prefixlen 64 scopeid 0x1
pepew# netstat -I fxp0 
Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs Colls
fxp0  1500  <Link>        00:20:e0:68:5b:cd  7080938     0  8990619     2     0
fxp0  1500  fe80::        fe80::220:e0ff:fe  7080938     0  8990619     2     0
fxp0  1500  10.28.5/24    pepew.local        7080938     0  8990619     2     0
pepew# ping -f pussyfoot
PING pussyfoot.local (10.28.5.6): 56 data bytes
^C

----pussyfoot.local PING Statistics----
41559 packets transmitted, 41559 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.148/0.159/9.726/0.110 ms
  6090.9 packets/sec sent,  6091.0 packets/sec received


To me that does not qualify as crap.

Saying that: I did replace a vr0 card in another computer because
of many problems. The _same_ problems showed up on the EPIA-M
machine (aka pussyfoot). The problems went away after I applied
the renegotiation patch. I haven't tested the old vr0 card since
then.

I have seen reports about other problems, mostly related to PCI-DMA
on some cards that also use a VIA Rhine chip. But on the EPIA-M
board the chip seems to work perfectly.


-- 
-- 
                                Michael van Elst
Internet: mlelstv@serpens.de
                                "A potential Snark may lurk in every tree."