Fedora 37 wifi issue

Ask Fedora
1

Hello

I recently upgraded to 37 and my wifi is not working anymore, but bluetooth is :confused:

inxi -N                       
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: N/A
  Device-3: Realtek RTL8125 2.5GbE driver: r8169


mcli con show
NAME                UUID                                  TYPE      DEVICE  
Wired connection 2  8d255bf6-8515-3418-93aa-f9c4790edb44  ethernet  enp8s0  
docker0             65922ce8-a511-410b-9bca-1010128691e9  bridge    docker0 
Wired connection 1  8ce194f2-ac27-3d88-bae3-b9747242846b  ethernet  --      

nmcli radio wifi
enabled

It doesn’t show ip in settings.
Any ideas on how to fix it?

2

No driver loads → not configured → can’t use. Device 2 of the inxi -N shows that.

The output of inxi -SNExxxy and the applicable part of lspci -nnv will give us info about the wifi adapter and possibly allow us to assist in getting the proper driver to load so the adapter will be functional. rfkill will also provide some info.

3 
inxi -SNExxxy
System:
  Host: fedora Kernel: 6.0.12-300.fc37.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 2.38-25.fc37 Desktop: GNOME v: 43.2 tk: GTK v: 3.24.35
    wm: gnome-shell dm: GDM v: 43.0 Distro: Fedora release 37 (Thirty Seven)
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: N/A pcie: speed: 5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 14c3:0616
    class-ID: 0280
  Device-3: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: c000 bus-ID: 08:00.0 chip-ID: 10ec:8125
    class-ID: 0200
Bluetooth:
  Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 3-12:2 chip-ID: 0e8d:0616 class-ID: e001 serial: 000000000
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends

lspci -nnv

07:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]
	Subsystem: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]
	Flags: fast devsel, IRQ 37, IOMMU group 1
	Memory at fcf0300000 (64-bit, prefetchable) [size=1M]
	Memory at 80200000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: <access denied>
	Kernel modules: mt7921e

rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
4

Linux hardware shows several hits with fedora 37 where that adapter works.

That does appear to be a newer adapter so this may be either a firmware or driver level error.

You might try a new boot then run dmesg and peruse the output to see if there are any lines with failed that might give a hint. dmesg | grep ailed would be a start. Once you see the time for that then take a deeper look at the dmesg output to see if you can pick out the surrounding or preceding entries that might help.

You also could do the same with journalctl -b 0 | grep ailed to get hints from there and dig deeper once you have a time span where the entries occurred.

I notice that the inxi output shows no driver but the lspci output shows the kernel module as mt7921e

To get more detail with the Capabilities from lspci repeat that command with sudo.

5

this is the MB i have MediaTek MT7922 802.11ax PCI Express Wireless Network Adapter

sudo dmesg | grep ailed
[    0.698827] hub 10-0:1.0: config failed, hub doesn't have any ports! (err -19)
[    3.229968] systemd[1]: memstrack.service - Memstrack Anylazing Service was skipped because all trigger condition checks failed.
[    5.651996] systemd-gpt-auto-generator[844]: Failed to dissect: Permission denied
[    5.659993] systemd[829]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1.
[    5.789045] systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of a failed condition check (ConditionPathExists=!/run/plymouth/pid).
[    5.813770] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
[    5.856039] systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because all trigger condition checks failed.
[    7.039008] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    7.809436] mt7921e 0000:07:00.0: driver own failed
[    7.809468] mt7921e: probe of 0000:07:00.0 failed with error -5

journalctl -b 0 | grep ailed
Dec 14 12:48:06 fedora kernel: mt7921e 0000:07:00.0: driver own failed
Dec 14 12:48:06 fedora kernel: mt7921e: probe of 0000:07:00.0 failed with error -5

If it helps i did a HW Probe HW probe of ASRock X670E Steel Legend Desktop Computer #fec86201de

1 Like
6

Did you look at either dmesg or journalctl output surrounding or preceding those entries to see what other information may be available.?

Those commands were intended to give you a starting point to use for locating any additional info that may have been logged.

Since the driver did not load properly it is necessary to find out why.