Disabling ath5k in 2.6.27
Bug #288148 reported by
Loïc Minier
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Critical
|
Tim Gardner | ||
Intrepid |
Fix Released
|
Critical
|
Tim Gardner | ||
linux-lpia (Ubuntu) |
Fix Released
|
Critical
|
Amit Kucheria | ||
Intrepid |
Fix Released
|
Critical
|
Amit Kucheria |
Bug Description
ath5k as released in 2.6.27 does not work very well for many people. Having it co-exist with madwifi also causes races like in bug 284354.
The better option is to disable the in-kernel ath5k and recommend that users install LBM
The linux-backports
Related branches
Changed in linux: | |
importance: | Undecided → Critical |
status: | New → In Progress |
Changed in linux-lpia: | |
assignee: | nobody → amitk |
Changed in linux: | |
milestone: | none → ubuntu-8.10 |
Changed in linux-lpia: | |
importance: | Undecided → Critical |
milestone: | none → ubuntu-8.10 |
Changed in linux-lpia: | |
status: | New → Fix Committed |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Fix Released → New |
To post a comment you must log in.
I'm not milestoning this; it's nice to get the driver disabled for intrepid, but hell wont freeze over if it isn't.
I'm tracking status in intrepid, and for jaunty we don't care: the in kernel ath5k as of early 2.6.28 will be good enough to replace madwifi completely.