Hopped distros to Tumbleweed at the start of the month with a new install. My setup is a dual boot with a drive for Win11 and a drive for Tumbleweed. I had Tumbleweed as first boot option, and windows was way down the list. I also installed Tumbleweed with secure boot enabled. Everything was running as expected for weeks, until I did a bios update a few days ago to get some CPU features on my motherboard.
After the update, secure boot is still enabled, but it changed the boot order to put windows first. I had to change opensuse bootloader to be #1 again, but there was also another entry for some kind of opensuse rescue (I’ll go into bios and update with the actual names after a reboot. Anyways, now when I boot, I don’t see the systemd or snapper menus anymore. It just sends me right into Plasma. If I open the Yast Snapper program, it looks like snapper is still making new entries, I just don’t see any choice to load them at boot.
Where should I go from here? I saw a similar situation on the EndeavorOS forums and it was resolved by bootctl install, but I don’t just want to throw around terminal commands I shouldn’t be. Thanks much!
Thanks for the reply I had to change the boot order after the update, but thankfully fastboot and SecureBoot stayed on the same settings they were pre-update.
The BIOS update made windows the default bootloader and I had to switch back to Tumbleweed bootloader, but now I don’t get the pre-desktop environment screen anymore.
That is why i wrote to check the settings regarding boot behaviour. There are (dependend of the BIOS/motherboard manufacturer ) additional settings which speed up the boot process. Not only fast boot. Sometimes you have additional options to not initialize hardware which may speed up the start process.
What does that mean? Do you still have the SDDM login screen or does your system login you now automatically?
If you now have autologin, it is no BIOS issue. You can disable autologin via
systemsettings->SDDM->Behaviour
If you are saying that you are not seeing the boot options for Windows & openSuse etc. then I think you might need to hit the space bar on boot up and increase the timeout to your desired time like 10 or 15 seconds as the reset may have defaulted it to zero.
See this previous thread on here where that was the solution to a similar problem - if this is your problem?
I had to change the boot order after the update, but thankfully fastboot and SecureBoot stayed on the same settings they were pre-update.