The
ath5k driver should have been auto-magically installed and running. (I'm using an HP dv9800 with an Atheros card using the
ath5k driver to write this message.)
One "gotcha" with the driver is that it doesn't change the light by the Wifi power switch to blue when the WiFi is working, so it's hard to tell if the switch (cleverly placed where sliding the laptop on your lap can power off the WiFi) is in the "off" position.
Here's what I see in the kernel messages on my laptop:
Code:
$ dmesg | egrep -i '(ath|lan)'
ricoh-mmc: Copyright(c) Philip Langdale
ath5k 0000:03:00.0: PCI INT A -> Link[LK4E] -> GSI 19 (level, low) -> IRQ 19
ath5k 0000:03:00.0: setting latency timer to 64
ath5k 0000:03:00.0: registered as 'phy0'
wmaster0 (ath5k): not using net_device_ops yet
wlan0 (ath5k): not using net_device_ops yet
ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
device-mapper: multipath: version 1.0.5 loaded
type=1400 audit(1245587556.835:5): avc: denied { mounton } for pid=1308 comm="mount.ntfs-3g" path="/Vista/Recovery" dev=sda1 ino=50318 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:fusefs_t:s0 tclass=dir
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with AP 00:13:49:54:4f:0c
wlan0: authenticated
wlan0: associate with AP 00:13:49:54:4f:0c
wlan0: authenticate with AP 00:13:49:54:4f:0c
wlan0: authenticated
wlan0: associate with AP 00:13:49:54:4f:0c
wlan0: RX AssocResp from 00:13:49:54:4f:0c (capab=0x431 status=0 aid=2)
wlan0: invalid aid value 2; bits 15:14 not set
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: authenticate with AP 00:13:49:54:4f:0c
wlan0: authenticated
wlan0: associate with AP 00:13:49:54:4f:0c
wlan0: RX ReassocResp from 00:13:49:54:4f:0c (capab=0x431 status=0 aid=2)
wlan0: invalid aid value 2; bits 15:14 not set
wlan0: associated
wlan0: no IPv6 routers present
ath5k phy0: unsupported jumbo
