From lro@trf4.gov.br Fri, 3 Nov 2000 16:15:13 -0300
Date: Fri, 3 Nov 2000 16:15:13 -0300
From: Luciano Rosa lro@trf4.gov.br
Subject: [realtek] Realtek PCI Network Card
This is a multi-part message in MIME format.
------=_NextPart_000_028C_01C045B1.3F6E6020
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello!
I'm learning about Linux and I think I'm in a little trouble.
I would like to know what I have to do, step by step, to compile the =
rtl8139.c.
I have the Linux RedHat 5.0( I know there is 7.0 and my linux is older).
Thanks.
Luciano Rosa,
Tribunal Regional Federal da 4=AA Regi=E3o
Brasil/RS- Porto Alegre
------=_NextPart_000_028C_01C045B1.3F6E6020
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello!
I'm learning about Linux and I think =
I'm in a=20
little trouble.
I would like to know what I have to do, =
step by=20
step, to compile the rtl8139.c.
I have the Linux RedHat 5.0( I know =
there=20
is 7.0 and my linux is older).
Thanks.
Luciano Rosa,
Tribunal Regional =
Federal da 4=AA=20
Regi=E3o
Brasil/RS- Porto Alegre
------=_NextPart_000_028C_01C045B1.3F6E6020--
From georg.ritter@uibk.ac.at Sat, 04 Nov 2000 15:24:54 +0100
Date: Sat, 04 Nov 2000 15:24:54 +0100
From: Georg Ritter georg.ritter@uibk.ac.at
Subject: [realtek] Realtek 8139 CardBus, (Planet ENW3504FC) troubles
Hi,
all I am trying to get my Planet ENW3504 CardBus adapter working. I ran
into troubles where I'm completely stuck.
What I did:
I compiled the newest pcmcia package pcmcia-cs-3.1.21
I fetched the newest driver from Donald Becker rtl8139, compiled it.
The I modified the /etc/pcmcia/config and added the cardinfo. This seems to
work because, when I insert the card, cardmgr plots the following messages
below (I renamed the rtl8139.c into rtl8139_cb.c for the Cardbus Version)
What is missing, or what does line # 11 exaktly mean.
Greetings,
GR
1 Nov 3 14:53:14 localhost kernel: cs: cb_alloc(bus 35): vendor 0x10ec,
device 0x8138
2 Nov 3 14:53:14 localhost cardmgr[31938]: initializing socket 1
3 Nov 3 14:53:14 localhost cardmgr[31938]: socket 1: Planet ENW3504FC
4 Nov 3 14:53:14 localhost cardmgr[31938]: product info: "Realtek",
"Rtl8139"
5 Nov 3 14:53:14 localhost cardmgr[31938]: function: 6 (network)
6 Nov 3 14:53:14 localhost cardmgr[31938]: PCI id: 0x10ec, 0x8138
7 Nov 3 14:53:14 localhost cardmgr[31938]: executing: 'modprobe
cb_enabler'
8 Nov 3 14:53:14 localhost cardmgr[31938]: executing: 'modprobe
rtl8139_cb'
9 Nov 3 14:53:14 localhost kernel: rtl8139.c:v1.12 9/14/2000 Donald
Becker, becker@scyld.com.
10 Nov 3 14:53:14 localhost kernel:
http://www.scyld.com/network/rtl8139.html
11 Nov 3 14:53:15 localhost cardmgr[31938]: get dev info on socket 1
failed: Resource temporarily unavailable
lsmod:
rtl8139_cb 11912 0 (unused)
cb_enabler 2472 1 [rtl8139_cb]
vfat 9404 1 (autoclean)
fat 30688 1 (autoclean) [vfat]
ds 6248 2 [cb_enabler]
i82365 22468 2
pcmcia_core 44768 0 [cb_enabler ds i82365]
nls_cp437 3876 3 (autoclean)
ide-cd 23628 1 (autoclean)
parport_pc 7464 0 (unused)
parport 7312 0 [parport_pc]
lockd 31176 1 (autoclean)
sunrpc 52964 1 (autoclean) [lockd]
agpgart 18600 0 (unused)
cardctl ident:
Socket 1:
product info: "Realtek", "Rtl8139"
manfid: 0x0000, 0x024c
function: 6 (network)
From milan@ala.cmm.ki.si Sun, 5 Nov 2000 11:18:54 +0100
Date: Sun, 5 Nov 2000 11:18:54 +0100
From: Milan Hodoscek milan@ala.cmm.ki.si
Subject: [realtek] Compilation problem of rtl8139.c with 2.4.0-test10
Hi,
I am trying to figure out why 2.4.0 kernel (using 8139too) is twice as
slow as 2.2.14 (rtl8139) on my application running on 8 boxes in
parallel. Maybe it is the driver maybe it is the TCP in the kernel? In
order to check this I want to compile rtl8139 with 2.4.0-test10. I am
not sure if this is suppose to work at all but pci-scan compiles OK,
and rtl8139 reports these errors:
==============================================================
rtl8139.c: In function `rtl8129_open':
rtl8139.c:704: structure has no member named `tbusy'
rtl8139.c:705: structure has no member named `interrupt'
rtl8139.c:706: structure has no member named `start'
rtl8139.c: In function `rtl8129_timer':
rtl8139.c:796: structure has no member named `interrupt'
rtl8139.c:802: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_tx_timeout':
rtl8139.c:929: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_start_xmit':
rtl8139.c:960: structure has no member named `tbusy'
rtl8139.c:983: structure has no member named `tbusy'
rtl8139.c:987: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_interrupt':
rtl8139.c:1012: structure has no member named `interrupt'
rtl8139.c:1015: structure has no member named `interrupt'
rtl8139.c:1092: structure has no member named `tbusy'
rtl8139.c:1093: `NET_BH' undeclared (first use in this function)
rtl8139.c:1093: (Each undeclared identifier is reported only once
rtl8139.c:1093: for each function it appears in.)
rtl8139.c:1168: structure has no member named `interrupt'
rtl8139.c: In function `rtl8129_close':
rtl8139.c:1291: structure has no member named `start'
rtl8139.c:1292: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_get_stats':
rtl8139.c:1369: structure has no member named `start'
==============================================================
I am using gcc-2.95.2 (standard Debian gcc) and the command from the
bottom of the rtl8139.c file.
Thanks for looking at this -- Milan Hodoscek
From georg.ritter@uibk.ac.at Sun, 05 Nov 2000 16:27:09 +0100
Date: Sun, 05 Nov 2000 16:27:09 +0100
From: Georg Ritter georg.ritter@uibk.ac.at
Subject: [realtek] Compilation problem of rtl8139.c with 2.4.0-test10
Hi,
having the same troubles (same kernel, pcmcia versions). It seems that some
header file in the kernel where subject to changes.
One also has to find out, how to integrate the rtl8139.o. Is it enough to
compile and load only this module? I've seen a cb_enabler.c file in the
kernel sources so this might be there already. When trying to load (force)
and rtl8139.o compiled for kernel 2.2.16 some symbols are missing. The doc
in the kernel sources say that the pcmcia interface was wrapped somehow, so
that there is no change visible to the drivers...
I also tried to compare to the driverfiles (3c5xxx.c) which are contained
in the distri (2.4.0-test10) but I did not yet found out how to adapt the
rtl8139.c...
Ideas welcome ;-).
Greetings,
Georg Ritter
From grune@embl-grenoble.fr Mon, 6 Nov 2000 11:03:42 +0100 (CET)
Date: Mon, 6 Nov 2000 11:03:42 +0100 (CET)
From: Tim Gruene grune@embl-grenoble.fr
Subject: [realtek] Compilation problem of rtl8139.c with 2.4.0-test10
Hi!
The struct member 'tbusy' is defined in in kernel
2.2.xx but no longer in 2.4.xx.
I am not a programmer and I don't know where to get information about the
kernel header files in order to port rtl8139.c to 2.4.xx, but I'd asked
Donald Becker whether he was planning to do so and he'd replied 'yes' once
there is a new kernel 2.4.xx- that was when 2.4.0-test9 was out, so he
seems to want to wait for a really stable version.
Cheers, Tim
Tim Gruene
EMBL Grenoble Outstation
6 rue Jules Horowitz
BP 156
F - 38042 Grenoble Cedex 9
--
grune@embl-grenoble.fr
Phone: +33 04 76 20 75 75
From georg.ritter@uibk.ac.at Mon, 06 Nov 2000 11:34:10 +0100
Date: Mon, 06 Nov 2000 11:34:10 +0100
From: Georg Ritter georg.ritter@uibk.ac.at
Subject: [realtek] Rtl8139 & 2.4.0-test10
Hi,
thanks for the hint! I was confused with the menu option "Pocket Adapters"
in the kernel config. I did not have the idea, that it could work with the
'normal' drivers.
So I compiled in the rtl8139too and have attached the messages I receive
when inserting the card, because smthg. fails
Greetings,
Georg Ritter
in /var/log/messages (RH7.0)
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfd83e, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 2: assuming transparent
PCI: Using IRQ router VIA [1106/0596] at 00:07.0
PCI: Found IRQ 5 for device 00:07.5
PCI: The same IRQ used for device 01:00.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
...
[drm] Initialized tdfx 1.0.0 20000928 on minor 63
Linux PCMCIA Card Services 3.1.22
options: [pci] [cardbus] [pm]
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kmem_create: Forcing size word alignment - nfs_fh
Yenta IRQ list 0808, PCI irq10
Socket status: 30000827
Yenta IRQ list 0808, PCI irq10
Socket status: 30000827
...
cs: cb_alloc(bus 2): vendor 0x10ec, device 0x8138
PCI: Failed to allocate resource 0 for PCI device 10ec:8138
PCI: Enabling device 02:00.0 (0000 -> 0003)
8139too Fast Ethernet driver 0.9.11 loaded
8139too: Invalid PCI region size(s), aborting
and the output of /proc/pci with the inserted card:
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies, Inc. VT8501 [Apollo MVP4] (rev 3).
Prefetchable 32 bit memory at 0xfd000000 [0xfdffffff].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT8501 [Apollo MVP4 AGP] (rev 0).
Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev
25).
Bus 0, device 7, function 1:
IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 6).
Master Capable. Latency=64.
I/O at 0x1000 [0x100f].
Bus 0, device 7, function 2:
USB Controller: VIA Technologies, Inc. UHCI USB (rev 10).
Master Capable. Latency=64.
I/O at 0x1020 [0x103f].
Bus 0, device 7, function 4:
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
32).
Bus 0, device 7, function 5:
Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
Controller (rev 33).
IRQ 5.
I/O at 0x1400 [0x14ff].
I/O at 0x1014 [0x1017].
I/O at 0x1010 [0x1013].
Bus 0, device 10, function 0:
CardBus bridge: O2 Micro, Inc. 6832 (rev 52).
IRQ 10.
Master Capable. Latency=168. Max Lat=5.
Non-prefetchable 32 bit memory at 0x10000000 [0x10000fff].
Bus 0, device 10, function 1:
CardBus bridge: O2 Micro, Inc. 6832 (#2) (rev 52).
IRQ 10.
Master Capable. Latency=168. Max Lat=5.
Non-prefetchable 32 bit memory at 0x10001000 [0x10001fff].
Bus 1, device 0, function 0:
VGA compatible controller: Trident Microsystems CyberBlade/i7d (rev
92).
IRQ 5.
Master Capable. Latency=64.
Non-prefetchable 32 bit memory at 0xfc000000 [0xfc7fffff].
Non-prefetchable 32 bit memory at 0xfb800000 [0xfb81ffff].
Non-prefetchable 32 bit memory at 0xfb000000 [0xfb7fffff].
Bus 2, device 0, function 0:
Ethernet controller: PCI device 10ec:8138 (rev 16).
IRQ 10.
Master Capable. No bursts. Min Gnt=32.Max Lat=64.
I/O at 0x1000 [0xfff].
Non-prefetchable 32 bit memory at 0x10800000 [0x108001ff].
From jgarzik@mandrakesoft.com Mon, 06 Nov 2000 05:43:34 -0500
Date: Mon, 06 Nov 2000 05:43:34 -0500
From: Jeff Garzik jgarzik@mandrakesoft.com
Subject: [realtek] Rtl8139 & 2.4.0-test10
This is a multi-part message in MIME format.
--------------8A627260B79BBD0D5FAB2E75
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Georg Ritter wrote:
> PCI: Failed to allocate resource 0 for PCI device 10ec:8138
> PCI: Enabling device 02:00.0 (0000 -> 0003)
> 8139too Fast Ethernet driver 0.9.11 loaded
> 8139too: Invalid PCI region size(s), aborting
This is a problem with the kernel's CardBus hotplug code... See "failed
to allocate resource 0" ?
In any case, does the attached patch improve things for you?
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
--------------8A627260B79BBD0D5FAB2E75
Content-Type: text/plain; charset=us-ascii;
name="8139too.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="8139too.patch"
--- 8139too.c.orig Mon Nov 6 05:42:05 2000
+++ 8139too.c Mon Nov 6 05:42:52 2000
@@ -650,6 +650,8 @@
}
tp = dev->priv;
+ pci_enable_device (pdev);
+
pio_start = pci_resource_start (pdev, 0);
pio_end = pci_resource_end (pdev, 0);
pio_flags = pci_resource_flags (pdev, 0);
--------------8A627260B79BBD0D5FAB2E75--
From VW@i405.com Mon, 6 Nov 2000 07:02:23 -0800
Date: Mon, 6 Nov 2000 07:02:23 -0800
From: Stephen Gutknecht (vw) VW@i405.com
Subject: [realtek] OT: realtek 8139c cards from Compgeeks for $10 each
A little off topic, but I thought of possible interest to this list.
I just ordered a couple RT 8139c cards from Compugeeks for $10 each. They
are Encore ENL832-TX and the Compgeeks web page says 8139a/b/c, but both of
mine came with 8139c chips (I suspect all of them are 8139c, just that
Compgeeks copies generic literature for their web site.) $10 for a new card
in box is a good deal, I got 3 of them.
http://www.compgeeks.com/details.asp?invtid=205-1832
I have ordered before from them. Their shipping is high, they seem to
charge $7 for UPS ground even if one item. The good news is that if you
order 3 or 5 items the shipping is still $7 for UPS ground. Suggestions for
other purchases: They have 50 pack 80min 12x CD-R disks for $9.50 (search
"80 min"). Just take care that they do sell used stuff, read the
descriptions.
Not affiliated with them, just a customer...
Stephen Gutknecht
Renton, Washington
From csyap@starnet.gov.sg Sat, 11 Nov 2000 03:22:48 +0800
Date: Sat, 11 Nov 2000 03:22:48 +0800
From: csyap@starnet.gov.sg csyap@starnet.gov.sg
Subject: [realtek] patching 8139too to use in 2.2x kernel
hi,
i've downloaded the following 3 files and successfully compiled 8139too.c
to 8139too.o(for kernel 2.4x) from 8139too-0.9.10.tar.gz.
pls kindly advise the procedure to apply the patch for 2.2.16-22 kernel.
what command must i execute pls. where must each file be kept?
8139too-0.9.10.diff.gz
8139too-0.9.10.tar.gz
patch-8139too-0.9.10-2.2.gz
thanks for your help
From csyap@starnet.gov.sg Sat, 11 Nov 2000 04:56:14 +0800
Date: Sat, 11 Nov 2000 04:56:14 +0800
From: csyap@starnet.gov.sg csyap@starnet.gov.sg
Subject: [realtek] which file to patch?
hi, i'm trying to patch the 8319too driver to be used for kernel 2.2.x.
after executing the following patch command, i'm prompted for a file to
patch. the question is what filename should i input and maybe secound?
[root@sharp too]# patch -sp1 < /root/too/patch-8139too-0.9.10-2.2
The text leading up to this was:
--------------------------
|diff -u -r -P -p linux-2.2.17/drivers/net/Config.in
linux-2.2.17-8139too/drivers/net/Config.in
|--- linux-2.2.17/drivers/net/Config.in Sun Sep 10 16:37:49 2000
|+++ linux-2.2.17-8139too/drivers/net/Config.in Wed Sep 27 21:54:14 2000
--------------------------
File to patch:
thanks for your help.
From jens_kriebitzsch@hotmail.com Sun, 12 Nov 2000 22:45:59 GMT
Date: Sun, 12 Nov 2000 22:45:59 GMT
From: Jens Kriebitzsch jens_kriebitzsch@hotmail.com
Subject: [realtek] via-rhine kills rtl8139
Hello,
I am happily using a SN5100TX PCI Fast Ethernet Card on PCI slot 2, with IRQ
10 with a via-rhine driver.
I am also happily using a Realtek 8139 based Ethernet Card on PCI slot 1,
with IRQ 10 as well.
Everything works nicely as long as I use only one of the two slots.
BUT: when I use my Realtek card on PCI slot 1, whith IRQ 10, and I plug the
via-rhine card into the _disabled_ PCI slot 2, with IRQ 11 assigned to it,
the Realtek card will not work any longer (that is I cannot ping my
ADSL-"modem" anymore, which I can when the via-rhine card is removed.
Although this is probably no driver problem, I do hope that some of you are
interested by this compatibility (?) problem, as I didn't find any mailing
list coming closer to it.
Any ideas on this one? Thank you for your help!
jens_kriebitzsch@hotmail.com
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
From VW@i405.com Sun, 12 Nov 2000 18:34:01 -0800
Date: Sun, 12 Nov 2000 18:34:01 -0800
From: Stephen Gutknecht (vw) VW@i405.com
Subject: [realtek] Asus CUSL2 (i815 chipset) mainboard and 8139c cards
Howdy,
I have two different Realtek RTL8139 cards to work with. One is a SMC
1211TX with unknown revision, the other is a Encore ENL832-TX with RTL8139c
chip on it.
My mainboard is an Asus CUSL2 - i815 chipset, I put the most recent 1004.03
(beta) BIOS on it.
My problem? I can't get the 8139 cards to work. I started out with a clean
(format) install of Redhat 7.0. This is kernel 2.2.16-22 -- the included
rtl8139.o driver didn't want to work. Reading about how this driver is out
of date, I next took on the task of building the 2.2.17 kernel. Same
problem. For fun, I even updated my modutils package (.19-2.rpm) and built
myself a 2.4.0-test10 kernel :) The 2.4.0-test10 kernel is my intended
platform.
The 2.4.0-test10 uses 8139too.o driver. That wouldn't work either. It
suggested "try pci=biosirq" -- is this a parameter you pass it?
I'm new to Linux, but not new to hardware. I suspect the problem lies in
how the Asus CUSL2 mainboard is assigning resources to the card. I've tried
every setting I can to "disable Plug and play" -- but this board doesn't
seem to have any option for that. Disabling power management is the best I
can do (it is an ACPI BIOS, the board has only been on the market for a few
months).
What information do I need to track this down? Anyone else using a i815
chipset board?
P.S. I built my system LILO config so I can select the kernel at system
start... I have the original 2.2.16-22 that came with Redhat 7.0, my own
2.2.17, and my own 2.4.0-test10 -- I'm willing to test different drivers or
do whatever will help. Just make sure you give step-by-step instructions on
any driver compiles :)
Thanks.
Stephen Gutknecht
Renton, Washington
-----Original Message-----
From: Stephen Gutknecht (vw) [mailto:VW@i405.com]
Sent: Monday, November 06, 2000 7:02 AM
To: realtek@scyld.com
Subject: [realtek] OT: realtek 8139c cards from Compgeeks for $10 each
A little off topic, but I thought of possible interest to this list.
I just ordered a couple RT 8139c cards from Compugeeks for $10 each. They
are Encore ENL832-TX and the Compgeeks web page says 8139a/b/c, but both of
mine came with 8139c chips (I suspect all of them are 8139c, just that
Compgeeks copies generic literature for their web site.) $10 for a new card
in box is a good deal, I got 3 of them.
http://www.compgeeks.com/details.asp?invtid=205-1832
I have ordered before from them. Their shipping is high, they seem to
charge $7 for UPS ground even if one item. The good news is that if you
order 3 or 5 items the shipping is still $7 for UPS ground. Suggestions for
other purchases: They have 50 pack 80min 12x CD-R disks for $9.50 (search
"80 min"). Just take care that they do sell used stuff, read the
descriptions.
Not affiliated with them, just a customer...
Stephen Gutknecht
Renton, Washington
_______________________________________________
realtek mailing list
realtek@scyld.com
http://www.scyld.com/mailman/listinfo/realtek
From VW@i405.com Sun, 12 Nov 2000 18:48:58 -0800
Date: Sun, 12 Nov 2000 18:48:58 -0800
From: Stephen Gutknecht (vw) VW@i405.com
Subject: [realtek] patching 8139too to use in 2.2x kernel
Did anyone ever answer this question?
Csyap: do you mind detailing the _exact steps_ of you compiled the 8139too.c
driver? I'm just learning myself and it would be great if we could share
notes.
I'm on Redhat 7.0, I upgraded modutils to 2.3.19-2 using RPM and compiled a
2.4.0-test10 kernel (which I can boot with fine - but no network, using a
Asus CUSL2 i815 main board).
Stephen Gutknecht
Renton, Washington
-----Original Message-----
From: csyap@starnet.gov.sg [mailto:csyap@starnet.gov.sg]
Sent: Friday, November 10, 2000 11:23 AM
To: realtek@scyld.com
Subject: [realtek] patching 8139too to use in 2.2x kernel
hi,
i've downloaded the following 3 files and successfully compiled 8139too.c
to 8139too.o(for kernel 2.4x) from 8139too-0.9.10.tar.gz.
pls kindly advise the procedure to apply the patch for 2.2.16-22 kernel.
what command must i execute pls. where must each file be kept?
8139too-0.9.10.diff.gz
8139too-0.9.10.tar.gz
patch-8139too-0.9.10-2.2.gz
thanks for your help
From VW@i405.com Sun, 12 Nov 2000 21:12:09 -0800
Date: Sun, 12 Nov 2000 21:12:09 -0800
From: Stephen Gutknecht (vw) VW@i405.com
Subject: [realtek] Asus CUSL2 (i815 chipset) mainboard and 8139c cards
Sorry about this.
On the CUSL2 the "Plug and Play OS: Yes/No" option is on the Boot menu. I
looked everywhere else but there :) As soon as I changed it the devices
were no longer being assigned IRQ-0 (OS-assigned IRQ).
Stephen
-----Original Message-----
From: Stephen Gutknecht (vw) [mailto:VW@i405.com]
Sent: Sunday, November 12, 2000 6:34 PM
To: realtek@scyld.com
Subject: [realtek] Asus CUSL2 (i815 chipset) mainboard and 8139c cards
[snip]
My mainboard is an Asus CUSL2 - i815 chipset, I put the most recent 1004.03
(beta) BIOS on it.
From csyap@starnet.gov.sg Mon, 13 Nov 2000 19:15:06 +0800
Date: Mon, 13 Nov 2000 19:15:06 +0800
From: Corisen csyap@starnet.gov.sg
Subject: [realtek] patching 8139too to use in 2.2x kernel
nope. this question was not answered since it was posted :(
i'm runinng RedHat7, kernel 2.2.16 on a Sharp Actius A250 notebook. The
notebook has a onboard Realtek NIC that is about to drive me crazy...
The original Realtek NIC driver (rtl8139.o) that came with RH7 *seems* to
work initially. I was able to get a dynamic IP and was able to ping upon
startup. however, after sometime, the connection dies off by itself. though
ifconfig still shows a IP but I was unable to ping anymore.
The second scenario that is guaranteed to kill the network connection is by
downloading a reasonably large file using ftp command. Whenever I try to
connect to my ftp server on any ftp server to download files, the download
process will stop after 1sec and the connection is lost.
Below describe the steps I took to compile the new drivers (but
unsuccessful):
1. download the source code from ftp://ftp.scyld.com/pub/network/rtl8139.c
2. gunzip to /root/rtl8139 (gcc version 2.96)
3. download pci-scan.c, pci-scan.h, and kern_compat.h to /root/rtl8139
4. gcc -DMODULE -D__KERNEL__ -O6 -c rtl8139.c
Below is a log of error messages reported by the gcc.
rtl8139.c: In function `rtl8129_open':
rtl8139.c:704: structure has no member named `tbusy'
rtl8139.c:705: structure has no member named `interrupt'
rtl8139.c:706: structure has no member named `start'
rtl8139.c: In function `rtl8129_timer':
rtl8139.c:796: structure has no member named `interrupt'
rtl8139.c:802: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_tx_timeout':
rtl8139.c:929: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_start_xmit':
rtl8139.c:960: structure has no member named `tbusy'
rtl8139.c:983: structure has no member named `tbusy'
rtl8139.c:987: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_interrupt':
rtl8139.c:1012: structure has no member named `interrupt'
rtl8139.c:1015: structure has no member named `interrupt'
rtl8139.c:1092: structure has no member named `tbusy'
rtl8139.c:1093: `NET_BH' undeclared (first use in this function)
rtl8139.c:1093: (Each undeclared identifier is reported only once
rtl8139.c:1093: for each function it appears in.)
rtl8139.c:1168: structure has no member named `interrupt'
rtl8139.c: In function `rtl8129_close':
rtl8139.c:1291: structure has no member named `start'
rtl8139.c:1292: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_get_stats':
rtl8139.c:1369: structure has no member named `start'
I'm really having a difficulty time compiling the new drivers for Realtek
8139.
Pls kindly advise where I have gone wrong and the correct procedure to
compile and install the drivers.
Any help would be greatly appreciated.
Thank you so much.
----- Original Message -----
From: Stephen Gutknecht (vw)
To: ;
Sent: Monday, November 13, 2000 10:48 AM
Subject: RE: [realtek] patching 8139too to use in 2.2x kernel
> Did anyone ever answer this question?
>
> Csyap: do you mind detailing the _exact steps_ of you compiled the
8139too.c
> driver? I'm just learning myself and it would be great if we could share
> notes.
>
> I'm on Redhat 7.0, I upgraded modutils to 2.3.19-2 using RPM and compiled
a
> 2.4.0-test10 kernel (which I can boot with fine - but no network, using a
> Asus CUSL2 i815 main board).
>
> Stephen Gutknecht
> Renton, Washington
>
>
> -----Original Message-----
> From: csyap@starnet.gov.sg [mailto:csyap@starnet.gov.sg]
> Sent: Friday, November 10, 2000 11:23 AM
> To: realtek@scyld.com
> Subject: [realtek] patching 8139too to use in 2.2x kernel
>
>
> hi,
>
> i've downloaded the following 3 files and successfully compiled 8139too.c
> to 8139too.o(for kernel 2.4x) from 8139too-0.9.10.tar.gz.
>
> pls kindly advise the procedure to apply the patch for 2.2.16-22 kernel.
> what command must i execute pls. where must each file be kept?
>
> 8139too-0.9.10.diff.gz
>
> 8139too-0.9.10.tar.gz
> patch-8139too-0.9.10-2.2.gz
>
> thanks for your help
From benjaminlee@consultant.com Tue, 14 Nov 2000 00:14:19 +1100
Date: Tue, 14 Nov 2000 00:14:19 +1100
From: Benjamin Lee benjaminlee@consultant.com
Subject: [realtek] patching 8139too to use in 2.2x kernel
A very quick reply ...
Note:
- RH 7.0 uses a 'broken' kernel source
- It also has developmental gcc and all kinds of nasty stuff. IMHO.
My solution for a newbie (?):
- Downgrade to RH6.2
- Go to http://www.scyld.com/network/updates.html
* Following SRPM compile instructions.
* Install SRPM
Other solution:
- Get vanilla 2.2.x kernel source
- Compile
- Get new drivers.
* Compile, etc.
> I'm really having a difficulty time compiling the new drivers for Realtek
> 8139.
>
> Pls kindly advise where I have gone wrong and the correct procedure to
> compile and install the drivers.
>
> Any help would be greatly appreciated.
>
> Thank you so much.
--
B. http://makelinux.org/ "Always real." http://realthought.net/
__________________________________________________________________________
The root of all superstition is that men observe when a thing hits,
but not when it misses.
-- Francis Bacon
From seanm@netwinder.org Mon, 13 Nov 2000 10:29:34 -0500 (EST)
Date: Mon, 13 Nov 2000 10:29:34 -0500 (EST)
From: Sean MacLennan seanm@netwinder.org
Subject: [realtek] patching 8139too to use in 2.2x kernel
You want to use the 8139too driver that came with 2.4.0-test10. It has
some important fixes.
Just make sure you selected the 8139 driver at config time as a module
and `make modules'.
Sean
--
From csyap@starnet.gov.sg Mon, 13 Nov 2000 23:55:10 +0800
Date: Mon, 13 Nov 2000 23:55:10 +0800
From: Corisen csyap@starnet.gov.sg
Subject: [realtek] patching 8139too to use in 2.2x kernel
i've tried compiling the 2.4.0-test10 kernel a few times. the same problem
persist. i'm able to get an IP but upon downloading using FTP, the
connection will die. i've used both gcc (v2.96) and kgcc (v2.91.66 as
recommded but the readme) and gcc 2.95.2 but the compilied driver still
gives the same problem. however, there was one time when i managed to
compile the kernel and driver and get it working with ftp but unfortunately,
i overwrote it :( and subsequent compilation did not produce a driver
working with ftp.
also, different version of complier produce different size of compiled
drivers.
may i know if there's a recommeded version of gcc for kernel/driver
compilation?
would really appreciate if someone send me a latest version of compiled
rtl8139.o (for 2.2.x) and 8139too.o (for both 2.2.x and 2.4) for testing on
my system.
thank you.
----- Original Message -----
From: Sean MacLennan
To: Stephen Gutknecht (vw)
Cc: ;
Sent: Monday, November 13, 2000 11:29 PM
Subject: RE: [realtek] patching 8139too to use in 2.2x kernel
>
> You want to use the 8139too driver that came with 2.4.0-test10. It has
> some important fixes.
>
> Just make sure you selected the 8139 driver at config time as a module
> and `make modules'.
>
> Sean
> --
>
>
> _______________________________________________
> realtek mailing list
> realtek@scyld.com
> http://www.scyld.com/mailman/listinfo/realtek
>
From csyap@starnet.gov.sg Tue, 14 Nov 2000 15:20:37 +0800
Date: Tue, 14 Nov 2000 15:20:37 +0800
From: Corisen csyap@starnet.gov.sg
Subject: [realtek] patching 8139too to use in 2.2x kernel
thanks. your file worked on my system. i've also managed to compile a
version that worked on my system. on RH7, i have to use kgcc to compile my
kernel/modules.
however, that's a weird behaviour on my system.
i'm able to download files using the command line ftp. but if i used the
gFTP or Netscape to download file, it will always stall. this is true
especially for larger files (>20MB) and whenever the connection speed is
fast >100K/sec.
sean, can you help me verify by connecting to a local site (LAN) to download
some big files?
i would to find out if the problem lies on the onboard Realtek NIC on my
Sharp Actius 250 notebook, compilation, or etc...
btw, has anyone experience such scenario before? any suggestions on how i
can "stablise" my connection?
thanks.
----- Original Message -----
From: Sean MacLennan
To: Corisen
Sent: Tuesday, November 14, 2000 12:28 AM
Subject: Re: [realtek] patching 8139too to use in 2.2x kernel
> Corisen writes:
> > would really appreciate if someone send me a latest version of compiled
> > rtl8139.o (for 2.2.x) and 8139too.o (for both 2.2.x and 2.4) for
testing on
> > my system.
>
> I only use the 8139too driver. Here is the version from 2.4.0-test10.
>
> Enjoy,
> Sean
>
>
----------------------------------------------------------------------------
----
>
>
> --
>
From mmendez@fcaglp.unlp.edu.ar Wed, 15 Nov 2000 19:32:57 -0300 (ARST)
Date: Wed, 15 Nov 2000 19:32:57 -0300 (ARST)
From: Mariano Mendez mmendez@fcaglp.unlp.edu.ar
Subject: [realtek] Can't load RTL8139.o module Rhat 7.0
Hi:
I have a PCMCIA Ethernet Card L100C32 2 10/100 Mbps 32 bits from
Dynalink. I'm trying to make it work on a Sony VAIO SR1K running
Redhat 7.0, kernel 2.2.16-22 using pcmcia-cs-3.1.22.
I'm unable to make the card work (the card does not seem to be
broken; it works in Windows 2000). I mailed the company, and
they say that the card is a Realtek chipset base card with the
card ID and the settings activated into the scripts, and that I
should download the latest driver from the net.
I have rtl8139.o from pcmcia-cs, which I guess is what I need.
After boot up I tried ifconfig, and I only get the output for
'lo'. If I try ifconfig eth0 I get 'Device not found'.
I first tried without defining the module in /etc/modules.conf.
Later on I added "alias eth0 rtl8139", but nothing changed.
lsmod shows me this:
Module Size Used by
nfs 28768 1 (autoclean)
ds 6248 1
i82365 22512 1
pcmcia_core 44768 0 [ds i82365]
lockd 31176 1 (autoclean) [nfs]
sunrpc 52964 1 (autoclean) [nfs lockd]
agpgart 18600 0 (unused)
nls_cp437 3876 4 (autoclean)
vfat 9404 2 (autoclean)
fat 30688 2 (autoclean) [vfat]
When I try to load the module manually using modprobe I get:
[root@pan /root]# modprobe rtl8139
/lib/modules/2.2.16-22/net/rtl8139.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters
/lib/modules/2.2.16-22/net/rtl8139.o: insmod /lib/modules/2.2.16-22/net/rtl8139.
o failed
/lib/modules/2.2.16-22/net/rtl8139.o: insmod rtl8139 failed
>From /proc/pci I see:
PCI devices found:
Bus 32, device 0, function 0:
Ethernet controller: Realtek Unknown device (rev 16).
Vendor id=10ec. Device id=8138.
Medium devsel. Fast back-to-back capable.
I would appreciate if any of you can help me on this one. I tried
several HOWTO's, mailing lists, etc., but so far I could not find
the solution.
Below there are a couple of logs that I hope could be useful.
Thanks!!
-Mariano.
This is from /var/log/messages when I insert or eject the card:
Nov 15 18:19:25 pan kernel: cs: cb_free(bus 32)
Nov 15 18:19:28 pan cardmgr[443]: initializing socket 0
Nov 15 18:19:28 pan cardmgr[443]: unsupported card in socket 0
Nov 15 18:19:28 pan kernel: cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8138
Nov 15 18:19:29 pan cardmgr[443]: product info: "PCMCIA", "CardBus Ethernet 10
/100 (R5)"
Nov 15 18:19:29 pan cardmgr[443]: manfid: 0x0260, 0x0235 function: 6 (network
)
Nov 15 18:19:29 pan cardmgr[443]: PCI id: 0x10ec, 0x8138
Nov 15 18:20:00 pan CROND[721]: (root) CMD ( /sbin/rmmod -as)
This from dmesg:
Linux version 2.2.16-22 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Aug 22 16:49:06 EDT 2000
Detected 494276 kHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 986.32 BogoMIPS
Memory: 62872k/65472k available (1048k kernel code, 412k reserved, 1076k data, 64k init, 0k bigmem)
Dentry hash table entries: 262144 (order 9, 2048k)
Buffer cache hash table entries: 65536 (order 6, 256k)
Page cache hash table entries: 16384 (order 4, 64k)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium III (Coppermine) stepping 03
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xfd9be
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Enabling memory for device 00:40
PCI: Enabling I/O for device 00:48
PCI: Enabling I/O for device 00:50
PCI: Enabling memory for device 00:50
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 65536 bhash 65536)
Linux IP multicast router 0.06 plus PIM-SM
Initializing RT netlink socket
Starting kswapd v 1.5
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.13)
Real Time Clock Driver v1.09
RAM disk driver initialized: 16 RAM disks of 4096K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:pio, hdd:pio
hda: IBM-DARA-209000, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: IBM-DARA-209000, 8623MB w/418kB Cache, CHS=1099/255/63
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
pII_mmx : 1099.566 MB/sec
p5_mmx : 1154.811 MB/sec
8regs : 848.868 MB/sec
32regs : 475.869 MB/sec
using fastest function: p5_mmx (1154.811 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 >
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 64k freed
Adding Swap: 176672k swap-space (priority -1)
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 27M
agpgart: Detected Intel 440BX chipset
agpgart: AGP aperture is 16M @ 0x40000000
Linux PCMCIA Card Services 3.1.22
kernel build: 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT 2000
options: [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xfdf60
Intel PCIC probe:
Ricoh RL5C475 rev 80 PCI-to-CardBus at slot 00:0c, mem 0x68000000
host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 32/34]
ISA irqs (default) = 3,4,5,7,10,11,12,15 PCI status changes
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x220-0x22f 0x330-0x337 0x370-0x377 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8138
--
Mariano Mendez
mmendez@fcaglp.unlp.edu.ar
From becker@scyld.com Thu, 16 Nov 2000 00:04:38 -0500 (EST)
Date: Thu, 16 Nov 2000 00:04:38 -0500 (EST)
From: Donald Becker becker@scyld.com
Subject: [realtek] Can't load RTL8139.o module Rhat 7.0
On Wed, 15 Nov 2000, Mariano Mendez wrote:
> I have a PCMCIA Ethernet Card L100C32 2 10/100 Mbps 32 bits from
> Dynalink. I'm trying to make it work on a Sony VAIO SR1K running
> Redhat 7.0, kernel 2.2.16-22 using pcmcia-cs-3.1.22.
[[ Various failed approaches deleted. ]]
> Nov 15 18:19:28 pan cardmgr[443]: unsupported card in socket 0
> Nov 15 18:19:28 pan kernel: cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8138
> Nov 15 18:19:29 pan cardmgr[443]: product info: "PCMCIA", "CardBus Ethernet 10
> /100 (R5)"
> Nov 15 18:19:29 pan cardmgr[443]: manfid: 0x0260, 0x0235 function: 6 (network
Update your driver using the directions in
http://www.scyld.com/network/updates.html
This is supported by the following lines:
________________
# The CardBus version of the RealTek rtl8139b.
device "realtek" class "network"
module "cb_enabler", "pci-scan", "cb_shim", "rtl8139"
card "Argosy EN235 RTL8139B" manfid 0x0260, 0x0235 bind "realtek"
________________
This card is supported out of the box by the Scyld Beowulf distribution.
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
From becker@scyld.com Thu, 16 Nov 2000 15:28:16 -0500 (EST)
Date: Thu, 16 Nov 2000 15:28:16 -0500 (EST)
From: Donald Becker becker@scyld.com
Subject: [realtek] via-rhine kills rtl8139
On Sun, 12 Nov 2000, Jens Kriebitzsch wrote:
> I am happily using a SN5100TX PCI Fast Ethernet Card on PCI slot 2, with IRQ
> 10 with a via-rhine driver.
> I am also happily using a Realtek 8139 based Ethernet Card on PCI slot 1,
> with IRQ 10 as well.
> Everything works nicely as long as I use only one of the two slots.
> BUT: when I use my Realtek card on PCI slot 1, whith IRQ 10, and I plug the
> via-rhine card into the _disabled_ PCI slot 2, with IRQ 11 assigned to it,
> the Realtek card will not work any longer (that is I cannot ping my
> ADSL-"modem" anymore, which I can when the via-rhine card is removed.
They are likely sharing bus-master control lines.
Read your motherboard manual very carefully.
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
From c.p.botha@its.tudelft.nl Mon, 27 Nov 2000 16:36:07 +0100
Date: Mon, 27 Nov 2000 16:36:07 +0100
From: Charl P. Botha c.p.botha@its.tudelft.nl
Subject: [realtek] transmit timeout revisited
--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Dear Realtek-People,
Has anyone really solved the transmit timeout problem yet? I've searched
the web far and wide, and have only found postings with the problem, but
none with solutions.
The attached kern.log shows the specific transmit timeout error.
This is on a dual 933MHz PIII system with Via Apollo Pro133A chipset,
running kernel 2.2.17 with the very latest rtl8139.c driver (v1.12). The
card is an SMC EZ Card (SMC1211TX/WL). 2.4.0 is not an option (I make heavy
use of nvidia 3d graphics, and on this machine 2.4.0 and nvidia drivers
aren't very happy together, in spite of patches).
I've also attached dumps of /proc/pci and /proc/interrupts. During these
timeouts (which regularly occur if there's network activity) ALL network
activity stops for a while. Things usually recover by themselves.
Any information on this would be greatly appreciated!
Thanks,
Charl
--
charl p. botha | computer graphics and cad/cam
http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="kern.log"
Nov 27 08:23:01 dutidad kernel: VFS: Disk change detected on device sr(11,0)
Nov 27 08:23:04 dutidad kernel: ISO 9660 Extensions: Microsoft Joliet Level 1
Nov 27 08:23:04 dutidad kernel: ISOFS: changing to secondary root
Nov 27 08:27:44 dutidad kernel: VFS: Disk change detected on device sr(11,0)
Nov 27 08:27:44 dutidad kernel: ISO 9660 Extensions: Microsoft Joliet Level 1
Nov 27 08:27:44 dutidad kernel: ISO 9660 Extensions: RRIP_1991A
Nov 27 08:30:17 dutidad kernel: eth0: Transmit timeout, status 0d 0000 media 18.
Nov 27 08:30:17 dutidad kernel: eth0: Tx queue start entry 301869 dirty entry 301865, full.
Nov 27 08:30:17 dutidad kernel: eth0: Tx descriptor 0 is 400843a6.
Nov 27 08:30:17 dutidad kernel: eth0: Tx descriptor 1 is 100805ea. (queue head)
Nov 27 08:30:17 dutidad kernel: eth0: Tx descriptor 2 is 000805ea.
Nov 27 08:30:17 dutidad kernel: eth0: Tx descriptor 3 is 100805ea.
Nov 27 08:30:17 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 08:35:17 dutidad kernel: eth0: Transmit timeout, status 0d 0000 media 18.
Nov 27 08:35:17 dutidad kernel: eth0: Tx queue start entry 99800 dirty entry 99796, full.
Nov 27 08:35:17 dutidad kernel: eth0: Tx descriptor 0 is 000805ea. (queue head)
Nov 27 08:35:17 dutidad kernel: eth0: Tx descriptor 1 is 000805ea.
Nov 27 08:35:17 dutidad kernel: eth0: Tx descriptor 2 is 100805ea.
Nov 27 08:35:17 dutidad kernel: eth0: Tx descriptor 3 is 400845ea.
Nov 27 08:35:17 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 10:15:27 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 10:15:27 dutidad kernel: eth0: Tx queue start entry 343582 dirty entry 343578, full.
Nov 27 10:15:27 dutidad kernel: eth0: Tx descriptor 0 is 10082076.
Nov 27 10:15:27 dutidad kernel: eth0: Tx descriptor 1 is 40082076.
Nov 27 10:15:27 dutidad kernel: eth0: Tx descriptor 2 is 00082076. (queue head)
Nov 27 10:15:27 dutidad kernel: eth0: Tx descriptor 3 is 00082076.
Nov 27 10:15:27 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 11:04:47 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 11:04:47 dutidad kernel: eth0: Tx queue start entry 37500 dirty entry 37496, full.
Nov 27 11:04:47 dutidad kernel: eth0: Tx descriptor 0 is 00082042. (queue head)
Nov 27 11:04:47 dutidad kernel: eth0: Tx descriptor 1 is 00082042.
Nov 27 11:04:47 dutidad kernel: eth0: Tx descriptor 2 is 10082042.
Nov 27 11:04:47 dutidad kernel: eth0: Tx descriptor 3 is 40082042.
Nov 27 11:04:47 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 12:15:17 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 12:15:17 dutidad kernel: eth0: Tx queue start entry 6935 dirty entry 6931, full.
Nov 27 12:15:17 dutidad kernel: eth0: Tx descriptor 0 is 00082048.
Nov 27 12:15:17 dutidad kernel: eth0: Tx descriptor 1 is 10082048.
Nov 27 12:15:17 dutidad kernel: eth0: Tx descriptor 2 is 40082048.
Nov 27 12:15:17 dutidad kernel: eth0: Tx descriptor 3 is 00082048. (queue head)
Nov 27 12:15:17 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 12:52:57 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 12:52:57 dutidad kernel: eth0: Tx queue start entry 28266 dirty entry 28262, full.
Nov 27 12:52:57 dutidad kernel: eth0: Tx descriptor 0 is 100821e2.
Nov 27 12:52:57 dutidad kernel: eth0: Tx descriptor 1 is 400821df.
Nov 27 12:52:57 dutidad kernel: eth0: Tx descriptor 2 is 00082042. (queue head)
Nov 27 12:52:57 dutidad kernel: eth0: Tx descriptor 3 is 00082042.
Nov 27 12:52:57 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 13:31:08 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 13:31:08 dutidad kernel: eth0: Tx queue start entry 7649 dirty entry 7645, full.
Nov 27 13:31:08 dutidad kernel: eth0: Tx descriptor 0 is 40082042.
Nov 27 13:31:08 dutidad kernel: eth0: Tx descriptor 1 is 00082042. (queue head)
Nov 27 13:31:08 dutidad kernel: eth0: Tx descriptor 2 is 00082042.
Nov 27 13:31:08 dutidad kernel: eth0: Tx descriptor 3 is 10082042.
Nov 27 13:31:08 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 14:20:13 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 14:20:13 dutidad kernel: eth0: Tx queue start entry 23566 dirty entry 23562, full.
Nov 27 14:20:13 dutidad kernel: eth0: Tx descriptor 0 is 10082042.
Nov 27 14:20:13 dutidad kernel: eth0: Tx descriptor 1 is 40082073.
Nov 27 14:20:13 dutidad kernel: eth0: Tx descriptor 2 is 00082073. (queue head)
Nov 27 14:20:13 dutidad kernel: eth0: Tx descriptor 3 is 00082073.
Nov 27 14:20:13 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 15:10:18 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 15:10:18 dutidad kernel: eth0: Tx queue start entry 29648 dirty entry 29644, full.
Nov 27 15:10:18 dutidad kernel: eth0: Tx descriptor 0 is 00082042. (queue head)
Nov 27 15:10:18 dutidad kernel: eth0: Tx descriptor 1 is 00082042.
Nov 27 15:10:18 dutidad kernel: eth0: Tx descriptor 2 is 10082042.
Nov 27 15:10:18 dutidad kernel: eth0: Tx descriptor 3 is 40082042.
Nov 27 15:10:18 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 15:25:13 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 15:25:13 dutidad kernel: eth0: Tx queue start entry 20829 dirty entry 20825, full.
Nov 27 15:25:13 dutidad kernel: eth0: Tx descriptor 0 is 40082042.
Nov 27 15:25:13 dutidad kernel: eth0: Tx descriptor 1 is 00082042. (queue head)
Nov 27 15:25:13 dutidad kernel: eth0: Tx descriptor 2 is 00082042.
Nov 27 15:25:13 dutidad kernel: eth0: Tx descriptor 3 is 10082042.
Nov 27 15:25:13 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 15:35:13 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 15:35:13 dutidad kernel: eth0: Tx queue start entry 4775 dirty entry 4771, full.
Nov 27 15:35:13 dutidad kernel: eth0: Tx descriptor 0 is 00082096.
Nov 27 15:35:13 dutidad kernel: eth0: Tx descriptor 1 is 10082096.
Nov 27 15:35:13 dutidad kernel: eth0: Tx descriptor 2 is 40082042.
Nov 27 15:35:13 dutidad kernel: eth0: Tx descriptor 3 is 0008203c. (queue head)
Nov 27 15:35:13 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 15:40:13 dutidad kernel: eth0: Transmit timeout, status 0d 0000 media 18.
Nov 27 15:40:13 dutidad kernel: eth0: Tx queue start entry 7032 dirty entry 7028, full.
Nov 27 15:40:13 dutidad kernel: eth0: Tx descriptor 0 is 00082073. (queue head)
Nov 27 15:40:13 dutidad kernel: eth0: Tx descriptor 1 is 00082073.
Nov 27 15:40:13 dutidad kernel: eth0: Tx descriptor 2 is 10082042.
Nov 27 15:40:13 dutidad kernel: eth0: Tx descriptor 3 is 4008203c.
Nov 27 15:40:13 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 16:00:13 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 16:00:13 dutidad kernel: eth0: Tx queue start entry 8554 dirty entry 8550, full.
Nov 27 16:00:13 dutidad kernel: eth0: Tx descriptor 0 is 10082073.
Nov 27 16:00:13 dutidad kernel: eth0: Tx descriptor 1 is 40082073.
Nov 27 16:00:13 dutidad kernel: eth0: Tx descriptor 2 is 00082042. (queue head)
Nov 27 16:00:13 dutidad kernel: eth0: Tx descriptor 3 is 00082042.
Nov 27 16:00:13 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 16:20:13 dutidad kernel: eth0: Transmit timeout, status 0d 2000 media 18.
Nov 27 16:20:13 dutidad kernel: eth0: Tx queue start entry 10723 dirty entry 10719, full.
Nov 27 16:20:13 dutidad kernel: eth0: Tx descriptor 0 is 00082042.
Nov 27 16:20:13 dutidad kernel: eth0: Tx descriptor 1 is 10082042.
Nov 27 16:20:13 dutidad kernel: eth0: Tx descriptor 2 is 40082073.
Nov 27 16:20:13 dutidad kernel: eth0: Tx descriptor 3 is 0008204d. (queue head)
Nov 27 16:20:13 dutidad kernel: eth0: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
Nov 27 16:30:20 dutidad kernel: cat uses obsolete /proc/pci interface
--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=proc_interrupts
CPU0 CPU1
0: 17289620 17178996 IO-APIC-edge timer
1: 37677 38743 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
12: 176597 210531 IO-APIC-edge PS/2 Mouse
13: 1 0 XT-PIC fpu
16: 14692823 14846630 IO-APIC-level nvidia
17: 104857 107666 IO-APIC-level aic7xxx
18: 623674 666379 IO-APIC-level ide2, es1371
19: 1132544 1133486 IO-APIC-level eth0
NMI: 0
ERR: 0
--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=proc_pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies VT 82C691 Apollo Pro (rev 196).
Medium devsel. Master Capable. No bursts.
Prefetchable 32 bit memory at 0xd8000000 [0xd8000008].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
Medium devsel. Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies VT 82C686 Apollo Super (rev 34).
Medium devsel. Master Capable. No bursts.
Bus 0, device 7, function 1:
IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 16).
Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.
I/O at 0xc000 [0xc001].
Bus 0, device 7, function 4:
Host bridge: VIA Technologies VT 82C686 Apollo Super ACPI (rev 48).
Medium devsel. Fast back-to-back capable.
Bus 0, device 12, function 0:
Unknown mass storage controller: Promise Technology Unknown device (rev 2).
Vendor id=105a. Device id=d30.
Medium devsel. IRQ 18. Master Capable. Latency=32.
I/O at 0xcc00 [0xcc01].
I/O at 0xd000 [0xd001].
I/O at 0xd400 [0xd401].
I/O at 0xd800 [0xd801].
I/O at 0xdc00 [0xdc01].
Non-prefetchable 32 bit memory at 0xdd000000 [0xdd000000].
Bus 0, device 15, function 0:
SCSI storage controller: Adaptec AIC-7892 (rev 2).
Medium devsel. Fast back-to-back capable. BIST capable. IRQ 17. Master Capable. Latency=32. Min Gnt=40.Max Lat=25.
I/O at 0xe000 [0xe001].
Non-prefetchable 64 bit memory at 0xdd020000 [0xdd020004].
Bus 0, device 16, function 0:
Multimedia audio controller: Ensoniq ES1371 (rev 8).
Slow devsel. IRQ 18. Master Capable. Latency=32. Min Gnt=12.Max Lat=128.
I/O at 0xe400 [0xe401].
Bus 0, device 17, function 0:
Ethernet controller: SMC 1211 TX (rev 16).
Medium devsel. Fast back-to-back capable. IRQ 19. Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0xe800 [0xe801].
Non-prefetchable 32 bit memory at 0xdd021000 [0xdd021000].
Bus 1, device 0, function 0:
VGA compatible controller: NVidia Unknown device (rev 163).
Vendor id=10de. Device id=150.
Medium devsel. Fast back-to-back capable. IRQ 16. Master Capable. Latency=248. Min Gnt=5.Max Lat=1.
Non-prefetchable 32 bit memory at 0xda000000 [0xda000000].
Prefetchable 32 bit memory at 0xd0000000 [0xd0000008].
--jI8keyz6grp/JLjh--
From seanm@netwinder.org Mon, 27 Nov 2000 11:30:08 -0500 (EST)
Date: Mon, 27 Nov 2000 11:30:08 -0500 (EST)
From: Sean MacLennan seanm@netwinder.org
Subject: [realtek] transmit timeout revisited
Charl,
Below is a copy of a message I sent to Jeff Garzik. We are currently
looking into the best solution to the problem. The fix in the message
works, and may tide you over till the correct solution is found.
Sean
From: Sean MacLennan
To: Jeff Garzik
Subject: 8139too race condition
Date: Wed, 22 Nov 2000 17:19:56 -0500 (EST)
X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Jeff,
I have found a race condition in the 8139too driver. Under heavy load
(I was using http_load) I could consistently get the driver to
timeout. The race condition is in start_xmit in the following code:
if ((atomic_read (&tp->cur_tx) - atomic_read (&tp->dirty_tx)) >= NUM_TX_DESC)
netif_stop_queue (dev);
What happens is that the if returns true, but by the time the
netif_stop_queue is called, the tx handler has written out the
buffers. This means everything hangs for 6 seconds until the stack
calls the tx_timeout routine.
I am using the following hack. If you have a better solution, let me
know.
if ((atomic_read (&tp->cur_tx) - atomic_read (&tp->dirty_tx)) >= NUM_TX_DESC) {
netif_stop_queue (dev);
if (atomic_read (&tp->cur_tx) == atomic_read (&tp->dirty_tx) &&
netif_queue_stopped(dev))
netif_wake_queue(dev);
}
If you have any questions (or the above code got mangled) let me know.
Sean
--
From c.p.botha@its.tudelft.nl Mon, 27 Nov 2000 17:50:40 +0100
Date: Mon, 27 Nov 2000 17:50:40 +0100
From: Charl P. Botha c.p.botha@its.tudelft.nl
Subject: [realtek] transmit timeout revisited
Sean,
Thanks for the prompt reply!
On Mon, Nov 27, 2000 at 11:30:08AM -0500, Sean MacLennan wrote:
> if ((atomic_read (&tp->cur_tx) - atomic_read (&tp->dirty_tx)) >= NUM_TX_DESC)
> netif_stop_queue (dev);
>
> What happens is that the if returns true, but by the time the
> netif_stop_queue is called, the tx handler has written out the
> buffers. This means everything hangs for 6 seconds until the stack
> calls the tx_timeout routine.
>
> I am using the following hack. If you have a better solution, let me
> know.
>
> if ((atomic_read (&tp->cur_tx) - atomic_read (&tp->dirty_tx)) >= NUM_TX_DESC) {
> netif_stop_queue (dev);
> if (atomic_read (&tp->cur_tx) == atomic_read (&tp->dirty_tx) &&
> netif_queue_stopped(dev))
> netif_wake_queue(dev);
> }
>
> If you have any questions (or the above code got mangled) let me know.
As far as I can make out, this race condition IS handled in v1.12 of Donald
Becker's rtl8139.c. I quote from line 979:
/* There is a race condition here -- we might read dirty_tx, take an
interrupt that clears the Tx queue, and only then set tx_full.
So we do this in two phases. */
if (++tp->cur_tx - tp->dirty_tx < NUM_TX_DESC) /* Typical path */
clear_bit(0, (void*)&dev->tbusy);
else {
set_bit(0, &tp->tx_full);
if (tp->cur_tx - (volatile int)tp->dirty_tx < NUM_TX_DESC) {
clear_bit(0, (void*)&dev->tbusy);
clear_bit(0, &tp->tx_full);
}
}
(note that Donald's else clause corresponds to Jeff's if)
In anycase, I can't test the 8139too.c, because there aren't any backports
of the latest driver (and I believe there are some bugs in the version that
have been backported) to 2.2.x.
Any other race conditions that you know of? :)
Thanks again!
Charl
--
charl p. botha | computer graphics and cad/cam
http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
From otsalone@cc.hut.fi Thu, 30 Nov 2000 11:00:36 +0200 (EET)
Date: Thu, 30 Nov 2000 11:00:36 +0200 (EET)
From: Olli Salonen otsalone@cc.hut.fi
Subject: [realtek] Problems installing the RTL8139 driver
Hi,
I'm having the following problem, and being a complete Linux-newbie I
don't know where to start.
I run Mandrake 7.2, which came with the 1.07 version of the RTL8139
driver. Anyway, I downloaded the binary RPM package and installed it. I
copied the pci-scan.o and rtl8139.o files over my previous files at
/lib/modules/2.2.17-21mdk/net and booted. Didn't work though.
When I try to insmod the rtl8139.o I get the following errors (insmod
pci-scan.o works fine though):
rtl8139.o: unresolved symbol skb_over_panic_Rff4558c6
rtl8139.o: unresolved symbol eth_type_trans_R268fea4a
rtl8139.o: unresolved symbol pci_drv_unregister
rtl8139.o: unresolved symbol netif_rx_R507bc694
rtl8139.o: unresolved symbol dev_close_Rf2863777
rtl8139.o: unresolved symbol __kfree_skb_Rb199cc61
rtl8139.o: unresolved symbol alloc_skb_Rbb37a2d1
rtl8139.o: unresolved symbol eth_copy_and_sum_R8c7c58f8
rtl8139.o: unresolved symbol unregister_netdev_Ref7eb65d
rtl8139.o: unresolved symbol init_etherdev_Rf1ebeb5a
rtl8139.o: unresolved symbol pci_drv_register
I also tried download the source files, but when I try to compile I get
something like this:
gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c rtl8139.c
In file included from /usr/include/linux/string.h:37,
from rtl8139.c:99:
/usr/include/asm/string.h:46: parse error before `size_t'
/usr/include/asm/string.h: In function `strncpy':
/usr/include/asm/string.h:47: number of arguments doesn't match prototype
/usr/include/linux/string.h:13: prototype declaration
....... this goes on for several screens ...
System works with the 1.07 driver ok, should I just use that?
Thank you in advance,
---
Olli Salonen olli@cabbala.net
Koivuviidantie 9B as. 2 http://www.cabbala.net/olli
02130 Espoo ... the less you know,
Finland the more you believe...