My initial suspicion is that madwifi attempts to initialize the RF MAC,
fails, and leaves the HW in a state that the ath5k driver cannot recover
from when next it is loaded. The proposed solution is to remove madwifi
from Jaunty LRM and make it a DKMS package.
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-meta => linux
Importance: Undecided => High
Assignee: (unassigned) => Tim Gardner (timg-tpi)
Status: New => Confirmed
Target: None => later
--
ath5k driver on Jaunty Alpha1
https://bugs.launchpad.net/bugs/306719
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
