Results 1 to 4 of 4
Ok i am not new to Linux but i am new to driver install... I have a driver for my D-Link DWL-520+ (If any one needs it post in here ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 01-21-2004 #1Just Joined!
- Join Date
- Jan 2004
- Posts
- 6
Need help installing Drivers on Mandrake 9.1
Ok i am not new to Linux but i am new to driver install... I have a driver for my D-Link DWL-520+ (If any one needs it post in here and i will send you an e-mail) It says something about "Make" these are the install notes
--------------------------------------------------------------------------
Introduction:
-------------
This document is intended to explain the steps necessary to get the binary
releases of the acx100 drivers up and running on distributions other than those
directly listed in the binary driver package.
The following table shows the available binary modules in the current binary
driver package (acx100_bin_20030503.tgz), the linux distribution they were built
with and the version of GCC that was used to compile them.
Module Distro GCC
------------------------------------------
2.4.18-14 RedHat 8.0 3.2
2.4.18-6mdk Mandrake 8.2 2.96
2.4.18-6mdk3 Mandrake 8.2 3.0.4
2.4.18-686 Debian 2.95.4
2.4.19-16mdk Mandrake 9.0 3.0.4
2.4.20-8 RedHat 9.0 3.2.2
2.4.21-0.13mdk Mandrake 9.1 3.2.2
Installation
------------
Make sure you have a recent enough version of wireless tools installed, the
binary drivers are built with wireless tools version 15.
Obtain and extract the binary driver package:
"tar -xvzf acx100_bin_20030503.tgz"
If you happen to be running a stock distribution that matches one of the
supplied binaries, then you should be able to simply run the installation script
"InstallAcx100" and skip straight to the Configuration section, lucky you.
Relabelling the module
----------------------
If your distribution doesn't match, or you are using a custom Linux system then
all is not lost, as long as your kernel is compatible with one of the binaries
you should be o.k.
The first step is to determine what you are running if you don't already know.
The kernel version can be obtained using "uname -r", you should also know what
version of gcc your kernel was compiled with. If you are using a distribution
and didn't compile it yourself then "gcc -v" will display the version of the gcc
compiler you have installed, which should match the compiler used to build the
kernel.
# TODO Perhaps add a list of popular distributions and their GCC versions?
The table above shows the names of the modules which match the kernel versions,
and the version of gcc that they are built with. You need to choose a module
that matches your kernel version and gcc version. Tip: If you are using a
'stock' 2.4.21 or 2.4.19 kernel, then you will probably find that the 2.4.20 and
2.4.18 kernels respectively are a closer match than the Mandrake kernels of the
same version number.
Next create a subdirectory in the installation directory that matches your
"uname -r" value and make a copy of the driver for your chosen kernel. The
kernel file should be renamed "acx100sta-"uname -r".o. (Clearly you don't
'need' to make a copy of the file in a subdirectory named as such if you
install the module by hand, but it might be handy to keep the installation all
together)
Then enter the new directory and relabel the kernel info on this file with the
following commands: echo -ne "kernel_version="`uname -r`"\0" > version
objcopy --remove-section=.modinfo --add-section=.modinfo=version acx100sta-*.o
Try to install using the install script to see if this works for you. If so,
just skip to the configuration section.
If the module fails to initialise then you'll most likely have unresolved
symbols problems. To see a list of the failed symbols, type: depmod -ae
If the dependency problem is with version information on symbol names you will
see a series of unresolved symbols ending in "_R" followed by a hex number
e.g. "__ioremap_R9eac042a".
If the missing symbols are due to mismatches between symbol name suffixes, then
running the "fixscript" script on the module may solve the problem. Then try
installing again.
If there are still missing symbols but they appear to be just for debugging /
logging, you may be able to get away with writing a small C app that creates a
small stub function and then using "ld -r" to link the object file into the
module.
Configuration
-------------
If the module loads without problems, (you will get a warning that loading the
module taints your kernel, its safe to ignore this warning) and the card springs
into life then you're ready for the next step....
Firstly add to /etc/modules.conf
alias eth1 acx100sta
Either write a start script to initialise your card, or modify your
distributions scripts to work around some of the problems with the binary
driver. It appears that it is necessary to repeat the iwconfig commands for the
card to associate correctly with an AP with a short delay in between.
Note, to change the rate of the card (e.g. to extend range) use:-
"iwconfig eth1 rate X" where X is (5=22M, 4=11M, 3=5.5M, 2=2M)
Generic start script
--------------------
#! /bin/bash
iwconfig eth1 nick "mynick" mode 2 channel 6 essid myessid
ifconfig eth1 192.168.0.x #for static ip
sleep 2
iwconfig eth1 key 012abc3456
iwconfig eth1 key restricted
iwconfig eth1 nick "mynick" mode 2 channel 6 essid any
sleep 5
iwconfig eth1 nick "mynick" mode 2 channel 6 essid myessid
ifconfig eth1 192.168.0.x
route add default gw 192.168.0.x
I have Wireless tools but i dont know how to install this:
- 01-21-2004 #2Linux Guru
- Join Date
- Oct 2001
- Location
- Täby, Sweden
- Posts
- 7,578
I don't really see what the problem is? On what step in these instructions did you stumble?
- 01-21-2004 #3Just Joined!
- Join Date
- Jan 2004
- Posts
- 6
Installing Drivers
Well I try to install wireless tools and theres no pakage just files... i click on them and they open in its not pad... theres no make command
- 01-21-2004 #4Linux Newbie
- Join Date
- Jan 2004
- Location
- Istanbul,Turkey
- Posts
- 151
(if i understood your problem correct)
the source files does not include make command,it is already installed with your distro.
unpack the sources,cd to them,
type:
Code:./configure make make install


Reply With Quote
