not rtl chipset on lancard

I recently bought a new lan card they mention the chipset as

RTL 8139D

which was not recognized by kudzu (can some one point out why)

My system has two lan cards one is onboard and the other one I added my self ,both work well in windows and I have use net and LAN on both lan cards in windows but linux did not detected the extra lan card that I had put in ,
then I saw as the vendors CD said look for some file like rtl8139.o in
/lib/..../..../kernel/net/....

any driver given by CD are not working
lspci -v
gives me
02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Intel Corporation Unknown device d601
Flags: bus master, medium devsel, latency 64, IRQ 21
I/O ports at 1100 [size=256]
Memory at 30000100 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2

02:03.0 Ethernet controller: Hangzhou Silan Microelectronics Co., Ltd. Unknown device 2031 (rev 01)
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at 30000000 (32-bit, non-prefetchable) [size=256]
I/O ports at 1000 [size=256]
Expansion ROM at 30300000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Vital Product Data
I use Fedora Core 6

what should I do and how to find the chipsets etc and how to make the lan card work

Check the realtek site for a Linux driver; they did have one for Realtek 8111/8168 so why not for your card? You'll have to compile it yourself, though.

It works fine with debian etch 2.6.18 ( also sarge 2.6.8 ), i have 2 cards of this type. I don't think you'll need to build modules.

These are my data, seems the same:

02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Surecom Technology EP-320X-R Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at a000 [size=256] Memory at e0104000 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2

Try the following:

$lsmod |grep 8139 8139cp 21920 0 8139too 25120 0 mii 5344 2 8139cp,8139too

So insmod 8139cp 8139too ( or modconf ).

Syntax should be something like this, if not play a bit ( modconf 8139too should be enought iirc )
insmod /lib/modules/2.6.18-4-686/kernel/drivers/net/8139*

Of cource you'll need to find where they are...

It looks like i'm in the same situation. typing:

$lsmod |grep 8139

i see the same results (8139cp and 8139too). But if i try to ping
the two lancards from a laptop running win2k it gives me timeout. So i'm not
able to understand if the two NICs are correctly installed or if there is
a problem of comunication between win2k and linux. Do you know how i can ping
card #1 from card #2 passing through the switch and not internally?

---
Claudio.

But if i try to ping the two lancards from a laptop running win2k it gives me timeout

Firewall?

Do you know how i can ping card #1 from card #2 passing through the switch and not internally?

Never tried. If you try a cross cable between the 2?

Or if you try to ping from linux to win2k after having setted up addresses? Are you using dhcp or manual configuration?

For manual, you can try sudo ifconfig eth0 192.168.1.10 netmask 255.255.255.0 , for example, then try a bit.

no firewall, no DHCP. Numbers are: 192.168.123.X (X=3 and 4 on linux, 12 on win2k)
subnet: 255.255.255.0.

I didn't try a cross cable but it's tha same with two cables and one switch: the problem
is that i would like to ping the two NICs each other.

The two lights on the switch, where the two NICs are connected, blinks continuously even
if i don't make anything: is it normal or i have to think to some kind of error?

---
Claudio

It looks like the drivers 8139cp and 8139too are the right ones for
my cards. So, there must be something else. Any idea or suggestion?

SOLVED! There was an IRQ conflict (more then one!).

Thanks in advance,
Claudio.

some search showed me
http://www.geocities.com/rohitksethi/

This new INTEX / ZEBRONICS card has chipsets printed saying RTC8139D or even RTL8139D....
But both these chipsets are fake...

http://geektalkin.blogspot.com/2006/...drtl8139d.html


but my problem remains still unanswered

hey this is Novemeber of year 2007 finally I got the solution to my problem which I was searching from february kernel 2.6.22.5 or above has a stable driver for this particular chipset names sc92031.c any one facing this problem can google it or reply me I will tell how to make it work.