A new install of tumbleweed 7-July-2027 produces the enclosed error and I do not know what it is refering.
Assuming that I’m reading that correctly (and that is a terribly worded error message), you need to go into the software selection, and manually select sdbootutil to be included.
But that shouldn’t happen. You need to file a bug.
1 Like
Thanks. Just to confirm this is Tubleweed, sha256 5f91ae541eaf9fc581c8ab924ff8fd7ef2af0368e442c7ebb702020ba84bab4b
I noticed when I downloaded that the i686 only had a hash for i586.
Do you use the 32bit ISO?
yes, i686 was downloaded
There are only i585 ISOs. Where did you find the i686 ones?
It says in the description, “Intel or AMD 32-bit desktops, laptops, and servers (i686)” from https://get.opensuse.org/tumbleweed/
Ah, seems like a typo. All 32bit ISOs have i565 in the name and that is also why the checksums are for i586.
ok. a bug and a typo.
@compis no bug, not supported… there is no 32bit version of sdbootutil, AFAIK you need to use grub2.
1 Like
Then it is absolutely is a bug as Opensuse provides the i586 software to install but it will not install asking for sdbootutil.
@compis No, no bug, 32bit is a happy go lucky creature and not supported (well application runtime support)… systemd-boot is the default, you need to modify your install.
Edit, You used these ones https://download.opensuse.org/ports/i586/tumbleweed/iso/
I am trying this version for the first time and do not understand how the i586 version that Opensuse has advertised on your main web site is not supported? Shouldn’t they remove the installation version? Why should someone trying what is on opensuse site search for what you provided ?
Is the SHA256 I provided correct if not what does it represent ?
Tumbleweed is targeted at developers and experienced users with some expectations on how it works and what it’s for.
I suspect a number of the product maintainers would be happy to let 32bit systems head off into the sunset… I don’t support or build any i586 versions of the applications I maintain…
Perhaps @mrmazda can help out here I think he has some 32bit setups… suffice to say, just select grub2 (if it still exists) and should install fine.
Thats fine but if it is not supported remove it from the the main web site.
1 Like
It is, just by yourself and other Community users who wish to keep it running/building…
Does the 32 bit version work?
I tried it and all I added was disk encryption everhing elses was standard and I got the installtion error.
grub2-2.14-14.1.i586.rpm dated 2 July is on the mirrors, but I don’t use it. All my 32bit TWs are on multiboot PCs booting from Grub Legacy, as are all but two 64bit on MBR PCs (>40). I have no idea what value sdbootutil could provide MBR or 32bit installations.
I see in OP the default systemd boot remains selected. Switching from it back to Grub 386 should dispose of the sdbootutil error message I should think. Seems like on the i586 port the default bootloader should not be any incarnation of BLS, systemd or otherwise.
Thanks. but I did a simple install taking all the defaults and I still got the error. I don’t think it works.
AFAICT, not working is expected. One cannot get Grub instead of Systemd Boot (which requires sdbootutil, while traditional Grub does not), using only defaults on 32bit. Systemd Boot is one of the defaults, even though for 32bit it doesn’t exist. IOW, the default bootloader selection, as i586 port installers ship, is defective. You need to change it from default to Grub. Then it should work just fine with all the remaining defaults.
1 Like