Can not establish WIFI connection with Intel Wireless 7265 [8086:095a] subsystem id [8086:5110] after upgrade to Ubuntu 19.10

Bug #1849891 reported by Markus Straub
70
This bug affects 15 people
Affects Status Importance Assigned to Milestone
backport-iwlwifi-dkms (Ubuntu)
Confirmed
Undecided
You-Sheng Yang

Bug Description

- WIFI is active, and I can see available networks, e.g. with iwlist wlp3s0 scan
- However, connecting to a network (with the GUI) fails: after entering credentials (for a password protrected WPA2 network) it tries to connect for a few seconds but then asks for a passphrase again .. and again ..
- Also the problem is not the GUI, the exact same behavior is shown by nmtui

Checking the output of NetworkManager in /var/log/syslog we can see that the association is the one that fails:

sudo cat /var/log/syslog | grep "(wlp3s0)" | sed 's/.*device //'

device (wlp3s0): Activation: starting connection 'MY_WIFI' (c5c790fb-86a8-4905-97b0-75170f5e985c)
device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) access point 'MY_WIFI' has security, but secrets are required.
device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) connection 'MY_WIFI' has security, and secrets exist. No new secrets needed.
device (wlp3s0): supplicant interface state: ready -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): supplicant interface state: scanning -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> disconnected
device (wlp3s0): Activation: (wifi) association took too long
device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) asking for new secrets
device (wlp3s0): supplicant interface state: disconnected -> scanning
device (wlp3s0): no secrets: User canceled the secrets request.
device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
device (wlp3s0): Activation: failed for connection 'MY_WIFI'
device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

This is what the log looked like before the update with Ubuntu MATE 19.04

device (wlp3s0): Activation: starting connection 'MY_WLAN' (b3dffdda-2b7b-467d-a1f5-2b3077d26eb3)
device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) access point 'MY_WLAN' has security, but secrets are required.
device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): Activation: (wifi) connection 'MY_WLAN' has security, and secrets exist. No new secrets needed.
device (wlp3s0): supplicant interface state: ready -> authenticating
device (wlp3s0): supplicant interface state: authenticating -> associating
device (wlp3s0): supplicant interface state: associating -> associated
device (wlp3s0): supplicant interface state: associated -> 4-way handshake
device (wlp3s0): supplicant interface state: 4-way handshake -> completed
device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "MY_WLAN"
device (wlp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
dhcp4 (wlp3s0): dhclient started with pid 20140
dhcp4 (wlp3s0): address 192.168.1.161
dhcp4 (wlp3s0): plen 24 (255.255.255.0)
dhcp4 (wlp3s0): gateway 192.168.1.1
dhcp4 (wlp3s0): lease time 43200
dhcp4 (wlp3s0): hostname 'whakaari'
dhcp4 (wlp3s0): nameserver '192.168.1.1'
dhcp4 (wlp3s0): state changed unknown -> bound
device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
device (wlp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
policy: set 'MY_WLAN' (wlp3s0) as default for IPv4 routing and DNS
device (wlp3s0): Activation: successful, device activated.

Checking the journal and logs I can not find any errors or warnings, but I noted that iwlwifi seems to have a debug mode activated.

sudo journalctl | grep iwlwifi for Ubuntu 19.04:

Sep 10 19:59:56 whakaari kernel: iwlwifi 0000:03:00.0: loaded firmware version 29.1044073957.0 op_mode iwlmvm
Sep 10 19:59:56 whakaari kernel: iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
Sep 10 19:59:56 whakaari kernel: iwlwifi 0000:03:00.0: base HW address: 5c:e0:c5:63:e2:a5
Sep 10 19:59:57 whakaari kernel: iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
Sep 10 19:59:57 whakaari sensors[873]: iwlwifi-virtual-0
Sep 10 19:59:58 whakaari NetworkManager[856]: <info> [1568138398.2497] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill3) (driver iwlwifi)

sudo journalctl | grep iwlwifi for Ubuntu 19.10:

Oct 19 16:16:30 whakaari kernel: iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM
Oct 19 16:16:30 whakaari kernel: iwlwifi 0000:03:00.0: Found debug configuration: 0
Oct 19 16:16:30 whakaari kernel: iwlwifi 0000:03:00.0: loaded firmware version 29.1654887522.0 op_mode iwlmvm
Oct 19 16:16:30 whakaari kernel: iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
Oct 19 16:16:30 whakaari kernel: iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
Oct 19 16:16:30 whakaari kernel: iwlwifi 0000:03:00.0: Allocated 0x00400000 bytes for firmware monitor.
Oct 19 16:16:30 whakaari kernel: iwlwifi 0000:03:00.0: base HW address: 5c:e0:c5:63:e2:a5
Oct 19 16:16:31 whakaari kernel: iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
Oct 19 16:16:32 whakaari sensors[941]: iwlwifi-virtual-0

More details and other people having the same issue:
https://askubuntu.com/questions/1181844/wifi-disabled-ubuntu-19-10-intel-wireless-7265

Tags: eoan
You-Sheng Yang (vicamo)
tags: added: eoan
summary: - Can not establish WIFI connection with Intel Wireless 7265 after upgrade
- to Ubuntu 19.10
+ Can not establish WIFI connection with Intel Wireless 7265 [8086:095a]
+ subsystem id [8086:5110] after upgrade to Ubuntu 19.10
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Hi, could you give some more details, what (kernel/firmware versions) was working, what is not? Could you test following combinations:

1. mainline v5.4-rc5 kernel[1] + linux-firmware HEAD[2]

2. bleeding edge backport-iwlwifi-dkms[3] + linux-firmware HEAD

3. linux-image-oem-osp1 kernel + linux-firmware HEAD

Please paste dmesg output for each of above tests.

[1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/
[3]: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/backport-iwlwifi

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in backport-iwlwifi-dkms (Ubuntu):
status: New → Confirmed
Revision history for this message
Markus Straub (markus-straub-at) wrote :
Download full text (3.9 KiB)

Thank you for your suggestions, You-Sheng Yang.

Which kernel/firmware version worked?
-> the default Ubuntu 19.04 kernel and firmware. I never installed a kernel or firmware from external sources and all minor updates that were available worked just fine. What also worked: all other versions of Ubuntu I used on my laptop, at least 18.04 and 18.10 too, most probably I also used 16.04 (not sure).

Which kernel/firmware does not work?
-> The versions at the release of Ubuntu 19.10 (on the .iso images) and also the latest update (5.3.0-19-generic).

An important detail could be, that when I boot Ubuntu 19.10 with the old kernel still installed from 19.04 the same behavior can be seen.

$ uname -a
Linux whakaari 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ dmesg | grep "iwlwifi\|wlp3s0"
[ 4.442485] iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM
[ 4.442487] iwlwifi 0000:03:00.0: Found debug configuration: 0
[ 4.442790] iwlwifi 0000:03:00.0: loaded firmware version 29.1654887522.0 op_mode iwlmvm
[ 4.495202] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
[ 4.509093] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 4.509828] iwlwifi 0000:03:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 4.520392] iwlwifi 0000:03:00.0: base HW address: 5c:e0:c5:63:e2:a5
[ 4.838622] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[ 6.741168] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 6.826404] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[ 6.829668] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[ 65.133013] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[ 65.139402] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[ 65.159113] wlp3s0: authenticated
[ 65.166457] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[ 65.274544] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[ 65.378575] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[ 65.482488] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[ 66.523712] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[ 66.530411] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[ 66.634538] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 2/3)
[ 66.644178] wlp3s0: authenticated
[ 66.646503] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[ 66.750461] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[ 66.854575] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[ 66.958583] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[ 68.401500] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[ 68.406079] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 1/3)
[ 68.510545] wlp3s0: send auth to 9c:4f:cf:a1:91:62 (try 2/3)
[ 68.520607] wlp3s0: authenticated
[ 68.522474] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 1/3)
[ 68.626486] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 2/3)
[ 68.730468] wlp3s0: associate with 9c:4f:cf:a1:91:62 (try 3/3)
[ 68.834507] wlp3s0: association with 9c:4f:cf:a1:91:62 timed out
[ 72.949579] wlp3s0: authenticate with 9c:4f:cf:a1:91:62
[ 72.954141] wlp3s0: send a...

Read more...

Revision history for this message
Markus Straub (markus-straub-at) wrote :
Download full text (11.9 KiB)

Results from your third suggestion (unfortunately no success):

$ sudo add-apt-repository ppa:canonical-hwe-team/backport-iwlwifi
$ sudo apt install backport-iwlwifi-dkms

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  backport-iwlwifi-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1.551 kB of archives.
After this operation, 9.942 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/canonical-hwe-team/backport-iwlwifi/ubuntu eoan/main amd64 backport-iwlwifi-dkms all 8042-0ubuntu1 [1.551 kB]
Fetched 1.551 kB in 2s (849 kB/s)
Selecting previously unselected package backport-iwlwifi-dkms.
(Reading database ... 320149 files and directories currently installed.)
Preparing to unpack .../backport-iwlwifi-dkms_8042-0ubuntu1_all.deb ...
Unpacking backport-iwlwifi-dkms (8042-0ubuntu1) ...
Setting up backport-iwlwifi-dkms (8042-0ubuntu1) ...
Loading new backport-iwlwifi-8042 DKMS files...
Building for 5.3.0-19-generic
Building initial module for 5.3.0-19-generic
Done.

compat.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

iwlwifi.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

iwlxvt.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

iwlmvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

mac80211.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

cfg80211.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-19-generic/updates/dkms/

depmod...

DKMS: install completed.

$ uname -a
Linux whakaari 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Then I rebooted and tried to connect to the WIFI

$ dmesg | grep "iwlwifi\|wlp3s0"
[ 4.247626] Loading modules backported from iwlwifi
[ 4.247627] iwlwifi-stack-public:master:8042:654c426c
[ 4.362032] iwlwifi 0000:03:00.0: Direct firmware load for iwl-dbg-cfg.ini failed with error -2
[ 4.367098] iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM
[ 4.367108] iwlwifi 0000:03:00.0: Found debug configuration: 0
[ 4.367369] iwlwifi 0000:03:00.0: loaded firmware version 29.62a39462.0 op_mode iwlmvm
[ 4.389809] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
[ 4.4...

Revision history for this message
Markus Straub (markus-straub-at) wrote :

Update: In my case WIFI works again after disabling 802.11n. I added the option 11n_disable=1 to /etc/modprobe.d/iwlwifi.conf - now it looks like this:

# /etc/modprobe.d/iwlwifi.conf
# iwlwifi will dyamically load either iwldvm or iwlmvm depending on the
# microcode file installed on the system. When removing iwlwifi, first
# remove the iwl?vm module and then iwlwifi.
remove iwlwifi \
(/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \
&& /sbin/modprobe -r mac8021
options iwlwifi 11n_disable=1

See also https://wiki.archlinux.org/index.php/Network_configuration/Wireless#iwlwifi (the iwlwifi parameters apply to Ubuntu too and Arch has great documentation )

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Markus, if neither dkms nor latest mainline kernel works for you, then we'll need to file an upstream bug to https://bugzilla.kernel.org/buglist.cgi?component=Wireless&product=Networking&resolution=---

Revision history for this message
Bernhard Hayden (burnoutberni) wrote :

Since my upgrade today to 19.10 I am affected by the same bug, but with different hardware

$ lspci -nnk | grep Network -A2
00:14.3 Network controller [0280]: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:9df0] (rev 30)
 Subsystem: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:0034]
 Kernel driver in use: iwlwifi

Tried backport-iwlwifi-dkms and the old kernel, none of which helped, so I'm using the 11n_disable workaround as well for the time being.

Revision history for this message
You-Sheng Yang (vicamo) wrote :

@Bernhard, you have a different card, it's not the same bug. Please file a separate bug instead.

@Markus, I found a model with Intel Wireless 7265 but with subsystem id [8086:5410]. The adapter works out-of-box with Eoan generic kernel 5.3.0-24-generic, and yes, and I also got endless auth retry with backport-iwlwifi-dkms 7906-0ubuntu3. So you might want to remove backport-iwlwifi-dkms as you don't really need it. backport-iwlwifi-dkms version 8042-0ubuntu2 from Focal also works well with this piece of hw.

Changed in backport-iwlwifi-dkms (Ubuntu):
assignee: nobody → You-Sheng Yang (vicamo)
Revision history for this message
Martin Dünkelmann (nc-duenkekl3-deactivatedaccount) wrote :

Same issue with my Intel Wireless 8260
Upgrading from 7906 to 8324 in Ubuntu 18.04 fixed this nasty bug for me.
I use now this and be happy
https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/backport-iwlwifi?field.series_filter=bionic

Revision history for this message
Martin Dünkelmann (nc-duenkekl3-deactivatedaccount) wrote :

PS I'm using kernel 5.3.0-26-generic

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.