I'm unable to get the card to connect with my wireless router (Netgear WGT624 V2). I have followed the Madwifi Newbie Guide to the letter and have compiled and installed without errors using madwifi-ng rev 1457. My kernel is 2.6.12-1.1381_FC3. Modprobe ath_pci and modprobe wlan_scan_sta returned no messages. My output from iwconfig at this point is:
wifi0 no wireless extensions

ath0 IEEE 802.11b ESSID:""
Mode: Managed Channel:0 Access Point: 00:00:00:00:00:00
Bit Rate:0 kb/s Tx-Power:50 dBm Sensitivity=0/3
Retryff RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=0/94 Signal level=-95dBm Noise level=-95dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx Excessive retries:0 Invalid misc:0 Missed beacon:0

Prior to bringing up the interface the power light blinks every 4 seconds or so. On bringing up the interface (ifconfig atho up) both lights on the card flash one after the other. Iwconfig has slight differences, as follows (I'm typing on a windows box since the wireless linux ain't up!):
ath0 IEEE 802.11g
Frequency:2.422GHz
Tx-Power:18 dBm

And here I'm stuck. I believe the basic network settings are good; the wired NIC works flawlessly (I have to remove it to put in the wireless NIC, and reboot). In the process of tearing my hair out over this in the past couple of weeks I have been able to make rare connections to the AP and have gotten on the net with the wireless setup, but I've lost the connection every time I've rebooted. The point is that the wireless NIC appears to be functioning properly.

I have noticed a couple of oddities at present.
1) I have no ifcfg-ath0 file - is this a function of having switched to the -ng from madwifi-old?
2) WHen the wireless is down, channel/freq settings set via iwconfig are reported properly. On bringing up the interface, though, it immediately starts scanning through all channels, confimred by issuing multiple iwconfig commands in a row. Each one yields a different frequency reading. The channel setting doesn't seem to "stick". All other iwconfig settings (essid, rate, etc) do stick, so basic commo with the card is working.
3) The System Log shows an entry:
localhost kernel: ath_pci: Unknown parameter 'irq'
the next entry is:
localhost kernel: ath_pci: 0.9.4.5 (svn 1457)
4) Using the gnome Network Configuration tool that is standard on FC3, I don't see ath0 as a device (the device tab), although the Atheros driver, associated with wifi0, does show up on the Hardware tab.
5) The settings for the atheros device on the hardware tab shows IRQ4, although if I'm reading the boot log correctly the wireless NIC is sharing IRQ 11. Again, is this something unique to the -ng iteration of Madwifi? BTW, IRQ4 is disabled on my PC as a serial IRQ.

So anyway...what the heck am I missing???

Thanks,

Al

Perhaps it would be best to try the RPM method of installing madwifi (which is slightly easier and more convenient) as described here on LQ: HOWTO Simple Installation of Madwifi in Fedora Core 4
I think the procedure for FC3 should be pretty much the same and doing it this way will no doubt also create any fedora specific files as well, which the source of madwifi will not do for you. See also http://madwifi.org/wiki/UserDocs/Distro/RedHat
Hope that helps.