[realtek] 8139too and rtl8139C Too! Also! Including! ARGH!
Kirk Wolff
kirk@kirk.homeip.net
Sun Jan 27 17:47:55 2002
This is a multi-part message in MIME format.
------=_NextPart_000_004F_01C1A751.E38F6660
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
ARGH =20
!) =20
/\--- twiching eye smiley
Hello, I am sure you have had this problem over and over again, but...
I have a win2k machine and Linux machine connected to a 10/100 switch. =
I am using some kind of generic RealTek 8139C network card. The =
/proc/pci entry is as follows:
Bus 0, device 10, function 0:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev =
16).
IRQ 12.
Master Capable. Latency=3D32. Min Gnt=3D32.Max Lat=3D64.
I/O at 0xdc00 [0xdcff].
Non-prefetchable 32 bit memory at 0xd1811000 [0xd18110ff].
The MAC is 00:48:54:1A:74:F5 incase you want to actually check the =
manufacturer.
I have the following entry in my modules.conf in order to attempt to get =
the card configured. I managed to figure out this line from searching =
through the 8139too.c file in the drivers/net directory.
alias eth2 8139too
options 8139too media=3D0x0030
The media type of 0x30 should FORCE it full duplex, 100Mbps right?
OK... Well I get the following in my /var/log/messages when I connect =
it:
Jan 26 18:45:19 ip-fwd kernel: 8139too Fast Ethernet driver 0.9.22
Jan 26 18:45:19 ip-fwd kernel: PCI: Found IRQ 12 for device 00:0a.0
Jan 26 18:45:19 ip-fwd kernel: PCI: Sharing IRQ 12 with 00:07.5
Jan 26 18:45:19 ip-fwd kernel: eth2: RealTek RTL8139 Fast Ethernet at =
0xd0816000, 00:48:54:1a:74:f5, IRQ 12
Jan 26 18:45:19 ip-fwd kernel: eth2: Media type forced to Full Duplex.
Jan 26 18:45:19 ip-fwd kernel: eth2: Setting full-duplex based on =
auto-negotiated partner ability 0000.
It says that I am getting 100Mbps, FD right? Well I look at my switch, =
and the Full Duplex light doesn't come on.
=20
I should add that I get the following from an ifconfig:
[kirk@ip-fwd linux]$ /sbin/ifconfig eth2
eth2 Link encap:Ethernet HWaddr 00:48:54:1A:74:F5
inet addr:44.94.17.110 Bcast:44.94.17.111 =
Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:826806 errors:183153 dropped:6136 overruns:6780 =
frame:0
TX packets:1024648 errors:0 dropped:0 overruns:19 carrier:0
collisions:0 txqueuelen:100
Interrupt:12 Base address:0x6000
notice the huge number of errors... =20
I have tried changing the MTU to 1500 and it doesn't help
I have an identical card installed in my Win2k machine, when I tell my =
driver to auto-detect, the Full Duplex light comes on for that card.
Here's why I am whining about this, whenever I try to do transfers from =
my windows 2000 machine onto my Linux machine, I get transfer rates that =
are totally pathetic. They are on the order of 20 to 80 kbps. When I =
try to do transfers from my Linux box to my windows machine, I get =
almost full speed transfers ~on the order of 70 or 80 Mbps (But I =
haven't actually measured this, but a 200 MB file will transfer within a =
few minutes without problem)
Do you have any idea how I can get this pathetic excuse for a network =
card to work properly? Should I try to do surgery on it with a hammer, =
or am I just not finding the correct documentation on how to configure =
it. I have noticed many, many, many, many other people that are trying =
to use it on a Linux box have similar problems. I think most people =
just go and buy a different $15 network card, but I am persistent enough =
to get the stupid thing working. I have been waiting for updates to get =
it working properly. I remember about a year or so ago, whatever driver =
was in the 2.2 or 2.3 kernel seemed to work well, but I might have been =
imagining this.
I eagerly await your reply.
------=_NextPart_000_004F_01C1A751.E38F6660
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>ARGH </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>!) </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>/\--- twiching eye smiley</FONT><FONT =
face=3DArial=20
size=3D2></DIV></FONT>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Hello, I am sure you have had this =
problem over and=20
over again, but...</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have a win2k machine and =
Linux machine=20
connected to a 10/100 switch. I am using some kind of generic =
RealTek=20
8139C network card. The /proc/pci entry is as =
follows:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Bus 0, device 10, =
function =20
0:<BR> Ethernet controller: Realtek Semiconductor Co., =
Ltd.=20
RTL-8139 (rev 16).<BR> IRQ=20
12.<BR> Master Capable. =
Latency=3D32. =20
Min Gnt=3D32.Max Lat=3D64.<BR> I/O at =
0xdc00=20
[0xdcff].<BR> Non-prefetchable 32 bit =
memory at=20
0xd1811000 [0xd18110ff].<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The MAC is 00:48:54:1A:74:F5 incase you =
want to=20
actually check the manufacturer.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have the following entry in my =
modules.conf in=20
order to attempt to get the card configured. I managed to figure =
out this=20
line from searching through the 8139too.c file in the drivers/net=20
directory.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>alias eth2 8139too<BR>options 8139too=20
media=3D0x0030<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The media type of 0x30 should FORCE it =
full duplex,=20
100Mbps right?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2>OK... Well I get the following in =
my=20
/var/log/messages when I connect it:</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Jan 26 18:45:19 ip-fwd kernel: =
8139too Fast=20
Ethernet driver 0.9.22<BR>Jan 26 18:45:19 ip-fwd kernel: PCI: Found IRQ =
12 for=20
device 00:0a.0<BR>Jan 26 18:45:19 ip-fwd kernel: PCI: Sharing IRQ 12 =
with=20
00:07.5<BR>Jan 26 18:45:19 ip-fwd kernel: eth2: RealTek RTL8139 Fast =
Ethernet at=20
0xd0816000, 00:48:54:1a:74:f5, IRQ 12<BR>Jan 26 18:45:19 ip-fwd kernel: =
eth2:=20
Media type forced to Full Duplex.<BR>Jan 26 18:45:19 ip-fwd kernel: =
eth2:=20
Setting full-duplex based on auto-negotiated partner ability=20
0000.<BR></FONT></FONT><FONT face=3DArial><FONT =
size=3D2></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>It says that I am getting =
100Mbps, FD=20
right? Well I look at my switch, and the Full Duplex light doesn't =
come=20
on.</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>I should add that I get the following =
from an=20
ifconfig:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>[kirk@ip-fwd linux]$ /sbin/ifconfig=20
eth2<BR>eth2 Link encap:Ethernet =
HWaddr=20
00:48:54:1A:74:F5<BR> &nbs=
p; inet=20
addr:44.94.17.110 Bcast:44.94.17.111 =20
Mask:255.255.255.248<BR> &=
nbsp;=20
UP BROADCAST RUNNING MULTICAST MTU:1492 =20
Metric:1<BR> RX=20
packets:826806 errors:183153 dropped:6136 overruns:6780=20
frame:0<BR> TX=20
packets:1024648 errors:0 dropped:0 overruns:19=20
carrier:0<BR> =
collisions:0=20
txqueuelen:100<BR> =
Interrupt:12 Base address:0x6000<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>notice the huge number of =
errors... =20
</FONT></DIV>
<DIV> </DIV>
<DIV>I have tried changing the MTU to 1500 and it doesn't=20
help</DIV></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2>I have an identical card =
installed in my=20
Win2k machine, when I tell my driver to auto-detect, the Full Duplex =
light comes=20
on for that card.</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Here's why I am whining about =
this, whenever=20
I try to do transfers from my windows 2000 machine onto my Linux =
machine, I get=20
transfer rates that are totally pathetic. They are on the order of =
20 to=20
80 kbps. When I try to do transfers from my Linux box to my =
windows=20
machine, I get almost full speed transfers ~on the order of 70 or 80 =
Mbps (But I=20
haven't actually measured this, but a 200 MB file will transfer within a =
few=20
minutes without problem)</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Do you have any idea how I can =
get this=20
pathetic excuse for a network card to work properly? Should I try =
to do=20
surgery on it with a hammer, or am I just not finding the correct =
documentation=20
on how to configure it. I have noticed many, many, many, many =
other people=20
that are trying to use it on a Linux box have similar problems. I =
think=20
most people just go and buy a different $15 network card, but I am =
persistent=20
enough to get the stupid thing working. I have been waiting for =
updates to=20
get it working properly. I remember about a year or so ago, =
whatever=20
driver was in the 2.2 or 2.3 kernel seemed to work well, but I might =
have been=20
imagining this.</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2>I eagerly await your=20
reply.</DIV></FONT></FONT>
<DIV><FONT face=3DArial size=3D2> </DIV></FONT></DIV></BODY></HTML>
------=_NextPart_000_004F_01C1A751.E38F6660--