setting up eth0 interface for DLINK ethernet

sr425 · 01-14-2002, 03:05 PM

I have RH 6.2 installed. Publisher's version. I am trying to setup ethernet interface.

ifconfig lists only lo and not any eth0 devices.

My BIOS is set to non plug and play. lspci shows my Ethernet Controller as unknown device.

The ethernel adapter is DLINK DFE 530 TX+. I got the "C" code for this card from the dlink website but just dont know how to create the driver.o module. I am looking for

a) "howto" on comipiling the code
b) what files to edit to include this new module to autoload on bootup

Appreciate any help I can get....

Thx..

finegan · 01-14-2002, 06:39 PM

Well, this may be a start, but the command line entry to compile the module, by convention, is the last lines in the .c code. Hopefully it will compile without errors. From a little googling, the module for that card (and that older version of redhat), is probably via-rhine and was included in the installation. Try:

modprobe via-rhine

Then see what happens. Try 'ifconfig eth0 up' to bring up the card. to automate it... er, hmm... depmod -a er, I can't remember how to do that in redhat, I'm such a gimp.

To automate its IP settings: netconfig.

Cheers,

Finegan

sr425 · 01-14-2002, 08:18 PM

Thanks a lot for your prompt reply. I checked my /modules/... directory and found via-rhine.o module. However, when I typed modprobe via-rhine, I get an error message..

Device or resource busy
blah....
Insmod via-rhine failed.

I have tried to compile the "RTL8139.C" code (the driver for my ethernet), following the instructions at the bottom of the code, but I got a message saying RTL8139.C does not exist even though I tried executing the command from the directory where the file was located. I am not sure what I am missing.

Is there a way, I can download the module directly (from the internet)and then try modprobe via-rhine ?

Thanks again...

DMR · 01-15-2002, 01:05 AM

The 530 TX (no "+") uses the via-rhine driver, but the 530 TX+ should use the rtl8139 module because it uses a Realtek chipset. Is this the compile command you are using:

Code:

gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c rtl8139.c

In your post you typed the name of the source (.c) file in all caps. Case-sensitivity counts; make sure the filename exactly matches that given in the compile command. Specific compile instructions can be found here; read them carefully, as you probably have to compile pci-scan.o before rtl8139.o.

sr425 · 01-15-2002, 09:05 AM

I typed in the file name wrong. Anyway, now when I try to compile the "c" code using the gcc comand, i get bunch of error messages that say that the following files were not found..

linux/version.h
linux/module.h
linux/ioport.h
....
....
...
...
....
....
....
linux/etherdevice.h

These seem to be header files, right ? Wonder what's going on....

Thx

sr425 · 01-15-2002, 09:55 AM

I have some more info. I managed to located the rtl8130.o and when I tried

insmod rtl8130

I get the message "device or resource busy" I have tried disabling my onboard sound card but that did not help.

I think I am getting close....

Thx for all the help...

finegan · 01-15-2002, 11:40 AM

This chipset seems to have danced accross a number of modules:

Originally via-rhine, then I think it was somewhere else before being in rtl8139, and now its part of the brand spanking new code: 8139too. Annoying. If the .c code you had did not come with a def file, then it was probably meant to be put in the kernel source directory and compiled with the kernel, or maybe your install didn't put kernel source on... This could make for a raging hastle.

You have to remember that modules (drivers and a lot of other things), are really just part of the Linux kernel, and have little to nothing to do with the distribution that you are using. Remember, its not a case of 'RedHat' didn't find my card, its always: kernel 2.2.10 didn't find my card, or whatever kernel. You also can't swap out modules from different kernels and run them in a different kernel then they were compiled for... well, okay, technically you can force it to work, but this can be very bad.

Honestly, you have a very old distro of RedHat right now. It went: 6.2, 7, 7.1, 7.2, so you're one major and 3 minor versions back and that could make all the difference in making the switch to linux very easy as RedHat especially has gotten much more newbie friendly in the past few years.

Sorry for not having anything encouraging to post really,

Luck,

Finegan