AskOverflow.Dev

AskOverflow.Dev Logo AskOverflow.Dev Logo

AskOverflow.Dev Navigation

  • 主页
  • 系统&网络
  • Ubuntu
  • Unix
  • DBA
  • Computer
  • Coding
  • LangChain

Mobile menu

Close
  • 主页
  • 系统&网络
    • 最新
    • 热门
    • 标签
  • Ubuntu
    • 最新
    • 热门
    • 标签
  • Unix
    • 最新
    • 标签
  • DBA
    • 最新
    • 标签
  • Computer
    • 最新
    • 标签
  • Coding
    • 最新
    • 标签
主页 / ubuntu / 问题 / 1181844
Accepted
0leg
0leg
Asked: 2019-10-19 02:41:13 +0800 CST2019-10-19 02:41:13 +0800 CST 2019-10-19 02:41:13 +0800 CST

禁用 Wifi:Ubuntu 19.10 - 英特尔无线 7265

  • 772

更新到 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
networking drivers iwlwifi 19.10
  • 2 2 个回答
  • 16568 Views

2 个回答

  • Voted
  1. evod
    2019-10-21T00:33:04+08:002019-10-21T00:33:04+08:00

    更新:在我的情况下,禁用 802.11n 后 WIFI 再次工作。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_configuration/Wireless#iwlwifi(iwlwifi参数也适用于 Ubuntu,Arch 有很好的文档)


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

    新安装的 Ubuntu MATE 也存在此问题,与升级无关 - 我尝试在 USB 记忆棒上使用 Ubuntu Mate 18.10 和 Kubuntu 19.10:行为相同。所以我想说所有的 Ubuntu 19.10 版本都会受到影响。

    我想详细说明不起作用的部分:

    • WIFI 处于活动状态,我可以看到可用的网络,例如iwlist wlp3s0 scan
    • 但是,连接到网络(使用 GUI)失败:输入凭据(对于受密码保护的 WPA2 网络)后,它尝试连接几秒钟,但随后再次要求输入密码.. 并再次..
    • 问题也不在于 GUI,完全相同的行为显示为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 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.
    

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

    sudo journalctl | grep iwlwifi对于 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对于 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
    
    • 6
  2. Best Answer
    Malarial
    2019-12-28T21:52:22+08:002019-12-28T21:52:22+08:00

    从 Ubuntu 19.04 更新到 19.10 后,我遇到了同样的问题。似乎在更新过程之前,我们都可能手动或自动安装了包“backport-iwlwifi-dkms”。该软件包为您所在的特定版本内核编译了驱动程序。虽然它可能在更新后大部分工作,但附加驱动程序工具发现与新内核的兼容性不匹配。

    对我来说解决方案非常简单:使用以下命令重新安装 backport-iwlwifi-dkms。无需禁用 802.11n 或其他任何东西!

    sudo apt install backport-iwlwifi-dkms
    

    安装完成后,关闭 Additional Drivers 窗口并重新打开它。窗口现在应该看起来像这样。

    窗口现在应该看起来像这样

    • 6

相关问题

  • 如何限制下载/上传带宽?

  • 如何通过 Windows 网络共享文件?

  • 类似于 Eyefinity 的东西?

  • 面板小程序以文本形式显示当前网络流量?

  • 在哪里可以找到 Brother HL-2170W 64 位打印机驱动程序?

Sidebar

Stats

  • 问题 205573
  • 回答 270741
  • 最佳答案 135370
  • 用户 68524
  • 热门
  • 回答
  • Marko Smith

    如何运行 .sh 脚本?

    • 16 个回答
  • Marko Smith

    如何安装 .tar.gz(或 .tar.bz2)文件?

    • 14 个回答
  • Marko Smith

    如何列出所有已安装的软件包

    • 24 个回答
  • Marko Smith

    无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗?

    • 25 个回答
  • Martin Hope
    Flimm 如何在没有 sudo 的情况下使用 docker? 2014-06-07 00:17:43 +0800 CST
  • Martin Hope
    Ivan 如何列出所有已安装的软件包 2010-12-17 18:08:49 +0800 CST
  • Martin Hope
    La Ode Adam Saputra 无法锁定管理目录 (/var/lib/dpkg/) 是另一个进程在使用它吗? 2010-11-30 18:12:48 +0800 CST
  • Martin Hope
    David Barry 如何从命令行确定目录(文件夹)的总大小? 2010-08-06 10:20:23 +0800 CST
  • Martin Hope
    jfoucher “以下软件包已被保留:”为什么以及如何解决? 2010-08-01 13:59:22 +0800 CST
  • Martin Hope
    David Ashford 如何删除 PPA? 2010-07-30 01:09:42 +0800 CST

热门标签

10.10 10.04 gnome networking server command-line package-management software-recommendation sound xorg

Explore

  • 主页
  • 问题
    • 最新
    • 热门
  • 标签
  • 帮助

Footer

AskOverflow.Dev

关于我们

  • 关于我们
  • 联系我们

Legal Stuff

  • Privacy Policy

Language

  • Pt
  • Server
  • Unix

© 2023 AskOverflow.DEV All Rights Reserve