From td@salesint.com Wed Dec 1 04:00:37 1999 Date: Wed Dec 1 04:00:37 1999 From: Technical Service - Sales International Holland B.V. td@salesint.com Subject: Got same message twice while loading module only once This is a multi-part message in MIME format. ------=_NextPart_000_000A_01BF3B4C.A59E1FE0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hey there, just wondering whether I'm doing something wrong. At boot time when the module loads I see the message 'rtl8139.c:v1.08 = 6/25/99 Donald Becker http://url.to.doc' twice while the configuration = line 'eth0 Realtek irq hex:hex:hex:hex:hex' only appears once. Is this normal? Kind regards, =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D * Ferry van Steen, Technical Service * Sales International Holland B.V. * E-Mail: td@salesint.com * Homepage: http://www.salesint.com * ICQ (Private): 191458 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D ------=_NextPart_000_000A_01BF3B4C.A59E1FE0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hey there,
 
just wondering whether I'm doing something = wrong.
 
At boot time when the module loads I see the message = 'rtl8139.c:v1.08 6/25/99 Donald Becker http://url.to.doc' twice while the = configuration=20 line 'eth0 Realtek irq hex:hex:hex:hex:hex' only appears = once.
 
Is this normal?
 
Kind regards,
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
* Ferry van Steen,=20 Technical Service
* Sales International Holland B.V.
* E-Mail: td@salesint.com
* Homepage: http://www.salesint.com
* ICQ = (Private):=20 191458
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
------=_NextPart_000_000A_01BF3B4C.A59E1FE0-- | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From becker@cesdis.gsfc.nasa.gov Wed Dec 1 12:59:05 1999 Date: Wed Dec 1 12:59:05 1999 From: Donald Becker becker@cesdis.gsfc.nasa.gov Subject: Got same message twice while loading module only once On Tue, 30 Nov 1999, Technical Service - Sales International Holland B.V. wrote: > just wondering whether I'm doing something wrong. Yes. Please don't send HTML-encoded email. > At boot time when the module loads I see the message 'rtl8139.c:v1.08 = > 6/25/99 Donald Becker http://url.to.doc' twice while the configuration = > line 'eth0 Realtek irq hex:hex:hex:hex:hex' only appears once. > > Is this normal? The module emits the message each time it loads, even if it doesn't detect a card. (You especially need the version info when a new card *isn't* detected.) My first reaction is that soemthing is trying to load the module twice, but normally this could only happen if it's loaded under a different name. If the driver is built into the kernel, instead of being loaded as a module, the PCI probe routines should only be called once. Some recent kernels have a buglet that calls the probe routine multiple times. That usually results in eight messages, not just two. Donald Becker Scyld Computing Corporation, and USRA-CESDIS, becker@cesdis.gsfc.nasa.gov | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From leopold@diku.dk Thu Dec 2 14:31:25 1999 Date: Thu Dec 2 14:31:25 1999 From: Martin Leopold leopold@diku.dk Subject: Bridging trouble with RTL 8139 Dear all. I have a somewhat tricky bugreport. Me setup is this: I have a 10 Mbps LAN with a Windows 98 box and a 100 Mbps LAN allso with Windows 98. As bridge between the two networks I have i Linux box with a NE2k comp. 10 Mbps ISA card and a RTL8139 100 Mbps PCI card. The Linux box is a Pentium 100 with 16 Mb RAM running Slackware Linux (3.3 I think) the kernel is 2.2.12. The trouble is this: When I try to access SMB shares from either side of the LAN I get some very wierd time-out errors. Windows reads half a directory, stops and waits (with no network activity) for a while, resumes and reads the rest. Just as if a frame got lost and both sides are waiting for each other. I tried changing the Windows machines with Linux boxes and it seems to be working fine (SMB, ftp, telnet) - why I have no idea. I've tried changing the RTL card with a 3Com 905B card and the bridging works fine. I wanted to use the RTL card as the bridge from 100 -> 10 because its so cheap and since the 10 Mbps card is surly going to be the bottle neck, it doesn't matter that the RTL card has such lousy preformance. If some points are unclear, send me a reply, and I'll try to explain them better. De bedste hilsner Martin Leopold, Datalogisk Institut, Københavns Universitet. www.scandicnetpay. com/tilmelding.php3?Ref=214585 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From becker@cesdis.gsfc.nasa.gov Thu Dec 2 16:08:01 1999 Date: Thu Dec 2 16:08:01 1999 From: Donald Becker becker@cesdis.gsfc.nasa.gov Subject: Bridging trouble with RTL 8139 On Thu, 2 Dec 1999, Martin Leopold wrote: > As bridge > between the two networks I have i Linux box with a NE2k comp. 10 Mbps ISA > card and a RTL8139 100 Mbps PCI card. The Linux box is a Pentium 100 with > 16 Mb RAM running Slackware Linux (3.3 I think) the kernel is 2.2.12. > > The trouble is this: When I try to access SMB shares from either side of > the LAN I get some very wierd time-out errors. Check /proc/net/dev for error count, and check your message logs for card time-outs. If the rtl8139 driver is timing out, the first step is to try an updated driver. Don't bother updating the driver otherwise. > I've tried changing the RTL card with a 3Com 905B card and the bridging > works fine. I wanted to use the RTL card as the bridge from 100 -> 10 > because its so cheap and since the 10 Mbps card is surly going to be the > bottle neck, it doesn't matter that the RTL card has such lousy preformance. The rtl8139 doesn't have lousy performance, it's data transfer architecture is just not as good as many other current 10/100 chips. It's much faster than a PCI NE2000 clone, which in turn is much faster than a ISA NE2000 card. An ISA Ethernet card will consume more than a third of your CPU cycles at full bandwidth. The ISA NE2000 overhead is while waiting on the ISA bus, so the load is independent of the processor speed. Most people think that they can make up for slow ISA devices with a faster processor. You only end up wasting more CPU cycles. In this case the slow ISA accesses might cause problems with the faster rtl8139 card. Summary: ISA Bad, PCI good. In contrast, a faster memory subsystem mitigates the extra rtl8139 copy. And the rtl8139-A and -B, with PCI v2.0 and v2.1 support, have improved the PCI burst transfer performance. At US$12/ea. for rtl8139b cards, there is no longer any reason to buy PCI NE2000 clones. And ISA cards should only be used on old systems without PCI slots. Donald Becker Scyld Computing Corporation, and USRA-CESDIS, becker@cesdis.gsfc.nasa.gov | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From Stefan.Meister@t-online.de Fri Dec 3 15:57:09 1999 Date: Fri Dec 3 15:57:09 1999 From: Stefan Meister Stefan.Meister@t-online.de Subject: Rx-Problem with 8139.c Driver Hello, I have a problem in receiving Data-Packets with an Lantech Fastnet TX PCI-Card with an 8139A. If i send files bigger than (ca.) 64K to the receiving Linux-Server the network-connection is broken. I tried this out while sending files with changing filesize increased step by step via ftp from an Windows (or OS/2-Warp) Client to the Linux-FTP-Server. Originally i was pointed to that Problem while using the Linux-PC as a Fileserver under Samba. When i copied Files to a shared Directory (with r/w permission) the Samba-Server was broken. I use a RedHat-Distribution with Kernel-Version 2.2.9 and the rtl8139.c Driver V. 1.06. I also got the V. 1.08 which i compiled in the Kernel with the same result as mentioned above. Server: ASUS SP3G, 486AMDx133, 32MB What can i do? Thank you & with kind regards... Stefan | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From becker@cesdis.gsfc.nasa.gov Fri Dec 3 16:10:12 1999 Date: Fri Dec 3 16:10:12 1999 From: Donald Becker becker@cesdis.gsfc.nasa.gov Subject: Rx-Problem with 8139.c Driver On Fri, 3 Dec 1999, Stefan Meister wrote: > I have a problem in receiving Data-Packets with an Lantech Fastnet TX > PCI-Card with an 8139A. > If i send files bigger than (ca.) 64K to the receiving Linux-Server ... > Server: ASUS SP3G, 486AMDx133, 32MB The SP3G uses a chipset with a broken PCI implementation. It does not work with modern cards using long bursts. You must limit write bursts to 8 longwords, preferably with 8 longword cache alignment. I don't recall if the bug is when spanning cache lines, or just with the length of the burst. Try setting the constant RX_DMA_BURST to 1 (16<< 1 = 32 bytes) in the source file. This *should* work around the hardware bug, although I have not verified this myself. Please send a report to the list. The Tulip driver used to explicitly check for this bug and silently implement the work-around. But it's no longer easy or accurate to check for a 486 PCI system, and not all 486-like systems use the buggy chipset. (Does anyone know a correct method for programmatically detecting this bug?) Donald Becker Scyld Computing Corporation, and USRA-CESDIS, becker@cesdis.gsfc.nasa.gov | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From Stefan.Meister@t-online.de Mon Dec 6 08:35:57 1999 Date: Mon Dec 6 08:35:57 1999 From: Stefan Meister Stefan.Meister@t-online.de Subject: Rx-Problem with 8139.c Driver Hello, I have a problem in receiving Data-Packets with an Lantech Fastnet TX PCI-Card with an 8139A. If i send files bigger than (ca.) 64K to the receiving Linux-Server the network-connection is broken. I tried this out while sending files with changing filesize increased step by step via ftp from an Windows (or OS/2-Warp) Client to the Linux-FTP-Server. Originally i was pointed to that Problem while using the Linux-PC as a Fileserver under Samba. When i copied Files to a shared Directory (with r/w permission) the Samba-Server was broken. I use a RedHat-Distribution with Kernel-Version 2.2.9 and the rtl8139.c Driver V. 1.06. I also got the V. 1.08 which i compiled in the Kernel with the same result as mentioned above. Server: ASUS SP3G, 486AMDx133, 32MB What can i do? Thank you & with kind regards... Stefan | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From td@salesint.com Mon Dec 6 08:46:25 1999 Date: Mon Dec 6 08:46:25 1999 From: Technical Service - Sales International Holland B.V. td@salesint.com Subject: How to compile driver into kernel This is a multi-part message in MIME format. ------=_NextPart_000_0016_01BF3B41.DBECB760 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hey there, I was wondering if it's possible to compile the driver into the kernel = like used to be possible. I used to run kernel 2.0.35 which has the = support for the Realtek 8139 build into it (driver shows up under the = menuconfig) however version 2.2.5 and 2.2.13 for some reason don't have = the driver. Now I was wondering how to compile the driver into the = kernel and why the driver isn't shipped with the kernel anymore. Thanks for any help. Kind regards, =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D * Ferry van Steen, Technical Service * Sales International Holland B.V. * E-Mail: td@salesint.com * Homepage: http://www.salesint.com * ICQ (Private): 191458 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D ------=_NextPart_000_0016_01BF3B41.DBECB760 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hey there,
 
I was wondering if it's possible to compile the = driver into=20 the kernel like used to be possible. I used to run kernel 2.0.35 which = has the=20 support for the Realtek 8139 build into it (driver shows up under the=20 menuconfig) however version 2.2.5 and 2.2.13 for some reason don't have = the=20 driver. Now I was wondering how to compile the driver into the kernel = and why=20 the driver isn't shipped with the kernel anymore.
 
Thanks for any help.
 
Kind regards,
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
* Ferry van Steen,=20 Technical Service
* Sales International Holland B.V.
* E-Mail: td@salesint.com
* Homepage: http://www.salesint.com
* ICQ = (Private):=20 191458
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
------=_NextPart_000_0016_01BF3B41.DBECB760-- | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From mdione@hal.famaf.unc.edu.ar Mon Dec 6 08:47:08 1999 Date: Mon Dec 6 08:47:08 1999 From: Marcos Dione mdione@hal.famaf.unc.edu.ar Subject: unknown errors (fwd) again... ---------- Forwarded message ---------- Date: Mon Dec 6 08:47:08 1999 From: Marcos Dione To: linux-realtek@beowulf.gsfc.nasa.gov Subject: unknown errors hi, I'm administrating 90 compaqs which came with the rtl8139. i'm using mdk-6.1 (i.e., kernel 2.2.13). the problem is: copying large files (with large=1Gb) from one machine to another I ramdonly get error messages like etho: Transmit timeout, status 0d000 media 00 : Tx queue start entry x+4 dirty entry x where x is some number. while the error isn't present, the copy is smooth, but when it shows, the copy stops a while, and restart after a ramdon time ranging from 1 min to never! any hint? | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From td@salesint.com Mon Dec 6 08:57:05 1999 Date: Mon Dec 6 08:57:05 1999 From: Technical Service - Sales International Holland B.V. td@salesint.com Subject: Got same message twice while loading module only once This is a multi-part message in MIME format. ------=_NextPart_000_000A_01BF3B4C.A59E1FE0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hey there, just wondering whether I'm doing something wrong. At boot time when the module loads I see the message 'rtl8139.c:v1.08 = 6/25/99 Donald Becker http://url.to.doc' twice while the configuration = line 'eth0 Realtek irq hex:hex:hex:hex:hex' only appears once. Is this normal? Kind regards, =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D * Ferry van Steen, Technical Service * Sales International Holland B.V. * E-Mail: td@salesint.com * Homepage: http://www.salesint.com * ICQ (Private): 191458 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D ------=_NextPart_000_000A_01BF3B4C.A59E1FE0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hey there,
 
just wondering whether I'm doing something = wrong.
 
At boot time when the module loads I see the message = 'rtl8139.c:v1.08 6/25/99 Donald Becker http://url.to.doc' twice while the = configuration=20 line 'eth0 Realtek irq hex:hex:hex:hex:hex' only appears = once.
 
Is this normal?
 
Kind regards,
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
* Ferry van Steen,=20 Technical Service
* Sales International Holland B.V.
* E-Mail: td@salesint.com
* Homepage: http://www.salesint.com
* ICQ = (Private):=20 191458
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
------=_NextPart_000_000A_01BF3B4C.A59E1FE0-- | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From tbrobst@cjnetworks.com Mon Dec 6 09:00:28 1999 Date: Mon Dec 6 09:00:28 1999 From: Tim Brobst tbrobst@cjnetworks.com Subject: NIC driver compiling errors/problems Hi everyone, I have the Kingston KNE120TX EtheRx nic for my ADSL line and my RH6.0 doesn't have a driver for this card. Being somewhat of a newbe in linux I would like to get some experience doing some downloading and compiling. I have been in contact with Kingston and they are "working" on my problem. They have referred me to this site (http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.c) for the driver for my nic card. Here is my problems, I have used both compile commands, (the one from the bottom of this driver page, and one that Kingston forwarded to me via email) the commands are the same except the one from Kingston has an added line. From the page: "gcc -DMODULE -D_KERNEL_ -Wall -Wstrict-prototypes -O6 -c rtl8139.c And here is the one that Kingston sent: gcc -DMODULE -D_KERNEL_ -Wall -Wstrict-prototypes -O6 -c rtl8139.c '[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS' When i use the first command I get the following information lines and errors: rtl8139.c:61:warning: #Warning You must compile this file with the correct options! rtl8139.c:62:warning: #Warning See the last lines of the source file. rtl8139.c:63:warning: #error You must compile this driver with "-O". I get the same information lines and errors when I run the command that Kingston sent me, except this "gcc" line comes in before all the rest: gcc: [ -f /usr/src/linux/modversions.h ] && echo -DMODVERSIONS: no such file or directory. I have followed all paths and have everything that's is listed in both commands, so I don't understand the "no such file or directory" that the second command returns. I have noticed that if I try to go into the /usr/src/linux directory it sends me into /usr/src/linux2.2.5 directory, why I have no idea, acts almost like a default path. I have downloaded the file into /usr/src/linux as I am told, but it shows up in the /usr/src/linux2.2.5 directory showing the same result as trying to get into the /linux directory of the same path. Any help is appreciated Tim Brobst tbrobst@cjnetworks.com | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From petr@scssoft.com Mon Dec 6 11:37:12 1999 Date: Mon Dec 6 11:37:12 1999 From: Petr Sebor petr@scssoft.com Subject: RTL8139 problems Hello, I have posted this information before to the linux-net, but if you are not reading that list I would like to share my problems here : After plugging rtl8139 / 100Mb ( SVEC ) card into linux machine and compiling the Donald Becker's driver v1.08 as a module, I am not able to establish communication between two machines ( 192.168.1.1 & 192.168.1.10 ) Honestly.. the linux does send successfuly several packets .. from 1 to 13 pings... then the driver dies with 'Destination unreachable' PING 192.168.1.10 (192.168.1.10) from 192.168.1.1 : 56 data bytes 64 bytes from 192.168.1.10: icmp_seq=0 ttl=128 time=8.9 ms 64 bytes from 192.168.1.10: icmp_seq=1 ttl=128 time=0.4 ms 64 bytes from 192.168.1.10: icmp_seq=2 ttl=128 time=0.3 ms >From ns.pixel (192.168.1.1): Destination Host Unreachable >From ns.pixel (192.168.1.1): Destination Host Unreachable >From ns.pixel (192.168.1.1): Destination Host Unreachable After turning debugging options to 6, I was able to get these messages: Dec 6 17:12:14 ns kernel: eth2: interrupt status=0x0001 new intstat=0x0000. Dec 6 17:12:14 ns kernel: eth2: In rtl8129_rx(), current e6f4 BufAddr 0044, free to e6e4, Cmd 0c. Dec 6 17:12:14 ns kernel: eth2: rtl8129_rx() status 0a02, size 0000, cur e6f4. Dec 6 17:12:14 ns kernel: eth2: Frame contents 02 0a 00 00 90 82 04 18 02 00 10 80 50 00 60 94 00 00 00 00 00 0 0 00 00 00 00 00 00 a0 00 00 00 00 50 00 01 00 02 00 40 0a 00 00 00 80 2a 20 10 80 00 00 00 00 00 24 00 05 00 00 00 50 a0 40 00 96 00 00 00 00 80. Dec 6 17:12:14 ns kernel: eth2: Ethernet frame had errors, status 0a02. Dec 6 17:12:14 ns kernel: eth2: set_rx_mode(1043) done -- Rx config 00009c00. Dec 6 17:12:14 ns kernel: eth2: Done rtl8129_rx(), current e6f8 BufAddr 0000, free to e6e8, Cmd 0d. Dec 6 17:12:14 ns kernel: eth2: interrupt status=0x0020 new intstat=0x0000. Dec 6 17:12:14 ns kernel: eth2: In rtl8129_rx(), current e6f8 BufAddr 0000, free to e6e8, Cmd 0d. Dec 6 17:12:14 ns kernel: eth2: Done rtl8129_rx(), current e6f8 BufAddr 0000, free to e6e8, Cmd 0d. Dec 6 17:12:14 ns kernel: eth2: Abnormal interrupt, status 00000020. Dec 6 17:12:14 ns kernel: eth2: interrupt status=0x0000 new intstat=0x0000. Dec 6 17:12:14 ns kernel: eth2: exiting interrupt, intr_status=0x4000000. Dec 6 17:12:15 ns kernel: eth2: Queued Tx packet at c1e4a342 size 42 to slot 1. Dec 6 17:12:15 ns kernel: eth2: interrupt status=0x0004 new intstat=0x0000. Dec 6 17:12:15 ns kernel: eth2: interrupt status=0x0000 new intstat=0x0000. Dec 6 17:12:15 ns kernel: eth2: exiting interrupt, intr_status=0x4000000. Dec 6 17:12:15 ns kernel: eth2: interrupt status=0x0001 new intstat=0x0000. Dec 6 17:12:15 ns kernel: eth2: In rtl8129_rx(), current e6f8 BufAddr 0044, free to e6e8, Cmd 0c. Dec 6 17:12:15 ns kernel: eth2: rtl8129_rx() status 18048290, size 1804, cur e6f8. Dec 6 17:12:15 ns kernel: eth2: Frame contents 90 82 04 18 02 00 10 80 50 00 60 94 00 00 00 00 00 00 00 00 00 0 0 00 00 a0 00 00 00 00 50 00 01 00 02 00 40 0a 00 00 00 80 2a 20 10 80 00 00 00 00 00 24 00 05 00 00 00 50 a0 40 00 96 00 00 00 00 80 00 00 10 00. Dec 6 17:12:15 ns kernel: eth2: Ethernet frame had errors, status 18048290. Dec 6 17:12:15 ns kernel: eth2: set_rx_mode(1043) done -- Rx config 00009c00. Dec 6 17:12:15 ns kernel: eth2: Done rtl8129_rx(), current ff00 BufAddr 0000, free to fef0, Cmd 0d. Dec 6 17:12:15 ns kernel: eth2: interrupt status=0x0020 new intstat=0x0000. Dec 6 17:12:15 ns kernel: eth2: In rtl8129_rx(), current ff00 BufAddr 0000, free to fef0, Cmd 0d. Dec 6 17:12:15 ns kernel: eth2: Done rtl8129_rx(), current ff00 BufAddr 0000, free to fef0, Cmd 0d. Dec 6 17:12:15 ns kernel: eth2: Abnormal interrupt, status 00000020. Dec 6 17:12:15 ns kernel: eth2: interrupt status=0x0000 new intstat=0x0000. Dec 6 17:12:15 ns kernel: eth2: exiting interrupt, intr_status=0x4000000. Dec 6 17:12:16 ns kernel: eth2: Media selection tick, Link partner 0000. Dec 6 17:12:16 ns kernel: eth2: Other registers are IntMask c07f IntStatus 0000 RxStatus fef00d00. Dec 6 17:12:16 ns kernel: eth2: Chip config 10 2c. Dec 6 17:12:20 ns kernel: eth2: Queued Tx packet at c07cf002 size 245 to slot 2. Dec 6 17:12:20 ns kernel: eth2: interrupt status=0x0004 new intstat=0x0000. Dec 6 17:12:20 ns kernel: eth2: interrupt status=0x0000 new intstat=0x0000. Dec 6 17:12:20 ns kernel: eth2: exiting interrupt, intr_status=0x4000000. Dec 6 17:12:20 ns kernel: eth2: Queued Tx packet at c07cf802 size 245 to slot 3. Dec 6 17:12:20 ns kernel: eth2: interrupt status=0x0004 new intstat=0x0000. Dec 6 17:12:20 ns kernel: eth2: interrupt status=0x0000 new intstat=0x0000. Dec 6 17:12:20 ns kernel: eth2: exiting interrupt, intr_status=0x4000000. along with a lot of theese : ec 6 17:09:55 ns kernel: eth2: Oversized Ethernet frame, status ffffffff! Dec 6 17:09:56 ns kernel: eth2: Oversized Ethernet frame, status c000ffff! Dec 6 17:09:56 ns kernel: eth2: Oversized Ethernet frame, status 050a! Dec 6 17:15:08 ns kernel: eth2: Oversized Ethernet frame, status 1000450a! Dec 6 17:15:09 ns kernel: eth2: Oversized Ethernet frame, status ffffffff! Dec 6 17:15:09 ns kernel: eth2: Oversized Ethernet frame, status c000ffff! Dec 6 17:15:11 ns kernel: eth2: Oversized Ethernet frame, status 2020204e! Dec 6 17:15:15 ns kernel: eth2: Oversized Ethernet frame, status 108008! Dec 6 17:15:16 ns kernel: eth2: Oversized Ethernet frame, status 1000008a! Dec 6 17:15:16 ns kernel: eth2: Oversized Ethernet frame, status 520010a! Dec 6 17:15:17 ns kernel: eth2: Oversized Ethernet frame, status 186c17ca! Dec 6 17:15:18 ns kernel: eth2: Oversized Ethernet frame, status 5504ffff! Dec 6 17:15:24 ns kernel: eth2: Oversized Ethernet frame, status 20008! Does it make sense to anyone ? I would like to do more tests if anyone would be so kind and provide me with tips what to do... Best regards, Petr Sebor PS : I am not on the list ... -- Petr Sebor Technology/Engine Development SCS Software [ http://www.scssoft.com ] | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From taso@esands.com Mon Dec 6 16:37:32 1999 Date: Mon Dec 6 16:37:32 1999 From: Taso Hatzi taso@esands.com Subject: unknown errors (fwd) Marcos Dione wrote: > > etho: Transmit timeout, status 0d000 media 00 > : Tx queue start entry x+4 dirty entry x > > any hint? > The driver is flaky. I'm using 1.08r and it too stops periodically. However, my system is 2.2.13SMP and I'm not sure the SMP bit is completely bug-free. Maybe you can try a newer driver. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From inaki.arenaza@jet.es Mon Dec 6 17:23:52 1999 Date: Mon Dec 6 17:23:52 1999 From: Ignacio Arenaza inaki.arenaza@jet.es Subject: Bug in RTL8139 driver? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, first of all, excuse my English! Second, I haven't received Appendix B with the welcome message Majordomo sends you when you subscribe, so I don't know what kind of information I have to send to the list to report a bug. The problem si I'm having some trouble with a RTL8139B (note de final B) NIC under Linux. The setup: * Debian Slink 2.1 * 2.2.13 kernel. * RTL8139 driver (v 1.06 directly from official web page) * AMD K6-2 * 128 MB RAM * EIDE Disk. * Connected to a 3COM SuperStack II 1100 switch (to a 10 Mbps auto-negotiating full-duplex port) * Cat. 5 FTP cabling. If I boot linux, no matter how I compile the driver (static or module), I can't send or receive a single frame. I get an average of 2 errors per second (I do an 'ifconfig eth0' every second, and the error counter increases every time). I shutdown linux and boot OpenBSD 2.5 from another partition, and it works without a hiccup for hours. I take this same machine and connect it to a 3COM SuperStack FMS Builder II Hub (non auto-negotiating 10 Mbps simplex port) and it works nicely. So it seems, somewhere in the auto-negotiation code there is something my 8139B chip doesn't like. I have tried to force the driver to use half-duplex mode, but it is the same. Just tell me the kind of additional info you need (systems logs, additional debugging output, whatever). Thanks in advance. Iñaki. - -- Linux Registered User #44369 Si este mensaje no esta firmado con PGP/GPG, entonces no es mio. If this message is not PGP/GPG signed, then it's not mine. Get PGP/GPG Keys at http://personales.jet.es/inaki.arenaza/pgpkey.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.4 and Gnu Privacy Guard iD8DBQE4S9gxZXLnGT1HLgcRAn0tAJ9bVO2Fk7Gti7wkQfsSS+BC0b3G5QCeOw9S tAqRNbe7jlnpTa6IdMI/nlQ= =jysV -----END PGP SIGNATURE----- | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From petr@scssoft.com Tue Dec 7 07:51:34 1999 Date: Tue Dec 7 07:51:34 1999 From: Petr Sebor petr@scssoft.com Subject: RTL8139 problems Well, I have almost went nuts about that card, after I have discovered a small notice on Donald Becker's RTL site that some older motherboards do not support PCI burst modes and that this may be the cause of the problem... My motherboard is not that old, but it is noname VX-PRO II board.. god knows who manufactured it. I have borrowed different board from another computer ( actually VX-PRO+ chipset on noname board but with AWARD BIOS instead of AMI ) and the card now runs like a charm... perfectly... Well, At least, I wanted to share this information, although it has been known for some time... Regards, Petr Sebor -- Petr Sebor Technology/Engine Development SCS Software [ http://www.scssoft.com ] | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From Stefan.Meister@t-online.de Wed Dec 8 16:06:13 1999 Date: Wed Dec 8 16:06:13 1999 From: Stefan Meister Stefan.Meister@t-online.de Subject: Fwd: Re: Rx-Problem with 8139.c Driver > On Sat, 4 Dec 1999, Stefan Meister wrote: > > to my Surprise the Problem was the Cache-Method of the Saturn-Chipset: > > I had to switch to »write-through«-Strategy and after that all other > > Settings > > could be set to »System-Settings« incl. enhanced DMA-Buffering etc. > Please send this message as a follow-up to linux-realtek. > That way it will be put in the hypermail archive. > Donald Becker > Scyld Computing Corporation, and > USRA-CESDIS, becker@cesdis.gsfc.nasa.gov | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From queike@163.net Fri Dec 10 07:42:48 1999 Date: Fri Dec 10 07:42:48 1999 From: jacky queike@163.net Subject: problem This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF4351.64546E10 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SXQncyByaWdodCB0byBpbnN0YWxsIG1vZHVsZSBydGw4MTM5Lm8sYnV0IHdoZW4gcnVuICJpZmNv bmZpZyBldGgwIDE5Mi4xNjguMC41IG5ldG1hc2sgMjU1LjI1NS4yNTUuMCIsIGl0IGFwcGVhcnMg InNpb2NzaWZmbGFnczogUmVzb3VyY2UgdGVtcG9yYXJpbHkgdW5hdmFpbGFibGUiIG9uIHRoZSBt b25pdG9yIHNjcmVlbi4gV2h5PyANCg== ------=_NextPart_000_0005_01BF4351.64546E10 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4yMDE0LjIxMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVBRD4NCjxC T0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkl0J3MmbmJzcDtyaWdodCB0 byBpbnN0YWxsJm5ic3A7bW9kdWxlIHJ0bDgxMzkubyxidXQgd2hlbiBydW4gDQoiaWZjb25maWcg ZXRoMCAxOTIuMTY4LjAuNSBuZXRtYXNrIDI1NS4yNTUuMjU1LjAiLCBpdCBhcHBlYXJzICJzaW9j c2lmZmxhZ3M6IA0KUmVzb3VyY2UgdGVtcG9yYXJpbHkgdW5hdmFpbGFibGUiIG9uIHRoZSBtb25p dG9yIHNjcmVlbi4gV2h5PyANCjwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K ------=_NextPart_000_0005_01BF4351.64546E10-- | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From gmader@geoanalytics.com Tue Dec 14 15:44:54 1999 Date: Tue Dec 14 15:44:54 1999 From: Greg Mader gmader@geoanalytics.com Subject: odd behavior with RTL8139 Dear ethernet gurus, I have a box set up to act as a router/firewall, with a 3com nic as the internal interface (192.168.x.x addresses), a Linksys tulip card as the external, and a ovislink RTL8139 as the DMZ interface. The machine started to act up and "freeze" ( no response to the keyboard, or mouse, had to power down the machine.) after we changed the ip addresses on the external and the DMZ interfaces. Specifically, daily operations are fine, except for backing up data from the email server on the DMZ to the backup server on the internal network. This means that high network traffic is going through the RTL8139 interface, and that is when the system hangs. Here is the message that I got at the console. >> eth2: transmit timeout, status 0d 0000 media 00 >> eth2: Tx queue start entry 735041 dirty entry 735041 This is the RTL8139 interface. Here is the version and setup info from Dmesg: rtl8139.c:v1.04 9/22/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html eth2: RealTek RTL8139 Fast Ethernet at 0xe400, IRQ 10, 00:4f:4e:03:41:53. So, I looked at your page, and you have come up with two revisions since this version. Is this system hang related to an old driver? Do you have any other ideas? Thanks, Greg Mader | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From gmader@geoanalytics.com Tue Dec 14 16:00:23 1999 Date: Tue Dec 14 16:00:23 1999 From: Greg Mader gmader@geoanalytics.com Subject: odd behavior with RTL8139 Dear ethernet gurus, I have a box set up to act as a router/firewall, with a 3com nic as the internal interface (192.168.x.x addresses), a Linksys tulip card as the external, and a ovislink RTL8139 as the DMZ interface. The machine started to act up and "freeze" ( no response to the keyboard, or mouse, had to power down the machine.) after we changed the ip addresses on the external and the DMZ interfaces. Specifically, daily operations are fine, except for backing up data from the email server on the DMZ to the backup server on the internal network. This means that high network traffic is going through the RTL8139 interface, and that is when the system hangs. Here is the message that I got at the console. >> eth2: transmit timeout, status 0d 0000 media 00 >> eth2: Tx queue start entry 735041 dirty entry 735041 This is the RTL8139 interface. Here is the version and setup info from Dmesg: rtl8139.c:v1.04 9/22/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html eth2: RealTek RTL8139 Fast Ethernet at 0xe400, IRQ 10, 00:4f:4e:03:41:53. So, I looked at your page, and you have come up with two revisions since this version. Is this system hang related to an old driver? Do you have any other ideas? Thanks, Greg Mader | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From cedric@itactics.itactics.com Wed Dec 15 19:56:26 1999 Date: Wed Dec 15 19:56:26 1999 From: Cedric Puddy cedric@itactics.itactics.com Subject: "could not allocate 65535 byte recieve ring" messages Hello folks, My apologies if this is an old topic (I have not yet located the list archive, and am therefore posting a rather less informed that I would normally like to be). In any case, I have recently started working with a resonably sized sample set of Linux 2.2.5 boxes (six) equiped with two RTL8139 NICs apiece. The message "Could not allocate 65535 byte recieve ring" comes up occationally on boot (accompanied by the card not initializing), or very often when I attempt to re-initialize a cad while the system is running. I cannot reliably reproduce this problem, though I have been able to produce it at least ounce on every system I have tried installing the cards in. When a system has multiple cards, it usually only affects one card. I do not have this problem with other cards, and other services do not fail. I upgraded some systems to 2.2.13, and continued to have the problem. I had someone with the appropriate experience and skill look through the kernel code and driver code in an attempt to figure out "who is at fault", and the verdict there was that the driver appeared to be making a perfectly ordinary request for a chunk of kernel memory, and that the kernel appearred to be refusing on account of believing itself to have instufficent resources to allocate the memory. This would sound to me like a "general kernel issue", except that I have been unable to reproduce similar problems with my "mottly crew" of 3c905b, NE2000 (ISA), racals, and SMC cards. I am therefore very interested in hearing if this is a "known issue" of some kind against either the driver or someother piece of code, if there is possibly some workaround that might be had (say, reducing the size of the recieve ring??), and so on. Thanks to everyone who works on these drivers - though the only name I know is Donald Becker (those driver pages have been really handy!). Regards, -Cedric - | CCj/ClearLine - Unix/NT Administration and TCP/IP Network Services | 118 Louisa Street, Kitchener, Ontario, N2H 5M3, 519-741-2157 \____________________________________________________________________ Cedric Puddy, IS Director cedric@thinkers.org PGP Key Available at: http://www.thinkers.org/cedric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From avpatel@ozemail.com.au Thu Dec 16 01:26:33 1999 Date: Thu Dec 16 01:26:33 1999 From: Alok Patel avpatel@ozemail.com.au Subject: problems installing driver This is a multi-part message in MIME format. ------=_NextPart_000_008B_01BF47E2.5FF78060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I need help I can't seem to install the driver. Regards, Alok Patel ------=_NextPart_000_008B_01BF47E2.5FF78060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I need help I can't seem to install the = driver.
 
Regards,
 
 
Alok Patel
------=_NextPart_000_008B_01BF47E2.5FF78060-- | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From raarts@netland.nl Thu Dec 16 03:39:45 1999 Date: Thu Dec 16 03:39:45 1999 From: Ron Arts raarts@netland.nl Subject: "could not allocate 65535 byte recieve ring" messages Cedric Puddy wrote: > > Hello folks, > > My apologies if this is an old topic (I have not yet > located the list archive, and am therefore posting > a rather less informed that I would normally like to > be). > > In any case, I have recently started working with a > resonably sized sample set of Linux 2.2.5 boxes (six) > equiped with two RTL8139 NICs apiece. > > The message "Could not allocate 65535 byte recieve ring" > comes up occationally on boot (accompanied by the card The only thing I have to say here is: me too. I used a pretty non-standard configuration (7 PCI RealTeks in one machine), I used kernel 2.0.37, afterwards switched to 2.2.13 but still experience lock-ups. I switched to Intel Ether Express Pro cards, this improved things, but the machine still locks up when I do >4 hour of full ethernet load on all 7 cards. This happens on two identical machines, so it can't be a hardware malfunction, I thought it might be some hardware design problem (there aren't many backplanes with 7 PCI slots) By the way I receive this message on more than one cards. And indeed, it's not consistent. On some reboots it's there, and sometimes it's not. Which is not to say the cards function properly after that, because I get total kernel lockups after 10 minutes of network load. Ron Arts > not initializing), or very often when I attempt to > re-initialize a cad while the system is running. I > cannot reliably reproduce this problem, though I have > been able to produce it at least ounce on every system > I have tried installing the cards in. When a > system has multiple cards, it usually only affects one > card. I do not have this problem with other cards, > and other services do not fail. > > I upgraded some systems to 2.2.13, and continued to > have the problem. > > I had someone with the appropriate experience and > skill look through the kernel code and driver code > in an attempt to figure out "who is at fault", > and the verdict there was that the driver appeared > to be making a perfectly ordinary request for > a chunk of kernel memory, and that the kernel > appearred to be refusing on account of believing > itself to have instufficent resources to > allocate the memory. > > This would sound to me like a "general kernel issue", > except that I have been unable to reproduce similar > problems with my "mottly crew" of 3c905b, NE2000 (ISA), > racals, and SMC cards. > > I am therefore very interested in hearing if this > is a "known issue" of some kind against either the > driver or someother piece of code, if there is > possibly some workaround that might be had (say, > reducing the size of the recieve ring??), and > so on. > > Thanks to everyone who works on these drivers - > though the only name I know is Donald Becker > (those driver pages have been really handy!). > > Regards, > > -Cedric > > - > | CCj/ClearLine - Unix/NT Administration and TCP/IP Network Services > | 118 Louisa Street, Kitchener, Ontario, N2H 5M3, 519-741-2157 > \____________________________________________________________________ > Cedric Puddy, IS Director cedric@thinkers.org > PGP Key Available at: http://www.thinkers.org/cedric > > | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the > | body of the mail, include only the text: > | unsubscribe this-list-name youraddress@wherever.org > | You will be unsubscribed as speedily as possible. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From sharkey@superk.physics.sunysb.edu Thu Dec 16 08:55:33 1999 Date: Thu Dec 16 08:55:33 1999 From: sharkey@superk.physics.sunysb.edu sharkey@superk.physics.sunysb.edu Subject: problems installing driver > I need help I can't seem to install the driver. > > Regards, > > > Alok Patel You will need to describe your problem more specifically if you expect to receive help from this list. And please don't send HTML mail. Eric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From avpatel@ozemail.com.au Thu Dec 16 19:19:06 1999 Date: Thu Dec 16 19:19:06 1999 From: Alok Patel avpatel@ozemail.com.au Subject: Problems compiling driver and installing it Hi all, Sorry bout the previous emails abiguity and the HTML format. Anyway I will describe the problems that I am having. I have the "latest" rtl8139.c file from the website. I have copied it onto my linux box and run the following lines to try and compile the code: gcc -o rtl8139.c gcc -o rtl8139.c rtl8139.o there was a line that someone gave me but I have lost it. As I am quite new to linux I was hoping that you could tell me the command line I should use to compile the code and then how I should install that module. I am running Debian Linux r2.1 on a Pentium II 300 w/128MB Ram. Thanks for your help. Regards, Alok Patel | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From homer@sgs.wh.tu-darmstadt.de Thu Dec 16 19:32:49 1999 Date: Thu Dec 16 19:32:49 1999 From: Holger Metschulat homer@sgs.wh.tu-darmstadt.de Subject: Oversized Ethernet Frame? Hi, we are using 3 ATI cards with the RTL8139 chip in a firewall. To do this, I had to set down the ring buffer size (RX_BUF_LEN_IDX) to 32k because otherwise the system could not allocate enough memory (is that okay?). Sometimes, especially when transmitting larges files with ftp through the firewall, the _egress_ card (the card that outputs the ftp data frames, the downstream side of the firewall) crashes with an oversized frame message: Dec 11 17:45:02 fsz-gw kernel: eth0: interrupt status=0x0001 new intstat=0x0000. Dec 11 17:45:02 fsz-gw kernel: eth0: In rtl8129_rx(), current 7300 BufAddr 0088, free to 72f0, Cmd 0c. Dec 11 17:45:02 fsz-gw kernel: eth0: rtl8129_rx() status bc3a6ebb, size bc3a, cur 7300. Dec 11 17:45:02 fsz-gw kernel: eth0: Frame contents bb 6e 3a bc 9f 15 37 c3 4e 61 4a 97 dd 1a 4b 25 4e 72 e7 e7 b3 f0 5e 86 42 a1 b1 97 94 d9 32 d8 38 72 72 ff bd ec 41 a6 ae 37 7d 0a 70 6e ca e1 94 44 35 70 ef f3 d9 ad 63 fa 79 6e 76 99 b1 67 6d b7 1b 6f 39 c1. Dec 11 17:45:02 fsz-gw kernel: eth0: Oversized Ethernet frame, status bc3a6ebb! Dec 11 17:45:02 fsz-gw kernel: eth0: Done rtl8129_rx(), current 2f40 BufAddr 0088, free to 2f30, Cmd 0d. Dec 11 17:45:02 fsz-gw kernel: eth0: interrupt status=0x0000 new intstat=0x0000. Dec 11 17:45:02 fsz-gw kernel: eth0: exiting interrupt, intr_status=0x4000000. As you can see, the driver gets garbage data from the chip (there is not even a hint on a valid ethernet frame in the logged frame contents). In my opinion the following problems could be the cause: - Switch is broken and sends corrupted packet back on line -> Card receives garbage. - Problems in the PCI system -> PCI data transfer between card and mainboard gets corrupted - driver problem - chip problem The card is then locked, so it has to be reinitialized with ifconfig. Anyone has a clue? -- Gruss * Holger Metschulat Holger * e-mail: homer@sgs.wh.tu-darmstadt.de * http://www.sgs.wh.tu-darmstadt.de/homer ** Who the hell is General Failure, and why is he reading my hard disk? ** | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From homer@sgs.wh.tu-darmstadt.de Thu Dec 16 19:36:20 1999 Date: Thu Dec 16 19:36:20 1999 From: Holger Metschulat homer@sgs.wh.tu-darmstadt.de Subject: "could not allocate 65535 byte recieve ring" messages Hi, > The message "Could not allocate 65535 byte recieve ring" > comes up occationally on boot (accompanied by the card I am using three NICs in one PC; setting RX_BUF_LEN_IDX to 3 in the file rtl8139.c helped with this message, but I get a problem during the usage of the card (see other mail); I don't know if there is a correlation between the two problems. -- Gruss * Holger Metschulat Holger * e-mail: homer@sgs.wh.tu-darmstadt.de * http://www.sgs.wh.tu-darmstadt.de/homer ** Who the hell is General Failure, and why is he reading my hard disk? ** | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From shh@ricochet.net Thu Dec 16 19:55:51 1999 Date: Thu Dec 16 19:55:51 1999 From: shh@ricochet.net shh@ricochet.net Subject: Cannot find the second card.. I compiled the rtl8139.c driver and installed it on my linux box. I have 2 rtl8139 cards in my machine. Freebsd can recognise both these cards however on linux i can see only one card. I am unable to find the second RealTek 8139 card with the latest driver. Any pointer will greatly help. Thanks. Shiv Dec 16 16:39:52 localhost kernel: rtl8139.c:v1.08 6/25/99 Donald Becker http://c esdis.gsfc.nasa.gov/linux/drivers/rtl8139.html Dec 16 16:39:52 localhost kernel: rtl8139.c:v1.08 6/25/99 Donald Becker http://c esdis.gsfc.nasa.gov/linux/drivers/rtl8139.html Dec 16 16:39:52 localhost kernel: eth0: RealTek RTL8139 Fast Ethernet at 0xd000, IRQ 11, 00:40:c7:87:04:76. Dec 16 16:39:52 localhost kernel: eth0: Media type forced to Full Duplex. Dec 16 16:39:52 localhost kernel: eth0: Setting full-duplex based on auto-negoti ated partner ability 0000. | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From cedric@itactics.itactics.com Fri Dec 17 00:06:15 1999 Date: Fri Dec 17 00:06:15 1999 From: Cedric Puddy cedric@itactics.itactics.com Subject: "could not allocate 65535 byte recieve ring" messages On Fri, 17 Dec 1999, Holger Metschulat wrote: > Hi, > > > The message "Could not allocate 65535 byte recieve ring" > > comes up occationally on boot (accompanied by the card > > I am using three NICs in one PC; setting RX_BUF_LEN_IDX to 3 in the file > rtl8139.c helped with this message, but I get a problem during the usage of > the card (see other mail); I don't know if there is a correlation between > the two problems. I am unaware of instances were a card has failed during normal operation, once initialized. I also am using these card for firewall work, and they are/were _so_ cheap... I can get a card to fail once it's operating, usually by merely re-ifconfiging it. I will have to try reducing the buffer size, since it you mention that you where able to do that without rendering the driver i inoperable. I understand though, that this did not remove the problem entirely. I should add that I in fact have three card in many systems - I've been buying a board that has on onboard Intel EExpress Pro 10/100 card. I have not had any problems to date with Intel NIC or the driver, though who knows what would happen if I loaded a system up with PCI Intel NICs... I get the impression that the same thing might happen. Regards all, -Cedric - | CCj/ClearLine - Unix/NT Administration and TCP/IP Network Services | 118 Louisa Street, Kitchener, Ontario, N2H 5M3, 519-741-2157 \____________________________________________________________________ Cedric Puddy, IS Director cedric@thinkers.org PGP Key Available at: http://www.thinkers.org/cedric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From osb19@tid.es Fri Dec 17 04:14:14 1999 Date: Fri Dec 17 04:14:14 1999 From: Orestes =?iso-8859-1?Q?S=E1nchez?= Benavente osb19@tid.es Subject: Problem with Realtek 8139 and MB Intel 440BX Hi. I have installed RedHat 6.1 with kernel 2.2.12-20, but network card is not activated. Is there any special option I must pass to the kernel? Thank you. -- Orestes Sánchez Benavente Grupo Apex, S.A. osb19@tid.es Agastia, 60 bajo 28034 MADRID Telefonica I+D Teléfono: 91-744-43-05 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From tegtmeier@ngate.de Fri Dec 17 06:27:37 1999 Date: Fri Dec 17 06:27:37 1999 From: Jan Tegtmeier tegtmeier@ngate.de Subject: Oversized Ethernet Frame? Buggy 8139-Chipset! Hi, >Dec 11 17:45:02 fsz-gw kernel: eth0: interrupt status=0x0001 new >intstat=0x0000. >Dec 11 17:45:02 fsz-gw kernel: eth0: In rtl8129_rx(), current 7300 BufAddr >0088, free to 72f0, Cmd 0c. >Dec 11 17:45:02 fsz-gw kernel: eth0: rtl8129_rx() status bc3a6ebb, size >bc3a, cur 7300. >Dec 11 17:45:02 fsz-gw kernel: eth0: Frame contents bb 6e 3a bc 9f 15 37 >c3 4e 61 4a 97 dd 1a 4b 25 4e >72 e7 e7 b3 f0 5e 86 42 a1 b1 97 94 d9 32 d8 >38 72 72 ff bd ec 41 a6 ae 37 7d 0a 70 6e ca e1 94 44 35 >70 ef f3 d9 ad 63 >fa 79 6e 76 99 b1 67 6d b7 1b 6f 39 c1. >Dec 11 17:45:02 fsz-gw kernel: eth0: Oversized Ethernet frame, status >bc3a6ebb! >Dec 11 17:45:02 fsz-gw kernel: eth0: Done rtl8129_rx(), current 2f40 >BufAddr 0088, free to 2f30, Cmd 0d. >Dec 11 17:45:02 fsz-gw kernel: eth0: interrupt status=0x0000 new >intstat=0x0000. >Dec 11 17:45:02 fsz-gw kernel: eth0: exiting interrupt, >intr_status=0x4000000. It looks the same at a few of our systems. We have some webserver running with the LanTech FastNet/TX with the Rtl8139-Chipset. Sometimes - often if there is much load on the nic, e.g. installing linux over nfs - the card stops responding to anything. The card doesn't even answer to Arp-Requests of other hosts. In the logfiles I found similiar entries: kernel: eth0: Oversized Ethernet frame, status 46424548! kernel: eth0: Oversized Ethernet frame, status ffffffff! kernel: eth0: Oversized Ethernet frame, status ffff! kernel: eth0: Oversized Ethernet frame, status 8e9d11c! kernel: eth0: Oversized Ethernet frame, status 865e865e! The systems produces these messages with always different status-code for about 24h (until we shut down that host) about every 1-10 seconds. >As you can see, the driver gets garbage data from the chip (there is not >even a hint on a valid ethernet frame in the logged frame contents). In my >opinion the following problems could be the cause: > >- Switch is broken and sends corrupted packet back on line -> Card receives > garbage. >- Problems in the PCI system -> PCI data transfer between card and mainboard >gets corrupted >- driver problem >- chip problem I heard that the chip has problems with some pci-chipsets of 486 mainboards... but I have also seen that problem on some pentium-systems so it is not the only problem the 8139 has :( It is not the driver! We have also some hosts running under Windows NT 4.0 Server having exactly the same problem (only the /var/log/messages is missing ;-) and with the handicap that it is not possible to reinitialize the devicedriver without a system-shutdown. >The card is then locked, so it has to be reinitialized with ifconfig. I thought about implementing a detection-function for the rtl8193.c that automatically reinitializes the chipset... but I don't habe the time to do so. Has anybody else done this or something similiar or could maybe do this? Best regards, Jan Tegtmeier (tegtmeier@ngate.de) -- -- NetGate Internetservice Web: http://www.ngate.de/ | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From sharkey@superk.physics.sunysb.edu Fri Dec 17 07:50:26 1999 Date: Fri Dec 17 07:50:26 1999 From: sharkey@superk.physics.sunysb.edu sharkey@superk.physics.sunysb.edu Subject: Problems compiling driver and installing it > Sorry bout the previous emails abiguity and the HTML format. Anyway I will > describe the problems that I am having. > > I have the "latest" rtl8139.c file from the website. > > I have copied it onto my linux box and run the following lines to try and > compile the code: > > gcc -o rtl8139.c That won't work. > gcc -o rtl8139.c rtl8139.o That won't either. "-o" means output file name. rtl8139.c is the input file name. You'd just overwrite your source with those commands. At least you would if gcc had anything to compile. > there was a line that someone gave me but I have lost it. > > As I am quite new to linux I was hoping that you could tell me the command > line I should use to compile the code and then how I should install that > module. > > I am running Debian Linux r2.1 on a Pentium II 300 w/128MB Ram. Did you compile your own kernel or are you using the standard Debian kernel? If you're using one of the standard Debian kernels, then I would recommend using the precompiled module provided by Debian. You may already have it installed and not know it. Look and see if you have /lib/modules//net/rtl8139.o where is the version of the kernel you are running. If you don't know what that is, you can find out with "uname -a". If this file is there, you can use it without compiling/installing anything. Just "insmod rtl8129" and you're done. If you compile your own kernels, I recommend using the driver version distributed with the kernel. It's not the latest version, but, it might be good enough. Select "Prompt for experimental" in the general configuration section, and then the driver for the RTL will appear with the rest of the network drivers and you can just compile it into your own kernel. If you need the latest version of the driver, either because you have experienced some bug or just want to have the very latest version, then follow the compilation instructions on this page: http://cesdis.gsfc.nasa.gov/linux/misc/modules.html Eric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From sharkey@superk.physics.sunysb.edu Fri Dec 17 08:23:36 1999 Date: Fri Dec 17 08:23:36 1999 From: sharkey@superk.physics.sunysb.edu sharkey@superk.physics.sunysb.edu Subject: Problem with Realtek 8139 and MB Intel 440BX > I have installed RedHat 6.1 with kernel 2.2.12-20, but network card is > not activated. Is there any special option I must pass to the kernel? I'm not sure how Red Hat manages its modules, but, I'd try "insmod rtl8139" at the command line as root. If this works, then you probably need to edit your conf.modules/modules.conf file in /etc. Eric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From sharkey@superk.physics.sunysb.edu Fri Dec 17 09:18:09 1999 Date: Fri Dec 17 09:18:09 1999 From: sharkey@superk.physics.sunysb.edu sharkey@superk.physics.sunysb.edu Subject: Problem with Realtek 8139 and MB Intel 440BX > sharkey@superk.physics.sunysb.edu wrote: > > > > > I have installed RedHat 6.1 with kernel 2.2.12-20, but network card is > > > not activated. Is there any special option I must pass to the kernel? > > > > I'm not sure how Red Hat manages its modules, but, I'd try "insmod rtl8139" > > at the command line as root. If this works, then you probably need to > > edit your conf.modules/modules.conf file in /etc. > > > > Eric > > The kernel automatically loads modules, so there is no need for the > manual insmod. > > I tried to load it manually and I got a IRQ 0 problem. Check /proc/pci. See what IRQ is being reported by the BIOS for this card. If it says zero there, you'll need to either change your bios settings or move the card to a new slot to get a real IRQ. Or your card is just whacked... Eric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From osb19@tid.es Fri Dec 17 10:31:48 1999 Date: Fri Dec 17 10:31:48 1999 From: Orestes =?iso-8859-1?Q?S=E1nchez?= Benavente osb19@tid.es Subject: Problem with Realtek 8139 and MB Intel 440BX sharkey@superk.physics.sunysb.edu wrote: > > > sharkey@superk.physics.sunysb.edu wrote: > > > > > > > I have installed RedHat 6.1 with kernel 2.2.12-20, but network card is > > > > not activated. Is there any special option I must pass to the kernel? > > > > > > I'm not sure how Red Hat manages its modules, but, I'd try "insmod rtl8139" > > > at the command line as root. If this works, then you probably need to > > > edit your conf.modules/modules.conf file in /etc. > > > > > > Eric > > > > The kernel automatically loads modules, so there is no need for the > > manual insmod. > > > > I tried to load it manually and I got a IRQ 0 problem. > > Check /proc/pci. See what IRQ is being reported by the BIOS for this > card. If it says zero there, you'll need to either change your bios settings > or move the card to a new slot to get a real IRQ. /proc/pci says nothing about IRQs. I thought it was right, because this card is PnP, isn't it? > Or your card is just whacked... The card works with Windows 98. Funny, isn't it? :^) Bye. -- Orestes Sánchez Benavente Grupo Apex, S.A. osb19@tid.es Agastia, 60 bajo 28034 MADRID Telefonica I+D Teléfono: 91-744-43-05 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From sharkey@superk.physics.sunysb.edu Fri Dec 17 10:50:55 1999 Date: Fri Dec 17 10:50:55 1999 From: sharkey@superk.physics.sunysb.edu sharkey@superk.physics.sunysb.edu Subject: Problem with Realtek 8139 and MB Intel 440BX > > > I tried to load it manually and I got a IRQ 0 problem. > > > > Check /proc/pci. See what IRQ is being reported by the BIOS for this > > card. If it says zero there, you'll need to either change your bios settings > > or move the card to a new slot to get a real IRQ. > > /proc/pci says nothing about IRQs. I thought it was right, because this > card is PnP, isn't it? You did say this was a RTL8139 didn't you? AFAIK, all RTL8139 based cards are PCI based. There are no ISA cards with the 8139. PCI cards get their IRQ's assigned by the BIOS. This is different than ISA P&P. If your /proc/pci doesn't say anything about IRQ's, then your whole system is whacked. Here's a sample of what the relevant section should look like. Bus 0, device 10, function 0: Ethernet controller: Realtek 8139 (rev 16). Medium devsel. Fast back-to-back capable. IRQ 12. Master Capable. Latency=64. Min Gnt=32.Max Lat=64. I/O at 0xec00 [0xec01]. Non-prefetchable 32 bit memory at 0xea002000 [0xea002000]. > > Or your card is just whacked... > > The card works with Windows 98. Funny, isn't it? :^) I haven't yet determined if Windows 98 is better classified as funny or sad. Eric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From homer@sgs.wh.tu-darmstadt.de Fri Dec 17 12:57:39 1999 Date: Fri Dec 17 12:57:39 1999 From: Holger Metschulat homer@sgs.wh.tu-darmstadt.de Subject: Oversized Ethernet Frame? Buggy 8139-Chipset! Hi all, > of other hosts. In the logfiles I found similiar entries: > > kernel: eth0: Oversized Ethernet frame, status 46424548! I compiled my module with debug set to 100, so my output is a bit more noisy. But it shows that no ethernet frame was received at all. > mainboards... but I have also seen that problem on some pentium-systems so > it is not the only problem the 8139 has :( We are running on a Pentium I system. > It is not the driver! We have also some hosts running under Windows NT 4.0 > Server having exactly the same problem (only the /var/log/messages is So is there a bug statement from the chipset's manufacturer? -- Gruss * Holger Metschulat Holger * e-mail: homer@sgs.wh.tu-darmstadt.de * http://www.sgs.wh.tu-darmstadt.de/homer ** Who the hell is General Failure, and why is he reading my hard disk? ** | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From osb19@tid.es Fri Dec 17 14:58:44 1999 Date: Fri Dec 17 14:58:44 1999 From: Orestes =?iso-8859-1?Q?S=E1nchez?= Benavente osb19@tid.es Subject: Problem with Realtek 8139 and MB Intel 440BX sharkey@superk.physics.sunysb.edu wrote: > > > I have installed RedHat 6.1 with kernel 2.2.12-20, but network card is > > not activated. Is there any special option I must pass to the kernel? > > I'm not sure how Red Hat manages its modules, but, I'd try "insmod rtl8139" > at the command line as root. If this works, then you probably need to > edit your conf.modules/modules.conf file in /etc. > > Eric The kernel automatically loads modules, so there is no need for the manual insmod. I tried to load it manually and I got a IRQ 0 problem. Thank you. -- Orestes Sánchez Benavente Grupo Apex, S.A. osb19@tid.es Agastia, 60 bajo 28034 MADRID Telefonica I+D Teléfono: 91-744-43-05 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From vishvesh@hotmail.com Mon Dec 20 18:59:13 1999 Date: Mon Dec 20 18:59:13 1999 From: vishvesh@hotmail.com vishvesh@hotmail.com Subject: problem This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF4B75.1ACECAC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hi, i am vishvesh from india. i am working as network engg & using Redhat linux from past 1 year we purches a new d-link card DFE-538TX a fast ethernet card i am using redhat linux 6.1 with latest kernal the card is detected as pnp card at bootup & linux detected as rtl8139 but we are unable to ping other m/c throu linux=20 the card is working fine & checked with ifconfig -a for card information i tried with recompiling a new kernal also i am using d-link switch=20 pl provide some help vishvesh ------=_NextPart_000_0005_01BF4B75.1ACECAC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hi,
i am vishvesh from india.
i am working as network engg & = using Redhat=20 linux from past 1 year
we purches a new d-link card DFE-538TX = a fast=20 ethernet card
i am using redhat linux 6.1 with latest = kernal
the card is detected as pnp card at = bootup &=20 linux detected as rtl8139
but we are unable to ping other m/c = throu linux=20
the card is working fine & checked = with=20 ifconfig -a for card information
i tried with recompiling a new kernal=20 also
i am using d-link switch
pl provide some help
 
vishvesh
------=_NextPart_000_0005_01BF4B75.1ACECAC0-- | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From sharkey@superk.physics.sunysb.edu Tue Dec 21 12:52:24 1999 Date: Tue Dec 21 12:52:24 1999 From: sharkey@superk.physics.sunysb.edu sharkey@superk.physics.sunysb.edu Subject: problem > hi, > i am vishvesh from india. > i am working as network engg & using Redhat linux from past 1 year > we purches a new d-link card DFE-538TX a fast ethernet card > i am using redhat linux 6.1 with latest kernal > the card is detected as pnp card at bootup & linux detected as rtl8139 > but we are unable to ping other m/c throu linux=20 It could be a routing or DNS problem. Are you passing an IP address or hostname as an argument to the ping command? Does "route -n" report the proper routing table you expect? Eric | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From osb19@tid.es Tue Dec 21 20:42:35 1999 Date: Tue Dec 21 20:42:35 1999 From: Orestes =?iso-8859-1?Q?S=E1nchez?= Benavente osb19@tid.es Subject: problem > vishvesh@hotmail.com wrote: > > hi, > i am vishvesh from india. > i am working as network engg & using Redhat linux from past 1 year > we purches a new d-link card DFE-538TX a fast ethernet card > i am using redhat linux 6.1 with latest kernal > the card is detected as pnp card at bootup & linux detected as rtl8139 > but we are unable to ping other m/c throu linux > the card is working fine & checked with ifconfig -a for card > information > i tried with recompiling a new kernal also > i am using d-link switch > pl provide some help > > vishvesh Hello. Have you tried "cat /proc/pci"? This is an extract of mine's: Ethernet controller: Realtek 8139 (rev 16). Medium devsel. Fast back-to-back capable. IRQ 0. Master Capable. Latency=32. Min Gnt=32.Max Lat=64. I/O at 0xa800 [0xa801]. Non-prefetchable 32 bit memory at 0xe1000000 [0xe1000000]. Look at the IRQ. If there is no IRQ message or the IRQ is 0, I have had the same problem, but it was a BIOS configuration problem. There is BIOS option called something like "Do you have a PnP operating system?". When this option is on, the BIOS DOES NOT assign IRQ nor addresses to some devices: it delegates it to the OS. Linux is not fully PnP, so it can manage it. If you turn the option off, the BIOS manage the resource asignment and the card get its IRQ. If the IRQ is right in the pci message, edit the file /etc/conf.modules and add option XXXXXX debug=10 for your card module. This options adds tons of debug messages to the /var/log/messages. Then try to unload manually the module with: ifdown eth0 modprobe -r XXXXX where XXXX is the module for your network card. Then try to load it again with: modprobe XXXXXX ifup eth0 Perhaps your kernel version is not syncronized with your modules version. Bye. -- Orestes Sánchez Benavente Grupo Apex, S.A. osb19@tid.es Agastia, 60 bajo 28034 MADRID Telefonica I+D Teléfono: 91-744-43-05 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible. From ivan.duplantie@sympatico.ca Tue Dec 28 15:10:29 1999 Date: Tue Dec 28 15:10:29 1999 From: Ivan ivan.duplantie@sympatico.ca Subject: subcribe | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the | body of the mail, include only the text: | unsubscribe this-list-name youraddress@wherever.org | You will be unsubscribed as speedily as possible.