I did manage to correct my problem.  I used the precompiled SuSE rpms and not the source code rpm.  I also installed them using the command line.  What I eventually discovered was that I had to use the “make” and “make install” commands.  Once I did, everything started to work perfectly.  I only had to choose to connect via the ath0 interface.  The “modprobe ath0” or “insmod ath0” never did work, and only produced errors.  As a last ditch effort I issued the “make install” command and that did the trick.


Ron Schmiegelt

CNE, MCSE, CCNA, CCEA, Linux +, Security +, A + 



From: Ronald Schmiegelt [mailto:rschmiegelt@sbcglobal.net]
Sent: Monday, April 23, 2007 11:04 PM
To: 'madwifi-users@lists.sourceforge.net'
Subject: DLink WDA-1320 on SuSE 10.1


I have been having problems getting a wireless card to work in my SuSE 10.1 platform.  I now have a DLink WDA-1320 with an Atheros AR 5005 chipset.  This card is on both the SuSE and MadWiFi HCL.  I downloaded and installed the most recent (0.9.3) SuSE rpms from MadWiFi.  The hwinfo and lspci correctly identify the card and chipset.  However, YaST detects it as a wireless PCI card with the Orinoco chipset. 


The only thing missing in the hwinfo is that this DLink card is not assigned a Device Name.  I don’t know what else I can do to properly configure this card and get it to work.  I will appreciate any help that I can get.


Ron Schmiegelt