Problems with wireless with F8 on MacBook

[PaulFXH]

Running Fedora 8 on a MacBook (C2D with Atheros chipset in wireless card). I've had no problem setting up wireless on a few other Linux distros I had tried on this machine and I always used the latest madwifi drivers.
However, in F8, things are not going so well.
First I installed the drivers from here and then I went through this madwifi guide to get the ath0 wireless device properly setup to the existing AP.
No errors were received until the final step where I use the command "dhclient ath0" to look for dhcp offers of IP addresses. Then I got this:

[root@localhost ~]# dhclient ath0
Internet Systems Consortium DHCP Client V3.0.6-Fedora
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
/sbin/dhclient-script: configuration for ath0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: ath0: No such file or directory
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:1c:b3:b4:9e:98
Sending on LPF/ath0/00:1c:b3:b4:9e:98
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.1.254
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.254
/sbin/dhclient-script: configuration for ath0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: ath0: No such file or directory
bound to 192.168.1.1 -- renewal in 1655 seconds.

The script /etc/sysconfig/network-scripts/network-functions contains no reference at all to an "ath" device but seems to use the term "eth" for wireless devices.
As madwifi seems to prefer "ath", I wonder if this is the source of my problem.
If it is, and I changed the line that reads

Wireless)
DEVICETYPE="eth"

to read "ath" instead, would this resolve this issue?

Thanks for any comments
Paul

[ppesci]

I have the same machine, and after some problems with madwifi (at that time the chip was not supported), I try with ndiswrapper snd worked fine.

HTH

[PaulFXH]

Thanks, but my preference is to only use Windows-associated stuff as a very last resort.
As it happens, my ath0 wireless device has suddenly started working although I don't at all understand why.
In particular, no offers whatsoever were received when I typed "dhclient ath0". In addition, I wasn't asked for the WEP key nor for the keyring password. Although I did input manually the WEP key, I can't find anywhere where it might be stored.
OK, great that it's now working but it would be nice to understand what were the key steps in getting it to finally work.