TW doesn't boot in dual boot system

English Install/Boot/Login
1

Hello,
I installed Tumbleweed yesterday on my laptop, the OS doesn’t boot by itself instead the windows install takes over, I have changed the boot order on the bios and tried booting into it manually however it takes me to the laptop’s diagnostic tool. Secure Boot is disabled. I am able to boot into it normally using a usb with the supergrub2 utility it finds the os and I boot into it normally there. I tried using the Yast Boot Loader utility, but it doesn’t fix the problem.

I didn’t partition the drive myself during installation so I assume that’s what causing the problem, not quite sure if I need to reinstall considering I can use the system otherwise.

This is the parted -l output.

Model: KINGSTON SNVS1000G (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  106MB   105MB   fat32           EFI system partition          boot, esp, no_automount
 2      106MB   123MB   16.8MB                  Microsoft reserved partition  msftres, no_automount
 3      123MB   499GB   498GB   ntfs            Basic data partition          msftdata
 4      499GB   499GB   805MB   ntfs                                          hidden, diag, no_automount
 5      499GB   998GB   499GB   btrfs
 6      998GB   1000GB  2148MB  linux-swap(v1)                                swap

efibootmgr output

BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0000,0004,0005
Boot0000* opensuse      HD(1,GPT,559ef791-d469-43a3-bff5-a38163db1ea9,0x800,0x32000)/File(\EFI\opensuse\grubx64.efi)
Boot0003* Windows Boot Manager  HD(1,GPT,4dcbb5d2-5522-4054-8f8e-b9c07a2b22ae,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000031000100000010000000040000007fff0400
Boot0004* UEFI: KINGSTON SNVS1000G, Partition 1 HD(1,GPT,4dcbb5d2-5522-4054-8f8e-b9c07a2b22ae,0x800,0x32000)/File(\EFI\Boot\BootX64.efi)0000424f
2

What does it mean?

Anyway, show

lsblk -f -o +partuuid
3

It means if I don’t go into the boot menu it just boots into windows normally.

lsblk -f -o +partuuid output

nvme0n1
│                                                                                       
├─nvme0n1p1
│    vfat   FAT32       D63C-9A26                                64M    33% /boot/efi   4dcbb5d2-5522-4054-8f8e-b9c07a2b22ae
├─nvme0n1p2
│                                                                                       dd94aef5-a9e4-428f-a7f6-567fa5fbba5d
├─nvme0n1p3
│    ntfs               7ACE3EB4CE3E6911                                                973bb9ec-de7d-4ea4-9fe9-54998a84ae93
├─nvme0n1p4
│    ntfs               C23ECDF93ECDE68F                                                498e9405-ed13-4c91-af6d-123444ba095e
├─nvme0n1p5
│    btrfs              5728cc89-a5db-49fe-aff9-cf1aa7cceb86  354.8G    23% /var        0322dd84-68bc-4f80-8e68-d85c450b0770
│                                                                           /usr/local  
│                                                                           /srv        
│                                                                           /root       
│                                                                           /opt        
│                                                                           /home       
│                                                                           /boot/grub2/x86_64-efi 
│                                                                           /.snapshots 
│                                                                           /boot/grub2/i386-pc 
│                                                                           /           
└─nvme0n1p6
     swap   1           4d8c6784-796f-47ad-9035-d0f00740b51f                [SWAP]      19e53850-7eb8-47b5-b764-920d6ac9c6a8
4

That’s not how you post command output. You copy and paste the complete command invocation and full output including both shell prompts. Only this way can we be reasonably sure that nothing is missing.

This partition does not exist so this boot entry is ignored. I do not know where it comes from. Run

update-bootloader --reinit

and post efibootmgr output again.

5

I apologize I didn’t know

here’s the efibootmgr output

Milky@localhost:~> sudo efibootmgr
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0000,0004,0005
Boot0000* opensuse      HD(1,GPT,4dcbb5d2-5522-4054-8f8e-b9c07a2b22ae,0x800,0x32000)/File(\EFI\opensuse\grubx64.efi)
Boot0003* Windows Boot Manager  HD(1,GPT,4dcbb5d2-5522-4054-8f8e-b9c07a2b22ae,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000031000100000010000000040000007fff0400
Boot0004* UEFI: KINGSTON SNVS1000G, Partition 1 HD(1,GPT,4dcbb5d2-5522-4054-8f8e-b9c07a2b22ae,0x800,0x32000)/File(\EFI\Boot\BootX64.efi)0000424f
Boot0005* UEFI: KingstonDataTraveler 3.0PMAP, Partition 2       PciRoot(0x0)/Pci(0x14,0x0)/USB(17,0)/HD(2,MBR,0xc1392872,0x7376000,0x10000)0000424f
6

So, does it boot now?

7

No it doesn’t boot.

8

And what happens? What exactly do you see after power on ? I am sorry, it is impossible to troubleshoot a problem when the only information is “no, it does not work”.

Again - what exactly does it mean? Where did you disable it?

9

I am sorry I’m probably making things harder than they should be, I appreciate the time you have taken to try and help me.

I disabled Secure Boot via the Bios Setup Menu.

Whenever I turn on my PC, it boots into Windows automatically. Unless I press the f12 key to open the Bios boot menu. The way I worked around the system not booting was, through choosing a usb that has ventoy and super-grub2, which detects os’ and lets you boot off the grub entries it finds.

This hasn’t happened before when I used other distributions. I decided to try and install from zero again, I will update if the boot loader problem happens again. This is my third time trying so I don’t think a clean install will work.

10

Which sounds like your BIOS ignores anything that is not Windows. There were reports of such systems.

11

It personally only has happened to me with OpenSUSE, other distributions it just goes directly into grub on power on.

12

Did you install openSUSE via Ventoy?

13

Yes. Should I try flashing the installer on a USB instead then?

14

Ventoy is known to render systems broken as it adds arbitrary boot parameters. Don’t use it with openSUSE.
https://en.opensuse.org/Create_installation_USB_stick#Ventoy

15

After reinstalling with another USB I flashed with rufus, my system now won’t boot it goes into grub rescue. Now windows does not work either.

16

Is it really rescue or just regular CLI? Post photo of this screen.

17

When booted it said
Error: unknown file system
And then it said grub rescue

I appreciate the help, however I have given up at this point. I’m not a very technical user. I would like to thank you guys for your time and once again I apologize for making things harder.

18

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