** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1743279
Title:
QCA6174 stops working on newer
** Tags added: verification-done-xenial
** Tags added: verification-needed-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1743279
Title:
QCA6174 stops working on newer
I've been testing version 1.157.16 from xenial-proposed for the last few
hours. It successfully fixes the issue, and I can confirm that the
correct firmware is loaded.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
@Seth You might have missed it (there's lots of text here, so it's more
than ok :-) ) but I already had said in one comment here that it affects
Artful as well (and Bionic, of course, but that is still in
development).
Pretty much it affects any distro using a kernel newer than or equal to
4.12.
@Seth All good after a night long connected without interruptions and/or
slowdowns. It's working great.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1743279
Title:
QCA6174
@Seth I just confirmed that it does fix the bug.
I forced the re-installation of version 1.157.14 and rebooted. I checked
that the old firmware was loaded and that the files in the
/lib/firmware/ath10k/QCA6174/hw3.0/ folder were indeed the ones that
came with the old package. Then I let the bug
AceLan, you can disconsider the last comment. I've found a way to use
mIRC on the web browser and I've contacted the Kernel team there.
They're already looking into this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
Hi there, AceLan,
I've subscribed you to this bug because of 1) I've noticed you reported
another bug, which had a fix submitted to xenial-proposed a few days
ago, and I'm looking for some guidance here on how to have this bug
fixed ASAP (even by me, if it means creating and submitting a new
While this isn't fixed in Ubuntu, users can fix this issue with the
following command:
sudo wget https://github.com/kvalo/ath10k-
firmware/raw/master/QCA6174/hw3.0/4.4.1/firmware-6.bin_WLAN.RM.4.4.1-00051-QCARMSWP-1
-O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin
** Description changed:
It's important to notice that this bugs affects any post-4.12 kernel, so
it's present in both 16.04.3 HWE and 17.10 versions.
** Description changed:
After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
WiFi would stop working after every 20 minutes or so. The problem
Reading https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/ath10k/QCA6174/hw3.0/firmware-6.bin?id=96a7402d4172f4786ee93dd9f7cb3f76e1a8025e
it seems the fix for this particular issue was made available in version
WLAN.RM.4.4.1-00051-QCARMSWP-1. Updating board-2.bin
Public bug reported:
After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
WiFi would stop working after every 20 minutes or so. The problem
initially seems related to some DNS services crashing because of what
happend in browsers and other software that usually rely on DNS but
Disabling Powersave in NetworkManager did it for me. I was barely
getting 300kB/s on certain workloads on my 2.4GHz network whereas I
could get full speed on my 5GHz one. By disabling the power management
in NetworkManager, I got full speed all the time and I haven't really
noticed any decrease in
13 matches
Mail list logo
