Tumblweed booting up is completely random, please help

Hello, I am new to OpenSUSE. I have been using debian on my laptop for a few years but wanted to try linux on my desktop (dual-boot win10 & tumblweed).

When I turn on my pc, the boot manager opens fine, but is extremly weird with like a hundred opensuse options and no windows. when I try to boot into opensuse it will either boot up or give some sort of error and then proceed to boot into windows. It has done that from the beginning for some weeks and I have almost lost all hope trying to fix it. Only thing I can think of is that NVIDIA bad as the graphics drivers are also kinda broken.

The error:
…/src/boot/boot.c:3044@call_image_start: Error preparing initrd: Device error
start_image() returned Device Error

PC specs:
cpu- Ryzen 9 5900x
gpu- GTX 1080
mb- msi B350 PC MATE
16gb ddr4 ram

WIN10 is on a nvme drive and Tumbleweed is on a sata ssd.

systemd-boot won’t pick up a windows install with an efi partition that’s on another drive unless you mess around with the EFI data manually (which I wouldn’t recommend). Not sure about your other errors.

A picture of what you’re seeing might be helpful here. What you’re possibly seeing with the multiple openSUSE options is different snapshots (a feature of the btrfs filesystem that lets you revert to an earlier installation if an update has issues), so the first option on the list should be the correct one.

How did you perform the installation - which media did you boot from during the installation? That also may be helpful to know.

I have a systemd-boot with two efi partitions (same disk) it works fine, MacOS though…

On the same EFI, it’s fine. I think systemd-boot looks for a Microsoft/ folder inside the partition that the bootloader runs from.

For windows I had to copy the Microsoft/ directory to the same EFI partition that systemd-boot was installed to, and then it worked fine. But considering I have issues with Bitlocker/TPM when booting Windows from a bootloader, I tend to not use it anymore. (I think systemd-boot actually has a workaround for this now but I don’t boot into Windows often enough to check).

I installed from a usb with the dvd installastion.
I have also re-installed it one time because on the original install windows was on legacy. I taught that might have been the problem, so I converted windows to UEFI and after that re-installed suse.

Used rufus for the usb stick, if that matters at all.

I added the boot manager picture to this comment, as it seems I can no longer edit the original post? I think you are right about the different snapshots. I just taught that it was weird that there were so many of them.

OK, yeah, you’ve got multiple snapshots showing there, and three different kernels (the display shows 1@7.2.2-1-default (second row) for example, that’s snapshot 1, kernel 7.2.2-1-default.

The ones that are prefixed with “Snapper:” are snapshots you can roll back to. You may want to read up on the use of snapper snapshots for system recovery - the wiki and documentation are a good starting place for that info.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.