[Lucid/Karmic] Atheros AR5001 fails to connect(but finds networks)

Bug #565367 reported by ciiccii
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Since 9.10 i can't use my laptop with ubuntu because i have ath5k doesn't work properly with my atheros chipset. It finds the the networks but can't connect.

$uname -a
Linux mistique 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux

This is the output of dmesg:

[16758.900902] __ratelimit: 4 callbacks suppressed
[16758.900913] ath5k phy0: noise floor calibration failed (2442MHz)
[16759.458961] ath5k phy0: noise floor calibration timeout (2417MHz)
[16759.635234] ath5k phy0: noise floor calibration failed (2427MHz)
[16759.738354] ath5k phy0: noise floor calibration failed (2432MHz)
[16759.853986] ath5k phy0: noise floor calibration failed (2437MHz)
[16760.125631] ath5k phy0: noise floor calibration failed (2442MHz)
[16760.223822] ath5k phy0: noise floor calibration failed (2447MHz)
[16760.324577] ath5k phy0: noise floor calibration failed (2452MHz)
[16760.584230] ath5k phy0: noise floor calibration failed (2457MHz)
[16760.874464] ath5k phy0: noise floor calibration failed (2462MHz)
[16818.734481] __ratelimit: 4 callbacks suppressed
[16818.734492] ath5k phy0: noise floor calibration failed (2442MHz)
[16819.182157] ath5k phy0: noise floor calibration timeout (2417MHz)
[16819.363967] ath5k phy0: noise floor calibration failed (2427MHz)
[16819.464543] ath5k phy0: noise floor calibration failed (2432MHz)
[16819.586548] ath5k phy0: noise floor calibration failed (2437MHz)
[16819.689925] ath5k phy0: noise floor calibration failed (2442MHz)
[16819.803771] ath5k phy0: noise floor calibration failed (2447MHz)
[16819.952555] ath5k phy0: noise floor calibration failed (2452MHz)
[16820.064614] ath5k phy0: noise floor calibration failed (2457MHz)
[16820.468863] ath5k phy0: noise floor calibration timeout (2462MHz)

$ sudo lshw -C Network
  *-network
       description: Wireless interface
       product: AR5001 Wireless Network Adapter
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wlan0
       version: 01
       serial: 00:15:af:02:63:b3
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath5k latency=0 multicast=yes wireless=IEEE 802.11bg
       resources: irq:19 memory:dc7f0000-dc7fffff
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: whoami 1401 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xdc6b8000 irq 22'
   Mixer name : 'Realtek ALC660-VD'
   Components : 'HDA:10ec0660,10430000,00100001 HDA:15433155,10431335,00100700'
   Controls : 18
   Simple ctrls : 12
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer INC. F3T
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=UUID=5f88d0d3-5368-49ca-8451-ea4eb405a3ec ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: lucid ubuntu-unity ubuntu-une networking needs-upstream-testing
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3TAS.223
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: F3T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3TAS.223:bd04/24/2007:svnASUSTeKComputerINC.:pnF3T:pvr1.0:rvnASUSTeKComputerINC.:rnF3T:rvr1.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: F3T
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
ciiccii (theguns) wrote :

after installing linux-backpports-modules-wireless-lucid-generic dmesg is showing me:

[46724.203194] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46724.400082] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46724.600338] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)
[46724.803350] wlan0: direct probe to AP 00:1c:4a:05:26:76 timed out
[46735.363162] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46735.560101] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46735.770046] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)
[46735.960195] wlan0: direct probe to AP 00:1c:4a:05:26:76 timed out
[46746.533157] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46746.730080] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46746.930094] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)
[46747.130086] wlan0: direct probe to AP 00:1c:4a:05:26:76 timed out
[46818.823183] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46819.020110] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46819.220087] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)
[46819.420105] wlan0: direct probe to AP 00:1c:4a:05:26:76 timed out
[46829.973194] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46830.170098] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46830.370084] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)
[46830.570067] wlan0: direct probe to AP 00:1c:4a:05:26:76 timed out
[46841.136460] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46841.332610] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46841.530091] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)
[46841.740112] wlan0: direct probe to AP 00:1c:4a:05:26:76 timed out
[46852.293327] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46852.490081] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46852.690104] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)
[46852.890124] wlan0: direct probe to AP 00:1c:4a:05:26:76 timed out
[46863.443153] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 1)
[46863.640099] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 2)
[46863.840129] wlan0: direct probe to AP 00:1c:4a:05:26:76 (try 3)

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi ciiccii,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 565367

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Reiche (grimsrud) wrote :

I can confirm this bug in a fresh install of 10.04 final with all updates.
Should I report a new bug as
apport-collect -p linux 565367
does not work for me as I am not the bug-reporter.

Revision history for this message
ciiccii (theguns) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
ciiccii (theguns) wrote : AplayDevices.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : ArecordDevices.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : BootDmesg.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : CurrentDmesg.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : IwConfig.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : Lspci.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : PciMultimedia.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : ProcInterrupts.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : ProcModules.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : UdevDb.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : UdevLog.txt

apport information

Revision history for this message
ciiccii (theguns) wrote : WifiSyslog.txt

apport information

Revision history for this message
ciiccii (theguns) wrote :

Ok, as you can see, now(after a kernel update) i can connect to а wireless network, which is encrypted with WPA-PSK. But the trouble is still remains - the connection dies often without to being disconnected from network (no data is being transmitted after it).
Unfortunately i have the other networks i want connected to, but the issue described on this bug-report remains . Those are encrypted with WEP, WPA2-CCMP and WPA-TKIP, and i can't change the encryption on those networks.

Revision history for this message
Jon Bryan (whatboxg8) wrote :

I can attest to this bug as well, i get a terminal screen followed immediately by a logout. This is on a thinkpad t42 btw

Revision history for this message
Nate Bargmann (n0nb) wrote :

Have you tried a mainline kernel as described at the https://wiki.ubuntu.com/KernelTeam/MainlineBuilds page? I installed 2.6.34 on a T42 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/ and it solved the issue described in bug #427439. It may be worth a try.

Revision history for this message
Angel-inn (christian-bizet) wrote :
Download full text (7.0 KiB)

I can confirm this bug in a fresh install of 10.04 final with all updates.

[ 13.413457] ath: EEPROM regdomain: 0x0
[ 13.413462] ath: EEPROM indicates default country code should be used
[ 13.413465] ath: doing EEPROM country->regdmn map search
[ 13.413469] ath: country maps to regdmn code: 0x3a
[ 13.413471] ath: Country alpha2 being used: US
[ 13.413474] ath: Regpair used: 0x3a
[ 13.426204] phy0: Selected rate control algorithm 'minstrel'
[ 13.427127] ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45)
[ 13.428202] cfg80211: Calling CRDA for country: US
[ 13.443514] cfg80211: Regulatory domain changed to country: US
[ 13.443521] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 13.443524] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 13.443528] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 13.443531] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.443534] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.443537] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.443540] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 13.524541] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.129341] gspca: probe ok
[ 14.129378] usbcore: registered new interface driver ov519
[ 14.129382] ov519: registered
[ 16.041773] agpgart-via 0000:00:00.0: AGP 3.5 bridge
[ 16.041801] agpgart-via 0000:00:00.0: putting AGP V3 device into 8x mode
[ 16.041920] nvidia 0000:01:00.0: putting AGP V3 device into 8x mode
[ 20.370530] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[ 52.948187] wlan0: deauthenticating from 00:60:b3:32:a2:b9 by local choice (reason=3)
[ 52.967025] wlan0: direct probe to AP 00:60:b3:32:a2:b9 (try 1)
[ 53.048104] wlan0: direct probe responded
[ 53.048112] wlan0: authenticate with AP 00:60:b3:32:a2:b9 (try 1)
[ 53.164587] wlan0: authenticated
[ 53.164621] wlan0: associate with AP 00:60:b3:32:a2:b9 (try 1)
[ 53.302350] wlan0: RX AssocResp from 00:60:b3:32:a2:b9 (capab=0x21 status=0 aid=10)
[ 53.302356] wlan0: associated
[ 53.303028] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 53.303130] cfg80211: Calling CRDA for country: US
[ 53.315325] cfg80211: Received country IE:
[ 53.315333] cfg80211: Regulatory domain: US
[ 53.315335] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 53.315339] (2402000 KHz - 2477000 KHz @ 40000 KHz), (10000 mBi, 10000 mBm)
[ 53.315341] cfg80211: CRDA thinks this should applied:
[ 53.315343] cfg80211: Regulatory domain: US
[ 53.315345] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 53.315348] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 53.315351] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 53.315353] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 53.315356] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 53.315359] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 53.315362] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 30...

Read more...

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.