Comment 19 for bug 784351

For anyone else with this problem, a workaround would be to install the latest snapshot of the madwifi driver from madwifi-project.org, which is working perfectly so far. (I'd still like to see ath5k fixed though :)