安装 backport-iwlwifi-dkms 后网络密码被拒绝

异形

在新的联想 P53 上全新安装 Kubuntu 19.10。

起初 Wifi 网络工作正常,我可以使用常用密码连接到我的家庭 Wifi。

驱动程序管理器建议安装backport-iwlwifi-dkms,我这样做了,但现在密码被拒绝。我也试过我的手机热点(有一个相当简单的密码),它也被拒绝了。如果我将它重新配置为无密码,我可以连接到电话热点。

密码可以显示并且没问题,我什至复制/粘贴了它。

来自 /var/log/syslog 的连接序列日志(似乎它首先尝试使用存储的密码进行连接,这很可能也是正确的密码):

Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9624] device (wlp82s0): Activation: starting connection 'HomeNetwork' (9ca67590-8a02-495c-a7cb-da56076aad08)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9627] audit: op="connection-activate" uuid="9ca67590-8a02-495c-a7cb-da56076aad08" name="HomeNetwork" pid=1633 uid=1000 result="success"
Jan 17 21:45:41 P53 kernel: [ 2997.428660] wlp82s0: authenticate with 14:0c:76:bc:ab:68
Jan 17 21:45:41 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9630] device (wlp82s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9643] manager: NetworkManager state is now CONNECTING
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9656] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9664] device (wlp82s0): Activation: (wifi) access point 'HomeNetwork' has security, but secrets are required.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9665] device (wlp82s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9684] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9687] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist.  No new secrets needed.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'scan_ssid' value '1'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9688] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9689] Config: added 'psk' value '<hidden>'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9793] device (wlp82s0): supplicant interface state: inactive -> authenticating
Jan 17 21:45:41 P53 NetworkManager[1121]: <info>  [1579293941.9793] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> authenticating
Jan 17 21:45:41 P53 kernel: [ 2997.433797] wlp82s0: send auth to 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0044] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0044] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:42 P53 kernel: [ 2997.458775] wlp82s0: authenticated
Jan 17 21:45:42 P53 kernel: [ 2997.461167] wlp82s0: associate with 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 kernel: [ 2997.463098] wlp82s0: RX AssocResp from 14:0c:76:bc:ab:68 (capab=0x111 status=0 aid=4)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:42 P53 kernel: [ 2997.468796] wlp82s0: associated
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0195] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 NetworkManager[1121]: <info>  [1579293942.0195] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 kernel: [ 2997.523928] wlp82s0: Limiting TX power to 17 (20 - 3) dBm as advertised by 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 kernel: [ 2998.015706] iwlwifi 0000:52:00.0: Unhandled alg: 0x707
Jan 17 21:45:43 P53 kernel: [ 2998.480972] wlp82s0: deauthenticating from 14:0c:76:bc:ab:68 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:bc:ab:68)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:bc:ab:68 reason=1 locally_generated=1
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:43 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:43 P53 NetworkManager[1121]: <warn>  [1579293943.0361] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0412] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0420] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0420] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.0424] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.1413] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:43 P53 NetworkManager[1121]: <info>  [1579293943.1413] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0258] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0262] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist.  No new secrets needed.
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'scan_ssid' value '1'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0265] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0266] Config: added 'psk' value '<hidden>'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0372] device (wlp82s0): supplicant interface state: inactive -> scanning
Jan 17 21:45:54 P53 NetworkManager[1121]: <info>  [1579293954.0372] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> scanning
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.490277] wlp82s0: authenticate with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0417] device (wlp82s0): supplicant interface state: scanning -> authenticating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0417] device (p2p-dev-wlp82s0): supplicant management interface state: scanning -> authenticating
Jan 17 21:45:55 P53 kernel: [ 3010.496321] wlp82s0: send auth to 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.520689] wlp82s0: authenticated
Jan 17 21:45:55 P53 kernel: [ 3010.521092] wlp82s0: associate with 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0662] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0662] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:55 P53 kernel: [ 3010.525437] wlp82s0: RX AssocResp from 14:0c:76:55:47:d1 (capab=0x411 status=0 aid=3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:55 P53 kernel: [ 3010.531546] wlp82s0: associated
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0822] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.0822] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:55:47:d1)
Jan 17 21:45:55 P53 kernel: [ 3010.543158] wlp82s0: deauthenticating from 14:0c:76:55:47:d1 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:55:47:d1 reason=1 locally_generated=1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:55 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:55 P53 NetworkManager[1121]: <warn>  [1579293955.1000] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1051] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1056] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1057] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.1060] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.2052] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:55 P53 NetworkManager[1121]: <info>  [1579293955.2052] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn>  [1579293957.0813] device (wlp82s0): no secrets: User canceled the secrets request.
Jan 17 21:45:57 P53 NetworkManager[1121]: <info>  [1579293957.0814] device (wlp82s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Jan 17 21:45:57 P53 NetworkManager[1121]: <info>  [1579293957.0817] manager: NetworkManager state is now DISCONNECTED
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn>  [1579293957.0824] device (wlp82s0): Activation: failed for connection 'HomeNetwork'
Jan 17 21:45:57 P53 NetworkManager[1121]: <info>  [1579293957.0826] device (wlp82s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

这部分lshw似乎相关:

        *-pci:3
             description: PCI bridge
             product: Cannon Lake PCH PCI Express Root Port #6
             vendor: Intel Corporation
             physical id: 1c.5
             bus info: pci@0000:00:1c.5
             version: f0
             width: 32 bits
             clock: 33MHz
             capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:125 memory:ce200000-ce2fffff
           *-network
                description: Ethernet interface
                product: Intel Corporation
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:52:00.0
                logical name: wlp82s0
                version: 1a
                serial: 94:e6:f7:f4:70:cc
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical
                configuration: broadcast=yes driver=iwlwifi driverversion=5.3.0-26-generic firmware=48.4fa0041f.0 latency=0 link=no multicast=yes
                resources: irq:17 memory:ce200000-ce203fff

有任何想法吗?

否则我如何重新安装以前的?

$$>dkms status
backport-iwlwifi, 7906, 5.3.0-26-generic, x86_64: installed
nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
nvidia, 435.21, 5.3.0-26-generic, x86_64: installed
海尼玛

无线网络工作。您安装了新驱动程序。无线网络坏了。

如何重新安装前一个(驱动程序)?

dkms status
backport-iwlwifi, 7906, 5.3.0-26-generic, x86_64: installed

要删除backport-iwlwifi-dkms驱动程序,并恢复到原始iwlwifi驱动程序...

sudo dkms remove backport-iwlwifi/7906 -k 5.3.0-26-generic

reboot

注意根据这篇文章,backport-iwlwifi-dkms 不能与内核 5.0.0+ 一起使用

本文收集自互联网,转载请注明来源。

如有侵权,请联系[email protected] 删除。

编辑于
0

我来说两句

0条评论
登录后参与评论

相关文章

来自分类Dev

如何撤消backport-iwlwifi的安装?

来自分类Dev

如何安装dkms?

来自分类Dev

dkms已安装内核模块,但重启后无法工作

来自分类Dev

从backport安装ath9k后找不到wlan0-Ubuntu 14.04

来自分类Dev

Ubuntu 14.04 backport中的systemd要在安装后删除许多文件-为什么?

来自分类Dev

安装内核时dkms挂起

来自分类Dev

从Debian Jessie上的backport安装Certbot

来自分类Dev

安装kali linux时出现iwlwifi错误

来自分类Dev

安装 Nvidia 驱动程序 DKMS 失败后无法启动 ubuntu

来自分类Dev

在自制Linux系统上安装DKMS

来自分类Dev

安装virtualbox-guest-dkms失败

来自分类Dev

如何删除添加(未安装)的 dkms

来自分类Dev

包“dkms”没有安装候选

来自分类Dev

软件更新后安装新内核时,将无法正确构建2个DKMS驱动程序

来自分类Dev

已安装Virtualbox,dkms,linux-header和virtualbox-dkms,但据说丢失了吗?

来自分类Dev

安装acpi-call-dkms时出现此错误

来自分类Dev

Virtualbox 4.3.26 dkms无法在Linux内核4.1上正确安装

来自分类Dev

帮助卸载通过dkms安装的驱动程序

来自分类Dev

在 Ubuntu 20 上安装 virtualbox-dkms 时出错

来自分类Dev

无法在 Ubuntu 20.04.1 LTS 上安装 Rock-dkms

来自分类Dev

内核升级后,dkms不会自动重建

来自分类Dev

安装asyncio backport trollius时出现gcc错误(Python 2.7.5和Win7)

来自分类Dev

内核更新到 5.3.0-43 内核后 iwlwifi 崩溃

来自分类Dev

debian Stretch wifi无法正常工作-iwlwifi已安装但无法正确加载

来自分类Dev

如何安装wifi驱动程序iwlwifi 4.2.0-16-generic

来自分类Dev

为UNCLAIMED Wireless 8260安装英特尔iwlwifi固件吗?

来自分类Dev

Dell上的Alps触摸板:如何安装DKMS驱动程序以启用多点触摸?

来自分类Dev

Dell上的Alps触摸板:如何安装DKMS驱动程序以启用多点触摸?

来自分类Dev

带Ubuntu 14.04 LTS的VirtualBox VM解析问题(已安装的virtualbox-guest-dkms)

Related 相关文章

  1. 1

    如何撤消backport-iwlwifi的安装?

  2. 2

    如何安装dkms?

  3. 3

    dkms已安装内核模块,但重启后无法工作

  4. 4

    从backport安装ath9k后找不到wlan0-Ubuntu 14.04

  5. 5

    Ubuntu 14.04 backport中的systemd要在安装后删除许多文件-为什么?

  6. 6

    安装内核时dkms挂起

  7. 7

    从Debian Jessie上的backport安装Certbot

  8. 8

    安装kali linux时出现iwlwifi错误

  9. 9

    安装 Nvidia 驱动程序 DKMS 失败后无法启动 ubuntu

  10. 10

    在自制Linux系统上安装DKMS

  11. 11

    安装virtualbox-guest-dkms失败

  12. 12

    如何删除添加(未安装)的 dkms

  13. 13

    包“dkms”没有安装候选

  14. 14

    软件更新后安装新内核时,将无法正确构建2个DKMS驱动程序

  15. 15

    已安装Virtualbox,dkms,linux-header和virtualbox-dkms,但据说丢失了吗?

  16. 16

    安装acpi-call-dkms时出现此错误

  17. 17

    Virtualbox 4.3.26 dkms无法在Linux内核4.1上正确安装

  18. 18

    帮助卸载通过dkms安装的驱动程序

  19. 19

    在 Ubuntu 20 上安装 virtualbox-dkms 时出错

  20. 20

    无法在 Ubuntu 20.04.1 LTS 上安装 Rock-dkms

  21. 21

    内核升级后,dkms不会自动重建

  22. 22

    安装asyncio backport trollius时出现gcc错误(Python 2.7.5和Win7)

  23. 23

    内核更新到 5.3.0-43 内核后 iwlwifi 崩溃

  24. 24

    debian Stretch wifi无法正常工作-iwlwifi已安装但无法正确加载

  25. 25

    如何安装wifi驱动程序iwlwifi 4.2.0-16-generic

  26. 26

    为UNCLAIMED Wireless 8260安装英特尔iwlwifi固件吗?

  27. 27

    Dell上的Alps触摸板:如何安装DKMS驱动程序以启用多点触摸?

  28. 28

    Dell上的Alps触摸板:如何安装DKMS驱动程序以启用多点触摸?

  29. 29

    带Ubuntu 14.04 LTS的VirtualBox VM解析问题(已安装的virtualbox-guest-dkms)

热门标签

归档