My D-Link DFE-530TX+

[Gathius]

ok I am setting up linux for the first time, and am having some difficulty. My NIC, the D-Link 530TX+ came with a driver in a c source file.. when I try to compile it I get errors. Can anyone tell me the correct procedure for compiling the driver and inserting it?
Thanks.

[lm72]

Did you read the linux.txt file in archive with drivers.

It in help folder once extract it.

[Gathius]

ok the instructions that I got from d-link.com said to copy the file to /root and compile it with the following command:
kgcc -I /usr/src/linux/include -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -c rtl8139.c `[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS`
However when I do that, I get the following errors:
kgcc: rt18139.c: No such file or directory
kgcc: [ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS: No such file or directory

kgcc: unrecognized option '-06'
kgcc: No input files

I have no idea what I am doing wrong.... :confused:
Thanks for the help.

[Molecule Man]

Which kernel are you using? It has been a standard part of the kernel for a long time.

For 2.2.x try modprobe rtl8139

For 2.4.x try modprobe 8139too

[Gathius]

ok when I did that I got an error that the device or resource is busy.
I got the same error when I tried to do an insmod rtl8139.
:(

[bdg1983]

Try turning off PnP OS in the bios first and then try loading those modules again.

Device or resource is busy usually means a irq or i/o conflict and the bios trick sometimes works. If not, post back.

[Gathius]

ok the PnP os was enabled so I turned it off. when I tried to do the modprobe or insmod again I still got the device or resource busy error....
I ran a lspci -v and no other devices were using IRQ 11 which it is using. Hmm.. this is getting frustrating. :mad: Any ideas?

[bdg1983]

Do you have another pci slot you could move the D-Link to? If you do, give that a try and post back. If not, then I'll try and help you more when i get home from work.

[Gathius]

Ugh what a mess. Ok I have 3 free pci slots. I moved the nic to another pci slot, and when I turned the computer back on, started getting POST beeps. Yay. I fixed that though, all I had to do was reseat the video card..... who knows. Anyways, changing the pci slot of the nic didn't help. I tried two other slots, and still got device or resource busy when I did the modprobe/insmod.
An interesting note: I did a boot w/o the card in, and still got the same error upon doing a modprobe.

[rick420]

I wish I could help you more, but I just wanna let you know that I have the same card and it worked from install.....I had it working from the install in Mandrake 7.2, 8.0 and now 8.1. I just wanted to let you know it does work in Linux...

[bdg1983]

Do we know what distro and version you are using? If it's older than your NIC then you may have problems.

Are you trying to load the modules that are included with your distro or did you successfully compile your own?

[Molecule Man]

One other thing, are you sure that it is a DFE530tx+? There is also a DFE530tx.

DFE530tx+ uses the RealTek 8139 chipset.

DFE530tx uses the Via-Rhine chipset.

You could always try modprobe via-rhine.

Also, try posting a copy of your /proc/pci

[Gathius]

Ah, ok, I got it working.. in fact I am in linux right now as I post this....
Here's what I did to fix it: reinstalled. What I did differently this time is include the kernel source which I didn't do last time.... anyways I could compile that driver this time and was able to insert it no problem. I was then able to successfully configure the interface... except for one thing. Whenever I boot I get an error message about bringing up the eth0 interface. It says that "insmod rtl8139" failed. However, when it boots up, I can open up a terminal and do a quick insmod rtl8139 and it will be up and running.... Anyone know why it will not load automatically? At least it works now, thanks for your help, everyone!
:)

[bdg1983]

You can try adding a line with rtl8139 to /etc/modules.conf. It works for me at work for my Intel nic (eepro100).

[lm72]

Just use module 8139too for D-Link 530tx or 538 TX that's what have and it works great.

Their both based on same chips on realtek chipset but not all work with realtek module.

Regards,

Alex :)

[w_doug]

Okay well I seem to have run a problem with the same card and I can't get the rtl8139.c file to compile either. I tried reinstalling with the source but no luck there and am returning to post for help. I'm running Debian 2.2 with that kernel. Modprobe won't pick up rtl8139 but it will get 8139too except it is a device or resource busy. I have tried different slots and making sure irq is okey dokey to no avail. If the 8139too will work for the 530tx+ then I'd be happy using it instead of working through compiling the other file (long ugly list of errors, dereferencing, source not known but it scrolls over the screen) just need to get device or resource not busy :D. Much thanks for anybody taking their time to read through this.

[Gathius]

ok do you have the TX+? If you do, the driver disk should have a makefile... just get a terminal window and go to the floppy directory/linux, and type make -k. That's what I did, and it created the rtl8139.o file on the disk. I then copied it to the /lib/modules/2.2.x/net/ directory and insmod/modprobe then worked.

[Gathius]

ok I am still having the boot problem... it won't bring up the eth0 interface on boot. It says
"insmod /lib/modules/2.2.x/net/rtl8139.o failed" but if I log into root and type "insmod rtl8139" it says it's using that same file, and works fine. Anyone have any ideas?

[SkyNet]

Gathius,

In your /etc/modules.conf file make sure the rtl8139 is not commented out.

Also another way of doing this is to go into your rc.d dir and then edit your rc.modules file so that the modprobe for the rtl8139 module is not commented out.

3rd way is to add a line in the rc.local file that is insmod rtl8139

At least one of these should fix the problem.