ATH9K wireless signal weak

Bug #1160188 reported by Joey Stevense on 2013-03-26
228
This bug affects 44 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Gentoo Linux)
New
Undecided
Unassigned
linux (Ubuntu)
Medium
Unassigned

Bug Description

AR9485 Wireless Network Adapter has a low signal when in close range of station.

I disabled hardware encryption with putting:
  options ath9k nohwcrypt=1
in
  /etc/modprobe.d/ath9k.conf

That doesn't seemed to help.

The signal has 2 bars while it has full strength in windows. (I am 2 meters away from the wifi station)

s400ca:~$ rfkill list all
2: asus-wlan: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: asus-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
4: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
5: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-26-generic 3.5.0-26.42
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jintux 1988 F.... pulseaudio
Date: Tue Mar 26 06:33:06 2013
InstallationDate: Installed on 2013-03-25 (0 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: ASUSTeK COMPUTER INC. S400CA
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=52689dee-4881-48b6-8cca-602e15292652 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-26-generic N/A
 linux-backports-modules-3.5.0-26-generic N/A
 linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/28/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: S400CA.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: S400CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.203:bd09/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: S400CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Joey Stevense (joey2524) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc4-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Download full text (4.1 KiB)

Hi Joseph,

No that is not possible because I use the installation for serious
purposes, like work.

Met vriendelijke groet, / Best regards,
*Joey Stevense*

On Tue, Mar 26, 2013 at 4:05 PM, Joseph Salisbury <
<email address hidden>> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.9 kernel[0] (Not a kernel in the daily directory) and install both
> the linux-image and linux-image-extra .deb packages.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> 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.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc4-raring/
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1160188
>
> Title:
> ATH9K wireless signal weak
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> AR9485 Wireless Network Adapter has a low signal when in close range
> of station.
>
> I disabled hardware encryption with putting:
> options ath9k nohwcrypt=1
> in
> /etc/modprobe.d/ath9k.conf
>
> That doesn't seemed to help.
>
> The signal has 2 bars while it has full strength in windows. (I am 2
> meters away from the wifi station)
>
> s400ca:~$ rfkill list all
> 2: asus-wlan: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 3: asus-bluetooth: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 4: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 5: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: linux-image-3.5.0-26-generic 3.5.0-26.42
> ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
> Uname: Linux 3.5.0-26-generic x86_64
> ApportVersion: 2.6.1-0ubuntu10
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: jintux 1988 F.... pulseaudio
> Date: Tue Mar 26 06:33:06 2013
> InstallationDate: Installed on 2013-03-25 (0 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
> (20121017.5)
> MachineType: ASUSTeK COMPUTER INC. S400CA
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic
> root=UUID=52689dee-4881-48b6-8cca-602e15292652 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.5.0-26-generic N/A
> l...

Read more...

Roy Meissner (roymeissn) wrote :

I've tested Kernel 3.8.5 from upstream --> still the same problem

Tomasz Wysocki (tomwys) wrote :

I have the same problem on Asus Vivobook S500CA. Have tried all work-arounds I have found on the internet but none helped. I you have any solutions or workarounds it will be helpful. For now I'm buing USB wifi adapter to be able to use wifi.

I have Ubuntu 13.04 now, but problem also occures on 12.10.

lspci:
02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)

uname -a
Linux tomwys-laptop 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

PS. If you are interested in more details of my computer configuration please ask. I will try other GNU/Linux distributions today to check if any fixed this issue. I will send any results here.

i have same bug on ubuntu 13.04 64 bits

Asus Zenbook, Ux31e

Emilio Sansano (emsansan) wrote :

Same bug here, running ubuntu 13.04 64bits on Asus Zenbook ux31e. Very weak signal or no signal at all where Windows connects fine.

kernel: 3.8.0-19

Marcus Sundman (sundman) wrote :

It's not just the signal that is low, it also disconnects frequently. (Quantal neither had low signal nor disconnected in the same situation.)

Marcus Sundman (sundman) wrote :

When it disconnects it goes like so:
May 15 21:06:51 hal wpa_supplicant[1748]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:16:01:8c:50:08 reason=4
May 15 21:06:51 hal kernel: [507716.316710] cfg80211: Calling CRDA to update world regulatory domain
May 15 21:06:51 hal NetworkManager[10608]: <info> (wlan0): supplicant interface state: completed -> disconnected
May 15 21:06:51 hal kernel: [507716.329493] cfg80211: World regulatory domain updated:
May 15 21:06:51 hal kernel: [507716.329505] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May 15 21:06:51 hal kernel: [507716.329515] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 15 21:06:51 hal kernel: [507716.329524] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 15 21:06:51 hal kernel: [507716.329533] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 15 21:06:51 hal kernel: [507716.329541] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 15 21:06:51 hal kernel: [507716.329552] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 15 21:06:51 hal NetworkManager[10608]: <info> (wlan0): supplicant interface state: disconnected -> scanning
May 15 21:06:52 hal wpa_supplicant[1748]: wlan0: SME: Trying to authenticate with 00:16:01:8c:50:08 (SSID='bubba' freq=2452 MHz)
...

Guy Korland (gkorland) wrote :

I have the same issue with ubuntu 13.04 64 bits
Asus Zenbook, Ux31e

Emilio Sansano (emsansan) wrote :

I tried upgrading kernel to 3.9, but the poor connection signal persisted. Then I installed compat-drivers from:

http://drvbp1.linux-foundation.org/~mcgrof/rel-html/compat-drivers/

now the connection signal is better than before. Not as good as with windows, but I get to connect in places where I couldn't before.

To try this you need to:
- download the drivers that match your kernel version. In my case, I downloaded compat-drivers-v3.9-rc4-2 because I'm on 3.9 kernel (you can check your kernel v. with uname -r)
- extact tar file.
- cd Downloads/compat-drivers-3.9-rc4-2-su
- sudo make
- sudo make install
- sudo modprobe -r ath9k
- sudo modprobe ath9k

There is no known workaround for this yet.

I used to work well in Ubuntu 12.04, with "options ath9k nohwcrypt=1".

I am using Ubuntu 13.04 x86-64 with packages up to date.

Tried compat-drivers 3.8.3-2-snpu and 3.9-rc4-2-su with no luck.

I've tested Kernel 3.10.0-031000rc2-generic from upstream --> still the same problem

Asus Zenbook, ux31e

Also have the problem... The reception is horrible and works fine in windows.
from dmesg:
[ 220.903488] WARNING: at /build/buildd/linux-3.8.0/drivers/net/wireless/ath/ath9k/hw.c:794 ar9003_get_pll_sqsum_dvc+0xb6/0xc0 [ath9k_hw]()
[ 220.903492] Hardware name: UX31E
[ 220.903495] Modules linked in: usb_storage(F) ip6table_filter(F) ip6_tables(F) ebtable_nat(F) ebtables(F) snd_hrtimer(F) ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_state(F) nf_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) iptable_filter(F) ip_tables(F) x_tables(F) bridge(F) stp(F) llc(F) joydev(F) dm_crypt(F) parport_pc(F) ppdev(F) rfcomm bnep kvm_intel kvm asus_nb_wmi asus_wmi sparse_keymap snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep(F) rts5139(C) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) snd_rawmidi(F) snd_seq(F) uvcvideo videobuf2_vmalloc arc4(F) videobuf2_memops videobuf2_core videodev ath9k ath9k_common ath9k_hw snd_seq_device(F) snd_timer(F) ath mac80211 mac_hid microcode(F) snd(F) coretemp cfg80211 ath3k mei btusb soundcore(F) lp(F) parport(F) bluetooth psmouse(F) serio_raw(F) lpc_ich ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) xts(F) lrw(F) gf128mul(F) ablk_helper(F) cryptd(F) wmi i915 video(F) i2c_algo_bit drm_kms_helper ahci(F) libahci(F) drm
[ 220.903633] Pid: 214, comm: kworker/u:5 Tainted: GF C 3.8.0-21-generic #32-Ubuntu
[ 220.903637] Call Trace:
[ 220.903650] [<ffffffff810587ef>] warn_slowpath_common+0x7f/0xc0
[ 220.903658] [<ffffffff8105884a>] warn_slowpath_null+0x1a/0x20
[ 220.903676] [<ffffffffa038e9a6>] ar9003_get_pll_sqsum_dvc+0xb6/0xc0 [ath9k_hw]
[ 220.903693] [<ffffffffa03fe2e3>] ath_hw_pll_work+0x53/0xd0 [ath9k]
[ 220.903702] [<ffffffff8107676c>] process_one_work+0x15c/0x4d0
[ 220.903710] [<ffffffff81077fce>] worker_thread+0x16e/0x480
[ 220.903718] [<ffffffff81077e60>] ? manage_workers+0x2a0/0x2a0
[ 220.903725] [<ffffffff8107d300>] kthread+0xc0/0xd0
[ 220.903732] [<ffffffff8107d240>] ? kthread_create_on_node+0x120/0x120
[ 220.903742] [<ffffffff816d372c>] ret_from_fork+0x7c/0xb0
[ 220.903748] [<ffffffff8107d240>] ? kthread_create_on_node+0x120/0x120
[ 220.903753] ---[ end trace 7faecf033a2db336 ]---
[ 220.903758] ath: phy0: PLL4 meaurement not done
[ 221.015326] ath: phy0: PLL4 meaurement not done
[ 221.127122] ath: phy0: PLL4 meaurement not done
[ 221.239037] ath: phy0: PLL4 meaurement not done
[ 221.350902] ath: phy0: PLL4 meaurement not done

imedina (imedina) wrote :

I have the same issue: very low connectivity or even none. Asus UX21 with 13.04 64bits.

I do not try compat-drivers yet.

description: updated
xcalin (xcalin16-gmail) wrote :

I have also this bug with the wireless and it's very annoying

My UX31E also disconnect often. I do have signal, but weak. It doesn't disconnect as often when I'm closer to the router.

What I want to report that I have not seen anyone else mention is that it will only behave like this when on battery. I have turned off power saving (iwconfig wlan0 power off) but that does not help.

Christoph Vogler (vogler-c) wrote :

I have the same Problem with all tested Kernels. Last was 3.10-rc3.
Signal is very weak even close to the Router. On Windows signal strength is fine.

xcalin (xcalin16-gmail) wrote :

I tested 3.6.3-030603-generic and here the signal it's a little good double than on 3.8 or 3.10

jintux (jintux) on 2013-06-02
tags: added: kernel-unable-to-test-upstream
tags: added: kernel-bug-exists-upstream
removed: kernel-unable-to-test-upstream
jintux (jintux) on 2013-06-02
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
hroost (hroostik) wrote :

I have also this bug with the wireless and it's very annoying too
UX31E 3.8.0-23-generic x86_64
One and a half years having this problems

bjornegil (bejohansen) wrote :

I have the same problem. UX31E. x86_64. The wireless signal has been a bit weak all the time - but my impression was that it got worse on updating to ubuntu 13.04.
I have tried 3.9 kernel and the compat drivers without any improvement.

Does anybody know if this problem is present in 32-bit version as well?

Pionero (dmerino76) wrote :
Download full text (3.4 KiB)

Yes, 32-bit ubuntu 13.04 has the same problem.

2013/6/6 bjornegil <email address hidden>

> I have the same problem. UX31E. x86_64. The wireless signal has been a bit
> weak all the time - but my impression was that it got worse on updating to
> ubuntu 13.04.
> I have tried 3.9 kernel and the compat drivers without any improvement.
>
> Does anybody know if this problem is present in 32-bit version as well?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1160188
>
> Title:
> ATH9K wireless signal weak
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> AR9485 Wireless Network Adapter has a low signal when in close range
> of station.
>
> I disabled hardware encryption with putting:
> options ath9k nohwcrypt=1
> in
> /etc/modprobe.d/ath9k.conf
>
> That doesn't seemed to help.
>
> The signal has 2 bars while it has full strength in windows. (I am 2
> meters away from the wifi station)
>
> s400ca:~$ rfkill list all
> 2: asus-wlan: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 3: asus-bluetooth: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 4: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 5: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: linux-image-3.5.0-26-generic 3.5.0-26.42
> ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
> Uname: Linux 3.5.0-26-generic x86_64
> ApportVersion: 2.6.1-0ubuntu10
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: jintux 1988 F.... pulseaudio
> Date: Tue Mar 26 06:33:06 2013
> InstallationDate: Installed on 2013-03-25 (0 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
> (20121017.5)
> MachineType: ASUSTeK COMPUTER INC. S400CA
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic
> root=UUID=52689dee-4881-48b6-8cca-602e15292652 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.5.0-26-generic N/A
> linux-backports-modules-3.5.0-26-generic N/A
> linux-firmware 1.95
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 09/28/2012
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: S400CA.203
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: S400CA
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrS400CA.203:bd09/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
> dmi.product.name: S400CA
> dmi.product.version: 1.0
> ...

Read more...

Anton Nikityuk (antony-sq) wrote :

Are there any news?

153 comments hidden view all 220 comments

The second patch is applicable for a specific model of AR9485. Can you please attach the output of "dmidecode" to this bug ? Also, the contents of "modal_eeprom" in the ath9k debugfs directory.

The power management issue appears to be different, so we can analyze it in a new bug report.

(In reply to comment #99)
> OK ! If you need me test anything, feel free to ask.

Please test this patch: https://patchwork.kernel.org/patch/2696121/

Download full text (12.0 KiB)

Here's the info from kernel version 3.8.0 (suppose that doesn't matter but just saying in case), (that's because for some reason the internal display of this computer doesn't work with the 3.10rc4 kernel and I'm on the move without a display cable).

modal_eeprom:

   2GHz modal Header :
 Chain0 Ant. Control : 16
 Chain1 Ant. Control : 16
 Chain2 Ant. Control : 16
 Ant. Common Control : 1088
Ant. Common Control2 : 559240
           Ant. Gain : 0
       Switch Settle : 44
    Chain0 xatten1DB : 30
    Chain1 xatten1DB : 0
    Chain2 xatten1DB : 0
Chain0 xatten1Margin : 5
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
          Temp Slope : 38
          Volt Slope : 0
      spur Channels0 : 180
      spur Channels1 : 140
      spur Channels2 : 164
      spur Channels3 : 100
      spur Channels4 : 0
 Chain0 NF Threshold : -1
 Chain1 NF Threshold : 0
 Chain2 NF Threshold : 0
          Quick Drop : 0
       txEndToXpaOff : 0
      xPA Bias Level : 0
  txFrameToDataStart : 14
       txFrameToPaOn : 14
      txFrameToXpaOn : 14
              txClip : 3
    ADC Desired size : -30
   5GHz modal Header :
 Chain0 Ant. Control : 0
 Chain1 Ant. Control : 0
 Chain2 Ant. Control : 0
 Ant. Common Control : 272
Ant. Common Control2 : 139810
           Ant. Gain : 0
       Switch Settle : 45
    Chain0 xatten1DB : 0
    Chain1 xatten1DB : 0
    Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
          Temp Slope : 68
          Volt Slope : 0
      spur Channels0 : 0
      spur Channels1 : 0
      spur Channels2 : 0
      spur Channels3 : 0
      spur Channels4 : 0
 Chain0 NF Threshold : -1
 Chain1 NF Threshold : 0
 Chain2 NF Threshold : 0
          Quick Drop : 0
       txEndToXpaOff : 0
      xPA Bias Level : 0
  txFrameToDataStart : 14
       txFrameToPaOn : 14
      txFrameToXpaOn : 14
              txClip : 3
    ADC Desired size : -30

dmidecode with some id info removed:

# dmidecode 2.11
# SMBIOS entry point at 0xda152198
SMBIOS 2.7 present.
23 structures occupying 1673 bytes.
Table at 0xDA130018.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
 Vendor: American Megatrends Inc.
 Version: TX300CA.207
 Release Date: 01/03/2013
 Address: 0xF0000
 Runtime Size: 64 kB
 ROM Size: 6144 kB
 Characteristics:
  PCI is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  BIOS ROM is socketed
  EDD is supported
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard serv...

(In reply to comment #110)
> Here's the info from kernel version 3.8.0 (suppose that doesn't matter but
> just
> saying in case), (that's because for some reason the internal display of this
> computer doesn't work with the 3.10rc4 kernel and I'm on the move without a
> display cable).

Thanks.

Here is a patch adding support for this card:
http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch

Can you test this ? This will apply on top of the earlier patch ("Assign default xlna config for AR9485").

Also, after you explicitly unload/reload ath9k (modprobe -r ath9k; modprobe ath9k), the line "Set parameters for CUS198" should be seen in dmesg.

Applied first https://patchwork.kernel.org/patch/2696121/ then http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch on top of Ubuntu kernel 3.8.0-26 which I have running now.

Patch(1) applied it with some fuzz and I had to manually apply the patch to pci.c.

Seems to work fine with a short test: decent bandwidth, keeps up, shows 65 Mbps as rate, link quality between 40 and 50, and I get the kernel message:

ath: phy1: Set parameters for CUS198

I can test later with some other kernel versions if needed.

(In reply to comment #109)
> (In reply to comment #99)
> > OK ! If you need me test anything, feel free to ask.
>
> Please test this patch: https://patchwork.kernel.org/patch/2696121/

I need a few precisions :
- do I have to apply this patch only ?
- on top of the 3.10-rc5 kernel ?
- with powersave mode off ?
- what do I have to post (logs...) after testing ?

On top of Linus Torvalds' tree, apply these patches:

https://patchwork.kernel.org/patch/2696121/
http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch

PS has been disabled by default in mainline now.

Reload ath9k and in dmesg, the message "Set parameters for CUS198" should be seen.

Sorry I'm a kernel newbie...
How can I download Linus' tree ?
Previously, I downloaded the sources from kernel.org

Hm, in that case, you can just apply the patches on top of the 3.10-rc5 tarball.

Tested also with mainline 3.9.5, applied first https://patchwork.kernel.org/patch/2696121/ then http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch. Applied with some fuzz, no manual intervention required, results look the same as with 3.8.0.

Same good results with mainline 3.10-rc5, applied first
https://patchwork.kernel.org/patch/2696121/ then
http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch.
Applied with some fuzz, no manual intervention required, results look the same
as with 3.8.0 and 3.9.5.

Out of topic probably, but as I see that bluetooth is in the same device: seems like there is a problem with bluetooth also, but could be something else than the driver. Device is found, hciconfig shows bytes sent and received, but hcitool scan doesn't show devices.

What does lsusb -v show ?

Download full text (8.7 KiB)

Bus 001 Device 003: ID 13d3:3402 IMC Networks
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 64
  idVendor 0x13d3 IMC Networks
  idProduct 0x3402
  bcdDevice 0.01
  iManufacturer 1
  iProduct 2
  iSerial 3
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 177
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 4
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
       bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x03 EP 3 OUT
        bmAttributes 1
    ...

Read more...

Hm, that's weird. What does 'ls -l /sys/bus/usb/drivers' show ? Does it have ath3k ?

No - there's "btusb" with contents:

lrwxrwxrwx 1 root root 0 kesä 13 19:30 1-1.1:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0
lrwxrwxrwx 1 root root 0 kesä 13 19:30 1-1.1:1.1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1
--w------- 1 root root 4096 kesä 13 19:30 bind
lrwxrwxrwx 1 root root 0 kesä 13 19:30 module -> ../../../../module/btusb
-rw-r--r-- 1 root root 4096 kesä 13 19:30 new_id
-rw-r--r-- 1 root root 4096 kesä 13 19:30 remove_id
--w------- 1 root root 4096 kesä 13 19:02 uevent
--w------- 1 root root 4096 kesä 13 19:30 unbind

One last question before testing : do I have to disable ATH9K_RATE_CONTROL or not ?

Download full text (9.0 KiB)

Hmm, probably ran lsusb -v without root access, here's with root, has some more info:

Bus 001 Device 003: ID 13d3:3402 IMC Networks
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 64
  idVendor 0x13d3 IMC Networks
  idProduct 0x3402
  bcdDevice 0.01
  iManufacturer 1 Atheros Communications
  iProduct 2 Bluetooth USB Host Controller
  iSerial 3 Alaska Day 2006
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 177
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 4 BT HCI
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
      Endpoint De...

Read more...

(In reply to comment #124)
> One last question before testing : do I have to disable ATH9K_RATE_CONTROL or
> not ?

Yes, ATH9K_RATE_CONTROL has to be disabled.

(In reply to comment #125)
> Hmm, probably ran lsusb -v without root access, here's with root, has some
> more
> info:
>
> Bus 001 Device 003: ID 13d3:3402 IMC Networks
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass 224 Wireless
> bDeviceSubClass 1 Radio Frequency
> bDeviceProtocol 1 Bluetooth
> bMaxPacketSize0 64
> idVendor 0x13d3 IMC Networks
> idProduct 0x3402
> bcdDevice 0.01
> iManufacturer 1 Atheros Communications
> iProduct 2 Bluetooth USB Host Controller
> iSerial 3 Alaska Day 2006

Ok, I am not familiar with bluetooth - I'll try to get more information.

Ah, I wondered I might have forgotten something with my 3.8.0 test - now I remember, it was ATH9K_RATE_CONTROL:

# grep RATE_CONTROL .config
CONFIG_ATH9K_RATE_CONTROL=y

Seems to work quite well even with this.

For 3.9.5 and 3.10 I had it disabled:

# grep RATE_CONTROL .config
# CONFIG_ATH9K_RATE_CONTROL is not set

So I've applied both patches on top of the 3.10-rc5 kernel.

Everything looks OK :
gfmichaud@dragonfly:~$ sudo rmmod ath9k
[sudo] password for gfmichaud:
gfmichaud@dragonfly:~$ sudo modprobe ath9k
gfmichaud@dragonfly:~$ dmesg | grep -i parameters
[ 289.311397] ath: phy0: ANI parameters: SI=3, ofdmWS=on FS=7 MRCcck=on listenTime=25 ofdmErrs=64 cckErrs=892
[ 297.359862] ath: phy1: Set parameters for CUS198

However, it looks like powersave is on by default (I've removed the item in /etc/pm/power.d that disabled it) :
gfmichaud@dragonfly:~$ iw dev wlan0 get power_save
Power save: on

Link quality seems to have improved a lot :
- in 3.8 without patches, "iw dev wlan0 link" shows me "signal" between -74 and -86 dBm
- in 3.10-rc5 with the patches, it shows me "signal" between -55 and -62 dBm

I'll do futher testing and report here.

(In reply to comment #129)
> However, it looks like powersave is on by default (I've removed the item in
> /etc/pm/power.d that disabled it) :
> gfmichaud@dragonfly:~$ iw dev wlan0 get power_save
> Power save: on

The PS/rate-control patches will be in -rc6.

I've been using it with all doors closed at home and experienced no disconnection and no lag.
Looks really great !!! :-)

No problems here either, seems to work fine in longer term (well, a few hours) use too. Power management has been on for me though so far, will try with power management off.

With power management off, when I look at the iwconfig bit rate every five seconds, it's mostly 65 Mbps but about every once in 25 .. once in 50 it's 1 Mbps.

With power management off, occasionally there are longer periods of low speed (1..30 Mbps) and this affects also practical usability quite a lot.

178 comments hidden view all 220 comments
jief (jf.monfort) wrote :

Same problem here

Ubuntu 13.04
Kernel Linux laptop 3.9.5-030905-generic #201306071748 SMP Fri Jun 7 21:49:35 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

179 comments hidden view all 220 comments

Can you open separate bugs for the PS and bluetooth issues ? Thanks.

John, I think this bug can be closed now, patch has been sent:
https://patchwork.kernel.org/patch/2718041/

OK, I will - and big thanks for making the wireless much more usable!

Yes, thank you very very much ! :-)

181 comments hidden view all 220 comments
Szilard Novaki (novaki) wrote :

This has been just fixed in 3.10 kernel: https://bugzilla.kernel.org/show_bug.cgi?id=49201

can someone backport it to 12.04.2 LTS?

xcalin (xcalin16-gmail) wrote :

I tested kernel 3.10.0-031000rc5-generic still not fixed.

here you could get the kernel
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc5-saucy/

xcalin (xcalin16-gmail) wrote :

from what i read in that article would be avalabile in 3.10.rc6

2013/6/15 Calin Sirian <email address hidden>

> I tested kernel 3.10.0-031000rc5-generic still not fixed.
>
> here you could get the kernel
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc5-saucy/
>

--

Software Developer Mobile: (+40) 728 574 471

**

S.C. MoreDevs S.R.L. Email: <email address hidden> ****

** **

This message can contain privileged or confidential information and it
is intended only for addressee. ****

Any unauthorized disclosure is strictly prohibited.

xcalin (xcalin16-gmail) wrote :

I've compiled a kernel 3.10-rc5 with the patch included

here is the script that downloads and installs modules and kernel i have
compiled
i tested it on ubuntu 13.04 64bit

wget -O kernel.sh http://ubuntuone.com/1iJaMuISila67x9wV07SW4 && chmod +x
kernel.sh

2013/6/15 Calin Sirian <email address hidden>

> from what i read in that article would be avalabile in 3.10.rc6
>
>
> 2013/6/15 Calin Sirian <email address hidden>
>
>> I tested kernel 3.10.0-031000rc5-generic still not fixed.
>>
>> here you could get the kernel
>> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc5-saucy/
>>
>
>
>
> --
>
>
> Software Developer Mobile: (+40) 728 574 471
>
> **
>
> S.C. MoreDevs S.R.L. Email: <email address hidden> ****
>
> ** **
>
> This message can contain privileged or confidential information and it is intended only for addressee. ****
>
>
> Any unauthorized disclosure is strictly prohibited.
>
>

--

Software Developer Mobile: (+40) 728 574 471

**

S.C. MoreDevs S.R.L. Email: <email address hidden> ****

** **

This message can contain privileged or confidential information and it
is intended only for addressee. ****

Any unauthorized disclosure is strictly prohibited.

Christoph Vogler (vogler-c) wrote :

3.10-rc6 is available now.
Can someone test the kernel i'm not able this time.

bjornegil (bejohansen) wrote :
Download full text (3.3 KiB)

I tried the 3.10-rc6 on ubuntu 13.04 amd64. No improvement. I assume the
patch did not make it into rc6.

I tried the script for updated kernel 3.10-rc5 that Xcalin posted. I have
yet not tested it to depth but so far it seems to be working great. Better
connection. So far no disconnections. I am very satisfied.

Thanks a lot!

Bjørn

2013/6/16 Christoph Vogler <email address hidden>

> 3.10-rc6 is available now.
> Can someone test the kernel i'm not able this time.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1160188
>
> Title:
> ATH9K wireless signal weak
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> AR9485 Wireless Network Adapter has a low signal when in close range
> of station.
>
> I disabled hardware encryption with putting:
> options ath9k nohwcrypt=1
> in
> /etc/modprobe.d/ath9k.conf
>
> That doesn't seemed to help.
>
> The signal has 2 bars while it has full strength in windows. (I am 2
> meters away from the wifi station)
>
> s400ca:~$ rfkill list all
> 2: asus-wlan: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 3: asus-bluetooth: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 4: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 5: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: linux-image-3.5.0-26-generic 3.5.0-26.42
> ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
> Uname: Linux 3.5.0-26-generic x86_64
> ApportVersion: 2.6.1-0ubuntu10
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: jintux 1988 F.... pulseaudio
> Date: Tue Mar 26 06:33:06 2013
> InstallationDate: Installed on 2013-03-25 (0 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
> (20121017.5)
> MachineType: ASUSTeK COMPUTER INC. S400CA
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic
> root=UUID=52689dee-4881-48b6-8cca-602e15292652 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.5.0-26-generic N/A
> linux-backports-modules-3.5.0-26-generic N/A
> linux-firmware 1.95
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 09/28/2012
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: S400CA.203
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: S400CA
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrS400CA.203:bd09/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
> ...

Read more...

Szilard Novaki (novaki) wrote :

I've backported the patch from https://bugzilla.kernel.org/show_bug.cgi?id=49201 to precise. It can be applied to the source of 3.5.0-34-generic (cd /usr/src && sudo apt-get source linux-image-3.5.0-34-generic) after entering drivers/net/wireless/ath/ath9k directory.

I recompiled ath9k modules using this guide: http://www.codewhirl.com/2012/04/how-to-compile-a-single-module-in-ubuntu-linux/. Now the signal strength is the same as on other notebooks and it does not disconnect.

tags: added: patch
Mathieu Laurent (mla) wrote :

It will be possible to fix this in an update of linux-image of Ubuntu 12.04, 13.04 ?

Joseph Salisbury (jsalisbury) wrote :

It appears the patch[0] was sent to John Linville and <email address hidden>. However, the fix has not made it into Linus' tree as of v3.10-rc6.

[0] https://patchwork.kernel.org/patch/2718041/

Changed in linux:
importance: Unknown → Medium
status: Unknown → Fix Released

i tried kernel 3.10-rc7 on ux31e 64 bits... and it doesnt improve wifi signal .

Something else is necessary to install ?

xcalin (xcalin16-gmail) wrote :
Download full text (3.5 KiB)

I guess it's not yet implemented the patch

2013/6/25 Diego Carrera Gallego <email address hidden>

> i tried kernel 3.10-rc7 on ux31e 64 bits... and it doesnt improve wifi
> signal .
>
> Something else is necessary to install ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1160188
>
> Title:
> ATH9K wireless signal weak
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> AR9485 Wireless Network Adapter has a low signal when in close range
> of station.
>
> I disabled hardware encryption with putting:
> options ath9k nohwcrypt=1
> in
> /etc/modprobe.d/ath9k.conf
>
> That doesn't seemed to help.
>
> The signal has 2 bars while it has full strength in windows. (I am 2
> meters away from the wifi station)
>
> s400ca:~$ rfkill list all
> 2: asus-wlan: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 3: asus-bluetooth: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 4: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 5: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: linux-image-3.5.0-26-generic 3.5.0-26.42
> ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
> Uname: Linux 3.5.0-26-generic x86_64
> ApportVersion: 2.6.1-0ubuntu10
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: jintux 1988 F.... pulseaudio
> Date: Tue Mar 26 06:33:06 2013
> InstallationDate: Installed on 2013-03-25 (0 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
> (20121017.5)
> MachineType: ASUSTeK COMPUTER INC. S400CA
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic
> root=UUID=52689dee-4881-48b6-8cca-602e15292652 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.5.0-26-generic N/A
> linux-backports-modules-3.5.0-26-generic N/A
> linux-firmware 1.95
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 09/28/2012
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: S400CA.203
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: S400CA
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrS400CA.203:bd09/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
> dmi.product.name: S400CA
> dmi.product.version: 1.0
> dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug...

Read more...

Marc Gondran (marc-gondran-n) wrote :

so how have we got to do ?

171 comments hidden view all 220 comments

How do we know in which kernel the patches will be committed ?
Will the be in 3.10 or later ?

tags: added: bios-outdated-209
tags: added: regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Fix Released

Were the patches merged on 3.11-rc6?

The fixes are in the 3.11 release.

*** Bug 55171 has been marked as a duplicate of this bug. ***

*** Bug 55901 has been marked as a duplicate of this bug. ***

(In reply to Sujith from comment #143)
> The fixes are in the 3.11 release.

Thanks! Could you queue them for the stable kernel trees as well?

Hi, can anyone help me?

How do I apply a patch? I got the same problem.

Displaying first 40 and last 40 comments. View all 220 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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