Craig G, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577800/comments/14
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
I haven't had any problems since upgrading to yakkety:
4.8.0-30-generic #32-Ubuntu
driver: iwlwifi
version: 4.8.0-30-generic
firmware-version: 22.361476.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Craig G, could you please advise if the updated kernel and linux-
firmware via the Ubuntu repositories fixes your issue?
** Changed in: linux-firmware (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
I updated to kernel 4.8 by installing 'linux-generic-hwe-16.04'. Now
ethtool reports firmware 22, so I think my problems are solved, but this
doesn't help people on the LTS kernel 4.4.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Would someone be so gracious as to detail the workaround for this bug
until it is fixed? I disabled secure boot and tried to build Core18
using instructions from the wireless.wiki.kernel.org page but I still
have firmware 16.242414.0 and my WiFi continues to disconnect. Here is
a summary of the
Craig G, unfortunately no because apport doesn't include useful data
when using a non-default Ubuntu kernel. It would be best to do to as
requested.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
I'm not sure I would say it worked well, but it did fix one of two
problems. The second was only fixed after both driver and firmware
upgrades. I'm no longer running the 19.ucode version. Would apport
data for the 21 version with the updated driver be useful?
--
You received this bug
Craig G, while booted into the default Xenial kernel, but with
iwlwifi-8000C-19.ucode, could you please execute the following command only
once, as it will automatically gather debugging information, in a terminal:
apport-collect -p linux 1577800
--
You received this bug notification because
Craig G, given you have tested iwlwifi-8000C-19.ucode with the Xenial
kernel and found this to work out well, then it would appear the path of
least resistance would be to backport to linux-firmware in Xenial.
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
I used version Core18 of the iwlwifi backports repository:
https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-iwlwifi.git/log/?h=release/LinuxCore18
and the current ubuntu 4.4 kernel with the following dkms.conf:
MAKE="'make' -j 12 KERNELDIR=/lib/modules/${kernelver}/build"
Craig G:
>"...AND rebuilding the iwlwifi modules with the latest version of the upstream
>driver code."
Could you please advise either which mainline kernel or up to which
commit specifically?
--
You received this bug notification because you are a member of Kernel
Packages, which is
It did indeed fix the problem I was seeing in this bug report. However,
I started having another less frequent issue shortly after (also
disconnects, but completely different errors). I was only able to solve
that one by getting the newest firmware (-21.ucode) AND rebuilding the
iwlwifi modules
Craig G, to clarify, you tested the upstream firmware and confirmed it
fixes the issue for your hardware?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are
Please see the upstream bug report for all of the necessary debugging
logs. However, the bug has already been identified and the issue here
is really just deciding how to package the fix.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
14 matches
Mail list logo
