blue@localhost:~> ls -lR /boot/efi/EFI
/boot/efi/EFI:
total 8
drwxr-xr-x. 2 root root 4096 Mar 31 13:43 boot
drwxr-xr-x. 2 root root 4096 Mar 31 13:43 opensuse
/boot/efi/EFI/boot:
total 1872
-rwxr-xr-x. 1 root root 965528 Mar 31 13:43 bootx64.efi
-rwxr-xr-x. 1 root root 90496 Mar 31 13:43 fallback.efi
-rwxr-xr-x. 1 root root 852312 Mar 31 13:43 MokManager.efi
/boot/efi/EFI/opensuse:
total 4180
-rwxr-xr-x. 1 root root 58 Mar 31 13:43 boot.csv
-rwxr-xr-x. 1 root root 375 Mar 31 13:43 grub.cfg
-rwxr-xr-x. 1 root root 2111344 Mar 31 13:43 grub.efi
-rwxr-xr-x. 1 root root 335872 Mar 31 13:43 grubx64.efi
-rwxr-xr-x. 1 root root 852312 Mar 31 13:43 MokManager.efi
-rwxr-xr-x. 1 root root 965528 Mar 31 13:43 shim.efi
blue@localhost:
This should be bootable. Could you show from booted openSUSE and connect your Garuda disk:
lsblk -f -o +partuuid,parttype
lsblk -f -o +partuuid,parttype
blue@localhost:~> lsblk -f -o +partuuid,parttype
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID PARTTYPE
sda
├─sda1
│ vfat FAT32 9B7B-D390 1G 1% /boot/efi b32da5bc-3dac-43aa-990a-18cc46a761ec c12a7328-f81f-11d2-ba4b-00a0c93ec93b
├─sda2
│ btrfs 8408fb06-85c4-4992-ab01-02d9d27c8fe8 227.3G 3% /opt 7ef020c2-f816-470e-a9b6-f99f2190a5c2 0fc63daf-8483-4772-8e79-3d69d8477de4
│ /root
│ /srv
│ /usr/local
│ /var
│ /boot/grub2/x86_64-efi
│ /boot/grub2/i386-pc
│ /home
│ /.snapshots
│ /
└─sda3
swap 1 2053365b-dfba-42eb-acb4-c57f641b80c8 [SWAP] 42401a45-ade5-4689-9b89-74b3d31478b5 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f
sdb
├─sdb1
│ vfat FAT32 D239-3E20 a5eaddbc-6907-4420-8dd7-3f74ac288e8b c12a7328-f81f-11d2-ba4b-00a0c93ec93b
└─sdb2
btrfs 79dc25fb-deea-48ac-b6e8-1ef009e6956c 180G 18% /run/media/blue/79dc25fb-deea-48ac-b6e8-1ef009e6956c
20ffd4c6-e72b-44fb-ba5e-aa23cc837ef8 0fc63daf-8483-4772-8e79-3d69d8477de4
nvme0n1
│
├─nvme0n1p1
│ f13052fe-d0b0-402c-b6a4-6c02cf888e56 e3c9e316-0b5c-4db8-817d-f92df00215ae
├─nvme0n1p2
│ vfat FAT32 SYSTEM DFEE-5EF1 8d66d018-a078-42d1-941d-4ba06f51dc13 c12a7328-f81f-11d2-ba4b-00a0c93ec93b
├─nvme0n1p3
│ BitLoc 2 dc8db57e-55f3-4f04-86aa-24b9c14b6aa7 ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
└─nvme0n1p4
ntfs Recovery 367960ACF444FE6E 0709e6f3-3391-4d00-9f33-ea74020c80fa de94bba4-06d1-4d40-a16a-bfd50179d6ac
blue@localhost:~>
I expect that your BIOS should offer booting from the openSUSE disk as from the removable system. I am not sure where this entry comes from:
But as it is not shown when you boot openSUSE I believe it is auto-generated. In which case I also expect it to be auto-generated for openSUSE as well.
From openSUSE side everything looks OK. It is up to your BIOS to present this device. You may try
efibootmgr -a 4
to activate the entry for openSUSE, check with efibootmgr if it got * after its number. But BIOS may reset it when this disk is not present.
This is what I’m getting:
blue@localhost:~> sudo efibootmgr -a 4
You must specify a entry to activate (see the -b option)
blue@localhost:~>
How do I do that?
openSUSE is not the only distro that my BIOS doesn’t show. For some reason certain distros show and others don’t. MX linux, Garuda, Manjaro all show while openSUSE, TinyCore and several others don’t.
Could this be something that can be resolved by changing something in the BIOS settings?
Of course it could. But that is something you need to ask in the right place (where your hardware is discussed).
Thank you. I appreciate your help.
Turn on the Compatibility Support Module in your BIOS.
It’s called CSM.
I don’t see such an option anywhere in the BIOS.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.