I'm certainly no expert at this but I'm not quite sure how to pass the full_duplex parameter to a driver that is compiled into the kernel. You may have to modify the source for that. But if you compile the via-rhine driver as a module you can pass the parameter two ways that I know. You can interrupt the boot process with the left-shift key and after the linux: prompt add
linux: via-rhine full_duplex=1 or you can add a line in your modules.conf file like this: options via-rhine full_duplex=1 There is some minimal documentation in the source file on this. You might check the syntax I've provided for accuracy. The second method I'm sure is correct. The first one I'm not 100% sure of but it may work for both modules and compiled-in drivers. If you have more than one card installed using the same driver, you can set them all to full duplex by separating the parameters with a comma, such as full_duplex=1,0,1,0. This makes the first and third cards full duplex and the second and fourth cards not. good luck, -- tony mollica [EMAIL PROTECTED] Arcady Genkin wrote: > > I have a D-Link 530 card using a compiled-in via-rhine driver as eth0. > The card is talking to an identical card in a computer that runs > FreeBSD. I'm seeing collisions on the Linux side of the link, and am > wondering what parameters I should pass the kernel to force the card > into Full-duplex 100base mode, and how to pass those params. (I > already did that on the FreeBSD side). > Arcady Genkin > Don't read everything you believe. > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
