I don't think this is a regression. This driver was poor in jaunty as well for me:
01:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
Subsystem: D-Link System Inc Device 3a70
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at f8ff0000 (64-bit, non-prefetchable) [size=64K] Capabilities: <access denied>
Kernel driver in use: ath9k
Kernel modules: ath9k
The current kernel is definitely an improvement over jaunty either stock or with backports. I no longer see the disassociations and with wpa_supplicant the card sticks solidly to the access point. However it does still just stop working several times a day and requires an ifdown / ifup to get it going again. This is a PCI-Express card btw, not sure if that makes any difference.
I don't think this is a regression. This driver was poor in jaunty as well for me:
01:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
Capabilities: <access denied>
Subsystem: D-Link System Inc Device 3a70
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at f8ff0000 (64-bit, non-prefetchable) [size=64K]
Kernel driver in use: ath9k
Kernel modules: ath9k
The current kernel is definitely an improvement over jaunty either stock or with backports. I no longer see the disassociations and with wpa_supplicant the card sticks solidly to the access point. However it does still just stop working several times a day and requires an ifdown / ifup to get it going again. This is a PCI-Express card btw, not sure if that makes any difference.