168c:002a ath9k - no 5GHz networks

[H.-Dirk Schmitt]

Same experience as in bug #429748.
System is oneiric with a precise kernel

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.2.0-17-generic 3.2.0-17.26
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** Liste der Hardware-Geräte (CAPTURE) ****
 Karte 0: Intel [HDA Intel], Gerät 0: ALC269 Analog [ALC269 Analog]
   Sub-Geräte: 1/1
   Sub-Gerät #0: subdevice #0
AudioDevicesInUse:
 BEN. PID ZUGR. BEFEHL
 /dev/snd/controlC0: dschmi 6087 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2800000 irq 45'
   Mixer name : 'Intel Cantiga HDMI'
   Components : 'HDA:10ec0269,10cf0000,00100004 HDA:80862802,80860101,00100000'
   Controls : 28
   Simple ctrls : 12
Date: Wed Feb 22 10:11:55 2012
HibernationDevice: RESUME=/dev/mapper/system-swap
IwConfig: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
MachineType: FUJITSU SIEMENS LifeBook T4410
ProcEnviron:
 LANGUAGE=de_DE:de:en_US:en
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LC_PAPER=de_DE.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-17-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-17-generic N/A
 linux-backports-modules-3.2.0-17-generic N/A
 linux-firmware 1.60.1
RfKill: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
SourcePackage: linux
UdevDb: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog: Feb 22 09:41:41 cap NetworkManager[2003]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
dmi.bios.date: 09/30/2009
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.05
dmi.board.name: FJNB206
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: LifeBook T4410
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd09/30/2009:svnFUJITSUSIEMENS:pnLifeBookT4410:pvr10601127896:rvnFUJITSU:rnFJNB206:rvr:cvnFUJITSUSIEMENS:ct10:cvrLifeBookT4410:
dmi.product.name: LifeBook T4410
dmi.product.version: 10601127896
dmi.sys.vendor: FUJITSU SIEMENS

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc4 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc4'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc4-precise/

[H.-Dirk Schmitt (dirk-computer42)]

Currently I couldn't test upstream kernel.

[Joseph Salisbury (jsalisbury)]

Did you have this issue in previous releases of Ubuntu, or is this a new issue in 12.04(Precise)?

[H.-Dirk Schmitt (dirk-computer42)]

I haven't checked it earlier - but I think it was also before. See duplicate report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/429748

[Joseph Salisbury (jsalisbury)]

Can you run the following and post the output:
sudo modinfo ath9k

[Joseph Salisbury (jsalisbury)]

Can you not see any available 5GHz networks from NetworkManager? Or can you see the 5GHz networks, but cannot connect to them?

[H.-Dirk Schmitt (dirk-computer42)]

 modinfo ath9k
filename: /lib/modules/3.2.0-17-generic/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko
license: Dual BSD/GPL
description: Support for Atheros 802.11n wireless LAN cards.
author: Atheros Communications
srcversion: DFA76C9838E2E6C715339FB
alias: platform:ar934x_wmac
alias: platform:ar933x_wmac
alias: platform:ath9k
alias: pci:v0000168Cd00000034sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000033sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000032sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000030sv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Esv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Dsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Csv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Bsv*sd*bc*sc*i*
alias: pci:v0000168Cd0000002Asv*sd*bc*sc*i*
alias: pci:v0000168Cd00000029sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000027sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000024sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000023sv*sd*bc*sc*i*
depends: ath9k_hw,ath9k_common,mac80211,cfg80211,ath
intree: Y
vermagic: 3.2.0-17-generic SMP mod_unload modversions
parm: debug:Debugging mask (uint)
parm: nohwcrypt:Disable hardware encryption (int)
parm: blink:Enable LED blink on activity (int)
parm: btcoex_enable:Enable wifi-BT coexistence (int)

[H.-Dirk Schmitt (dirk-computer42)]

iwlist wlan0 scanning |grep Freque
                    Frequency:2.452 GHz (Channel 9)
                    Frequency:2.412 GHz (Channel 1)
                    Frequency:2.412 GHz (Channel 1)

Before invoking this command I have ensured that the 5Ghz network was enabled on my wlan router.

[Joseph Salisbury (jsalisbury)]

What was the issue when you attempted to test the upstream kernel?

[David Sklar (david-sklar+ubuntulaunchpad)]

I tested with upstream kernel 3.4.0 (uname -a says "Linux armonica 3.4.0-030400-generic #201205210521 SMP Mon May 21 09:22:02 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux", the .debs I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/ were linux-image-3.4.0-030400-generic_3.4.0-030400.201205210521_amd64.deb, linux-headers-3.4.0-030400-generic_3.4.0-030400.201205210521_amd64.deb, and linux-headers-3.4.0-030400_3.4.0-030400.201205210521_all.deb) and the issue persisted.

I have a 5Ghz network (broadcasting SSID) that my MacBook Air can see and connect to just fine. The machine with ubuntu precise can neither see nor connect to this network.

Interestingly (?) even though "iw reg get" tells me:

$ iw reg get
country 00:
        (2402 - 2472 @ 40), (3, 20)
        (2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS
        (2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
        (5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
        (5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS

iw list only shows frequences in the 2.4Ghz range:

$iw list
Wiphy phy0
        Band 1:
                Capabilities: 0x11ce
                        HT20/HT40
                        SM Power Save disabled
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-7
                Frequencies:
                        * 2412 MHz [1] (14.0 dBm)
                        * 2417 MHz [2] (15.0 dBm)
                        * 2422 MHz [3] (15.0 dBm)
                        * 2427 MHz [4] (15.0 dBm)
                        * 2432 MHz [5] (15.0 dBm)
                        * 2437 MHz [6] (15.0 dBm)
                        * 2442 MHz [7] (15.0 dBm)
                        * 2447 MHz [8] (15.0 dBm)
                        * 2452 MHz [9] (15.0 dBm)
                        * 2457 MHz [10] (15.0 dBm)
                        * 2462 MHz [11] (15.0 dBm)
                        * 2467 MHz [12] (15.0 dBm) (passive scanning)
                        * 2472 MHz [13] (14.0 dBm) (passive scanning)
                        * 2484 MHz [14] (17.0 dBm) (passive scanning)
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        Coverage class: 0 (up to 0m)
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2...

[David Sklar (david-sklar+ubuntulaunchpad)]

/sheepish -- I am using an Atheros 9285-based card, it is 2.4Ghz only. So works-as-it-should from me.

[penalvch (penalvch)]

H.-Dirk Schmitt, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]