Wifi-禁用: Ubuntu 19.10 - Intel Wireless 7265

Question

更新到Ubuntu 19.10之后：

单击继续使用..。重新检查不使用..。

试图从微软网站下载驱动程序，并将它们放到lib/firmware中。

不过，WiFi可以工作。

什么是正确的工作，以确保正确的驱动程序被使用？

rfkill list all
0: hci0: Bluetooth
    Soft blocked: yes
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

lspci -nnk | grep 0280 -A2
02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59)
    Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5110]
    Kernel driver in use: iwlwifi

ls -al /lib/firmware | grep 7265
-rw-r--r--  1 root root  736844 Mar 30  2017 iwlwifi-7265-10.ucode
-rw-r--r--  1 root root  880604 Mar 30  2017 iwlwifi-7265-12.ucode
-rw-r--r--  1 root root  885224 Mar 30  2017 iwlwifi-7265-13.ucode
-rw-r--r--  1 root root 1180224 Oct 17 21:10 iwlwifi-7265-14.ucode
-rw-r--r--  1 root root 1180356 Mar 30  2017 iwlwifi-7265-16.ucode
-rw-r--r--  1 root root 1180412 Oct  8 21:54 iwlwifi-7265-17.ucode
-rw-r--r--  1 root root  690452 Mar 30  2017 iwlwifi-7265-8.ucode
-rw-r--r--  1 root root  697828 Mar 30  2017 iwlwifi-7265-9.ucode
lrwxrwxrwx  1 root root      21 Nov 17  2017 iwlwifi-7265D-10.ucode -> iwlwifi-7265-10.ucode
-rw-r--r--  1 root root 1002800 Mar 30  2017 iwlwifi-7265D-12.ucode
-rw-r--r--  1 root root 1008692 Mar 30  2017 iwlwifi-7265D-13.ucode
-rw-r--r--  1 root root 1384256 Oct 17 21:10 iwlwifi-7265D-14.ucode
-rw-r--r--  1 root root 1384500 Mar 30  2017 iwlwifi-7265D-16.ucode
-rw-r--r--  1 root root 1383604 Nov 17  2017 iwlwifi-7265D-17.ucode
-rw-r--r--  1 root root 1385368 Nov 17  2017 iwlwifi-7265D-21.ucode
-rw-r--r--  1 root root 1028376 Apr 24  2018 iwlwifi-7265D-22.ucode
-rw-r--r--  1 root root 1032740 Dec  5  2017 iwlwifi-7265D-27.ucode
-rw-r--r--  1 root root 1036668 Oct  8 21:54 iwlwifi-7265D-29.ucode

Answer 1

在从Ubuntu19.04升级到19.10之后，我也遇到了同样的问题。在更新之前，我们可能都安装了"backport-iwlwifi-dkms“包，无论是手动的还是自动的。该包为您所在的特定版本内核编译了一个驱动程序。虽然它可能在更新之后大部分都能工作，但是附加的驱动程序工具发现了与新内核的兼容性不匹配。

对于我来说，解决方案非常简单:用以下命令重新安装backport dkms。没有必要禁用802.11n或其他任何东西！

sudo apt install backport-iwlwifi-dkms

安装完成后，关闭“附加驱动程序”窗口并重新打开它。窗口现在应该是这样的。

Answer 2

更新:在我的例子中，WIFI在禁用802.11n之后再次工作。我将选项11n_disable=1添加到/etc/modprobe.d/iwlwifi.conf中，现在看起来如下所示：

# /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

还请参阅https://wiki.archlinux.org/index.php/Network_配置/无线#iwlwifi ( iwlwifi参数也适用于Ubuntu，Arch有很好的文档)

我有完全相同的问题(升级到Ubuntu 19.10后没有WIFI连接)和完全相同的WIFI卡(相同的lspci输出)。

这个问题也存在于Ubuntu的新安装中，并且与升级无关--我尝试了Ubuntu 18.10和Kubuntu 19.10的USB接口:相同的行为。所以我想说所有的Ubuntu19.10口味都会受到影响。

我想详细说明什么是不起作用的部分：

• WIFI是活动的，我可以看到可用的网络，例如iwlist wlp3s0 scan
• 然而，连接到网络(用图形用户界面)失败:输入凭据(密码被标记为WPA2网络)之后，它尝试连接几秒钟，然后再次请求密码。再一次..。
• 而且问题不是图形用户界面，完全相同的行为由nmtui显示。

检查NetworkManager在/var/log/syslog中的输出，我们可以看到关联是失败的：

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')

这就是Ubuntu 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.

查看日志和日志，我找不到任何错误或警告，但我注意到iwlwifi似乎激活了调试模式。

Ubuntu19.04的sudo journalctl | grep iwlwifi：

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)

Ubuntu19.10的sudo journalctl | grep iwlwifi：

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