(C)Copyright 2003-2006 Marvell(R). All rights reserved. -------------------------------------------------------------------------------- dlgebsd60x86-8.14.8.3.htm created 17-Jan-2007 Readme File for dlgebsd60x86-8.14.8.3.tgz DGE-530T/560T Gigabit Ethernet Adapter This file contains 1 Overview 2 Required Files 3 Installation 3.1 Installation of driver software 3.2 Deinstallation of driver software 4 Parameters -------------------------------------------------------------------------------- 1 Overview The dlgebsd driver supports the DGE-530T/560T Gigabit Ethernet Adapter on the FreeBSD 6.0 operating system running on Intel x86 hardware. 2 Required Files For proper software installation the following package file is required: dlgebsd60x86-8.14.3.3.tgz . 3 Installation This section describes the installation of the driver software on a computer running FreeBSD 6.0. 3.1 Installation of driver software NOTE: root privileges are necessary to install the driver. First of all, the package containing the driver software must be installed. This is done by typing: pkg_add dlgebsd60x86-8.14.3.3.tgz This installs the driver binary into /boot/kernel and the manpage into /usr/share/man/man4. In order for the system to load the driver automatically on booting, the following line must be added to the file /boot/loader.conf: if_dlge_load="YES" In addition to this, the following line must be added to the /etc/rc.conf file to configure the interface when the system is booted: ifconfig_dlge0="inet 192.168.100.1" This assumes a local IP address of 192.168.100.1. You must replace this IP address with your computer's IP address. On reboot, the driver will be loaded and the interface configured automatically. It is also possible to load and unload the kernel module by hand. To load the kernel module by hand, type: kldload if_dlge.ko To unload the kernel module by hand, type: kldunload if_dlge.ko 3.2 Deinstallation of driver software To deinstall the driver, type: pkg_delete dlgebsd60x86-8.14.3.3 This removes the driver kernel module from the /boot/kernel directory, as well as the manpage from the /usr/share/man/man4 directory. If you have set up your machine to load the driver automatically, you must delete the lines you added in /boot/loader.conf and /etc/rc.conf 4 Parameters There are a number of driver parameters that can be changed to suit different operating conditions. These parameters include: o Speed o Duplex settings o Hardware checksumming o Clocking Master o Virtual LANs o Jumbo frames o Interrupt moderation All these parameters except DualNet mode and Interrupt moderation are modified with the ifconfig utility. For detailed information about the usage of this program, please consult the relevant FreeBSD manual pages (ie. man ifconfig). Speed ===== The following adapter speed settings are available: auto Auto-negotiated speed setting (default) 1000baseTX 1000baseTX, no auto-negotiation 100baseTX 100baseTX, no auto-negotiation 10baseT/UTP 10baseT/UTP, no auto-negotiation To change the adapter speed setting to 100baseTX, type: ifconfig dlge0 media 100baseTX To switch it back to auto-negotiation, type: ifconfig dlge0 media auto Duplex ====== Please note that half duplex at 1000baseTX is not supported. Duplex settings (full or half duplex) are set with the mediaopt keyword. For example, to set 100baseTX, half duplex, type: ifconfig dlge0 media 100baseTX mediaopt half-duplex To clear half-duplex mode, prefix the mediaopt keyword with a hyphen: ifconfig dlge0 media 100baseTX -mediaopt half-duplex Note that clearing half-duplex mode implies setting full-duplex. Checksumming ============ By default, hardware checksumming is enabled for both receive and transmit. To turn this feature off, type: ifconfig dlge0 -rxcsum or ifconfig dlge0 -txcsum Note that it is currently not possible to switch hardware checksumming on or off independently. It is only possible to switch both transmit and receive together. To turn hardware checksumming on, type: ifconfig dlge0 rxcsum or ifconfig dlge0 txcsum Clocking Master =============== This parameter only applies to Copper adapters with a fixed speed of 1000baseTX. In this case, autonegotiation is disabled and each side of the link must agree on who is clocking master and who is slave. By default, the adapter is clocking slave ie. the other end is the master. If the reverse is desired (this adapter should be clocking master), the "flag0" media option must be set via ifconfig. To set clocking master, type: ifconfig dlge0 media 1000baseTX mediaopt flag0 To reset clocking master to the default of slave, type: ifconfig dlge0 media 1000baseTX -mediaopt flag0 Virtual LANs ============ Virtual LAN (VLAN) functionality is supported by the dlge driver in conjunction with FreeBSD's if_vlan driver. This can be verified by checking the output of ifconfig, where the line listing the interface options should include VLAN_MTU. This means that the driver (and thus the hardware) can accept packets that are 4 bytes longer than the norm (due to the added vlan tag). For further details, see the section 4 manpage for vlan. To use vlans, one or more vlan interfaces must be created and bound to the physical interface. In the example below, we assume a physical interface of dlge0 and two vlan interfaces, vlan0 and vlan1, with vlan IDs of 2 and 3 respectively. Create two vlan interfaces: ifconfig vlan0 create ifconfig vlan1 create Assign a vlan ID to each vlan device and attach a physical interface: ifconfig vlan0 vlan 2 vlandev dlge0 ifconfig vlan1 vlan 3 vlandev dlge0 Use vlan interface as normal: ifconfig vlan0 inet 192.168.100.1 ifconfig vlan1 inet 192.168.101.1 To remove the vlans and their interfaces: ifconfig vlan0 destroy ifconfig vlan1 destroy Jumbo frames ============ For some applications throughput can be enhanced by the use of frames larger than the default of 1500 bytes. These so-called jumbo frames are set by the mtu (maximum transfer unit) switch of ifconfig. To set the frame size to the maximum of 9000 bytes, type: ifconfig dlge0 mtu 9000 To reset the adapter to use normal (1500 byte) frames, type: ifconfig dlge0 mtu 1500 Note that any frame size between 1500 and 9000 is valid. Note also that your switch must be capable of processing large frames and must be appropriately configured to do so. If you are using jumbo frames, do not forget to configure other hosts on the same switch and network to use the same frame size. Failure to do this will result in faulty network operation with large numbers of frame errors. Interrupt moderation ==================== In certain circumstances, it may be desirable to limit the number of interrupts the card generates per second in order to reduce the interrupt processing overhead. This is done with the sysctl command, which allows the user to examine and set the value of the driver's interrupt moderation variable. This value can be displayed by typing: sysctl hw.dlgec0 It can be modified by typing: sysctl -w hw.dlgec0.max_ints_per_sec=4000 In order for the setting to take effect automatically on system boot, the above line may be added to the file /etc/sysctl.conf A value of 0 stops interrupt moderation. The value to set depends on the speed of the computer (higher for faster machines) and your requirements for throughput versus response time. Note that high throughput is achieved at the expense of response time. A value between 1000 and 20000 is reasonable, although the exact setting for optimum performance has to be determined for each system via benchmark tests. ***End of Readme File***Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.