Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
OEM Priority Project |
Fix Released
|
Critical
|
Alex Tu | ||
linux-firmware (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
-------
STATUS 2016-03-17:
==========
WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22
==========
The support for this card has now been merged to https:/
sudo mkdir -p /lib/firmware/
sudo rm /lib/firmware/
sudo wget -O /lib/firmware/
sudo wget -O /lib/firmware/
sudo wget -O /lib/firmware/
Reboot or reload the ath10k_pci module and you should be able to connect!
-------
STATUS 2015-12-22:
Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work.
There are a couple of issues regarding the fix for some people (not all):
1. Wireless works, but network throughput stops some time after connecting to access point
2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi
-------
Original description:
I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04.
The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https:/
The computer has just been released this summer and is Intel Skylake -based.
I've tried the patch from bug 1383184, which has a fix for the card revision 20:
Make the directory /lib/firmware/
board.bin
firmware-4.bin
notice_
ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly:
dmesg | grep ath
[ 5.452683] ath10k_pci 0000:07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
[ 5.678420] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/
[ 5.678773] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/
[ 5.678781] ath10k_pci 0000:07:00.0: failed to load spec board file, falling back to generic: -2
[ 5.679445] ath10k_pci 0000:07:00.0: Direct firmware load for ath10k/
[ 5.679453] ath10k_pci 0000:07:00.0: could not fetch firmware file 'ath10k/
[ 7.802316] ath10k_pci 0000:07:00.0: qca6174 hw3.2 (0x05030000, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.
[ 7.802329] ath10k_pci 0000:07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 8.200607] ath: EEPROM regdomain: 0x6c
[ 8.200614] ath: EEPROM indicates we should expect a direct regpair map
[ 8.200619] ath: Country alpha2 being used: 00
[ 8.200621] ath: Regpair used: 0x6c
[ 8.216605] ath10k_pci 0000:07:00.0 wlp7s0: renamed from wlan0
[ 13.462029] ath10k_pci 0000:07:00.0: failed to enable dynamic BW: -11
[ 16.461416] ath10k_pci 0000:07:00.0: could not suspend target (-11)
[ 24.760062] ath10k_pci 0000:07:00.0: failed to enable dynamic BW: -11
[ 27.759534] ath10k_pci 0000:07:00.0: could not suspend target (-11)
[ 36.046205] ath10k_pci 0000:07:00.0: failed to set arp ac override parameter: -11
[ 39.045729] ath10k_pci 0000:07:00.0: could not suspend target (-11)
[ 47.344304] ath10k_pci 0000:07:00.0: failed to enable dynamic BW: -11
[ 50.343794] ath10k_pci 0000:07:00.0: could not suspend target (-11)
[ 58.630534] ath10k_pci 0000:07:00.0: failed to enable dynamic BW: -11
[ 61.629936] ath10k_pci 0000:07:00.0: could not suspend target (-11)
[ 69.920624] ath10k_pci 0000:07:00.0: failed to enable dynamic BW: -11
[ 72.920132] ath10k_pci 0000:07:00.0: could not suspend target (-11)
[ 81.206812] ath10k_pci 0000:07:00.0: failed to enable dynamic BW: -11
[ 84.206218] ath10k_pci 0000:07:00.0: could not suspend target (-11)
...
Then it just constantly prints the last two messages on and on.
I can weirdly enough see the card in iwconfig:
wlp7s0 IEEE 802.11abgn ESSID:off/any
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
And I can see the wireless-icon in the toolbar, but scanning for access points or trying to connect to one doesn't work.
This is the furthest I've gotten. I suspect this card needs a new firmware in ath10k?
---
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2015-11-11 (15 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b520 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp.
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire VN7-792G
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.153
Tags: xenial
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/25/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.02
dmi.board.
dmi.board.name: Aspire VN7-792G
dmi.board.vendor: Acer
dmi.board.version: V1.02
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.name: Aspire VN7-792G
dmi.product.
dmi.sys.vendor: Acer
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Committed |
status: | Fix Committed → Fix Released |
status: | Fix Released → In Progress |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: wily |
tags: | added: vivid |
Changed in linux (Ubuntu): | |
status: | In Progress → Confirmed |
description: | updated |
tags: | added: latest-bios-1.02 |
description: | updated |
description: | updated |
description: | updated |
affects: | linux (Ubuntu) → linux-firmware (Ubuntu) |
information type: | Public → Public Security |
information type: | Public Security → Public |
tags: | added: lp1734862 |
affects: | ubuntux → oem-priority |
tags: | added: originate-from-1734862 somerville |
Changed in oem-priority: | |
importance: | Undecided → Critical |
assignee: | nobody → Alex Tu (alextu) |
Changed in oem-priority: | |
status: | New → In Progress |
status: | In Progress → Triaged |
Changed in oem-priority: | |
status: | Triaged → Fix Released |
Changed in linux-firmware (Ubuntu): | |
assignee: | nobody → Alex (leksander3) |
Changed in linux-firmware (Ubuntu): | |
assignee: | Alex (leksander3) → nobody |
Changed in hwe-next: | |
status: | New → Fix Released |
tags: | added: oem-priority |
Changed in linux-firmware (Ubuntu): | |
status: | Confirmed → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1520343/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]