← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22

 

** Also affects: linux-firmware (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Changed in: linux-firmware (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: linux-firmware (Ubuntu Zesty)
       Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Zesty)
     Assignee: (unassigned) => Seth Forshee (sforshee)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1647826

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-firmware source package in Yakkety:
  In Progress
Status in linux-firmware source package in Zesty:
  In Progress

Bug description:
  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi 0000:6e:00.0: Microcode SW error detected.
  Restarting 0x2000000.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions