New installation doesn't show in boot options

imane13 · April 2, 2025, 11:08am

Hi
I have installed Tumbleweed on an external SSD. I followed the instructions laid out here:

The installation finished ok but when restarting the computer, the installation doesn’t show in the boot options.

Here’s the system that I have:

System:
  Kernel: 6.13.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc
    avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=79dc25fb-deea-48ac-b6e8-1ef009e6956c rw rootflags=subvol=@ quiet loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0 wm: kwin_wayland vt: 1
    dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: Nimo Direct product: N154B v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: Nimo Direct model: Portable Computer serial: <superuser required> part-nu: 850066064764
    uuid: <superuser required> UEFI: American Megatrends LLC. v: DN21CRV202 date: 09/28/2024
Battery:
  ID-1: BAT0 charge: 40.6 Wh (78.7%) condition: 51.6/53.6 Wh (96.3%) volts: 12.0 min: 11.4
    model: Intel SR 1 SR Real Battery type: Unknown serial: <filter> status: discharging
CPU:
  Info: model: 12th Gen Intel Core i3-1215U bits: 64 type: MST AMCP arch: Alder Lake level: v3
    note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
    microcode: 0x436
  Topology: cpus: 1x dies: 1 clusters: 3 cores: 6 threads: 8 mt: 2 tpc: 2 st: 4 smt: enabled
    cache: L1: 544 KiB desc: d-4x32 KiB, 2x48 KiB; i-2x32 KiB, 4x64 KiB L2: 4.5 MiB
    desc: 2x1.2 MiB, 1x2 MiB L3: 10 MiB desc: 1x10 MiB
  Speed (MHz): avg: 595 min/max: 400/1200:900 scaling: driver: intel_pstate governor: powersave
    cores: 1: 595 2: 595 3: 595 4: 595 5: 595 6: 595 7: 595 8: 595 bogomips: 39936
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Alder Lake-UP3 GT1 [UHD Graphics] vendor: IP3 Tech driver: i915 v: kernel
    alternate: xe arch: Xe process: Intel 10nm built: 2020-21 ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:46b3 class-ID: 0300
  Device-2: Sunplus IT Co PC Camera driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:3 chip-ID: 2ef4:4944 class-ID: 0102
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 compositor: kwin_wayland
    driver: X: loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0c4e built: 2023 res: mode: 1920x1080 hz: 60
    scale: 125% (1.25) to: 1536x864 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
    drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.2-arch1.2 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Graphics (ADL GT2) device-ID: 8086:46b3 memory: 15.17 GiB
    unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 5 device: 0 type: integrated-gpu name: Intel Graphics (ADL GT2)
    driver: N/A device-ID: 8086:46b3 surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe
    (LLVM 19.1.7 256 bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: IP3 Tech driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51c8
    class-ID: 0401
  Device-2: Sunplus IT Co PC Camera driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:3 chip-ID: 2ef4:4944 class-ID: 0102
  API: ALSA v: k6.13.8-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-
ID: 8086:51f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 3-10:5 chip-ID: 8087:0026 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: no address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no
    pairing: no
Drives:
  Local Storage: total: 1.13 TiB used: 40.79 GiB (3.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD Green SN350 1TB 2G0C
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 236050WD temp: 20.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 4096 B logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: SSD serial: <filter> fw-rev: 0214 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 40.79 GiB (18.3%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 608 KiB (0.2%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 40.79 GiB (18.3%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 40.79 GiB (18.3%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 40.79 GiB (18.3%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.08 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 8 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 24.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 31.08 GiB used: 2.28 GiB (7.3%)
  Processes: 267 Power: uptime: 1m states: freeze,mem,disk suspend: s2idle avail: deep wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.42 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: 1552 pm: pacman pkgs: 1545 libs: 434 tools: gnome-software,octopi,paru pm: flatpak
    pkgs: 7 Compilers: clang: 19.1.7 gcc: 14.2.1 Client: shell wrapper v: 5.2.37-release inxi: 3.3.37
Garuda (2.7.2-1):
  System install date:     2025-02-23
  Last full system update: 2025-03-29
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

Help is appreciated.

arvidjaar · April 2, 2025, 11:31am

Explain what boot options you are talking about.

jjis · April 2, 2025, 12:17pm

Since you installed to an external drive, boot is presumably still set to your main SSD, although it’s not clear to me what you have on that, although there is some mention of Windows at the end of your system details.

If not and you are running another Linux Distro(s) on your main drive then you could try updating your GRUB on there and that should / may then show your new Opensuse install perhaps?

imane13 · April 2, 2025, 12:49pm

Windows 11 is installed on the internal drive, but I never use it. I use Garuda Linux on an external SSD. I edited the boot order in the BIOS/EFI so that USB disk is searched for first in the boot order. @arvidjaar What I meant was that the BIOS shows only the Windows and Garuda as an option but not openSUSE.

If the SSD on which I installed openSUSE is plugged in and also the USB stick on which the openSUSE .iso is are plugged in, then I can choose the option of booting from the installed openSUSE.

@jjis I don’t know what specifically to do to follow your advice of “updating you grub”.

arvidjaar · April 2, 2025, 12:55pm

Show output of

efibootmgr
lsblk -f -o +partuuid

from openSUSE or another Linux (depending on the efibootmgr version there you many need to use efibootmgr -v).

jjis · April 2, 2025, 12:55pm

These are the instruction on GRUB for Garuda, although I’m not sure if it need to be a complicated as they say, but probably best be guided by this if that’s your main OS I guess.
Multiple installations on one partition | Garuda Linux wiki

imane13 · April 2, 2025, 1:44pm

Also another thought; just before hitting the install button, there was a summary of everything that the installation was going to do. What stood out to me was the top part, where it said that secure boot was enabled. I’m not familiar with the nuts and bolts of operating systems but I have been told with previous distros that it’s better to set secure boot to ‘disable’. Could this be the reason why I’m having this problem?

gogalthorp · April 2, 2025, 2:01pm

Assuming your are not doing a legacy install secure boot should not hurt.

jjis · April 2, 2025, 2:19pm

Not sure if there were any GRUB options when you installed it. Alternatively you could try having a look at these instructions in an old forum post. So that your New Opensuse install handles the boot options instead of Garuda perhaps? Maybe more admin types can take a look & say if these instructions would still be applicable / help?
https://forums.opensuse.org/t/update-grub/132037

imane13 · April 2, 2025, 2:55pm

I don’t know that what I have is actually Grub. I took photos of what I see when I start the computer with F2 pressed. But the system here doesn’t let me upload them. They’re all jpg files size 4.4-5.6 mb. How can I share those with the forum?

arvidjaar · April 2, 2025, 3:02pm

I requested the text output of two commands which fits in the single post. I am not interested in huge pictures which will show the same information in much less usable form.

hcvv · April 2, 2025, 3:18pm

Maybe a bit of explanation to a newcomer.
lease, to make the pieces of computer code in your posts better consumable by technical oriented people:

And post as complete as possible. That is starting with the line with the prompt and the command, then all output, and ending with the new prompt line.
When you really feel you need to change anything in such a copy, then in a comment, else we take all characters literally.

imane13 · April 2, 2025, 3:29pm

blue@blue in ~
╰─λ efibootmgr
lsblk -f -o +partuuid
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0000,0001,0003,0002,0005,0004
Boot0000* Windows Boot Manager  HD(2,GPT,8d66d018-a078-42d1-941d-4ba06f51dc13,0x40800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000000e000100000010000000040000007fff0400
Boot0001  Garuda        HD(1,GPT,a5eaddbc-6907-4420-8dd7-3f74ac288e8b,0x1000,0x96000)/\EFI\Garuda\grubx64.efi
Boot0002  opensuse      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003  Manjaro       VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004  opensuse-secureboot   VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0005  BigLinux      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0006* UEFI OS       HD(1,GPT,a5eaddbc-6907-4420-8dd7-3f74ac288e8b,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
NAME FSTYPE FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda
├─sda1
│    vfat   FAT32          D239-3E20                             298.8M     0% /boot/efi   a5eaddbc-6907-4420-8dd7-3f74ac288e8b
└─sda2
btrfs                 79dc25fb-deea-48ac-b6e8-1ef009e6956c  179.9G    18% /var/log    20ffd4c6-e72b-44fb-ba5e-aa23cc837ef8
/var/tmp
/var/cache
/srv
/home
/root
/
zram0
swap   1     zram0    ee9ffd61-13e9-4dcd-aeb4-aa5750173617                [SWAP]
nvme0n1
│
├─nvme0n1p1
│                                                                                          f13052fe-d0b0-402c-b6a4-6c02cf888e56
├─nvme0n1p2
│    vfat   FAT32 SYSTEM   DFEE-5EF1                                                       8d66d018-a078-42d1-941d-4ba06f51dc13
├─nvme0n1p3
│    BitLoc 2              2c1fc135-3496-4d9f-bc0f-3a8e45643ddf                            dc8db57e-55f3-4f04-86aa-24b9c14b6aa7
└─nvme0n1p4
ntfs         Recovery 367960ACF444FE6E                                                0709e6f3-3391-4d00-9f33-ea74020c80fa

╭─blue@blue in ~ took 0s
╰─λ

imane13 · April 2, 2025, 3:30pm

The above shows the internal HD with Windows and the Garuda with which I work on an external SSD.

imane13 · April 2, 2025, 3:33pm

Now I ran the same command with the openSUSE SSD plugged in as well:

blue@blue in ~ took 0s
╰─λ efibootmgr
lsblk -f -o +partuuid
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0000,0001,0003,0002,0005,0004
Boot0000* Windows Boot Manager  HD(2,GPT,8d66d018-a078-42d1-941d-4ba06f51dc13,0x40800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000000e000100000010000000040000007fff0400
Boot0001  Garuda        HD(1,GPT,a5eaddbc-6907-4420-8dd7-3f74ac288e8b,0x1000,0x96000)/\EFI\Garuda\grubx64.efi
Boot0002  opensuse      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003  Manjaro       VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004  opensuse-secureboot   VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0005  BigLinux      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0006* UEFI OS       HD(1,GPT,a5eaddbc-6907-4420-8dd7-3f74ac288e8b,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
NAME        FSTYPE    FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS                PARTUUID
sda
├─sda1      vfat      FAT32          D239-3E20                             298.8M     0% /boot/efi                  a5eaddbc-6907-4420-8dd7-3f74ac288e8b
└─sda2      btrfs                    79dc25fb-deea-48ac-b6e8-1ef009e6956c  179.9G    18% /var/log                   20ffd4c6-e72b-44fb-ba5e-aa23cc837ef8
/var/tmp
/var/cache
/srv
/home
/root
/
sdb
├─sdb1      vfat      FAT32          9B7B-D390                                                                      b32da5bc-3dac-43aa-990a-18cc46a761ec
├─sdb2      btrfs                    8408fb06-85c4-4992-ab01-02d9d27c8fe8  227.3G     3% /run/media/blue/8408fb06-85c4-4992-ab01-02d9d27c8fe8
│                                                                                                                   7ef020c2-f816-470e-a9b6-f99f2190a5c2
└─sdb3      swap      1              2053365b-dfba-42eb-acb4-c57f641b80c8                                           42401a45-ade5-4689-9b89-74b3d31478b5
zram0       swap      1     zram0    ee9ffd61-13e9-4dcd-aeb4-aa5750173617                [SWAP]
nvme0n1
├─nvme0n1p1                                                                                                         f13052fe-d0b0-402c-b6a4-6c02cf888e56
├─nvme0n1p2 vfat      FAT32 SYSTEM   DFEE-5EF1                                                                      8d66d018-a078-42d1-941d-4ba06f51dc13
├─nvme0n1p3 BitLocker 2              2c1fc135-3496-4d9f-bc0f-3a8e45643ddf                                           dc8db57e-55f3-4f04-86aa-24b9c14b6aa7
└─nvme0n1p4 ntfs            Recovery 367960ACF444FE6E                                                               0709e6f3-3391-4d00-9f33-ea74020c80fa

╭─blue@blue in ~ took 0s
╰─λ

arvidjaar · April 2, 2025, 5:30pm

Doing it from within openSUSE would also show mount points, but anyway - yes, there is no boot menu entry for the openSUSE. I am not sure what those VenHw are or do, but all of them are disabled anyway.

Boot openSUSE and post the output of

grep -Ev '^#|^$' /etc/sysconfig/bootloader
lsblk -f -o +partuuid
efibootmgr

And please, execute each command separately, so it is clear where output of one command ends and the next command starts.

imane13 · April 2, 2025, 5:54pm

blue@localhost:~> grep -Ev '^#|^$' /etc/sysconfig/bootloader
LOADER_TYPE="grub2-efi"
SECURE_BOOT="yes"
TRUSTED_BOOT="no"
UPDATE_NVRAM="yes"
blue@localhost:~> lsblk -f -o +partuuid
NAME FSTYPE FSVER LABEL                          UUID                                 FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda
├─sda1
│    vfat   FAT32                                9B7B-D390                                 1G     1% /boot/efi   b32da5bc-3dac-43aa-990a-18cc46a761ec
├─sda2
│    btrfs                                       8408fb06-85c4-4992-ab01-02d9d27c8fe8  227.3G     3% /root       7ef020c2-f816-470e-a9b6-f99f2190a5c2
│                                                                                                    /var
│                                                                                                    /home
│                                                                                                    /usr/local
│                                                                                                    /srv
│                                                                                                    /opt
│                                                                                                    /boot/grub2/x86_64-efi
│                                                                                                    /boot/grub2/i386-pc
│                                                                                                    /.snapshots
│                                                                                                    /
└─sda3
     swap   1                                    2053365b-dfba-42eb-acb4-c57f641b80c8                [SWAP]      42401a45-ade5-4689-9b89-74b3d31478b5
sdb  iso966 Jolie openSUSE-Tumbleweed-DVD-x86_64 2025-03-29-16-27-54-01
├─sdb1
│    vfat   FAT16 openSUSE-Tumbleweed-DVD-x86_64 C21B-C1D8                                                       5f6e76bd-01
└─sdb2
     iso966 Jolie openSUSE-Tumbleweed-DVD-x86_64 2025-03-29-16-27-49-95                                          5f6e76bd-02
sdc
└─sdc1
     vfat   FAT32 USB256DATA                     8E32-3C42                             169.1G    29% /run/media/blue/USB256DATA
                                                                                                                 7c28e505-01
nvme0n1
│
├─nvme0n1p1
│                                                                                                                f13052fe-d0b0-402c-b6a4-6c02cf888e56
├─nvme0n1p2
│    vfat   FAT32 SYSTEM                         DFEE-5EF1                                                       8d66d018-a078-42d1-941d-4ba06f51dc13
├─nvme0n1p3
│    BitLoc 2                                                                                                    dc8db57e-55f3-4f04-86aa-24b9c14b6aa7
└─nvme0n1p4
     ntfs         Recovery                       367960ACF444FE6E                                                0709e6f3-3391-4d00-9f33-ea74020c80fa
blue@localhost:~> efibootmgr
Absolute path to 'efibootmgr' is '/usr/sbin/efibootmgr', so running it may require superuser privileges (eg. root).
blue@localhost:~> sudo efibootmgr

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

For security reasons, the password you type will not be visible.

[sudo] password for root:
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0000,0004,0001,0002,0005,0003
Boot0000* Windows Boot Manager  HD(2,GPT,8d66d018-a078-42d1-941d-4ba06f51dc13,0x40800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000000e000100000010000000040000007fff0400
Boot0001  Garuda        VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0002  opensuse      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003  Manjaro       VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004  opensuse-secureboot   HD(1,GPT,b32da5bc-3dac-43aa-990a-18cc46a761ec,0xffff,0x20ffdf)/File(\EFI\opensuse\shim.efi)
Boot0005  BigLinux      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0006* UEFI: KingstonDataTraveler 3.00000    PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/CDROM(1,0xb4c,0xc0f0)0000424f
blue@localhost:

arvidjaar · April 2, 2025, 6:52pm

As expected, BIOS hides boot menu entries which point to missing devices. When you rebooted with this removable disk plugged in, the entry is there. It is exactly the same situation as shown when you booted from another disk with Garuda - Garuda menu entry was visible (now hidden) and openSUSE menu entry was hidden (now visible).

Please show

ls -lR /boot/efi/EFI

imane13 · April 2, 2025, 8:11pm

Still from openSUSE? With both openSUSE and Garuda plugged in?

arvidjaar · April 3, 2025, 3:47am

Yes

It does not matter, I am interested in the content of /boot/efi in openSUSE.