From narong.j@cdg.co.th Sun, 2 Sep 2001 21:29:41 +0700
Date: Sun, 2 Sep 2001 21:29:41 +0700
From: Narong Jaturonkaosan narong.j@cdg.co.th
Subject: [realtek] Redhat7 with REALTEK
This is a multi-part message in MIME format.
------=_NextPart_000_0009_01C133F6.607A8C60
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_000A_01C133F6.607A8C60"
------=_NextPart_001_000A_01C133F6.607A8C60
Content-Type: text/plain;
charset="windows-874"
Content-Transfer-Encoding: quoted-printable
HI ALL,
I cannot use REDHAT7 with Ethernet card d-link
DFE-538TX (using Realtext rtl8139.c). I tried 3 weeks
ago. But I get some errors. Please suggest me. I must=20
use this for my Thesis at Chulalongkorn University,
Bangkok Thailand. (Attached file show some error while
compiling).
Regards,
Narong Jaturonkaosan
Chulalongkorn University
Bangkok Thailand.
------=_NextPart_001_000A_01C133F6.607A8C60
Content-Type: text/html;
charset="windows-874"
Content-Transfer-Encoding: quoted-printable
HI ALL,
I =
cannot use=20
REDHAT7 with Ethernet card d-link
DFE-538TX (using Realtext =20
rtl8139.c). I tried 3 weeks
ago. But I get some errors. Please suggest =
me. I must=20
use this for my Thesis at =
Chulalongkorn=20
University,
Bangkok Thailand. (Attached file show some =
error=20
while
compiling).
Regards,
Narong Jaturonkaosan
Chulalongkorn University
Bangkok =
Thailand.
------=_NextPart_001_000A_01C133F6.607A8C60--
------=_NextPart_000_0009_01C133F6.607A8C60
Content-Type: application/octet-stream;
name="Err1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="Err1"
gcc -D__KERNEL__ -DMODULE -O2 -m486 -Wall -finline-functions -I =
/usr/src/linux/include -DMODVERSIONS -c -o rtl8139.o rtl8139.c
rtl8139.c: In function `rtl8129_open':
rtl8139.c:675: structure has no member named `tbusy'
rtl8139.c:676: structure has no member named `interrupt'
rtl8139.c:677: structure has no member named `start'
rtl8139.c: In function `rtl8129_timer':
rtl8139.c:777: structure has no member named `interrupt'
rtl8139.c:783: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_tx_timeout':
rtl8139.c:910: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_start_xmit':
rtl8139.c:940: structure has no member named `tbusy'
rtl8139.c:963: structure has no member named `tbusy'
rtl8139.c:967: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_interrupt':
rtl8139.c:992: structure has no member named `interrupt'
rtl8139.c:995: structure has no member named `interrupt'
rtl8139.c:1072: structure has no member named `tbusy'
rtl8139.c:1152: structure has no member named `interrupt'
rtl8139.c: In function `rtl8129_close':
rtl8139.c:1275: structure has no member named `start'
rtl8139.c:1276: structure has no member named `tbusy'
rtl8139.c: In function `rtl8129_get_stats':
rtl8139.c:1354: structure has no member named `start'
make: *** [rtl8139.o] Error 1
------=_NextPart_000_0009_01C133F6.607A8C60--
From fluido@fluido.as Sun, 2 Sep 2001 18:59:18 +0200
Date: Sun, 2 Sep 2001 18:59:18 +0200
From: Carlo E. Prelz fluido@fluido.as
Subject: [realtek] Changing RX_BUF_LEN_IDX to 3 in 8139too stops driver from working...
Hello all. I already wrote to the list in the past to look for some
help im identifying the reason why a single-board computer with a
RTL-8139C chip had lower-than-expected performance. My conclusion has
been that the responsible is the CPU (a 233MHz NatSemi Geode) that is
not sufficient for the task. But today I came back to the problem, and
I tried to increase the receive buffer to see if this changed
something.
Well, I changed RX_BUF_LEN_IDX from 2 to 3 (should bump the in-memory
receive ring from 32k to 64k) and with this change the new kernel was
not able to talk to the network anymore (could not find the
nfs-mounted root partition).
Does anybody know why? And, what is the correct way to increase the
receive buffer?
Thanks!
Carlo (now running 2.4.9)
--
* Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as che bisogno ci sarebbe
* di parlare tanto di amore e di rettitudine? (Chuang-Tzu)
From marcelo-rtl@ucongreso.edu.ar Mon, 3 Sep 2001 16:02:43 -0300
Date: Mon, 3 Sep 2001 16:02:43 -0300
From: Marcelo Roccasalva marcelo-rtl@ucongreso.edu.ar
Subject: [realtek] rtl8139 and UltraSparc 5
Hello,
I'm trying to use a rtl8139 in an UltraSparc 5 with little success... I have
RedHat 6.2 installed, using the stock kernel 2.2.19 rpm (64 bits).
My dmesg told me about latency=0 so I tried several values, 255 being the
better, but when I ifup eth1, I get no more than 10 pings ok, and the iface
gets silent. With short latencies (<64) I get "packet too big" messages. I
don't have any MAC address problems...
Is there any kind of BIOS issues with this hardware or something I must know
about?
TIA,
--
Marcelo
From sebastian@haberey.de Tue, 4 Sep 2001 16:09:31 +0200
Date: Tue, 4 Sep 2001 16:09:31 +0200
From: Sebastian Haberey sebastian@haberey.de
Subject: [realtek] rtl8139.o - Tx queue start entry xxx dirty entry yyy
Hi,
I'm experiencing a problem with rtl8139.o under SuSE linux 7.1 mentioned
before in this list; however I didn't manage to find the solution.
Symptoms: when under high load (transferring 30Mb files @ 100Mbit/s) transfer
stops for about 5 to 10 seconds and the log shows entries like
Sep 4 15:34:05 firewall kernel: eth0: Tx queue start entry 15639 dirty
entry 15639.
Sep 4 15:34:05 firewall kernel: eth0: Tx descriptor 0 is 8008a03c.
Sep 4 15:34:05 firewall kernel: eth0: Tx descriptor 1 is 8008a03c.
Sep 4 15:34:05 firewall kernel: eth0: Tx descriptor 2 is 8008a03c.
Sep 4 15:34:05 firewall kernel: eth0: Tx descriptor 3 is 8008a03c. (queue
head)
Sep 4 15:34:15 firewall kernel: eth0: Tx queue start entry 2275 dirty entry
2275.
Sep 4 15:34:15 firewall kernel: eth0: Tx descriptor 0 is 8008a03c.
Sep 4 15:34:15 firewall kernel: eth0: Tx descriptor 1 is 8008a03c.
Sep 4 15:34:15 firewall kernel: eth0: Tx descriptor 2 is 8008a03c.
Sep 4 15:34:15 firewall kernel: eth0: Tx descriptor 3 is 8008a03c. (queue
head)
and so on. I tried to revert to older SuSE 6.3 and SuSE 6.2 rtl8139.o
binaries - no success. The log still show the above entries.
Any ideas?
Sebastian Haberey
--
__ __
.-----. | |--.---.-.| |--.-----.----.-----.--.--.
|__ --|__| | _ || _ | -__| _| -__| | |
|_____|__|__|__|___._||_____|_____|__| |_____|___ |
|_____|
From shaikh_intekhab@hotmail.com Wed, 05 Sep 2001 04:55:01 +0000
Date: Wed, 05 Sep 2001 04:55:01 +0000
From: Intekhab-e-AAlum Shaikh shaikh_intekhab@hotmail.com
Subject: [realtek] Help on RealTek RTL 8139 Driver
Hi,
I am a beginner in linux.
I want to install the driver for 8139.
The web page is so confusing.
I have Red Hat Linux 7.1.
I have the rtl8139.c file.
Can someone explain the steps i should
perform to install the driver.
Shaikh
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
From sriram@vxl.co.in Wed, 5 Sep 2001 15:02:31 +0530
Date: Wed, 5 Sep 2001 15:02:31 +0530
From: Sriram sriram@vxl.co.in
Subject: [realtek] Need Help
This is a multi-part message in MIME format.
------=_NextPart_000_00B2_01C1361B.C9830B70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I am working on a embedded product. In that we are using AM186CH as =
the host and RTL8019AS as the Ethernet controller. I am having a problem =
, since the AM186CH is not having a interrupt controller which is 8259 =
compatible. As the reason the interrupt controller in AM186CH will not =
generate Interrupt Acknowledge Signal (IACK) to the device that had =
interrupted, Instead if the controller will jump to the corresponding =
interrupt vector if it service the interrupt request.Inorder to notify =
the RTL regarding the service of it's interrupt request, if i reset the =
corresponding interrupt bit in the Interrupt status register of the RTL =
will the RTL will treat it as interrupt acknowledge or it will aware =
that it's interrupt request to AMD is serviced by the host. Can anybody =
help me in this regard.
with regards,
sriramkumar. R
R.Sriramkumar
Software Engineer
VXL Etech
17 House of Excellence
Electronic City
Bangalore 561 229
INDIA
sriram@vxl.co.in
www.vxletech.com
------=_NextPart_000_00B2_01C1361B.C9830B70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I am working on a =
embedded=20
product. In that we are using AM186CH as the host and RTL8019AS as the =
Ethernet=20
controller. I am having a problem , since the AM186CH is not having a =
interrupt=20
controller which is 8259 compatible. As the reason the interrupt =
controller in=20
AM186CH will not generate Interrupt Acknowledge Signal (IACK) to the =
device that=20
had interrupted, Instead if the controller will jump to the =
corresponding=20
interrupt vector if it service the interrupt request.Inorder to notify =
the RTL=20
regarding the service of it's interrupt request, if i reset the =20
corresponding interrupt bit in the Interrupt status register of the RTL =
will=20
the RTL will treat it as interrupt acknowledge or it will aware that =
it's=20
interrupt request to AMD is serviced by the host. Can anybody help me in =
this=20
regard.
with regards,
sriramkumar. R
R.Sriramkumar
Software =
Engineer
VXL=20
Etech
17 House of Excellence
Electronic City
Bangalore 561=20
229
INDIA
------=_NextPart_000_00B2_01C1361B.C9830B70--
From becker@scyld.com Thu, 6 Sep 2001 01:35:15 -0400 (EDT)
Date: Thu, 6 Sep 2001 01:35:15 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] Redhat7 with REALTEK
On Sun, 2 Sep 2001, Narong Jaturonkaosan wrote:
> I cannot use REDHAT7 with Ethernet card d-link
> DFE-538TX (using Realtext rtl8139.c). I tried 3 weeks
> ago. But I get some errors. Please suggest me. I must
> use this for my Thesis at Chulalongkorn University,
> Bangkok Thailand. (Attached file show some error while
> compiling).
You must use the updated driver and (especially) the updated
kern_compat.h when compiling with a 2.4 kernel.
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, 6 Sep 2001 01:37:45 -0400 (EDT)
Date: Thu, 6 Sep 2001 01:37:45 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] Changing RX_BUF_LEN_IDX to 3 in 8139too stops driver
from working...
On Sun, 2 Sep 2001, Carlo E. Prelz wrote:
> Hello all. I already wrote to the list in the past to look for some
> help im identifying the reason why a single-board computer with a
> RTL-8139C chip had lower-than-expected performance. My conclusion has
> been that the responsible is the CPU (a 233MHz NatSemi Geode) that is
> not sufficient for the task. But today I came back to the problem, and
> I tried to increase the receive buffer to see if this changed
> something.
>
> Well, I changed RX_BUF_LEN_IDX from 2 to 3 (should bump the in-memory
> receive ring from 32k to 64k) and with this change the new kernel was
> not able to talk to the network anymore (could not find the
> nfs-mounted root partition).
...
> Carlo (now running 2.4.9)
I'm guessing that you are using the "8139too" driver. I suspect that it
does not correctly handle the changed wrap behavior of the chip with a
64KB receive buffer vs. a 8, 16 or 32KB buffer.
You should contact the last person to modify that driver to have it fixed.
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, 6 Sep 2001 01:40:38 -0400 (EDT)
Date: Thu, 6 Sep 2001 01:40:38 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] rtl8139 and UltraSparc 5
On Mon, 3 Sep 2001, Marcelo Roccasalva wrote:
> I'm trying to use a rtl8139 in an UltraSparc 5 with little success... I have
> RedHat 6.2 installed, using the stock kernel 2.2.19 rpm (64 bits).
What driver? And what version number?
> My dmesg told me about latency=0 so I tried several values, 255 being the
> better, but when I ifup eth1, I get no more than 10 pings ok, and the iface
> gets silent. With short latencies (<64) I get "packet too big" messages. I
> don't have any MAC address problems...
A few possible issues:
Endian correction (unlikely, if a few packets are getting through)
Burst length problems (although I don't know of any specific Sparc bugs)
A problem with the ring wrap (we need to know the driver version).
This could be interacting with the DMA-able page allocation on the Sparc
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, 6 Sep 2001 01:41:50 -0400 (EDT)
Date: Thu, 6 Sep 2001 01:41:50 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] rtl8139.o - Tx queue start entry xxx dirty entry yyy
On Tue, 4 Sep 2001, Sebastian Haberey wrote:
> I'm experiencing a problem with rtl8139.o under SuSE linux 7.1 mentioned
> before in this list; however I didn't manage to find the solution.
What driver version?
What is the detection message?
Is this an SMP or uniprocessor? A SMP kernel?
> Symptoms: when under high load (transferring 30Mb files @ 100Mbit/s) transfer
> stops for about 5 to 10 seconds and the log shows entries like
>
> Sep 4 15:34:05 firewall kernel: eth0: Tx queue start entry 15639 dirty
> entry 15639.
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 marcelo-rtl@ucongreso.edu.ar Thu, 6 Sep 2001 20:01:39 -0300
Date: Thu, 6 Sep 2001 20:01:39 -0300
From: Marcelo Roccasalva marcelo-rtl@ucongreso.edu.ar
Subject: [realtek] rtl8139 and UltraSparc 5
Hello Donald,
On Thu, Sep 06, 2001 at 01:40:38AM -0400, Donald Becker wrote:
> On Mon, 3 Sep 2001, Marcelo Roccasalva wrote:
>
> > I'm trying to use a rtl8139 in an UltraSparc 5 with little success... I have
> > RedHat 6.2 installed, using the stock kernel 2.2.19 rpm (64 bits).
>
> What driver? And what version number?
The relevant part of kernel messages:
sunhme.c:v1.10 27/Jan/99 David S. Miller (davem@caipfs.rutgers.edu)
eth0: HAPPY MEAL (PCI/CheerIO) 10/100BaseT Ethernet 08:00:20:ab:d2:96
The PCI BIOS has not enabled the device at 2/8! Updating PCI command 0003->0007.
rtl8139.c:v1.07 5/6/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html
eth1: RealTek RTL8139 Fast Ethernet at 0xfffff9fe02000400, IRQ 6447936, 00:e0:7d:a8:b9:a2.
PCI latency timer (CFLT) is unreasonably low at 0. Setting to 64 clocks.
eth0: Link is up using internal transceiver at 100Mb/s, Half Duplex.
As you can see, there's an integrated sun device... I can't say what does the
message on the third line mean...
> > My dmesg told me about latency=0 so I tried several values, 255 being the
> > better, but when I ifup eth1, I get no more than 10 pings ok, and the iface
> > gets silent. With short latencies (<64) I get "packet too big" messages. I
> > don't have any MAC address problems...
>
> A few possible issues:
> Endian correction (unlikely, if a few packets are getting through)
> Burst length problems (although I don't know of any specific Sparc bugs)
> A problem with the ring wrap (we need to know the driver version).
> This could be interacting with the DMA-able page allocation on the Sparc
I've done a few more tests. Sniffing the cable while pinging _from_ the sparc I
can see the initial arp request and answer, and the echo req and echo reply,
but by the time the other machine tries to re-check mac address, the echo
replies are not heard anymore by the sparc, but the packets come and go along
the cable...
> 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
>
--
Marcelo
From becker@scyld.com Thu, 6 Sep 2001 20:19:43 -0400 (EDT)
Date: Thu, 6 Sep 2001 20:19:43 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] rtl8139 and UltraSparc 5
On Thu, 6 Sep 2001, Marcelo Roccasalva wrote:
> On Thu, Sep 06, 2001 at 01:40:38AM -0400, Donald Becker wrote:
> > On Mon, 3 Sep 2001, Marcelo Roccasalva wrote:
> >
> > > I'm trying to use a rtl8139 in an UltraSparc 5 with little success... I have
> > > RedHat 6.2 installed, using the stock kernel 2.2.19 rpm (64 bits).
> >
> > What driver? And what version number?
> The relevant part of kernel messages:
...
> rtl8139.c:v1.07 5/6/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html
> eth1: RealTek RTL8139 Fast Ethernet at 0xfffff9fe02000400, IRQ 6447936, 00:e0:7d:a8:b9:a2.
> PCI latency timer (CFLT) is unreasonably low at 0. Setting to 64 clocks.
> eth0: Link is up using internal transceiver at 100Mb/s, Half Duplex.
This message is not from my v1.07 driver. You are using a modified
driver, and I do not support modified code.
Perhaps someone else knows what the problem is.
> > A problem with the ring wrap (we need to know the driver version).
> > This could be interacting with the DMA-able page allocation on the Sparc
I suspect this...
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 daro@d1.nu Tue, 11 Sep 2001 14:10:46 +0200
Date: Tue, 11 Sep 2001 14:10:46 +0200
From: Daniel Rovaniemi daro@d1.nu
Subject: [realtek] Problems with Zonet 1200 CARDBUS CARD..
I Have tried to compile te realtek_cb module with the rtl8139.c
source but failed.
Then I tried the 8139too.c code that came with the kernel and it
compiled but complained about unused fuctions.
Copied the file to the pcmcia kernel drivers katalog and ran depmod.
Edited the pcmcia config file and adde the lines for the card.
When I insert the card the module dosen\t load, it reports an error...
"unresolved symbol synchronize_irq"
I use the stock kernel from Slackware 8.0 it\s version 2.4.5
/regards
Daniel
From yjjang@smallbig.com Tue, 18 Sep 2001 17:03:55 +0900
Date: Tue, 18 Sep 2001 17:03:55 +0900
From: yjjang yjjang@smallbig.com
Subject: [realtek] how to porting for arm7 (os-linux)
hello there,
I'd like to porting "realtek 8019 driver" for arm7.(OS is linux 2.2.14)
Please, Teach me how to porting into embeded linux.
I don't know how to handing linux.
I tried to porting times. but I failed.
kernel doesn't work about driver.
I will look forward to your help.
Thank you.
GooBye~~~.
From e_de_ruiter@hotmail.com Tue, 18 Sep 2001 10:39:11 +0200
Date: Tue, 18 Sep 2001 10:39:11 +0200
From: Eric de Ruiter e_de_ruiter@hotmail.com
Subject: [realtek] problems with heavy load
Hi
Is someone aware of the problems the 8139too driver has with heavy loaded
networks? I have a rtl8139 working in a server on a 10baseT network with a
current collision rate of over 20%! the 8139too driver gives me the
following output when having some traffic:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 68810 dirty entry 68806.
eth0: Tx descriptor 0 is 00002000.
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000. (queue head)
eth0: Tx descriptor 3 is 00002000.
eth0: media is unconnected, link down, or incompatible connection
this is very annoying since the card is down for sometime, no packets are
lost though.
Does someone have a solution to this problem or must I buy another
networkcard???
Thanx,
Eric
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
From timk@harbornet.com Tue, 18 Sep 2001 23:39:07 -0700
Date: Tue, 18 Sep 2001 23:39:07 -0700
From: tk timk@harbornet.com
Subject: [realtek] Device or resource busy
Hello,
I have a SMC 1211TX card with the rtl8139 chip. I had installed
RedHat6.2 and had my machine up a running with net access. For some
reason I can no longer access this netwrok card. I consistently get the
following message:
/tmp/rtl8139.o: init_module: Device or resource busy
Any ideas?
Tim
From becker@scyld.com Wed, 19 Sep 2001 09:59:45 -0400 (EDT)
Date: Wed, 19 Sep 2001 09:59:45 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] Device or resource busy
On Tue, 18 Sep 2001, tk wrote:
> I have a SMC 1211TX card with the rtl8139 chip. I had installed
> RedHat6.2 and had my machine up a running with net access. For some
> reason I can no longer access this netwrok card. I consistently get the
> following message:
> /tmp/rtl8139.o: init_module: Device or resource busy
Did your software or hardware configuration change?
If not, check that the board hasn't worked it way loose from the PCI slot.
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 boig@casitadelterror.com Thu, 20 Sep 2001 21:57:23 -0500
Date: Thu, 20 Sep 2001 21:57:23 -0500
From: Arquimedes Canedo boig@casitadelterror.com
Subject: [realtek] pcmcia realtek8139
Hello.
I have a problem with my laptop.
My laptop is a compaq 1202LA, i bought a PC CARD NIC, it has a
realtek8139 chip.
In windows works perfectly.
I use slackware/kernel 2.4.5, the problem is that i can't load the
8139too driver.
This is part of my dmesg
It seems that i have a irq conflict, i've tried to change the irq_list
parameters but nothing happens.
- dmesg
Linux PCMCIA Card Services 3.1.26
options : [pci] [cardbus]
Intel PCIC probe: <6>PCI:Found IRQ 11 for device 00:0b.0
PCI: The same IRQ used for device 00:07.2
TI 1410 rev 01 PCI-to-Cardbus at slot 00:0b, mem 0x10000000
host opts[0]: [ring][pci+serial irq] [pci irq 11] [lat 32/176] [bus
2/5]
PCI card interrupts, PCI status changes
cs: cb_alloc(bus2): vendor 0x10ec, device 0x8139
-end
if i try a 'cardctl ident'
dumps this :
Socket 0:
product info: "CardBus", "10/100Mbps Ethernet Card","",""
manfid: 0x0000, 0x024c
function: 6(network)
PCI id: 0x10ec, 0x8139
When I try to load the 8139too dumps this :
'modprobe 8139too'
/lib/modules/2.4.5/kernel/drivers/net/8139too.o.gz : init_module: No
such device
...: Hint: insmod errors can be caused by incorrect module parameters,
including IO or IRQ parameters
...: insmod 8139too failed
i've compiled the rtl8139-diag tool and dumps this :
...
Index #1: Found a RealTek RTL8139 adapter at 0.
This chip has not been assigned a valid IRQ, and will not function.
This must be fixed in the PCI BIOS setup. The device driver has no way
of changing the PCI IRQ settings.
..
This is my big problem. My BIOS a Phoenix4.0 Release 6 doesn't have
'ADVANCED OPTIONS', so i cannot change even PnP OS to OFF.
I can't change anything from my bios except the date and other minor
settings.
Please I need help to solve this problem
Thank You
Arquimedes Canedo
From john@jura47.org Fri, 21 Sep 2001 17:47:05 +0200
Date: Fri, 21 Sep 2001 17:47:05 +0200
From: John Donath john@jura47.org
Subject: [realtek] Confusion: rtl8139.o versus 8139too.o (Linux 2.4.9)
This is a multi-part message in MIME format.
--------------816C713C6F303F96D4DE6AAA
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi there,
I try to figure out which approach to use implementing a Linux
router with 3 RealTek 8139 chipset based NIC's. There seems to be quite
a lot confusion going on regarding 8139.o versus the concurring 8139too.o.
I had some bad and frustrating experiences with the 8139too driver on a
RH7.1 i386 system running kernel 2.4.9. I actually met problems with using
multiple of these cards at one box ...
I noticed Linux 2.4.x ships the 8139too driver but there seem to
be lots of people using Donald Beckers original rtl8139 driver. This leaves
me with a couple of questions:
1) Which of the two drivers mentioned above is
the preferred (and most stable) one on a Intel Linux 2.4.9 platform ??
2) Suppose Donald Beckers driver is the preferred
one, which obstacles will I encounter trying to get things compiled and
running on an i386 box using kernel 2.4.9 ??
3) Summarizing, which direction should I follow
??
Thanks a lot,
John Donath
--------------816C713C6F303F96D4DE6AAA
Content-Type: text/x-vcard; charset=us-ascii;
name="john.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for John Donath
Content-Disposition: attachment;
filename="john.vcf"
begin:vcard
n:Donath;John
tel;cell:+31629555308
tel;home:+31302672529
tel;work:+31629555308
x-mozilla-html:TRUE
url:http://www.marviq.com
org:MarviQ;Operations
adr:;;Ringpark Building Nachtwachtlaan 20;Amsterdam;;1058 EA;Netherlands
version:2.1
email;internet:donath@knoware.nl
title:System architect
x-mozilla-cpt:;0
fn:John Donath
end:vcard
--------------816C713C6F303F96D4DE6AAA--
From timk@harbornet.com Sun, 23 Sep 2001 12:34:28 -0700
Date: Sun, 23 Sep 2001 12:34:28 -0700
From: tk timk@harbornet.com
Subject: [realtek] Device or resource busy
Long story short,
I was having MB problems. I had this replaced. At some point either during
the problems or thereafter I booted linux and the auto-config whatever removed
this device. I have since reloaded Redhat but it still will not recognize
device.
I may have the card in a different slot now, but I tried moving the card
through all slots with no outcome.
I have also tried cold boot - no avail.
Funny, the card works fine in Windows. So, do these cards have flash-rom and
was it maybe flashed by windows? Or does windows and linux access this card
in different ways?
TK
Donald Becker wrote:
> On Tue, 18 Sep 2001, tk wrote:
>
> > I have a SMC 1211TX card with the rtl8139 chip. I had installed
> > RedHat6.2 and had my machine up a running with net access. For some
> > reason I can no longer access this netwrok card. I consistently get the
> > following message:
> > /tmp/rtl8139.o: init_module: Device or resource busy
>
> Did your software or hardware configuration change?
>
> If not, check that the board hasn't worked it way loose from the PCI slot.
>
> 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
>
> _______________________________________________
> realtek mailing list
> realtek@scyld.com
> http://www.scyld.com/mailman/listinfo/realtek
From becker@scyld.com Mon, 24 Sep 2001 03:35:06 -0400 (EDT)
Date: Mon, 24 Sep 2001 03:35:06 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] Device or resource busy
On Sun, 23 Sep 2001, tk wrote:
> I was having MB problems. I had this replaced. At some point either during
> the problems or thereafter I booted linux and the auto-config whatever removed
> this device. I have since reloaded Redhat but it still will not recognize
> device.
> I may have the card in a different slot now, but I tried moving the card
> through all slots with no outcome.
What does 'rtl8139-diag' report?
It may be that the PCI ID, which is stored in the EEPROM, has been corrupted.
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 timk@harbornet.com Mon, 24 Sep 2001 22:13:08 -0700
Date: Mon, 24 Sep 2001 22:13:08 -0700
From: tk timk@harbornet.com
Subject: [realtek] Device or resource busy
FYI,
Linux 2.2.14-5.0
PnP OS not enabled in Bios (Award Modular Bios v6.00PG)
I ran rtl8139-diag with the '-p' and '-t' options because it would not work
otherwise.
So, I first used the i/o address found in windows, where the card works:
./rtl8139-diag -t 2 -p 1400 -e >& diag-1.log
This returned the following which I piped into a file:
--------
rtl8139-diag.c:v2.04 8/08/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Assuming a SMC1211TX EZCard 10/100 (RealTek RTL8139) adapter at 0x1400.
Decoded EEPROM contents:
PCI IDs -- Vendor 0xffff, Device 0xffff.
PCI Subsystem IDs -- Vendor 0xffff, Device 0xffff.
PCI timer settings -- minimum grant 255, maximum latency 255.
General purpose pins -- direction 0xff value 0xff.
Station Address FF:FF:FF:FF:FF:FF.
Configuration register 0/1 -- 0xff / 0xff.
EEPROM active region checksum is 17e8.
-----
Then I looked at /proc/pci:
------
Bus 0, device 13, function 0:
Ethernet controller: Unknown vendor Unknown device (rev 16).
Vendor id=1. Device id=1211.
Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable.
Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0xdc00 [0xdc01].
Non-prefetchable 32 bit memory at 0xde008000 [0xde008000].
------
and used the i/o address of the card found there:
./rtl8139-diag -p 0xdc00 -t 2 -e >& diag-3.log
This returned the following which I piped into a file:
------
rtl8139-diag.c:v2.04 8/08/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Assuming a SMC1211TX EZCard 10/100 (RealTek RTL8139) adapter at 0xdc00.
Decoded EEPROM contents:
PCI IDs -- Vendor 0x0001, Device 0x1211.
PCI Subsystem IDs -- Vendor 0x1113, Device 0x1211.
PCI timer settings -- minimum grant 32, maximum latency 64.
General purpose pins -- direction 0xe1 value 0x10.
Station Address 00:E0:29:88:BC:C7.
Configuration register 0/1 -- 0x4d / 0xc2.
EEPROM active region checksum is 0798.
------
and adding -ee options gives:
------
rtl8139-diag.c:v2.04 8/08/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Assuming a SMC1211TX EZCard 10/100 (RealTek RTL8139) adapter at 0xdc00.
Decoded EEPROM contents:
PCI IDs -- Vendor 0x0001, Device 0x1211.
PCI Subsystem IDs -- Vendor 0x1113, Device 0x1211.
PCI timer settings -- minimum grant 32, maximum latency 64.
General purpose pins -- direction 0xe1 value 0x10.
Station Address 00:E0:29:88:BC:C7.
Configuration register 0/1 -- 0x4d / 0xc2.
EEPROM active region checksum is 0798.
EEPROM contents (64 words):
0x00: 8129 0001 1211 1113 1211 4020 e110 e000
0x08: 8829 c7bc 4d10 ffc2 8401 b388 58fa 8708
0x10: d843 ad38 d843 ad38 d843 ad38 d843 ad38
0x18: 0000 0000 0000 0000 0000 0000 0000 0000
0x20: 0000 0000 0000 0000 0000 0000 0000 0000
0x28: 0000 0000 0000 0000 0000 0000 0000 0000
0x30: 0000 0000 0000 0000 0000 0000 0000 0000
0x38: 0000 0000 0000 0000 0000 0000 0000 0000
------
So, now I am lost. The card appears to be found on a pci scan but linux and the
rtl8139 driver cannot access the card. What should be in the EEPROM?
Also, I noticed that IRQ=11 is assigned to both the ethernet card and a scsi card -
I believe IRQ sharing is now handled by OS's (Windows and Linux).
Thanks for any help, TK
Donald Becker wrote:
> On Sun, 23 Sep 2001, tk wrote:
>
> > I was having MB problems. I had this replaced. At some point either during
> > the problems or thereafter I booted linux and the auto-config whatever removed
> > this device. I have since reloaded Redhat but it still will not recognize
> > device.
> > I may have the card in a different slot now, but I tried moving the card
> > through all slots with no outcome.
>
> What does 'rtl8139-diag' report?
>
> It may be that the PCI ID, which is stored in the EEPROM, has been corrupted.
>
> 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
>
> _______________________________________________
> realtek mailing list
> realtek@scyld.com
> http://www.scyld.com/mailman/listinfo/realtek
From becker@scyld.com Tue, 25 Sep 2001 01:32:49 -0400 (EDT)
Date: Tue, 25 Sep 2001 01:32:49 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] Device or resource busy
On Mon, 24 Sep 2001, tk wrote:
> Linux 2.2.14-5.0
> PnP OS not enabled in Bios (Award Modular Bios v6.00PG)
Not important here..
> I ran rtl8139-diag with the '-p' and '-t' options because it would not work
> otherwise.
...
> Bus 0, device 13, function 0:
> Ethernet controller: Unknown vendor Unknown device (rev 16).
> Vendor id=1. Device id=1211.
Bad... the vendor ID is invalid.
> and used the i/o address of the card found there:
> ./rtl8139-diag -p 0xdc00 -t 2 -e >& diag-3.log
>
> This returned the following which I piped into a file:
> ------
> rtl8139-diag.c:v2.04 8/08/2001 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
> Assuming a SMC1211TX EZCard 10/100 (RealTek RTL8139) adapter at 0xdc00.
> Decoded EEPROM contents:
> PCI IDs -- Vendor 0x0001, Device 0x1211.
> PCI Subsystem IDs -- Vendor 0x1113, Device 0x1211.
> PCI timer settings -- minimum grant 32, maximum latency 64.
> General purpose pins -- direction 0xe1 value 0x10.
> Station Address 00:E0:29:88:BC:C7.
> Configuration register 0/1 -- 0x4d / 0xc2.
> EEPROM active region checksum is 0798.
Everything is OK except the checksum and the Vendor ID.
The Vendor ID has been corrupted -- it should be 0x1113.
Around line 635 in rtl8139-diag.c make the following change
}
}
+ new_ee_contents[1] = 0x1113;
/* To set another EEPROM value do new_ee_contents[xxx] = new_value; */
- if (set_hwaddr || new_default_media >= 0) {
+ if (set_hwaddr || new_default_media >= 0 || 1) {
> Also, I noticed that IRQ=11 is assigned to both the ethernet card and a scsi card -
Not a problem.
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 timk@harbornet.com Tue, 25 Sep 2001 22:26:42 -0700
Date: Tue, 25 Sep 2001 22:26:42 -0700
From: tk timk@harbornet.com
Subject: [realtek] Device or resource busy
Great!! That worked!
So, I don't understand why windows was able to find the driver and why it put (and still
does) the i/o address at 1400?
Also, what is in the registers shown with the -ee option?
Just curious, but I really do appreciate the help!
Thanks, TK
Donald Becker wrote:
> On Mon, 24 Sep 2001, tk wrote:
>
> > Linux 2.2.14-5.0
> > PnP OS not enabled in Bios (Award Modular Bios v6.00PG)
>
> Not important here..
>
> > I ran rtl8139-diag with the '-p' and '-t' options because it would not work
> > otherwise.
> ...
> > Bus 0, device 13, function 0:
> > Ethernet controller: Unknown vendor Unknown device (rev 16).
> > Vendor id=1. Device id=1211.
>
> Bad... the vendor ID is invalid.
>
> > and used the i/o address of the card found there:
> > ./rtl8139-diag -p 0xdc00 -t 2 -e >& diag-3.log
> >
> > This returned the following which I piped into a file:
> > ------
> > rtl8139-diag.c:v2.04 8/08/2001 Donald Becker (becker@scyld.com)
> > http://www.scyld.com/diag/index.html
> > Assuming a SMC1211TX EZCard 10/100 (RealTek RTL8139) adapter at 0xdc00.
> > Decoded EEPROM contents:
> > PCI IDs -- Vendor 0x0001, Device 0x1211.
> > PCI Subsystem IDs -- Vendor 0x1113, Device 0x1211.
> > PCI timer settings -- minimum grant 32, maximum latency 64.
> > General purpose pins -- direction 0xe1 value 0x10.
> > Station Address 00:E0:29:88:BC:C7.
> > Configuration register 0/1 -- 0x4d / 0xc2.
> > EEPROM active region checksum is 0798.
>
> Everything is OK except the checksum and the Vendor ID.
> The Vendor ID has been corrupted -- it should be 0x1113.
>
> Around line 635 in rtl8139-diag.c make the following change
> }
> }
> + new_ee_contents[1] = 0x1113;
> /* To set another EEPROM value do new_ee_contents[xxx] = new_value; */
> - if (set_hwaddr || new_default_media >= 0) {
> + if (set_hwaddr || new_default_media >= 0 || 1) {
>
> > Also, I noticed that IRQ=11 is assigned to both the ethernet card and a scsi card -
>
> Not a problem.
>
> 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
>
> _______________________________________________
> realtek mailing list
> realtek@scyld.com
> http://www.scyld.com/mailman/listinfo/realtek
From becker@scyld.com Wed, 26 Sep 2001 01:44:21 -0400 (EDT)
Date: Wed, 26 Sep 2001 01:44:21 -0400 (EDT)
From: Donald Becker becker@scyld.com
Subject: [realtek] Device or resource busy
On Tue, 25 Sep 2001, tk wrote:
> So, I don't understand why windows was able to find the driver
Because it was looking for the subsystem ID, not the primary PCI ID.
> and why it put (and still does) the i/o address at 1400?
Windows re-maps the PCI addresses.
The original reason was to use old ISA drivers for PCI devices, but not
it's to support hardware such as PCMCIA cards which require dynamically
allocating I/O regions.
> Also, what is in the registers shown with the -ee option?
The EEPROM settings -- the persistent configuration.
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 sf@infesto.de Wed, 26 Sep 2001 20:04:39 +0200
Date: Wed, 26 Sep 2001 20:04:39 +0200
From: Sebastian Frankfurt sf@infesto.de
Subject: [realtek] problems using 2 cards with rtl8139
Hello ;-)
I am using RH7.0 with Kernel 2.2.18. If I use one network adapter
with the realtek 8139 chipset everything is working, but if I
add another adaptor to that machine, the cards stopped working:
I added:
alias eth0 rtl8139
alias eth1 rtl9139
to /etc/modules.conf
The interfaces eth0/eth1 are up.
If I run a ping on that machine, both adaptors response, but
if I try to ping a different machine on the network, nothing
happened.
There are no kernel messages (/var/log/syslog) or tty-msgs.
And also, a ping from another machine to that one is not
working as well. It seems, as if the machine with the 2 adaptors
is not existent inside the network.
I tried to download and compile the new driver, but on Redhat 7.0
there are too much errors, so I tried using the 8139too on a
Kernel 2.4.6, but it is the sae problem -> no messages and the
machine is unreachable inside the network.
Any ideas?
thanx,
Sebastian
PS: please make a cc to fortune@gmx.de 'cause I'm not on the list ;-)
From laster@monmouth.com Wed, 26 Sep 2001 23:14:22 -0400
Date: Wed, 26 Sep 2001 23:14:22 -0400
From: Donald R. Laster Jr. laster@monmouth.com
Subject: [realtek] problems using 2 cards with rtl8139
Sebastian,
Double check your IP addresses assigned to the ethernet
interfaces. It almost sounds like both interfaces are using the
same IP address which might present a problem.
Is "alias eth1 rtl9139" a typo?
Don Laster Jr.
Sebastian Frankfurt wrote:
>
> Hello ;-)
>
> I am using RH7.0 with Kernel 2.2.18. If I use one network adapter
> with the realtek 8139 chipset everything is working, but if I
> add another adaptor to that machine, the cards stopped working:
>
> I added:
> alias eth0 rtl8139
> alias eth1 rtl9139
>
> to /etc/modules.conf
>
> The interfaces eth0/eth1 are up.
> If I run a ping on that machine, both adaptors response, but
> if I try to ping a different machine on the network, nothing
> happened.
> There are no kernel messages (/var/log/syslog) or tty-msgs.
>
> And also, a ping from another machine to that one is not
> working as well. It seems, as if the machine with the 2 adaptors
> is not existent inside the network.
>
> I tried to download and compile the new driver, but on Redhat 7.0
> there are too much errors, so I tried using the 8139too on a
> Kernel 2.4.6, but it is the sae problem -> no messages and the
> machine is unreachable inside the network.
>
> Any ideas?
>
> thanx,
>
> Sebastian
>
> PS: please make a cc to fortune@gmx.de 'cause I'm not on the list ;-)
>
> _______________________________________________
> realtek mailing list
> realtek@scyld.com
> http://www.scyld.com/mailman/listinfo/realtek
--
===========================================================================
Donald R. Laster Jr. laster@monmouth.com
DOT4 Inc. dlaster@dot4.com
25 Heidl Ave laster@garban.com
West Long Branch, NJ 07764
Phones: (732) 263-9235 (Evening) (732) 263-9236 (Office)
(212) 815-6880 (NYC/Garban) (732) 263-9280 (Fax)
===========================================================================
From sf@infesto.de Thu, 27 Sep 2001 09:32:18 +0200
Date: Thu, 27 Sep 2001 09:32:18 +0200
From: Sebastian Frankfurt sf@infesto.de
Subject: [realtek] problems using 2 cards with rtl8139
Donald R. Laster Jr. wrote:
>
> Double check your IP addresses assigned to the ethernet
> interfaces. It almost sounds like both interfaces are using the
> same IP address which might present a problem.
;-)
yeah, I checked it:
eth0 192.168.100.1
eth0:1 192.168.100.5
eth1 192.168.40.1
Even if I shutdown eth1, this machine is not reachable :-(
> Is "alias eth1 rtl9139" a typo?
well, sorry, was a typo. inside /etc/modules.conf is:
alias eth1 rtl8139
any other idea?
maybe it has something to do with another problem?
If I do not use a direct x-cable to connect to
this machine, the realtek card also does not respond
and gets unreachable.
Only when I use a x-cable the adaptor will work.
And again, If the card will not work, I receive
no messages.
But in syslog I see, that the card is only in
half-duplex mode. This happens only, if I do not
use a x-cable und plug the machine into a hub.
thanx in advance
Sebastian
From eggers@apollo.gat.com Thu, 27 Sep 2001 15:06:42 -0700
Date: Thu, 27 Sep 2001 15:06:42 -0700
From: Charles Eggers eggers@apollo.gat.com
Subject: [realtek] Trouble building for D-Link DFE-530TX+ PCI
Hi -
I'm having some major problems building a driver under Linux 7.1 from
either source or RPM for a D-Link DFE-530TX+ PCI. The last attempt
was from source files 3c59x.c, pci-scan.c, pci-scan.h, and
kern_compat.h (up to date, I presume, from the ftp site). The C
files compile OK but subsequent insmod on the object files lets loose
a torrent of unresolved symbols. Obviously, I'm missing something,
but don't know what. Help?
Thanks,
Chuck
Charles Eggers
Senior Programmer/Analyst
General Atomics
3550 General Atomics Court
San Diego, CA 92121-1194
Office: 858.455.3564
mailto:eggers@fusion.gat.com
http://fusion.gat.com/comp/analysis/
From laster@monmouth.com Thu, 27 Sep 2001 14:19:09 -0400
Date: Thu, 27 Sep 2001 14:19:09 -0400
From: Donald R. Laster Jr. laster@monmouth.com
Subject: [realtek] problems using 2 cards with rtl8139
Sebastian,
Over the weekend I will try to put two realtek cards in a test
system and see what happens. Could one of the cards be broken? Are
you getting any IRQ conflicts?
Donald R. Laster Jr.
Sebastian Frankfurt wrote:
>
> Donald R. Laster Jr. wrote:
>
> >
>
> > Double check your IP addresses assigned to the ethernet
> > interfaces. It almost sounds like both interfaces are using the
> > same IP address which might present a problem.
>
> ;-)
> yeah, I checked it:
>
> eth0 192.168.100.1
> eth0:1 192.168.100.5
> eth1 192.168.40.1
>
> Even if I shutdown eth1, this machine is not reachable :-(
>
> > Is "alias eth1 rtl9139" a typo?
>
> well, sorry, was a typo. inside /etc/modules.conf is:
>
> alias eth1 rtl8139
>
> any other idea?
>
> maybe it has something to do with another problem?
> If I do not use a direct x-cable to connect to
> this machine, the realtek card also does not respond
> and gets unreachable.
> Only when I use a x-cable the adaptor will work.
> And again, If the card will not work, I receive
> no messages.
> But in syslog I see, that the card is only in
> half-duplex mode. This happens only, if I do not
> use a x-cable und plug the machine into a hub.
>
> thanx in advance
>
> Sebastian
>
> _______________________________________________
> realtek mailing list
> realtek@scyld.com
> http://www.scyld.com/mailman/listinfo/realtek
--
===========================================================================
Donald R. Laster Jr. laster@monmouth.com
DOT4 Inc. dlaster@dot4.com
25 Heidl Ave laster@garban.com
West Long Branch, NJ 07764
Phones: (732) 263-9235 (Evening) (732) 263-9236 (Office)
(212) 815-6880 (NYC/Garban) (732) 263-9280 (Fax)
===========================================================================
From krasserm@freenet.de Sun, 30 Sep 2001 14:59:01 +0000
Date: Sun, 30 Sep 2001 14:59:01 +0000
From: Martin Krasser krasserm@freenet.de
Subject: [realtek] ressource allocation problem - rtl8139 cardbus
Dear All,
I recently bought a Realtek rtl8139 cardbus card and updated the rtl8139
driver following the instructions at
http://www.scyld.com/network/rtl8139.html
http://www.scyld.com/network/updates.html
http://www.scyld.com/network/modules.html
but the card cannot be assigned an IRQ or ressources cannot be
allocated.
The system settings are:
- Kernel 2.2.16 (SuSE 7.0)
- PCMCIA 3.1.17
The System in running on a Dell Inspiron 4000 Laptop.
The problems differ depending on the socket where the card is inserted:
Socket 0:
Resources for CardBus device 'RealTek RTL8139 Fast Ethernet' have not
been allocated. Activation has been delayed.
Socket 1:
PCI device 'RealTek RTL8139 Fast Ethernet' was not assigned an IRQ. It
will not be activated.
In both cases the command 'network eth0 start' (see syslog later) does
not start the network.
>From the pci-scan.c code I know that the message for socket 0 comes from
a a broken cardbus activation, message for socket 1 from an IRQ
assignment 0 or 255. I also followed the irq-conflict.html but without
success.
Can anyone help me to solve this problem - after reading howtos, emails,
... for about 3 days I couldn't find a way to solve this problem.
Here's the output from lspci -v (why has the Ethernet controller this
number: 20:00.0 ?)
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev 03)
Flags: bus master, medium devsel, latency 32
Memory at e0000000 (32-bit, prefetchable)
Capabilities: [a0] AGP version 1.0
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
(rev 03) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 32
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fd000000-feffffff
Prefetchable memory behind bridge: e4000000-ebffffff
00:03.0 CardBus bridge: Texas Instruments PCI1420
Subsystem: Dell Computer Corporation: Unknown device 00b0
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at (32-bit, non-prefetchable)
Bus: primary=00, secondary=20, subordinate=22, sec-latency=32
I/O window 0: 00000200-000002ff
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001
00:03.1 CardBus bridge: Texas Instruments PCI1420
Subsystem: Dell Computer Corporation: Unknown device 00b0
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at (32-bit, non-prefetchable)
Bus: primary=00, secondary=23, subordinate=25, sec-latency=32
I/O window 0: 00000000-00000003
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001
00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
Flags: bus master, medium devsel, latency 0
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
Flags: bus master, medium devsel, latency 32
I/O ports at 0860
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
(prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at dce0
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03)
Flags: medium devsel
00:08.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i
PCI Audio Accelerator (rev 10)
Subsystem: Dell Computer Corporation: Unknown device 00b0
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d800
Memory at fbffe000 (32-bit, non-prefetchable)
Capabilities: [c0] Power Management version 2
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility M3 AGP
2x (rev 02) (prog-if 00 [VGA])
Subsystem: Dell Computer Corporation: Unknown device 00b0
Flags: stepping, 66Mhz, medium devsel, IRQ 11
Memory at e8000000 (32-bit, prefetchable)
I/O ports at ec00
Memory at fdffc000 (32-bit, non-prefetchable)
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 2
20:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139
(rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 0200
Memory at a0003000 (32-bit,
non-prefetchable)
System log (after a restart of the pcmcia services):
rcpcmcia: /sbin/insmod /lib/modules/2.2.16/pcmcia/pcmcia_core.o
kernel: Linux PCMCIA Card Services 3.1.17
kernel: kernel build: 2.2.16 #11 Mon Sep 24 22:26:56 GMT 2001
kernel: options: [pci] [cardbus] [apm]
kernel: PCI routing table version 1.0 at 0xfbd80
rcpcmcia: /sbin/insmod /lib/modules/2.2.16/pcmcia/i82365.o
kernel: Intel PCIC probe:
kernel: TI 1420 rev 00 PCI-to-CardBus at slot 00:03, mem 0x68000000
kernel: host opts [0]: [ring] [pci + serial irq] [pci irq 11] [lat
32/32] [bus 32/34]
kernel: host opts [1]: [ring] [pci + serial irq] [pci irq 11] [lat
32/32] [bus 35/37]
kernel: ISA irqs (scanned) = 3,4,7,9,10 PCI status changes
rcpcmcia: /sbin/insmod /lib/modules/2.2.16/pcmcia/ds.o
cardmgr[1634]: starting, version is 3.1.17
cardmgr[1634]: watching 2 sockets
kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
kernel: cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f
kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f
0x3f8-0x3ff 0x4d0-0x4d7
kernel: cs: IO port probe 0x0a00-0x0aff: clean.
kernel: cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8139
cardmgr[1634]: initializing socket 0
cardmgr[1634]: socket 0: RealTek RTL8139
cardmgr[1634]: executing: 'modprobe cb_enabler'
cardmgr[1634]: executing: 'modprobe pci-scan'
cardmgr[1634]: executing: 'modprobe cb_shim'
kernel: cb_shim.c:v1.00 4/15/2000 Donald Becker
kernel: http://www.scyld.com/linux/drivers.html
cardmgr[1634]: executing: 'modprobe rtl8139'
kernel: rtl8139.c:v1.15 8/1/2001 Donald Becker, becker@scyld.com.
kernel: http://www.scyld.com/network/rtl8139.html
kernel: Resources for CardBus device 'RealTek RTL8139 Fast Ethernet'
have not been allocated.
kernel: Activation has been delayed.
kernel: cs: cb_config(bus 32)
kernel: fn 0 bar 1: io 0x200-0x2ff
kernel: fn 0 bar 2: mem 0x60001000-0x600011ff
kernel: irq 11
kernel: cs: cb_enable(bus 32)
kernel: bridge io map 0 (flags 0x21): 0x200-0x2ff
kernel: bridge mem map 0 (flags 0x1): 0x60001000-0x60001fff
kernel: Found a RealTek RTL8139 Fast Ethernet at 32/0 address
0x201->0x200 IRQ 11.
kernel: RealTek RTL8139 Fast Ethernet at 32/0 command 0x7.
kernel: eth0: RealTek RTL8139 Fast Ethernet at 0x200, IRQ 11,
00:50:fc:2d:02:60.
cardmgr[1634]: executing: './network start eth0'
PCMCIA: Shutting down Name Service Cache
Daemon^M^[[132C^[[9D^[[32m^[[1mdone^[[m^O
PCMCIA: Starting Name Service Cache
Daemon^M^[[132C^[[9D^[[32m^[[1mdone^[[m^O
cardmgr[1634]: initializing socket 1
cardmgr[1634]: socket 1: Serial or Modem
kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
cardmgr[1634]: executing: 'modprobe serial_cs'
kernel: Serial driver version 4.27 with HUB-6 MANY_PORTS MULTIPORT
SHARE_IRQ enabled
kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
kernel: tty01 at 0x0af8 (irq = 3) is a 16550A
cardmgr[1634]: executing: './serial start
ttyS1'
best regards
Martin