Not quite sure when it went tits up, but sometime in the last week. Wifi is fortunately only a backup and was working fine last weekend. It always hit kwallet to get the password for the link to the router, but currently if I try and access the ‘Previously used’ connection in Wifi & networking then it asks for the kwallet password, but connect is not active.
lspci -nnk is listing the ‘MT7922 802.11ax PCI Express Wireless Network Adapter’ and I am sure that it’s not been switched off in the bios. I’ve even flashed the latest BIOS for the motherboard as a problem with wifi was listed in the bios history - B550M PRO-VDH WIFI - which screwed the boot loader, but is now working again.
What can I kick next to try and switch it on, can I roll back to an previous kernel from 6.18.9-1-default (64-bit) 6.18.8 is giving the same problem 
As start, post the output of
sudo rfkill
Nothing what so ever 
It also runs happily without the sudo
What I have spotted is that lspci -nnk shows that neither mt7921e or wl kernel modules are in use.
Why not showing us?
wl is also the wrong Module for that Chip.
29: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]
Kernel modules: mt7921e, wl
Wired is working fine ...
2a:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7c95]
Kernel driver in use: r8168
Kernel modules: r8169, r8168
Edit by Sauerland
Use Code-Tags
So post:
zypper se -si broadcom r8168 kmp
Use Code-Tags as decribed here:
Code-Tags
lester@desktop:~/Videos/Raw> sudo zypper se -si broadcom r8168 kmp
[sudo] password for root:
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-------------------------------+---------+---------------------------------------+--------+------------------
i+ | broadcom-wl-kmp-default | package | 6.30.223.271_k6.18.9_1-1699.27.pm.133 | x86_64 | (System Packages)
i+ | broadcom-wl-ueficert | package | 6.30.223.271-1699.27.pm.133 | x86_64 | (System Packages)
i+ | nvidia-driver-G06-kmp-default | package | 580.126.09_k6.18.4_1-44.2 | x86_64 | NVIDIA
i+ | nvidia-driver-G06-kmp-default | package | 580.126.09_k6.18.4_1-44.2 | x86_64 | repo-non-free
i+ | r8168-blacklist-r8169 | package | 8.053.00-1699.2.pm.322 | x86_64 | (System Packages)
i+ | r8168-kmp-default | package | 8.053.00_k6.18.9_1-1699.2.pm.322 | x86_64 | (System Packages)
Which are the latest wired drivers … it’s the wireless one that is not being loaded , which is part of the core kernel?
These are for Broadcom Wlan Chips.
So if you don’t own such a Chip, delete them and lock them.
Why have you disabled or autorefresh disabled the Packman Repo?
Post
zypper lr -d
Was using ‘Packman Essentials Repository’ but switched to ‘openSUSE_Tumbleweed | Packman Repository’ due to missing bits … not sure why it had been switched off again
lester@desktop:~/Videos/Raw> zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
---+----------------------------------------+-------------------------------+---------+-----------+---------+------+----------+--------+---------------------------------------------------------------------------------+---------
1 | Application:Geo | Application:Geo | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/Application:/Geo/openSUSE_Tumbleweed |
2 | NVIDIA | NVIDIA | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.nvidia.com/opensuse/tumbleweed |
3 | NVIDIA:repo-non-free | repo-non-free | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.nvidia.com/opensuse/tumbleweed | NVIDIA
4 | PlexRepo | PlexRepo | No | ---- | ---- | - | 99 | N/A | https://downloads.plex.tv/repo/rpm/x86_64/ |
5 | code | Visual Studio Code | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://packages.microsoft.com/yumrepos/vscode |
6 | ftp.gwdg.de-Essentials | Packman Essentials Repository | No | ---- | ---- | - | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials |
7 | ftp.gwdg.de-openSUSE_Tumbleweed | Packman Repository | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ |
8 | openSUSE:repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss | openSUSE
9 | openSUSE:repo-openh264 | repo-openh264 | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://codecs.opensuse.org/openh264/openSUSE_Tumbleweed | openSUSE
10 | openSUSE:repo-oss | repo-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss | openSUSE
11 | openSUSE:repo-oss-debug | repo-oss-debug | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/debug/tumbleweed/repo/oss | openSUSE
12 | openSUSE:repo-oss-source | repo-oss-source | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/source/tumbleweed/repo/oss | openSUSE
13 | openSUSE:update-tumbleweed | update-tumbleweed | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/update/tumbleweed | openSUSE
14 | opensuse-guide.org-openSUSE_Tumbleweed | libdvdcss repository | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/
Have deleted the broadcom modules and just rebooting again. One niggle is that startup is a lot slower than it used to be … I’m sitting waiting for some time before will display any activity …
lester@desktop:~/Videos/Raw> sudo zypper se -si broadcom r8168 kmp
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-------------------------------+---------+----------------------------------+--------+-------------------
i+ | nvidia-driver-G06-kmp-default | package | 580.126.09_k6.18.4_1-44.2 | x86_64 | NVIDIA
i+ | nvidia-driver-G06-kmp-default | package | 580.126.09_k6.18.4_1-44.2 | x86_64 | repo-non-free
i+ | r8168-blacklist-r8169 | package | 8.053.00-1699.2.pm.322 | x86_64 | Packman Repository
i+ | r8168-kmp-default | package | 8.053.00_k6.18.9_1-1699.2.pm.322 | x86_64 | Packman Repository
lester@desktop:~/Videos/Raw>
OK the real question perhaps is just when in the boot process should the mt7921e driver be loaded and what would prevent it from being loaded?
Post:
journalctl -b | grep -Ei 'error|wlan|mt79|network|firmw'
Lots of stuff but filtering down …
lester@desktop:~> sudo journalctl -b | grep -Ei 'mt79'
Feb 14 19:36:24 desktop.rdm1.uk kernel: mt7921e 0000:29:00.0: enabling device (0000 -> 0002)
Feb 14 19:36:25 desktop.rdm1.uk kernel: mt7921e 0000:29:00.0: driver own failed
Feb 14 19:36:25 desktop.rdm1.uk kernel: mt7921e 0000:29:00.0: probe with driver mt7921e failed with error -5
The files for mt7921e seem to be updated and have times from yesterdays reboot but also ‘3 minutes ago’ is showing currently.
/usr/src/linux-6.18.9-1-obj/x86_64/default/include/config/MT7921E has a date of 06/02/2026 but is empty and 6.18.8-1 is dated 30/1/2026