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.
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.