VIA Rhine Driver Bug
Luke B. Bishop
nanosoft@nanosoft.hypermart.net
Sat May 13 11:09:58 2000
I think this is the right place to post this, please excuse me if I'm
misdirected.
I have some sort of an Acer network card with a VIA Rhine chip on it.
lspci identifies it as follows:
00:0b.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine
10/100] (rev 06)
Subsystem: Acer Incorporated [ALI]: Unknown device 0320
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 118 min, 152 max, 64 set, cache line size 08
I'm currently using it quite happily on kernel 2.3.38, which detects it
as follows (during boot):
via-rhine.c:v1.01 2/27/99 Written by Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/via-rhine.html
eth0: VIA VT3043 Rhine at 0xcc00, 00:60:67:44:55:c6, IRQ 18.
eth0: MII PHY found at address 1, status 0x782d advertising 05e1 Link
0021.
PCI latency timer (CFLT) is unreasonably low at 32. Setting to 64
clocks.
However, when I try to use any more recent kernel, I get the following
(during boot):
via-rhine.c:v1.01 2/27/99 Written by Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/via-rhine.html
eth0: VIA VT3043 Rhine at 0xc800, 00:60:67:44:55:c6, IRQ 18.
eth0: MII PHY found at address 1, status 0x7809 advertising 05e1 Link
0000.
And the following error immediately when the first network interaction
is attempted:
eth0: Oversized Ethernet frame spanned multiple buffers, entry 0x1
length 0 status 00000000!
eth0: Oversized Ethernet frame cf74a010 vs
cf74a010.
After this point, the network card is left completely non-functional.
| To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the
| body of the mail, include only the text:
| unsubscribe this-list-name youraddress@wherever.org
| You will be unsubscribed as speedily as possible.