> > Here is a patch the Urban Widmark originally came up
> > with for 2.4.17,
> > and I retrofitted to 2.4.18. I do not know if it
> > will patch vs 2.4.19-pre3:
> It does. However the problem persists.
> I changed the default debug value to 7 again.
That patch was an attempt to fix failed transmission and it contains all
sorts of junk. It worked for Andy, but not for one of the others with that
problem (and that motherboard, a Dragon+ with on-board eth chip).
You probably shouldn't use that patch at all ...
VIA has drivers for VT86c100A, the VT6102 and the VT6105, available here:
They are all obviously derived from the Donald Becker and the in-kernel
driver and are as such GPL, even if there is no mention of any license.
(someone should probably talk to VIA about that ...)
What you could do is:
a) Try those drivers instead and see if any one works better.
The 6105 driver should work with the older chips too.
b) Start moving bits of code from those drivers to the kernel driver.
The drivers have lots of "if vt3065 do this" comments, and then they
flip some bit that you couldn't have guessed needed flipping ...
I think there is very little chance of you frying your controller by
But watch out for the multiple entry points, they support 2.2 and 2.4
by having both old and new init code.
There is also the Donald Becker driver at http://www.scyld.com/
There is an explanation of common "something wicked" errors on
001a would be
0010 "Transmit FIFO underrun" = Slow or busy PCI bus
0008 "Transmit error" = Transmit aborted because of excessive collisions
So if you trust the explanations of the errors it could just be something
with cable/hub/switch or a fun PCI error. I know some have solved their
001a's by switching slots for their cards.
> The opposite side repeatedly logs:
> eth0: lost link beat
> eth0: found link beat
> eth0: autonegotiation complete: 100BaseT-FD selected
You had a "VT86c100A"? I think this is a bug in that patch where it
misdetects link changes or something. There were ideas on changed meaning
of an interrupt bit (0x0200) and the "fix" for that is probably causing
The other main idea for Andy's problem was that the initial tx threshold
should be increased. The 6105 driver has code that allows you to set the
default as a module parameter, which could be useful.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/