Re: Onboard VT6102 Rhine II ethernet broken under Linux kernel 2.4.x (was Re: Network fails with (almost) no error messages on LFS, but works on Debian)

isac <> wrote:
>[. . .]
>I had no problem using this onboard nic for transferring big files from
>the Internet either. [. . .]
>For the sake of interest, did you test your nic in a LAN instead of the
>Internet (which usually has limited bandwidth) to verify it really lived
>upto (or close enough to) its specified throughput (100Mbps)?

I haven't had a chance to do that yet (I don't yet have Samba up on
my Linux From Scratch system). When I get this up, I do plan to test it. If
it stops up, I'll keep your experience in mind.

I wonder what Windows XP is doing with this ethernet chip (at least on
your system) to make it work at full speed that the Linux kernel doesn't know
how to do?

--
Lucius Chiaraviglio
Approximate E-mail address:
To get the exact address: ^^^ ^replace this with 'r'
|||
replace this with single digit meaning the same thing
(Spambots of Doom, take that!).

Lucius Chiaraviglio wrote:
>
> I haven't had a chance to do that yet (I don't yet have Samba up on
> my Linux From Scratch system). When I get this up, I do plan to test it. If
> it stops up, I'll keep your experience in mind.
>
> I wonder what Windows XP is doing with this ethernet chip (at least on
> your system) to make it work at full speed that the Linux kernel doesn't know
> how to do?
>

I'd tend to believe there is a bug in either the mainboard layout or its
bios although a buggy rhine II driver for linux was also possible (after
all, the addon rtl8139 had no problem in my case). I had bad experience
getting round different 'funny things' found in different models of
mainboards from this manufacturer (PCCHIPS which I used to call PC
Cheap). I wouldn't call them 'bugs' because these funny things only
showed up in certain versions of linux, never with Windows (at least
during my test with 98 and XP). Apparently, the mainboard manufacturer
did their product prototype and factory tests (including the rhine II
driver), they focused on Windows only and hence managed to fix those
Windows-related bugs only. Well, as long as Microsoft remain the
dominant player in the OS market, I guess this will remain a common
practice in the PC industry?

isac