Atheros AR5211 unable to connect to WPA-Personal AP

Bug #463581 reported by Leann Ogasawara
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Linux
Expired
Medium
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I'm opening this new bug on behalf of bug reporter bjaglin. Will attach the relevant debug files and comments they posted to bug 461419:

bjaglin wrote:

"Attached log files via apport-collect as requested after:

1) Confirming this remains with the Karmic 9.10 release candidate or final release
    http://cdimage.ubuntu.com/releases/karmic/
2) Confirming this remains after having installed and tested with linux-backports-modules-wireless-karmic-generic
    sudo apt-get install linux-backports-modules-wireless-karmic-generic

I can't connect at all to my home WPA-Personal AP. I could not get any better results by getting closer to the signal. AFAIK, I was using madwifi under Jaunty on the same hardware, and despite a slow rate that I thought was due to the old 802.11b adapter, it was reliable. I have a rt2870sta USB dongle which had a similar symptom (association to the AP failing); installing linux-backports-modules fixed the problem for it, but not for the built-in adapter.

The same hardware at the exact same distance from the AP works just fine in Win7. If I had no USB dongle, this would be a showstopper for me."

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: brice 1449 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f5dfae80-7439-4d40-890b-fc06c78c51c8
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091026.1)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 2373G1G
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=8ee24573-73d0-498d-babd-af66746a8ef4 ro elevator=deadline hpet=force quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_DK.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic 2.6.31-14.16
 linux-firmware 1.24
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1493): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1493): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1554): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1563): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 02/27/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDOWW (3.20 )
dmi.board.name: 2373G1G
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1RETDOWW(3.20):bd02/27/2006:svnIBM:pn2373G1G:pvrThinkPadT40p:rvnIBM:rn2373G1G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2373G1G
dmi.product.version: ThinkPad T40p
dmi.sys.vendor: IBM

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :
description: updated
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi bjaglin,

I've also gone ahead and opened a bug upstream for you:

http://bugzilla.kernel.org/show_bug.cgi?id=14512

If you can, please also subscribe to that upstream bug and respond to any additional questions/comments posted by the upstream developers. Note, you may first need to create an account with the upstream bugzilla.kernel.org before you can subscribe to the upstream bug. Thanks!

Changed in linux:
status: Unknown → Confirmed
Changed in linux:
status: Confirmed → Incomplete
Revision history for this message
Bill Blesbok (bblesbok) wrote :

here's a hack that worked for me with ath5k driver on LinuxMint kernel 2.6.31-14-generic. It's only for those who'd connect to an unencrypted network.

In my case, my AP was associating only to be immediately disassociated again. Since wpa_supplicant seemed to be getting in the way, I disabled it. CODE:

cp /etc/dbus-1/system.d/wpa_supplicant.conf /home/myname/backup/etc.dbus-1.system.d.wpa_supplicant.conf
sudo rm /etc/dbus-1/system.d/wpa_supplicant.conf

Revision history for this message
alcarola (alcarola) wrote :

I got tired of the problems with ath5k, such as freezing my computer (90% sure ath5k was the culprit), network manger roaming to none etc. and installed the windows driver under ndiswrapper. Worked like a charm -- why didn't I think of this immediately?

Instructions in the last post in the following thread: http://ubuntuforums.org/archive/index.php/t-429537.htm

Maybe this can be of some help to someone else as well.

(Sorry for crossposting this comment to several discussion threads.)

Changed in linux:
status: Incomplete → Expired
Changed in linux:
importance: Unknown → Medium
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.