1. To freshly make the driver go to the /nsc/lin2.2 directory and execute "make" 2. To remove the binaries execute "make clean" 3. If the machine on which the testing is done is an SMP machine, please include the flag -D__SMP__ in the CFLAGS of the Makefile. 4. After the dpm.o ( The driver module ) is made, to load the driver execute the command "insmod dpm.o". We can uload the driver by doing "rmmod dpm". 5. After loading the driver, get the interface name( eg: eth0, eth1 etc) for the device. The last line in the messages listed will indicate the name of the interface for the driver. If the message is not coming on the console, we can see the messages in the kernel buffer by executing "dmesg" on the command line. The last line in that will indicate the interface name 6. To configure IP for the interface. ifconfig <interface-name> <ip-addr> eg: ifconfig eth0 10.10.10.1 To shutdown the interface. ifconfig <interface-name> down eg: ifconfig eth0 down Please note that it may appear to hang on doing an "ifconfig", but it is just momentary and it will soon come out of that. The link becomes active only after about 20 seconds since the "ifconfig". 7. Now we are all set to go with the driver. 8. To make the driver load when the system boots up, the following lines needs to be put in any of the startup scripts like /etc/rc.d/rc.local or /etc/rc.d/init.d/network /sbin/insmod /working/oct1/dpm.o /sbin/ifconfig <interface-name> <ip-addr> 9. The tunable parameters of the driver, can be given at load time as parameters to "insmod". eg: insmod dpm.o MaxTxDesc=150 MaxRxDesc=150 RxBufSize=2048 insmod dpm.o SetAutoNeg=0 MediaSpeed=100 The various tunable parameters are: (a) MaxTxDesc This is the maximum number of transmit descriptors that will be allocated. This value should be atleast 100. The default value is 200. (b) MaxRxDesc This is the maximum number of receive descriptors that will be allocated. This value should be atleast 100. The default value is 200. (c) RxBufSize This is the size of the receive descriptors that are allocated. The default value is 2048. It should be 2048 for good performances. The values of this should be 4096 when using jumbo frames to get better performances. (d) SetAutoNeg This is the flag to request Auto Negotiation. A value of 1 will enable auto negotiation and a value of 0 indicates disabling auto negotiation, in this scenario the MediaSpeed can be set appropriately to force the Link speed to the desired value. Default value is 1. (e) MediaSpeed This value indicates the MediaSpeed to which the NIC should be forced to, in the case of Auto Negotiation being disabled. This value assumes significance only when SetAutoNeg = 0. The default is 1000. (f) NCBit If IEEE Compliance then NCBit should have value 1 else 0. Default value is 1. 10.To try jumbo frames, the mtu size can be increased using the ifconfig utility, as follows ifconfig <interface-name> mtu <mtu-size> eg: ifconfig eth0 mtu 3000 The "RxBufSize" tunable parameter should have a value of 4096 to get better performance when using jumbo frames. <mtu-size> can be increased upto 4000 bytes for sane operation. 11.The priority queues in the driver can be enabled by compiling the driver with the PRIORITY_QUEUES cflag put in the makefile. When priority queues are enabled, the number of receive descriptors ( MaxRxDesc ) may have to be reduced or the allocation may fail on low end systems with the memory limitations. 12.The failure messages, like failure in allocating resources like receive buffers etc can be printed if the driver is made with the FAILURE_MESSAGES cflag in the makefile. 13.The checksum offload feature can be turned on by compiling the driver with the CHECKSUM cflag in the makefile. 14.The driver can have both memory mapped and programmed i/o. This can be done by compiling the driver with the appropriate cflags in the makefile for memory mapped I/O the cflag used should be MEMMAPPED_IO and for programmed I/O it should be IOMAPPED_IO. In systems like the HP KAYAK, the memory mapped I/O may not work, and we may have to use programmed I/O. 15.If any messages begining with "ASSERTION FAILED" is seen, it is an erroneous behaviour and please inform the support team.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.