As of yesterdays system update my wifi on my laptop stopped working. I perfomed a rollback and wifi is working again, so no hardware issue. Is anyone else having wifi issues after the last aeon (or tumbleweed) update?
Problem is, I don’t have lan available, so only wifi that doesn’t work, so I can’t access this forum from within the broken snapshot. How to best proceed?
kernel 6.14.2 arrived in snapshot 20250414, likely something related to the iwlwifi driver there. Can you still boot kernel 6.14.1 from the last snapshot and check?
I had a similar issue with my LAN driver and it was related to the fact the new kernel-defaults (6.14.2-1-default) does not match the kernel used by the new snapshot (still 6.14.1-1). You can see the discrepancy by looking at the boot entries vs the kernel defaults installed in /usr/lib/modules and the logs in dmesg which says that it cannot find certain files in there.
I fixed it by doing the upgrade from the snapshot with a kernel different from the last working snapshot (the latter was running 6.14.1-1 while the previous snapshot was running 6.14.0-1).
And I suspect this user on Reddit came across the same issue.
It feels like your issue might be related to all that. I fixed my issue since then by reinstalling fresh.
Since I have a working system now I can’t test anything but I suspect it’s due to running “sudo transactional-update dup” which sounds stupid I know but it’s what people with broken systems have done in common so far. (Except the person who made the Bugzilla report I don’t know if they manually updated)
Try booting into the working snapshot and running “sudo systemctl start transactional-update.service”(While plugged into the charger) instead?
zypper se -s kernel-firmware-iwlwifi
S | Name | Type | Version | Arch | Repository
---+-------------------------+--------+--------------+--------+------------------------
i | kernel-firmware-iwlwifi | pakket | 20250312-1.1 | noarch | openSUSE-Tumbleweed-Oss
But as mentioned before I am now in
wim@linux:~> uname -srm
Linux 6.14.1-1-default x86_64
And can’t get a wifi working when using 6.14.2-1.1.x86_64, but I’m gonna recheck anyway. I’ll keep you posted.
@WimDeWinter But your booting into an older snapshot I suspect? Anyway I just ran into what I think is your issue. So as root user run sdbootutil -v add-all-kernels you will probably see some warnings, then reboot and you need to press the space bar to get to the systemd boot menu, look in the list for the 6.14.2 kernel, select that and boot.
@malcolmlewis Did what you asked. Here is some output:
So first, before reboot
wim@linux:~> uname -srm
Linux 6.14.1-1-default x86_64
wim@linux:~> zypper se -s kernel-firmware-iwlwifi
Bezig met ophalen van installatiebrongegevens…
Bezig met inlezen van geïnstalleerde pakketten…
S | Name | Type | Version | Arch | Repository
---+-------------------------+--------+--------------+--------+------------------------
i | kernel-firmware-iwlwifi | pakket | 20250312-1.1 | noarch | openSUSE-Tumbleweed-Oss
wim@linux:~> sudo sdbootutil -v add-all-kernels
[sudo] wachtwoord voor wim:
Installing all kernels
Found kernel 6.14.1-1-default = aa8e4476b4373f6ffc2398dfc011d08661c2c620
Found kernel 6.14.2-1-default = 2489b274b21bdf8f02dddf32f5fce9be4d9d8486
Installing kernel 6.14.1-1-default
Found existing initrd /aeon/6.14.1-1-default/initrd-dc1e495b38553560e8e42e57a04410d66add90ec
Required free space in ESP: 15172 KB
Reusing /boot/efi/aeon/6.14.1-1-default/linux-aa8e4476b4373f6ffc2398dfc011d08661c2c620
Installed /boot/efi/loader/entries/aeon-6.14.1-1-default-3.conf
Removing /boot/efi/loader/entries/aeon-6.14.1-1-default-3.conf.bak
Installing kernel 6.14.2-1-default
Generating new initrd
dracut-install: ERROR: installing 'grub2-editenv'
dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.d7MNaKi/initramfs -a date btrfs awk grub2-editenv
Required free space in ESP: 57208 KB
Installed /boot/efi/aeon/6.14.2-1-default/linux-2489b274b21bdf8f02dddf32f5fce9be4d9d8486
Installed /boot/efi/aeon/6.14.2-1-default/initrd-6cee5f2f053130e3708a62d7fa703328d522b402
Installed /boot/efi/loader/entries/aeon-6.14.2-1-default-3.conf
Loading config file /etc/sysconfig/fde-tools
Generating TPM2 predictions with systemd-pcrlock
Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
Generating TPM2 predictions with systemd-pcrlock (systemd-boot)
Garbage after device path end, ignoring.
NVIndex policy created
Then I reboot, press space, choose snapshot with 6.14.2-1, log in and I have a system with working wifi:
wim@linux:~> uname -srm
Linux 6.14.2-1-default x86_64
wim@linux:~> zypper se -s kernel-firmware-iwlwifi
Bezig met ophalen van installatiebrongegevens…
Bezig met inlezen van geïnstalleerde pakketten…
S | Name | Type | Version | Arch | Repository
---+-------------------------+--------+--------------+--------+------------------------
i | kernel-firmware-iwlwifi | pakket | 20250312-1.1 | noarch | openSUSE-Tumbleweed-Oss
@WimDeWinter Seems like the boot order didn’t change and kernels drivers not present in the linked location, you should be fine now going forward. However, not sure it can be duplicated for a bug report…
Did you by any chance boot windows just before? It seems that some network-cards don’t work during first boot after running windows. I am not sure why, but probably they are in a weird state or something when kernel loads, and it does not try again later. Restarting the (linux) system resets the mode of the card and it starts working.
, Aeon cannot be used in a multiboot setup, even if I would want it