Thank you for the pointers. I'm pretty sure that I have the correct
source package installed on my system. In fact, it is the only source
package on my Debian installation ISO. Debian seems to have their
own naming scheme for the various different packages associated with a
particular kernel version. After investigating things further, I
determined that the problem is with the madwifi makefile and the
method of calculating the variable "KERNELRELEASE". The algorithm
doesn't quite work for the Debian source package because it does not
have any of the files that it looks for to determine the version. I
simply set it like this from the command line:
export KERNELRELEASE=$(uname -r)
and everything built and installed just fine and in the correct place
as far as Debian is concerned, which on my system was:
After installing to the right place, iwconfig worked as expected and I
was able to configure and bring up the ath0 interface.
Hopefully this will help any other Debian users who may have
experienced the same difficulty.
On Mon, Apr 28, 2008 at 9:06 PM, Pavel Roskin <proski@...> wrote:
> Quoting Dallas Clement <dallas.a.clement@...>:
> > Hi All,
> > I am having difficulty getting the madwifi drivers to work with my
> > D-Link adapter which happens to use the Atheros chipset. I built the
> > most recent trunk version of the madwifi code:
> > madwifi-trunk-r3574-20080426
> > I was able to build and install it just fine I think. At least I can
> > see that the ath_pci, wlan, and ath_hal modules have loaded just fine.
> It's still possible that it's different modules.
> > However, when I type iwconfig do not see any ath0 interface having
> > been created.
> > Here is the output of the 'lspci' command. As you can see, the
> > Atheros device is showing up as an 'unknown device'. Not sure if this
> > is something to worry about.
> That shouldn't be a problem. The PCI ID is not in the PCI ID database, but
> the driver knows it.
> > 03:00.0 Network controller: Atheros Communications, Inc. Unknown
> > device 0024 (rev 01)
> That's AR5008X.
> > I have also attached the full output of the 'dmesg' command. I have
> > extracted select portions here for your convenience. As you can see,
> > the kernel gets tainted when trying to load the ath modules.
> That's a clear sign that something is wrong with your installation. I
> suggest that you move away all old MadWifi modules (they start with "ath"
> and "wlan") and compile MadWifi against the header files corresponding tio
> the kernel you are running.
> Please follow the instructions in the INSTALL file.
> > I have some additional information also. When I installed the madwifi
> > binaries, I noticed that it placed the kernel module.dep and other
> > related files in the following location:
> > /lib/modules/2.6.18
> It means that you compiled it for a different kernel. I don't know why it
> happened, and I'm not a regular user of Debian, so I cannot provide mode
> details, but I suggest that you check whether the development kernel package
> matches the kernel you are running.
> > After installing the madwifi modules, I noticed that none of them were
> > being loaded because they had a separate modules.dep file. The only
> > way I was able to get the ath modules to load was to append the
> > modules.dep file found in the /lib/modules/2.6.18 dir to the
> > modules.dep file found in the /lib/modules/2.6.18-6-amd64 dir. I'm
> > sure there must be a better way to do this.
> Don't do it. Compile for the correct kernel.
> Pavel Roskin