automatically detected
using the "8139too" driver

my lspci differs:
00:08.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)

I'm glad this NIC is working for others, but it is not working for me.

Please note that I have 2 completely boxes running the same distribition of Linux using this card, and the card fails in the same manner on both. Another brand of NIC works fine in either box.

It works just great on a lot of kernels I've used, but the two that I use the most are the two defined above. If for some reason you can't get it to work by default, download the kernel source, extract it, do make menuconfig, then in Network Device Support goto Ethernet 10 100 mbit, then put in the RTL-8139 drivers. Then compile it and it should work! If you don't know how to compile a kernel just look it up in mabye the software forum. Otherwise this card works great.

Installed like a dream. Put it in, recompiled the kernel with the 8139 driver, no problems out of it whatsoever. The $0 paid - it was given to me.

Had an older SMC 10M Tulip-based card in the machine initally, wasn't recognized at all. Picked up a NETGEAR WG311v2 wireless card and got it working with manual setup using ACX100/111 drivers.

Pulled out the SMC, then based on a posting I believe I read here, went into BIOS and turned PCI bus mastering ON. Added the D-Link 10/100Mbps card (picked it up for $5 after a rebate from OfficeMax) and presto, recognized it right away, installed and configured perfectly with no intervention.

May go back and re-try the SMC now.

But thumbs-up for the D-Link & FC2.

This would have been a 10 but initially the OS picked/loaded the wrong driver.


Thanks to previous reviews here I corrected the driver the card wanted and BOOM!!!!

I'm in business configuring iptables with 2 NICS!


Thx Everyone

This thing saved me!


Nice NIC! Recently, my router became useless as a router (damn DI-624), kept reseting evry 15 seconds. I didn't waste a second. it was always my dream to turn my fileserver into an advanced, highly configurable and solid router. But I had only one ethernet card built-in on my mobo.

Not even taking a chance to think, I went to BestBuy and bought this one out of the 2 they had ("huge" selection :D), previously checking to be sure that the DI-624 can be used as a "switch+access point".

I did a couple of stupid mistakes that just stole my time, but in an hour, this card was set up as an external interface device, while my onboard device was the internal one. Did some wire-cutting to turn a regular ethernet cable into a crossover, reseted my router a couple of times, hooked everything up and followed a guide to set up SuSE as a router, then... voila! I have my network all set.

What can I say... It works. I wouldn't be typing this message right now without it, cuz I wouldn't have internet connection!



svinka

You just have to add alias eth0 8139too to modules.conf and comment out 8319too rc.modules then your ready to go

isnt that easy

Haven't started using it yet.
Just wanted to post that rev F uses
the via-rhine module, not 8139too

Bob

Does this card support in IpCop ?

I have checked the IpCop hardware compatibility list.

This cards is based on RealTek chipset. From the website of FreeBSD, the RealTek chipset is sucks.

I need your opinion.

Thanks for your help.

Dlink DFE530TX+ ver F2

This card works with the via_rhine module in all three distros listed above running versions of the 2.6 kernel.

Dlink recommends compiling the rhinefet module (tar ball supplied on the CD supplied with the card) but I couldn't get it to compile. After googling on the problem, I tried the via_rhine module which was recommended for earlier versions of the DFE530TX+ card. After setting up the card, I rebooted and had internet connection.

I've also tried the 8139too module, but it didn't work on my machine.

I bought it at Target, dirt cheap on clearance. Installed it with absolutely no problems. Wake-on-LAN works fine too.

Tried a LNE100TX which has been my goto LAN card for quite some time and it was recognized but was not functioning. Took it back and picked up 2 of these(just in case) and BAM! Happy internal LAN working as it should.