WLan not working after Kernel update (HWE)

Does this regression happen with the Ubuntu 4.8.0-45 and newer kernels? If so we can bisect between 4.8.0-44 and 4.8.0-45.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1681904

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

There are not may commits between 4.8.0-44 and 4.8.0-45, so knowing the exact kernel when the regression started would be very helpful.

>Does this regression happen with the Ubuntu 4.8.0-45 and newer kernels?

@Joseph: yes, i have the issue with .45 and .46 while .44 is OK. i can boot all versions from grub.

should i do the apport-collect and if so with what version booted?

thanks for the very fast reply!

I started a kernel bisect between v4.8.0-44 and v4.8.0-45.

I built the first test kernel, up to the following commit:
ac48b37537fd6218731af4108666239b2a578397

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1681904

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Note, with this test kernel, you need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance

That version has the bug.

I built the next test kernel, up to the following commit:
3105082594ea260feb8c95893a0597b87c7cfe30

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1681904

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

The issue also appear with the kernel 4.8.0-45-generic #48~lp1681904Commit3105082594ea.

I see you have a prepared text for that comments, very good.

The bisect reported that commit 3105082594 introduced the regression, which is strange since that commit is just the "Start new release".

Just to be sure the bisect was started with the proper range, I built a 4.8.0-44 kernel by hand.

This kernel can also be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1681904

Can you test that kernel and see if it also has the bug?

Kernel 4.8.0-44-generic #47~lp1681904StockKernel don't have the issue.

In what repo can i find that commit?

That commit is in the Yakkety repo:
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety

Can you see if this bug is also happening in the Zesty kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/12405875

You need to install both the linux-image and linux-image-extra .deb packages for this kernel as well.

I can reproduce the issue with Linux kernel 4.10.0-19-generic.

Can you test the following kernel next? It is -44 with a pick of 3105082594e on top:
http://kernel.ubuntu.com/~jsalisbury/lp1681904

I can reproduce the issue with Linux kernel 4.8.0-45-generic #48~lp1681904Commit3105082594OntopOfStock44.

How is it going on?

Sorry for the delay. Can you see if this bug is still happening with the Artful kernel? It is available from:

https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/12451317

A review of commit 3105082594 does not indicate any changes that could have caused this, but I'll investigate further.

Thanks.

I can still reproduce the issue with Linux kernel 4.10.0-20-generic.

When testing 4.10.0-20-generic, can you confirm that you installed both the linux-image and the linux-image-extra .deb packages?

We would like to collect some additional information about your system. From a terminal, please run the following:

apport-collect 1681904

Can you run this while booted into the kernel exhibiting the bug?

apport information

apport information

apport information

apport information

I can confirm that i installed both packages.

root@unibook:/home/davidak/Downloads# ls linux-image-*
linux-image-4.10.0-20-generic_4.10.0-20.22_amd64.deb linux-image-extra-4.10.0-20-generic_4.10.0-20.22_amd64.deb
root@unibook:/home/davidak/Downloads# dpkg -i linux-image-*

I collected the additional information.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I built a test kernel with the two commits that came in with -45.

This kernel can also be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1681904

Can you test that kernel and see if it also has the bug?

I can reproduce the issue with Linux kernel 4.8.0-51-generic #54~lp1681904CommitsReverted.

Any progress?

I can still reproduce the issue after an update to the latest kernel 4.10.0-20-generic #22-Ubuntu.

I think 4331 should be supported by wl driver.

Please attach the output of `dkms status`.

This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

root@unibook:/home/davidak# dkms status
bcmwl, 6.30.223.271+bdcom, 4.8.0-44-generic, x86_64: installed
virtualbox, 5.0.40, 4.8.0-44-generic, x86_64: installed
root@unibook:/home/davidak# uname -a
Linux unibook 4.8.0-44-generic #47~lp1681904StockKernel SMP Wed Apr 12 17:28:21 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Should i also attach the output with current HWE kernel where i have the issue?

Sure. I think the current HWE stack is tracking 4.10 series.

I have done the latest updates.

root@unibook:/home/davidak# dkms status
bcmwl, 6.30.223.271+bdcom, 4.8.0-44-generic, x86_64: installed
virtualbox, 5.0.40, 4.8.0-44-generic, x86_64: installed
root@unibook:/home/davidak# uname -a
Linux unibook 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

and removed the manually installed bcmwl from source.

root@unibook:/home/davidak# dkms status
virtualbox, 5.0.40, 4.8.0-44-generic, x86_64: installed
root@unibook:/home/davidak# uname -a
Linux unibook 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Now it also don't work with 4.8.0-44. Isn't the driver in the mainline kernel?

I think your chip needs to use bcmwl.

Please try to reinstall it:
$ sudo apt purge bcmwl-kernel-source
$ sudo apt install bcmwl-kernel-source

the install seams to be succesfull.

root@unibook:/home/davidak# apt install bcmwl-kernel-source
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden NEUEN Pakete werden installiert:
  bcmwl-kernel-source
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 3 nicht aktualisiert.
Es müssen 1.544 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 8.059 kB Plattenplatz zusätzlich benutzt.
Holen:1 http://de.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu1~1.1 [1.544 kB]
Es wurden 1.544 kB in 0 s geholt (1.987 kB/s).
Vormals nicht ausgewähltes Paket bcmwl-kernel-source wird gewählt.
(Lese Datenbank ... 266558 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.1_amd64.deb ...
Entpacken von bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.1) ...
bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.1) wird eingerichtet ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
First Installation: checking all kernels...
Building for 4.8.0-44-generic and 4.10.0-20-generic
Building for architecture x86_64
Building initial module for 4.8.0-44-generic
Done.

wl:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.8.0-44-generic/extra/

depmod....

DKMS: install completed.
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
update-initramfs: deferring update (trigger activated)
Trigger für shim-signed (1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) werden verarbeitet ...
Secure Boot not enabled on this system.
Trigger für initramfs-tools (0.122ubuntu8.8) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-4.10.0-20-generic
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for module i915

but again wifi only works with kernel 4.8.0-44 bootet.

root@unibook:/home/davidak# dkms status
bcmwl, 6.30.223.271+bdcom, 4.8.0-44-generic, x86_64: installed
virtualbox, 5.0.40, 4.8.0-44-generic, x86_64: installed
root@unibook:/home/davidak# uname -a
Linux unibook 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Can i provide any further details that help to solve this?

Please boot using kernel 4.10.0-20, and run
"sudo dkms install bcmwl/6.30.223.271+bdcom -k `uname -r`"
And see what really happens.

davidak@unibook:~$ sudo dkms install bcmwl/6.30.223.271+bdcom -k `uname -r`
[sudo] Passwort für davidak:
Error! echo
Your kernel headers for kernel 4.10.0-20-generic cannot be found at
/lib/modules/4.10.0-20-generic/build or /lib/modules/4.10.0-20-generic/source.

I had to install the kernel headers.

davidak@unibook:~$ sudo apt install linux-headers-$(uname -r)
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden zusätzlichen Pakete werden Installiert
  linux-headers-4.10.0-20
Die folgenden NEUEN Pakete werden installiert:
  linux-headers-4.10.0-20 linux-headers-4.10.0-20-generic
0 aktualisiert, 2 neu installiert, 0 zu entfernen und 19 nicht aktualisiert.
Es müssen 11,2 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 81,8 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
Holen:1 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-4.10.0-20 all 4.10.0-20.22~16.04.1 [10,5 MB]
Holen:2 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-4.10.0-20-generic amd64 4.10.0-20.22~16.04.1 [683 kB]
Es wurden 11,2 MB in 13 s geholt (846 kB/s).
Vormals nicht ausgewähltes Paket linux-headers-4.10.0-20 wird gewählt.
(Lese Datenbank ... 266640 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../linux-headers-4.10.0-20_4.10.0-20.22~16.04.1_all.deb ...
Entpacken von linux-headers-4.10.0-20 (4.10.0-20.22~16.04.1) ...
Vormals nicht ausgewähltes Paket linux-headers-4.10.0-20-generic wird gewählt.
Vorbereitung zum Entpacken von .../linux-headers-4.10.0-20-generic_4.10.0-20.22~16.04.1_amd64.deb ...
Entpacken von linux-headers-4.10.0-20-generic (4.10.0-20.22~16.04.1) ...
linux-headers-4.10.0-20 (4.10.0-20.22~16.04.1) wird eingerichtet ...
linux-headers-4.10.0-20-generic (4.10.0-20.22~16.04.1) wird eingerichtet ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-20-generic /boot/vmlinuz-4.10.0-20-generic

davidak@unibook:~$ sudo dkms install bcmwl/6.30.223.271+bdcom -k `uname -r`
Module bcmwl/6.30.223.271+bdcom already installed on kernel 4.10.0-20-generic/x86_64

What does it say about the issue? How can we achieve that it just work and is usable for normal people?

No idea why the header package is not installed - it should be automatically pulled by meta package.

I guess something went wrong in the upgrade process?

Maybe there was "no space left on device" on /boot once, but i don't know exactly.

My workaround is to use a Dell device now to be able to work.

Status changed to 'Confirmed' because the bug affects multiple users.