Re: forcing D-Link 530 into Full-Duplex
Alvin Oga <aoga@Mail.Linux-Consulting.com> writes:
> try using the RT1839 driver instead ???
Well, I know that I'm using the correct driver. My question is ``How
do I pass it parameters; and what parameters should I pass to force it
into full-duplex?''
> > 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).
> >
> > FWIW, here's the output from ifconfig and dmesg:
> >
> > ,----[ dmesg ]
> > | 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 0xe800, 00:50:ba:a9:13:f6, IRQ 10.
> > | eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 0000.
> > | PCI latency timer (CFLT) is unreasonably low at 32. Setting to 64 clocks.
> > `----
> >
> > ,----[ ifconfig ]
> > | eth0 Link encap:Ethernet HWaddr 00:50:BA:A9:13:F6
> > | inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
> > | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > | RX packets:448934 errors:0 dropped:0 overruns:0 frame:0
> > | TX packets:266302 errors:0 dropped:0 overruns:0 carrier:0
> > | collisions:7766 txqueuelen:100
> > | Interrupt:10 Base address:0xe800
> > `----
--
Arcady Genkin
Don't read everything you believe.
Reply to: