硬重置 Ubuntu 22.04 后未找到板载 Wifi 适配器

硬重置 Ubuntu 22.04 后未找到板载 Wifi 适配器

编辑/解决方案:问题不在于 Ubuntu,而在于我的电源管理/主板!

启动时,BIOS 会给我各种错误消息,但我今天决定特别调查其中一条(因为我不记得确切的错误,所以进行了总结):

"USB device not accepting address"

最终,在启动时,我的 USB 无线适配器也无法工作。因此,我谷歌了一下这个错误,然后我发现这个非常简单的指南说原因很可能是硬件故障。我关闭了电脑,拔掉了所有 USB 设备,关闭电源开关并拔掉了电源,然后等了 2 分钟。然后我重新打开电脑并重新插入所有设备,然后它就正常工作了!

我将把所有最初的故障排除保留在下面,以便作为文档/标签,以防将来其他人遇到此问题。




我提交这个问题是因为我之前认识到在船上强制关机后 Wifi 适配器不再可用。有时,当我从睡眠状态唤醒 PC 时,Ubuntu 不会加载,我的电脑只会显示空白屏幕。在这些情况下,我通过以下方式强制关机按住电源按钮 5 秒钟。上次我这样做之后,我登录到我的电脑,但 Ubuntu 无法连接到互联网(右上角的 wifi 图标消失了),当我进入 wifi 设置时,我没有发现网络硬件。

我找到了一个旧的 USB Wifi 适配器,我可以为其安装驱动程序,并且可以在我的 PC 上运行,但是在启动时需要几分钟才能注册,我宁愿让我的板载 wifi 再次被识别。

我看了看这个问题,看起来非常相似,并按照其中的步骤(创建一个新的conf文件并修改规则文件),但这并不能解决我的问题。

我将在下面提供软件信息,如果您需要更多信息或需要我运行任何命令,请告诉我。我对 Ubuntu 的了解非常初级,所以我应该能够在终端中运行您要求的任何命令。

命令输出sudo lshw -C network

 *-network                 
       description: Ethernet interface
       product: RTL8125 2.5GbE Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:0c:00.0
       logical name: enp12s0
       version: 05
       serial: 74:56:3c:43:0c:15
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.19.0-32-generic firmware=rtl8125b-2_0.0.2 07/13/20 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:34 ioport:d000(size=256) memory:81800000-8180ffff memory:81810000-81813fff
  *-network
       description: Network controller
       product: MEDIATEK Corp.
       vendor: MEDIATEK Corp.
       physical id: 0
       bus info: pci@0000:0d:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm bus_master cap_list
       configuration: driver=mt7921e latency=0
       resources: iomemory:fc0-fbf irq:97 memory:fc02100000-fc021fffff memory:81900000-81907fff
  *-network
       description: Wireless interface
       physical id: d
       bus info: usb@1:3
       logical name: wlx0013eff6b9c8
       serial: 00:13:ef:f6:b9:c8
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl88x2bu driverversion=v5.13.1-20-gbd7c7eb9d.20210702_ firmware=30.20 ip=192.168.106.106 link=yes multicast=yes wireless=IEEE 802.11AC

命令输出lspci | grep -i net


0c:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
0d:00.0 Network controller: MEDIATEK Corp. Device 0616

命令输出modinfo mt7921e | grep alias

alias:          pci:v000014C3d00000616sv*sd*bc*sc*i*
alias:          pci:v000014C3d00000608sv*sd*bc*sc*i*
alias:          pci:v000014C3d00007922sv*sd*bc*sc*i*
alias:          pci:v000014C3d00007961sv*sd*bc*sc*i*

我已经按照上面链接的问题中的步骤操作,并尝试运行命令modprobe mt7921e来自动添加驱动程序,但我的板载 wifi 仍然无法识别。

命令输出rfkill list all


1: phy2: Wireless LAN
    Soft blocked: no
    Hard blocked: no

如果您需要我的 USB Wifi 适配器信息,这里是输出lsusb


Bus 001 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey]

输出service NetworkManager status

● NetworkManager.service - Network Manager
     Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-02-27 08:22:50 CST; 1 day 6h ago
       Docs: man:NetworkManager(8)
   Main PID: 1010 (NetworkManager)
      Tasks: 3 (limit: 37395)
     Memory: 13.0M
        CPU: 6.228s
     CGroup: /system.slice/NetworkManager.service
             └─1010 /usr/sbin/NetworkManager --no-daemon

Feb 28 13:29:45 zeta NetworkManager[1010]: <info>  [1677612585.5108] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Feb 28 13:29:45 zeta NetworkManager[1010]: <info>  [1677612585.5109] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Feb 28 13:29:45 zeta NetworkManager[1010]: <info>  [1677612585.5110] device (tun0): Activation: successful, device activated.
Feb 28 13:31:37 zeta NetworkManager[1010]: <info>  [1677612697.3712] dhcp4 (wlx0013eff6b9c8): state changed new lease, address=192.168.106.106
Feb 28 14:01:37 zeta NetworkManager[1010]: <info>  [1677614497.3558] dhcp4 (wlx0013eff6b9c8): state changed new lease, address=192.168.106.106
Feb 28 14:31:37 zeta NetworkManager[1010]: <info>  [1677616297.3574] dhcp4 (wlx0013eff6b9c8): state changed new lease, address=192.168.106.106
Feb 28 15:01:37 zeta NetworkManager[1010]: <info>  [1677618097.3556] dhcp4 (wlx0013eff6b9c8): state changed new lease, address=192.168.106.106
Feb 28 15:07:00 zeta NetworkManager[1010]: <info>  [1677618420.6335] manager: NetworkManager state is now CONNECTED_SITE
Feb 28 15:07:01 zeta NetworkManager[1010]: <info>  [1677618421.0782] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 28 15:10:06 zeta NetworkManager[1010]: <info>  [1677618606.4966] agent-manager: agent[712460a0b443d1cb,:1.95/org.gnome.Shell.NetworkAgent/1000]: agent registered
~

输出ip route


ip route
default via 192.168.106.1 dev wlx0013eff6b9c8 proto dhcp metric 600 
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
192.168.106.0/24 dev wlx0013eff6b9c8 proto kernel scope link src 192.168.106.106 metric 600 

输出ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp12s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 74:56:3c:43:0c:15 brd ff:ff:ff:ff:ff:ff
3: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
5: wlx0013eff6b9c8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 00:13:ef:f6:b9:c8 brd ff:ff:ff:ff:ff:ff

输出sudo dmesg | grep mt76

[49391.166058] Modules linked in: xt_addrtype xt_nat nft_masq bridge stp llc nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nvidia_uvm(PO) ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_multiport xt_cgroup xt_mark xt_owner xt_tcpudp nft_compat nf_tables libcrc32c nfnetlink binder_linux joydev input_leds nvidia_drm(PO) snd_hda_codec_realtek binfmt_misc snd_hda_codec_generic nvidia_modeset(PO) ledtrig_audio snd_hda_codec_hdmi intel_rapl_msr snd_hda_intel intel_rapl_common amdgpu nvidia(PO) nls_iso8859_1 snd_intel_dspcfg snd_usb_audio snd_intel_sdw_acpi snd_hda_codec snd_usbmidi_lib snd_hda_core iommu_v2 mc snd_hwdep gpu_sched mt7921e snd_pcm drm_ttm_helper mt7921_common ttm snd_seq_midi drm_display_helper mt76_connac_lib snd_seq_midi_event edac_mce_amd cec mt76 snd_rawmidi kvm_amd 88x2bu(OE) rc_core snd_seq mac80211 drm_kms_helper snd_seq_device kvm i2c_algo_bit snd_timer fb_sys_fops crct10dif_pclmul syscopyarea snd ghash_clmulni_intel sysfillrect cfg80211 libarc4

关于如何进一步调查这个问题,我有什么想法吗?

答案1

解决方案:问题不在于 Ubuntu,而在于我的电源管理/主板!

启动时,BIOS 会给我各种错误消息,但我今天决定特别调查其中一条(因为我不记得确切的错误,所以进行了总结):

“USB 设备不接受地址”

最终,在启动时,甚至连我的 USB 无线适配器都无法工作。因此,我在 Google 上搜索了该错误,并找到了一个非常简单的指南,其中说原因很可能是硬件故障。我关闭了计算机,拔下了所有 USB 设备,关闭电源开关并拔下电源,然后等待了 2 分钟。然后我重新打开计算机并重新插入所有设备,然后它就正常工作了!

我将保留所有初始故障排除,以便作为文档/标签,以防其他人将来遇到此问题。

相关内容