I would suggest that users affected first try out one of the latest compat-wireless module before marking this bug, as there has been a lot of changes to the ath5k module in the last month or so. And despite completely silence from the devs on the bug rapports, this has solved at least the problems I was experiencing - using the compat-wireless-2010-05-22.tar.bz2 and running ./scripts/driver-select ath5k before compiling.
I would suggest that users affected first try out one of the latest compat-wireless module before marking this bug, as there has been a lot of changes to the ath5k module in the last month or so. And despite completely silence from the devs on the bug rapports, this has solved at least the problems I was experiencing - using the compat- wireless- 2010-05- 22.tar. bz2 and running ./scripts/ driver- select ath5k before compiling.