Newbie: Have RedHat 7.3 running, want D-Link DFE-630TX+ NIC to work too.

The both the CD that came with this NIC and D-Link's own site are both vague
(to my understanding level) over how to get this card running with Linux.

I've un-tarred the contents of the gzip file into a temp directory. There
are several .c and .h files along with a Makefile and a readme called
linux.txt. But, there isn't any instructions about how to use the Makefile
to compile the other stuff.

The linux.txt file itself contains somewhat OK instructions to get at the
contents of the .gz file and what to do with its contents. Yet, when it
comes to the actual compilation of the source that came with it, it says:
"Compile the driver source files and it will generate rhinefet.o, and copy
it to correct driver installation path (The installation directory is
different in different kernel versions." etc.....

Yea, right..

The D-Link site, however, has instructions to compile a .c file called
rtl8139.c that they also supply on the linux page for the NIC.

Which set of files is the best to use, the one from D-Link's site or those
off of the CD?

What's the command so I can compile the files supplied on the CD?

How do I get the results of the compilation to be used by the OS to run the
NIC?

TIA

Stu

Stuart Cox <(E-Mail Removed)> wrote:
> The both the CD that came with this NIC and D-Link's own site are both vague
> (to my understanding level) over how to get this card running with Linux.
[..]
> The D-Link site, however, has instructions to compile a .c file called
> rtl8139.c that they also supply on the linux page for the NIC.

> Which set of files is the best to use, the one from D-Link's site or those
> off of the CD?

You shouldn't have to compile anything, with a little luck kudzu
should have setup /etc/modules.conf already for you.

Try 'grep eth /etc/modules.conf'. If not look at the output of
'lspci' to gather info about your NIC and which driver to use.

--
Michael Heiming

Remove +SIGNS and www. if you expect an answer, sorry for
inconvenience, but I get tons of SPAM

On Sat, 24 Jan 2004 21:59:28 GMT, "Stuart Cox" <(E-Mail Removed)>
wrote:

>I've un-tarred the contents of the gzip file into a temp directory. There
>are several .c and .h files along with a Makefile and a readme called
>linux.txt. But, there isn't any instructions about how to use the Makefile
>to compile the other stuff.
>
>The linux.txt file itself contains somewhat OK instructions to get at the
>contents of the .gz file and what to do with its contents. Yet, when it
>comes to the actual compilation of the source that came with it, it says:
>"Compile the driver source files and it will generate rhinefet.o, and copy
>it to correct driver installation path (The installation directory is
>different in different kernel versions." etc.....

Generally speaking, unless otherwise instructed in some Readme or
Install text file, on Linux you compile source code by changing to the
directory containing the source, doing a "./configure" (i.e., run the
configure script - if one is supplied, of course - from the current
directory), then do a "make", then a "make install". The screen
displays you get should show you where it got installed toward the end
of the output.

>The D-Link site, however, has instructions to compile a .c file called
>rtl8139.c that they also supply on the linux page for the NIC.
>
>Which set of files is the best to use, the one from D-Link's site or those
>off of the CD?

That one I can't help you with. Try one and if it doesn't work, try
the other?

>How do I get the results of the compilation to be used by the OS to run the
>NIC?

Look for the other driver object modules - probably under
/lib/modules/<kernel version>/kernel/drivers/net. That's where they
seem to be on my Red Hat 7.3 system.

You'll need to put something like "alias eth0 8139too" into
/etc/modules.conf. Use whatever the object file (the .o file) name
is. Back it up before you change it, edit it, save it, reboot.

Can't remember anything else that needs to be done. Well, you have to
do ifconfig of course to create your eth0 network interface
configuration before you reboot.

Hope this helps (and I haven't left out anything critical!)


--
Richard Steven Hack
"Whatever does not kill me makes me stronger" -
and YOU have not killed me!

Further to my attempts to get this card running:

D-Link's web site includes the following two commands.

vvvvvvvvvvvvv
$ gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -c rtl8139.c `[ -f
/usr/include/linux/modversions.h ] && echo -DMODVERSIONS`
$ insmod rtl8139.o
^^^^^^^^^^^

When I try the compilation command, gcc, I receive a bunch of lines saying
'include expects "FILENAME" or <FILENAME>' and a further bunch saying
there's a syntax error in an #if statement. Not too good.

I looked at the contents of the /usr/include/linux/modversions.h file and it
contains the following lines:

vvvvvvvvvvvvv
#error Modules should never use kernel-headers system headers,
#error but rather headers from an appropriate kernel-source package.
#error Change -I/usr/src/linux/include (or similar) to
#error -I/lib/modules/$(uname -r)/build/include
#error to build against the currently-running kernel.
^^^^^^^^^^

IMHO, I should change "/usr/include/linux/modversions.h" on the gcc line to
something else. Just what?

TIA
Stu

"Stuart Cox" <(E-Mail Removed)> wrote in message
news:4VBQb.249807$JQ1.170971@pd7tw1no...
> The both the CD that came with this NIC and D-Link's own site are both
vague
> (to my understanding level) over how to get this card running with Linux.
>
> I've un-tarred the contents of the gzip file into a temp directory. There
> are several .c and .h files along with a Makefile and a readme called
> linux.txt. But, there isn't any instructions about how to use the
Makefile
> to compile the other stuff.
>
> The linux.txt file itself contains somewhat OK instructions to get at the
> contents of the .gz file and what to do with its contents. Yet, when it
> comes to the actual compilation of the source that came with it, it says:
> "Compile the driver source files and it will generate rhinefet.o, and copy
> it to correct driver installation path (The installation directory is
> different in different kernel versions." etc.....
>
> Yea, right..
>
> The D-Link site, however, has instructions to compile a .c file called
> rtl8139.c that they also supply on the linux page for the NIC.
>
> Which set of files is the best to use, the one from D-Link's site or those
> off of the CD?
>
> What's the command so I can compile the files supplied on the CD?
>
> How do I get the results of the compilation to be used by the OS to run
the
> NIC?
>
> TIA
>
> Stu
>
>

On Mon, 26 Jan 2004 07:02:45 GMT, Stuart Cox <(E-Mail Removed)> wrote:
>Further to my attempts to get this card running:
>>(...)
>> The D-Link site, however, has instructions to compile a .c file called
>> rtl8139.c that they also supply on the linux page for the NIC.
>>(...)

can it maybe be, that you need the 8139too driver (.o.gz) in the
/lib/modules/2.x.x.-.../kernel/drivers/net/ directory or something alike.
In the Ethernet-HOWTO is something under D-Link DFE-538TX,
that refers to the RealTek 8129/39 .

Cor

On Mon, 26 Jan 2004 07:02:45 GMT, "Stuart Cox" <(E-Mail Removed)>
wrote:

>Further to my attempts to get this card running:
>
>D-Link's web site includes the following two commands.

Where did you get the info on the DFE-630TX? I went to the D-Link
site and I can't even find that model in their wired NIC section!
They have a 530TX+ - is that what you're using? I even did a search
using DFE-630TX+ and it came back with nothing.

If you're referring to this document:
ftp://ftp.dlink.com/NIC/dfe530tx+/Dr...inux/RTL8139.C
which is for the 530TX+, forget about it. This was done back in
1997-1999, apparently, and the last revision was in 2002.. This is
what they use to create the kernel module, apparently. You do NOT
need to compile it. And it explicitly says:
================================================== ====
- Use for 2.2.x or if your version of Linux does not have the RTL8139
module built-in.
================================================== ====

All you need is to select the proper kernel module which they
identified above and get it referenced in etc/modules.conf as
mentioned earlier and then configure the interface.


--
Richard Steven Hack
"Whatever does not kill me makes me stronger" -
and YOU have not killed me!