Did anybody successfully create a bootable USB with "openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240105-Media.iso’?
I am pretty blank with Linux and follow the instructions as documented on the OpenSuse Installation page.
All such worked fine for Leap 15.5 using RUFUS on Windows 11.
Now i try to upgrade to Tumbleweed. I downloaded the ISO via Opera on W11. Etcher failed as always before, but RUFUS again saved the day and created a USB as DD image. But booting from such fails with a validation error for ‘shim SBAT data’.
So i tried the same on Leap 15.5, downloaded the ISO again this time via Firefox. I used ‘Image Burn’ for creation of a ISO USB. interestingly ‘Image Burn’ shows on top an SHA256 number, which is different from the string posted in the OpenSuse Installation page.
The resulting ISO USB failed to boot with same error message as experienced before with those USBs created via W11.
Is the provided ISO semi-optimal - or are all my USB sticks broken? If my USB sticks are broken, why does ‘Image Burn’ display a different SHA256 before writing?
Or would you all recommend staying with Leap coz it works? (I am into gaming, but my Hardware is a few years old.)
That’s a different issue. It is not related to the checksum.
To deal with this, you will need to disable secure-boot in your BIOS. After that, you should be able to boot the USB. This is due to an incompatibility between Leap and Tumbleweed. See bug 1209985 for more details.
Oooh! My Leap Installation is using Secure Boot. Does such still work even if Secure Boot is off in UEFI? Can i re-activate Secure Boot later again after Tumbleweed upgrade (I saw tick box options in the Setting of Leap - i love YaST.)
Btw: This Forum is pretty awesome. I found meanwhile how to check sha256sum myself and got via terminal, that the downloaded ISO is okay. Such indicates, that your suggestion really makes sense - i shall follow your hint.
Yes, Leap will still boot if secure-boot is disabled in your BIOS (or UEFI firmware). Toward the end of that bug report – mostly comment 52 – there is a guide as to how you can reset the SBAT level. I do not know how long we will have to wait for Tumbleweed to update shim to the latest level.
You can leave the secure-boot settings in the boot loader. It is the BIOS settings that matter here.
As I am a GUI driven gamer, those terminal based mystery lines are beyond me
Having done the upgrade to Tumbleweed without Secure Boot, the System still has Dual Boot and I can launch W11.
But Tumbleweed launches a Gnome like black screen, frozen without reaction to mouse nor keyboard. Reboots clarified, that the launch works on with Secure Boot off, but always ends with a black screen.
Lesson learned: Gamers should keep their hands off from Tumbleweed.
I will try to rebuild a Leap 15.5 Flashdisk again, the original has not been recognised, and will try to “upgrade” back to Leap 15.5 if possible. Otherwise two month work on Linux been lost … .
Thanks ‘nrickert’ and ‘arvidjaar’. Appreciated. This forum is great.
Meanwhile i have my Leap 15.5 back running with Secure Boot and TPM2.0. I tried first a rollback to the snapshot taken before the failed upgrade to Tumbleweed, did run into a “Welcome to GRUB!”, burned a Leap 15.5 Installation USB, upgraded from there, finally noticed that i had to change in the Boot-priorities of my UEFI the OpenSuse - SATA to OpenSuse SecureBoot - reinstalled the Gnome Extensions for my default user (non-root) - and Steam and games run fine.
Indeed lesson learned: Tumbleweed is a no-go for GUI driven gamers! How was the packaging not even been tested if it can be booted after an upgrade at all? If even that does not work, then hands off from a rolling Distro.
I love Leap, getting Mesa upgrades there. And will wait with a new Graphic Card until second half of next year, when Leap 15.6 will have had provided a more up to date kernel - and Cards will hopefully have become more affordable.
Anyway, may thanks to the Suse team for the great and free OpenSuse Leap - i really love that one.
It was a user error by you. Tumblewed has the same QA procedures as Leap.
If you want to upgrade from Leap to Tumbleweed it is recommended to do afresh install to have a clean setup (unless you are more than a GUI driven gamer and are able to use a command line to navigate around minor issues…).
BTW what is a “GUI driven gamer”? Purely text based games without graphics dissapeared decades ago
Tumbleweed and games are a good combination. No issues with Steam and wine and proprietary Nvidia drivers here…
Tried again, not giving up easily. This time I did the online installation for upgrading Leap to Tumbleweed as advised in the Suse Wiki.
That installation did finish nicely. Neofetch told me, that I am running Tumbleweed.
But: On reboot with Secure Boot active, it stopped again due to validation error and the PC turned off.
I turned Secure Boot off, launched again and got this time a MOK Management screen. Skipped that, got the boot menu, selected Tumbleweed, got again that Blank Gnome screen with frozen mouse and not reaction to keyboard. That screen turned itself off after a minute or two. Now I have a blank screen with an underscore blinking in the top left corner … same 10 min later … .
Bit off topic, but I’d recommend ventoy for ISO installations. You set it up once and you just copy any number of ISOs to the USB Stick as normal. Booting from that ventoy USB stick then presents you with a list of ISOs to choose from. Hasn’t failed for me yet and comes with a key file to import if you get secure boot warnings.
This is going to continue to happen if you turn secure-boot on.
There are several ways to avoid this.
You can reset the SBAT level, as described in the Wiki or in that bug report.
You can try booting with the Leap boot menu. But this may cause other problems if you have not first enrolled the needed MOK certificate. Also, you would need to update your grub menu in Leap whenever there is a kernel update in Tumbleweed.
You can wait for Tumbleweed to update “shim” to a new sbat level. But this might mean a wait of several months (or longer).
It will be easier to just leave secure-boot disabled for now.
As mentioned above, my terminal knowledge is not sufficient to run advanced commands ( I learned years ago, that such is a brilliant way to ruin an installation since the web is full of terminal command suggestions with unknown side effects, requirements or preconditions).
I skipped MOK Management because I had never heard about it before it popped up. A quick google did indicate that it may come from UEFI and wants to ‘seal’ the kernel. Since the MOK menu asked me for a key but I had no key defined in UEFI, proceeding with Key=0 did not seem to be logical to me. That’s why I used the ‘Continue’ option, which assumable skipped the key story.
Secure Boot Off is NOT an option since such does allow reaching the EFI menu, but booting Tumbleweed leads to the broken / frozen Gnome screen as mentioned above, shortly followed by the top left blink of death.
I shall now go straight back once more to Leap via USB ‘upgrade’. And I am very positively impressed that such a return to Leap is possible at all after having experienced a messy upgrade scenario.
Not to bad. I love the idea of a slowroll and just hope, that at the time of all users running an upgrade of Leap 15.5 to Leap 15.6 such may be properly tested and functional.
Just by curiousity: Will Leap 15.6 turn itself automatically into a Slowroll or will such need another Upgrade?
Again, thanks for all the feedback and suggestions here. Seriously appreciated.
Yes. That’s the positive lesson from this mess: Rollback to old distro version works well. But needs indeed two steps: Rollback Snapshot and afterwards upgrade from USB to get Secure Boot sorted.
I am just a bit concerned how full meanwhile my root partition has become. What would the best way for cleaning that up?
Sorted. I found in File Manager on Trash in Setting the option for deleting all temporary files. That brought my root disc down from 75% to 35% filled. All cool. Happy to keep going with Leap.
Happy to keep going with Leap. 