Kernel update boots to system with no wifi, rollback advice sought

[Taipan]

I’ve tried to find recent threads with the same issue, assuming I’m not alone in this experience, and found nothing that helped, so apologies if I’m duplicating existing content…

Today, ‘Discover’ (which I only use for notifications) prompted me that updates were available, so I ran ‘zypper dup’, which included a kernel update. After rebooting, I found I had no wifi. Rebooting again into the older kernel available in Grub’s advanced options restored the wifi, so it would seem the settings haven’t been changed, just the drivers.

It looks like the kernel went from 6.13.8-1 to 6.14.0-1.

My reason for posting is to ask how I roll my system back to this previous kernel as default, as I’m concerned that the next update will leave me with the non-working 6.14 as the fallback and remove the working 6.13 completely. I’m afraid I’m not finding ‘snapper’ or ‘YaST2-snapper’ terribly intuitive, even with online documentation.

Alternatively, a known fix for my 6.14.0-1 wifi problem would also be appreciated, if available.

If further system information is required for better diagnostics, please feel free to ask…

[Silancu]

In Yast you can set the default initialization kernel, in the boot options, and you can choose which kernels to keep in zypp.conf. I don’t know if that answers your question.

https://en.opensuse.org/SDB:Keep_multiple_kernel_versions

[Taipan]

Thanks, those 2 suggestions look like they’ll keep me connected through the next kernel update - I’ll see if the issue persists at that point, and if it does, just carry on using what works.

[fkrueger]

Could you please open a bug report? This issue might be related to 219967 – Wifi not been detected in kernel version 6.14..