WiFi regression
I don't know if it's because of the most recent update or the previous one (I'm on the 5/5 image currently), but if I go to the most recent image, I lose access to the WiFi card (Mediatek MT7921)... what could be the culprit?
8 Replies
Looks like there is a very recent kernal regression for the Mediatek MT7921
https://lkml.org/lkml/2024/5/3/142
Looks like my Bazzite which I last updated this afternoon is running on kernal 6.8.9-301.fsync.fc40.x86_64 (
uname -r to see this info) and and you'll need to rollback to a Bazzite image that is using 6.6 or olderI have a laptop MSI Alpha 15 B5EEK with MT7921K (RZ608) Wi-Fi 6E 80MHz and I also I have problems with today's update:
ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:fc9a28cea12e89a10249afaaaac8f27f6ecfd838da1290019c8bd0ac3a62cb99
Version: 40.20240507.0 (2024-05-08T06:24:32Z)
Diff: 8 upgraded, 137 removed, 5 added
On this version works fine (I just rolled back to it):
ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:a3c96660a002f8cdde298e362cd1b86f5c94c93361f81b825f7a6ea55e0452fe
Version: 40.20240507.0 (2024-05-07T20:33:00Z)
Edit: kernel on the working version is 6.8.9-301.fsync.fc40.x86_64
The problem isn't on the kernel or something because that kernel is indeed working... something in the update (in this case, the two most recent ones) is borking the wifi
Upgraded:
btrfs-progs 6.8-1.fc40 -> 6.8.1-1.fc40
gamescope 100.3.14.12-1.bazzite -> 100.3.14.13-1.bazzite
gamescope-libs 100.3.14.12-1.bazzite -> 100.3.14.13-1.bazzite
gamescope-libs 100.3.14.12-1.bazzite -> 100.3.14.13-1.bazzite
joystickwake 0.0.git.64.28b95b26-1.fc40 -> 0.0.git.66.ed9be9bd-1.fc40
kwin 6.0.4.1-1.fc40 -> 6.0.4.1-2.fc40
kwin-common 6.0.4.1-1.fc40 -> 6.0.4.1-2.fc40
kwin-libs 6.0.4.1-1.fc40 -> 6.0.4.1-2.fc40
kwin-wayland 6.0.4.1-1.fc40 -> 6.0.4.1-2.fc40
libbsd 0.12.2-1.fc40 -> 0.12.2-3.fc40
ptyxis 0.0.git.49.2fa8401d-1.fc40 -> 0.0.git.102.34381369-1.fc40
python-pyqt6-rpm-macros 6.7.0-0.1^dev2404051544.fc40 -> 6.7.0-1.fc40
python3-pydantic 2.6.4-1.fc40 -> 2.7.1-1.fc40
python3-pydantic+email 2.6.4-1.fc40 -> 2.7.1-1.fc40
python3-pydantic-core 2.16.3-1.fc40 -> 2.18.2-1.fc40
python3-pyqt6 6.7.0-0.1^dev2404051544.fc40 -> 6.7.0-1.fc40
python3-pyqt6-base 6.7.0-0.1^dev2404051544.fc40 -> 6.7.0-1.fc40
vte-profile 0.76.0-4.fc40.prompt -> 0.76.1-4.fc40.ptyxis
vte291 0.76.0-4.fc40.prompt -> 0.76.1-4.fc40.ptyxis
vte291-gtk4 0.76.0-4.fc40.prompt -> 0.76.1-4.fc40.ptyxis
Removed:
libblkid-2.40-13.fc40.i686
libmount-2.40-13.fc40.i686
libuuid-2.40-13.fc40.i686
Added:
bootc-0.1.10-1.fc40.x86_64
bootupd-0.2.18-2.fc40.x86_64
libblkid-2.40.1-1.fc40.i686
libmount-2.40.1-1.fc40.i686
libuuid-2.40.1-1.fc40.i686Glad that you came right :).
I had to revert to the May 5th image because the new one is a bust... but I know that an update will come sooner rather than later - the beauty of an atomic system
Yeah just being able to jump back anywhere is really amazing.
Solution
New update solves the issue
Sweet! 🙂