From: Michael Renzmann <madwifi@no...> - 2006-05-17 05:10:10
Removed madwifi-devel from the CC list, as almost all questions are not
related to driver development.
> Output from 'iwconfig ath0':
> ath0 IEEE 802.11b ESSID:"goesh"
> Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
You don't have an association. Check whether the configuration of client
and AP do match, and correct settings that don't.
> If I do an "modprobe ath_pci autocreate=none", I don't see the ath0
> interface at all.
Of course not, since you tell the driver to not autocreate ath0. :)
Read more at http://madwifi.org/wiki/UserDocs/autocreate
> Also, where can I get hold of the Ath PCI interface spec?
Apart from the stuff that's in the wiki and the in-source comments there
are no publically available specs/docs about the internals of the card. If
you need that, you have to sign an NDA with Atheros.
From: Michael Renzmann <madwifi@no...> - 2006-05-17 07:22:41
> Encryption is off on both the client and the AP. What other configurations
> should I check?
SSID, for example. Mode of operation (if AP is set to 11g only, and the
client to 11a or 11b-only, the client won't be able to associate). The AP
might have a MAC-based ACL that prevents the client from associating. And
In case you don't find obvious reasons, you should enable debug output
related to scanning and associating, maybe that gives some valuable hints.
Refer to http://madwifi.org/wiki/DevDocs/AthDebug for details.