@Gps2010 When you boot to Tumbleweed, fire up YaST bootloader and make sure the nvram setting is unchecked, make sure the probe foreign os is unchecked and then go and change that distributor variable in /etc/default/grub to opensuse-tumbleweed, run that grub2-mkconfig command to make sure it’s easier to identify where/which of the three ESP’s it using…
Or you can look at swapping from using the Leap one to the Tumbleweed one, but you would need to boot to Leap and change there instead. But since we know Leap is working, might be better to stick with that one.
All of the above info is in the previous posts, so re-read, check your commands etc, make notes! Good Luck!!!
Each of those were intended to constitute templates showing different syntax from what malcolmlewis suggested. If I had noticed in time, I would have edited it shorter (removed the second). I’m surprised I had written in my notes that it had worked at the time (6 years ago).
I don’t boot Windows unless I’ve disconnected the ethernet cable first, unless I have 10 or 20 hours or 30 to spend waiting for it to update, undo, update, undo, update, undo until it gives up.
There is still a problem left, but I am happy I can boot Tumbleweed through leap.
Last nite tried to boot tumbleweed, from the mobo boot menu.
Then all I got, was that I had to insert a bootable device.
Gonna google and maybe go to an Asrock forum.
See if there is a way to clean up, because I think that were the , no room left message, comes from.
Maybe there is something like reg cleaner for uefi
sudo efibootmgr -b # -B, where # is the boot entry you wish removed from BIOS, determined from simply running sudo efibootmgr. If there is no entry in that output for TW, then your job fixing TW remains unfinished. Next new kernel installed in TW will very likely cause trouble if you don’t get this fixed, and understand, first, or disable TW’s boot management entirely (select not managed in TW’s YaST), so that booting TW from Leap will remain viable.
verify ESP is correctly mounting via /etc/fstab to /boot/efi/
delete directory /boot/efi/EFI/opensuse
assign a unique string to GRUB_DISTRIBUTOR= in /etc/default/grub
use YaST Bootloader to reconfigure its Grub
#6 will should a new NVRAM entry for UEFI BIOS to offer booting from, and a new ESP directory equal to your unique string, containing the file(s) that the BBS menu entry for TW will boot from. Depending what YB already shows, you might not need to make any changes. You do want it to write to NVRAM, so need that box checked if it isn’t already. However if you do not change anything, YB won’t have reason write to disk. So if necessary, change its timeout value to anything other than its current value, then save/exit YB. You might consider for timeout a much larger number, to give you more time to think about what you’re looking at when the Grub menu is onscreen and haven’t touched the keyboard to stop the countdown. Longer timeout value can be helpful in a multiboot environment.
Quick reply, my mobo and opensuse(grub) are set to 8 seconds.
So my mobo first shows for 8 seconds 4 keys to hit for boot menu or enter UEFI
Then Grub gives me 8 seconds, to choose something else then the default.
What got me in trouble probably, was on the first page of YB, check that second box.
The one below the NVRAM box. I changed something.
That YAST bootloader is awesome and beyond dangerous for people like me.
One wrong click and the ■■■■ hits the fan.
Delete Boot0011* sounds interesting.
Mobo boot menu shows samsung ssd, and this is the tumbleweed disk.
So your probably right about my mobo seeing the disk. (but is not able to boot from it)
