Re: [Rtl-8139] how to disable auto-negotation and set fixed speed?
On Thu, 2003-08-21 at 06:16, James wrote:
> Micha Feigin wrote:
>
> Hello Micha,
>
> This may or maynot help.
>
> I have Prostar Model 8800 with an onboard Realtek 8139. From dmesg we see:
>
> eth0: 8139too Fast Ethernet driver 0.9.18-pre4 Jeff Garzik
> <jgarzik@mandrakesoft.com>
> eth0: Linux-2.2 bug reports to Jens David <dg1kjd@afthd.tu-darmstadt.de>
> eth0: RealTek RTL8139 Fast Ethernet board found at 0xe009e000, IRQ 10
> eth0: Chip is 'RTL-8139C' - MAC address '00:90:f5:0d:30:0e'.
>
> I did the debian laptop installation, and it all worked flawlessly, with
> a 2.2.20
> Linux kernel. I'm in the process of tweaking a 2.4.21 kernel, and the
> ethernet
> works fine there. However if you are using a PCMCIA (pccard) ethernet, then
> you are will be using a different set of driver code, from what I've
> read about
> and been told. Bottom line, with both a 2.2.20 and 2.4.21 kernel, my
> 8139too driver for the Realtek worked in a vanilla installation process.
>
> James
>
I am not sure what this is in reply to, but in my case its an onboard
dud realtek. It doesn't work in 100Mbs also on M$
rtl8139_diag doesn't work to change settings on my card. ethtool does.
>
> >On Mon, 2003-08-18 at 22:36, ŁPP Rosa wrote:
> >
> >
> >>Hi all!
> >>
> >> I have written some time ago about LG LPNCII 10/100 Cardbus card on
> >>Realtek 8139 chip based (title: LG LPNCII PCMCIA (Rtl-8139)- cannot even
> >>ping; date: August 6, 2003 20:33 - I did not change the settings apart these
> >>mentioned below ("noapic" does not work either) ). I have tried several
> >>tricks and none of them works :^/. I have checked the Internet for help once
> >>more and find an idea, but I do not know how to do this - I think I need to
> >>do such a "thing":
> >>Auto-negotiation disabled, with Speed fixed at 10 mbps, full-duplex.
> >>or
> >>Auto-negotiation disabled, with Speed fixed at 10 mbps, half-duplex.
> >>
> >>Does anybody know how to do this?
> >>
> >>
> >>
> >
> >I have an onboard broken realtek, so I had to do this myself. What
> >worked for me was to use ethtool using:
> >ethtool speed 10 duplex half autoneg off
> >The package is ethtool
> >Also, doesn't help for changing the settings (should be returns errors
> >when I try) but does give good diagnostics is:
> >rtl8139-diag
> >use with the -mm option, at the end of the output it says exactly what
> >the card is advertising and whats the link status.
> >the package is nictools-pci
> >If it doesn't help, and rtl8139-diag -mm gives output then send the
> >output, maybe it will say more on the link status.
> >also, when pinging the network try to run tcpdump on the interface to
> >see if anything seems to go out, and if the card is picking up any
> >traffic on the network
> >Another thing, I don't remember how to do this, saw it somewhere, try to
> >look at the interupt count to see if the hardware is responding to
> >packets on the network.
> >
> >
> >
> >>I've got 2.4.20 kernel, I use yenta_socket and 8139too module (I also
> >>compiled my 819too_cb but nothing better with this...), laptop: HP OmniBook
> >>5700CTX (P166MMX), the other network card is Intel EtherExpress Pro ISA
> >>(10Mbps I use eepro module), cables and cards are fine, because everything
> >>works under windoze...
> >>I tried to "insmod mii" and "insmod 8139too[_cb] media=0x0001|0x0100|etc."
> >>but all I've got is:
> >>(from dmesg) for example:
> >>8139too Fast Ethernet driver 0.9.26
> >>eth0: RealTek RTL8139 Fast Ethernet at 0xc8a41000, 00:40:f4:5d:b5:fb, IRQ 10
> >>eth0: Identified 8139 chip type 'RTL-8139C'
> >> Forcing 10Mbps half|full-duplex operation.
> >>
> >>Am I doing something wrong? Is "media" parameter ok and the values?
> >>
> >>But when I try to ping the other computer (of course I did the ifconfig
> >>etc. - I think it's all right)
> >>- dmesg adds after "Forcing 10Mbps [...]"
> >>eth0: Setting full-duplex based on auto-negotiated partner ability 0000.
> >>NETDEV WATCHDOG: eth0: transmit timed out
> >>eth0: Tx queue start entry 4 dirty entry 0
> >>eth0: Tx descriptor 0 is 00002000. (queue head)
> >>eth0: Tx descriptor 1 is 00002000.
> >>eth0: Tx descriptor 2 is 00002000.
> >>eth0: Tx descriptor 3 is 00002000.
> >>eth0: Setting full-duplex based on auto-negotiated partner ability 0000.
> >>
> >>Anyone knows what to do? Any tips? ideas? feel free to wright.
> >>thanks in advance - rosa
> >>
> >>--
> >>status: a little bit sleepy...
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
Reply to: