D-link DFE-530TX 10/100M PCI 网卡驱动 V2.6.11

** ** ** D-Link PCI Fast Ethernet Adapter ** ** Linux Driver ** ** v5.04 Aug. 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. _osdep.h OS depended function and macro defined rhine_hw.h Rhine series MAC register supporting header file rhine_hw.c shared function for accessing and configurating Rhine series MAC 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 (rhinefet.tgz) 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/rhinefet.tgz /temp' command to copy the driver to the temporary directory): mcopy a:rhinefet.tgz . 4) untar the archive file: tar xzvf rhinefet.tgz cd rhinefet 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 8) 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-5.04.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/rhinefet.tgz /temp' command to copy the driver to the temporary directory): mcopy a:rhinefet.tgz . 4) untar the archive file: tar xzvf rhinefet.tgz 5) Change to the kernel source directory: cd /usr/src/<kernel source>/driver/net 6) Create a directory for rhine family adapter driver and change to it: mkdir rhinefet cd rhinefet 7) Copy driver source form temporary directory to it: cp /temp/rhinefet/* . 8) 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 rhine_hw.o obj-m := $(O_TARGET) include $(TOPDIR)/Rules.make 9) Add the rhinefet information to /usr/src/<kernel source>/drivers/net/Makefile: (add the lines with # in the head) ... ... subdir-$(CONFIG_E100) += e100 #subdir-$(CONFIG_RHINEFET) += rhinefet ... ... ifeq ($(CONFIG_E100),y) obj-y += e100/e100.o endif #ifeq ($(CONFIG_RHINEFET),y) # obj-y += rhinefet/rhinefet.o #endif 10) Add the rhinefet 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'. Note ==== 1) Make sure the link file /usr/src/linux (or /usr/src/linux-2.4) is linked to correctly kernel sources directory (eg: if you run 'uname -r', it appears "2.4.2-2", then the link file must be linked to /usr/src/linux-2.4.2 directory, or you will fail in compiling), and make sure there are kernel header files in /usr/src/linux/include directory (or /usr/src/linux-2.4/include), we need kernel header files in compling. 2) If you can't install driver in SUSE Linux using insmod or modprobe commands, and error messages appear (see below), please run 'uname -r' in command line. And make sure the result of 'uname -r' (eg: 2.4.2-4GB) is the same with the definition of UTS_RELEASE in /usr/src/linux/include/linux/version.h. If not, please modify the definition of UTS_RELEASE in /usr/src/linux/include/linux/version.h. rhinefet.o: