I am working on a home gate product which uses Atheros mini-pci to
support AP mode. The madwifi driver I am using is 0.9.2 and the Linux
kernel is 2.4.20. When I built the madwifi as a part of Linux kernel,
everything is working perfect. However, when I config the madwifi as a
loadable module, I have problem to bring up the wireless network
interface. The commands I am using to check is as follows:
sh-2.05a# ifconfig ath0 up
sh-2.05a# iwconfig ath0
ath0 IEEE 802.11b ESSID:""
Mode:Master Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm Sensitivity=3D0/3
Retry:off RTS thr:off Fragment thr:off
Link Quality=3D0/94 Signal level=3D-95 dBm Noise level=3D-95 =
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Do anyone have similar issue and provide me a solution or any clue?
From: Pavel Roskin <proski@gn...> - 2007-03-27 20:11:44
On Tue, 2007-03-27 at 15:23 -0400, Zhang, William wrote:
> I am working on a home gate product which uses Atheros mini-pci
> to support AP mode. The madwifi driver I am using is 0.9.2 and the
> Linux kernel is 2.4.20.
The oldest supported kernel is 2.4.22. The documentation in MadWifi
0.9.2 stated incorrectly that 2.4.20 was supported. You must have made
some modifications to compile MadWifi for Linux 2.4.20.
> When I built the madwifi as a part of Linux kernel, everything is
> working perfect. However, when I config the madwifi as a loadable
> module, I have problem to bring up the wireless network interface. The
> commands I am using to check is as follows:
Please don't write in HTML, it's hard to read and to quote. I don't see
anything wrong with iwconfig output. Sure, the master mode cannot work
without an ESSID, but you didn't say if you set it.
Generally, when describing as problem, describe what you do, what you
see and what you expect. Your expectation is unclear in this case.
Maybe you don't have CONFIG_KMOD enabled, so some modules are not loaded
See kernel messages using dmesg command for possible error messages from
From: Michael Renzmann <madwifi@no...> - 2007-03-28 04:46:00
> The commands I am using to check is as follows:
> sh-2.05a# ifconfig ath0 up
> sh-2.05a# iwconfig ath0
> ath0 IEEE 802.11b ESSID:""
> Mode:Master Frequency:2.412 GHz Access Point: Not-Associated
What behaviour are you expecting instead of that you see? You noticed that
the card is working in Master mode (hence works as AP), right?