D-Link DFE-530TX netword card doesn't work

[mynca_2000]

---

Hello,

first of all, let me say that I'm a Linux newbie and these are my first steps in the Linux world.
I have an old computer where I installed Fedora core 2 on (it's an old version but its also an old computer and with newer versions I have problems with the BIOS, which is too old and I can't seem to find an update for the BIOS). So I try to make the DFE-530TX to work under Fedora core 2 but I can't succeed
in it.
Fedora detects that a network card is present but I can't connect to the internet. Can anyone help me step by step how to install this card, or post a link where it is clearly explained (I repeat: For a Linux newbie).
I tried also to install the Linux drivers but they have to be compiled first which I also don't succeed in, so I actually need a good tutorial or manual on how to install drivers for network card or something similar

Thx in advance
mynca_2000

[AlexK]

Hi mynca_2000,
Could you post the results from these commands (you'll need to be root when you execute them):

ifconfig
route
ping -c 4 www.google.com

[mynca_2000]

These are the results:



[root@localhost root]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2664 errors:0 dropped:0 overruns:0 frame:0
TX packets:2664 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3502377 (3.3 Mb) TX bytes:3502377 (3.3 Mb)


[root@localhost root]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 lo
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

[root@localhost root]# ping -c 4 www.google.com
ping: unknown host www.google.com

[MikeTbob]

I have used this card before and if I remember correctly it works right out of the box on Linux because it's an 8139 chipset. So give this a Try:
modprobe 8139too
Then launch the network too with this command, as root:
neat &

[Evildragon]

hi all Im having some what the same problem.
for some reason I cant compile the source codes that it wants me to to compile
my kernel is a 2.6.x

here is the linux disk that came with my DFE 530tx+ card


D-Link DFE-530TX+ PCI Fast Ethernet Adapter Installation
for Linux

v4.39 February. 2005




Introduction:
=============

The instructions listed below are for linux driver installation. You must
compile the source code to generate rhinefet.o(rhinefet.ko in 2.6.x kernel,
please remember to replace rhinefet.o with rhinefet.ko in the following
sentences if you are using 2.6.x kernel) and use insmod command to insert
rhinefet.o as module.


Contents of the Subdirectory:
=============================

linux.txt This file.
Makefile Makefile for generating driver object file
rhine_main.c The linux core driver source code file
rhine_proc.c The source to create proc entries
rhine_wol.c The WOL supporting source file
rhine.h The extended driver header file
rhine_proc.h The header file for proc entries
rhine_wol.h The WOL supporting header file
rhine_cfg.h The general and basic info header file
kcompat.h The header file for Linux kernel version
compatibility.

Kernel Supported
================
This driver supports linux kernel version 2.2.x, 2.4.x and 2.6.x now.

CPU Supported
=============
This driver supports x86 and AMD64 based linux system.

Installation
============
Please enter the following commands at the UNIX prompt. Remember, UNIX is
case sensitive.

1) Create a temporary directory:
mkdir /temp

2) Change to the temporary directory:
cd /temp

3) Copy driver (dlkfet-4.39.tar.gz) from DOS disk, (mcopy below is one tool in
mtools, if you didn't install mtools, you can type
'mount -t msdos /dev/fd0 /mnt' and use 'cp /mnt/dlkfet-4.39.tar.gz /temp'
command to copy the driver to the temporary directory):
mcopy a:dlkfet-4.39.tar.gz .

4) untar the archive file:
tar xzvf dlkfet-4.39.tar.gz
cd dlkfet-4.39

5) 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. In 2.4.x/2.6.x kernel, the path
is /lib/modules/KERNEL_VERSION/kernel/drivers/net/, and in 2.2.x kernel,
the path is /lib/modules/KERNEL_VERSION/net/, the KERNEL_VERSION (see
above) means the kernel version of your Linux distribution. If you don't
know your kernel version , please run 'uname -r' command in command
line. The kernel version will look like '2.2.16', '2.4.2-2smp' etc.) :
make install

6) Check configuration file (/etc/modules.conf or /etc/conf.modules or
/etc/modprobe.conf, it depends on your Linux distribution) for loading
kernel modules. Make sure the first line below is appeared in the
configuration file, where # is the interface number (eg: alias eth0
rhinefet). If you need to set the driver options, below second line is
an example to set the NIC to 100Mbps fullduplex mode (remember to unmark
the line if it is put in the configuration file).
alias eth# rhinefet
#options eth# speed_duplex=2

7) Reboot now:
shutdown -r now

Install your driver module (If the driver module is in the wrong place,
an error message will appear, and say that can't find the driver
module):
insmod rhinefet.o

9) Use ifconfig command to assign the IP address, where # is network
interface number:
ifconfig eth# <IP>

10) Check the interface works:
ping <remote_host_IP>

Remove intermediate files
=========================
Please enter the following command to remove intermediate files generated
during the driver compilation:
make clean

Uninstallation
==============
Please enter the following command to uninstall your driver:
make uninstall

Bind the driver into kernel
===========================
In some applications (e.g. embedded OS), driver should be bound into the
kernel. The module installation/uninstallation describled in the above
sections are not appropriate. Below is the steps for binding driver in
kernel 2.4.x as an example:

1) Create a temporary directory:
mkdir /temp

2) Change to the temporary directory:
cd /temp

3) Copy driver (dlkfet-4.39.tar.gz) from DOS disk, (mcopy below is one tool in
mtools, if you didn't install mtools, you can type
'mount -t msdos /dev/fd0 /mnt' and use 'cp /mnt/dlkfet-4.39.tar.gz /temp'
command to copy the driver to the temporary directory):
mcopy a:dlkfet-4.39.tar.gz .

4) untar the archive file:
tar xzvf dlkfet-4.39.tar.gz

5) Change to the kernel source directory:
cd /usr/src/<kernel source>/driver/net

6) Create a directory for D-Link adapter driver and change to it:
mkdir dlkfet-4.39
cd dlkfet-4.39

7) Copy driver source form temporary directory to it:
cp /temp/dlkfet-4.39/* .

Replace the default Makefile with new Makefile with below 4 line content
(the Makefile used for driver binding into kernel is different with
the default one).
O_TARGET := rhinefet.o
obj-y := rhine_main.o rhine_proc.o rhine_wol.o
obj-m := $(O_TARGET)
include $(TOPDIR)/Rules.make

9) Add the dlkfet information to /usr/src/<kernel source>/drivers/net/Makefile:
(add the lines with # in the head)
...
...
subdir-$(CONFIG_E100) += e100
#subdir-$(CONFIG_RHINEFET) += dlkfet-4.39
...
...
ifeq ($(CONFIG_E100),y)
obj-y += e100/e100.o
endif
#ifeq ($(CONFIG_RHINEFET),y)
# obj-y += dlkfet-4.39/rhinefet.o
#endif

10) Add the dlkfet information to /usr/src/<kernel source>/drivers/net/Config.in:
(add the lines with # in the head)
...
...
mainmenu_option next_comment
comment 'Ethernet (10 or 100Mbit)'
bool 'Ethernet (10 or 100Mbit)' CONFIG_NET_ETHERNET
...
...
#dep_tristate 'D-Link PCI Fast Ethernet Adapter support' CONFIG_RHINEFET $CONFIG_PCI
...
...
endmenu

11) Now, when you use following command, make menuconfig or make xconfig,
you will find a new device in 'Network device support'->'Ethernet(10 or 100Mbits)'.
Its name is ' D-Link PCI Fast Ethernet Adapter support'.

when I do the mkdir/temp it tells me that the mkdir can not be completed because the /temp.file already exist that is one the other is the mount it wont let me monut anything at all can anyone help with this