AR5212 (Atheros Card) no longer functions since upgrade to Jaunty

Bug #374560 reported by Craig Huffstetler
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MadWifi
New
Undecided
Unassigned
linux-backports-modules-2.6.28 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

My Atheros 5212 on my IBM Z60m no longer functions after upgrading from Intrepid Ibex to Jaunty.

It functioned in the last two previous versions of Ubuntu just fine; however, no matter what I do (using MadWifi drivers, enabling the restricted driver, disabling the restricted driver, etc.) it will not function correctly.

This is what it does:

- It will find networks (WiFi),
- However, it will *sometimes* connect to the networks briefly (WPA, WEP, no security at all),
- But then it will immediately disconnect after connecting.

I do not understand why it is doing this, but I do know this issue did not exist at all during Intrepid or Hardy.

I have tried everything (above) to get it to work, however nothing worked.

This was the same for both of the following scenarios:
- Upgrade from Intrepid; and
- Clean install of Jaunty on said machine.

No matter what the WiFi connection does not function as intended (or as it did before the installation OR upgrade of Jaunty).

Revision history for this message
Craig Huffstetler (xq) wrote :
summary: - AR5212 no longer functions since upgrade to Jaunty
+ AR5212 (Atheros Card) no longer functions since upgrade to Jaunty
Revision history for this message
Craig Huffstetler (xq) wrote :
Revision history for this message
Craig Huffstetler (xq) wrote :
Revision history for this message
Craig Huffstetler (xq) wrote :
Revision history for this message
Craig Huffstetler (xq) wrote :
Revision history for this message
Craig Huffstetler (xq) wrote :
Revision history for this message
Craig Huffstetler (xq) wrote :
Revision history for this message
schmolch (saschaheid) wrote :

Same card, same problem.
Connection is up but data only transferred 1% of the time.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Craig,

I assume this is still an issue for you? If so, can you attach the output of:

sudo lspci -vnvn > lspci-vnvn.log

Additionally, can you try installing the linux-backports-modules-jaunty package:

sudo apt-get install linux-backports-modules-jaunty

It contains an updated compat-wireless stack which may help. Please let us know your results. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: compat-wireless
Revision history for this message
Craig Huffstetler (xq) wrote :

Greetings Leann,

I installed:

linux-backports-modules-jaunty

Awhile back. It did correct this problem for me after I:

disabled & re-enabled the "Atheros" driver in the Restricted Drivers panel.

Again, this solved the problem for me.

I know the "Atheros problem" exists for quite a few others (when doing a simple bug search). I've seen the problem reported quite a bit since beta and final release in Jaunty. I've been following them when I touch each of them. I'm not sure if this will fix the issue for the other bugs or not, but either way I'd like a usability sane way (like in Jaunty & Intrepid) to "just make the wireless cards work" upon install.

If I can do anything else to assist you -- please let me know.

Sincerely,

Craig

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Craig,

Thanks for the feedback. Indeed our goal is to make everything "just work" out of the box. Unfortunately with the Jaunty release we did see some atheros related issues which seemed to have been resolved with the updated compat-wireless stack in linux-backports-modules. The purpose of the linux-backports-modules package is to provide users with the ability to run these newer updates. Hopefully Karmic will not see this issue. For now, please continue to use linux-backports-modules. Thanks.

affects: linux (Ubuntu) → linux-backports-modules-2.6.28 (Ubuntu)
Changed in linux-backports-modules-2.6.28 (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.