This is the master tracking for bug ath5k driver connection and performance issues on IBM hardware running the latest Karmic 9.10 release. Please only post relevant debug information which will help developers track down the root cause of this issue. This means no ranting or comments to the affect of "me too's".
If you are affected by this issue using the ath5k driver on IBM hardware please be sure to verify the following before posting a comment or adding information:
1) Confirm this remains with the Karmic 9.10 release candidate or final release http://cdimage.ubuntu.com/releases/karmic/
2) Confirm if this remains after having installed and tested with linux-backports-modules-wireless-karmic-generic
sudo apt-get install linux-backports-modules-wireless-karmic-generic
3) If possible, also test and confirm with the latest upstream compat-wireless stack, this will allow for additional upstream developers to help examine this issue: http://wireless.kernel.org/en/users/Download
If step 1, 2, or 3 resolves this issue, please let us know. If you still can confirm this issue after steps 1 and 2, please run the following command which will automatically gather and attach relevant debug information:
This is the master tracking for bug ath5k driver connection and performance issues on IBM hardware running the latest Karmic 9.10 release. Please only post relevant debug information which will help developers track down the root cause of this issue. This means no ranting or comments to the affect of "me too's".
If you are affected by this issue using the ath5k driver on IBM hardware please be sure to verify the following before posting a comment or adding information:
1) Confirm this remains with the Karmic 9.10 release candidate or final release cdimage. ubuntu. com/releases/ karmic/ -modules- wireless- karmic- generic -modules- wireless- karmic- generic wireless. kernel. org/en/ users/Download
http://
2) Confirm if this remains after having installed and tested with linux-backports
sudo apt-get install linux-backports
3) If possible, also test and confirm with the latest upstream compat-wireless stack, this will allow for additional upstream developers to help examine this issue:
http://
If step 1, 2, or 3 resolves this issue, please let us know. If you still can confirm this issue after steps 1 and 2, please run the following command which will automatically gather and attach relevant debug information: