How to add a boot entry to garuda boot menu

Issues & Assistance Newbies
1

Hi, I installed on separate hdd Fedora KDE Spin, what should I do to add this distro to Garuda Boot Menu? Currently in Garuda Boot Menu I have GarudaLinux as default and Win 11 which is installed on another hdd.
Thanks for help
Raindrift

╭─kris@kris in ~
╰─λ efibootmgr
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,0000,0005,0002,0006
Boot0000* Windows Boot Manager  HD(2,GPT,21b338a8-efc1-40ae-8a29-57a62f87f2ca,0x109000,0x31800)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000004d000100000010000000040000007fff0400
Boot0002* Fedora        HD(1,GPT,f4df8b24-ea2f-46e3-9206-3d7c2cbd0d1c,0x800,0x12c000)/File(\EFI\FEDORA\SHIMX64.EFI)
Boot0004* Garuda        HD(1,GPT,a1abd635-4c2e-5944-bc4a-2cba7528acb1,0x800,0x100000)/File(\EFI\GARUDA\GRUBX64.EFI)
Boot0005* UEFI OS       HD(1,GPT,a1abd635-4c2e-5944-bc4a-2cba7528acb1,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0006* Fedora        HD(1,GPT,f4df8b24-ea2f-46e3-9206-3d7c2cbd0d1c,0x800,0x12c000)/File(\EFI\FEDORA\SHIM.EFI)0000424f

╭─kris@kris in ~ took 201ms
╰─λ garuda-inxi
System:
Kernel: 6.2.11-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9dfd21e4-8574-4945-88e4-b690a0acca4e rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=e3e128f1-2149-4ec6-9731-d3eed013d307 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MPG Z390 GAMING PLUS (MS-7B51) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 1.70
date: 08/08/2019
CPU:
Info: model: Intel Core i7-9700F bits: 64 type: MCP arch: Coffee Lake
gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xD (13) microcode: 0xF4
Topology: cpus: 1x cores: 8 smt: <unsupported> cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB L3: 12 MiB
desc: 1x12 MiB
Speed (MHz): avg: 800 min/max: 800/4700 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 bogomips: 48000
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Gigabyte
driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-03) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 2 speed: 5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1e84
class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 4480x1440 s-dpi: 108 s-size: 1054x342mm (41.50x13.46")
s-diag: 1108mm (43.63")
Monitor-1: DP-2 pos: primary,right res: 2560x1440 dpi: 109
size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
Monitor-2: HDMI-0 pos: left res: 1920x1080 hz: 60 dpi: 94
size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce RTX 2070
SUPER/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI
driver: snd_hda_intel bus-ID: 2-3:2 v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl chip-ID: 0499:172f
class-ID: 0103 bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:10f8 class-ID: 0403
Device-3: Yamaha Steinberg UR22C type: USB driver: snd-usb-audio
API: ALSA v: k6.2.11-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.69 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 Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 5 TiB used: 655.41 GiB (12.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 4B2QEXM7 temp: 35.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung
model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B2QEXM7 temp: 48.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM003-1CH162
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: CC47 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST1000DM003-1CH162
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: CC47 scheme: MBR
Partition:
ID-1: / raw-size: 1.79 TiB size: 1.79 TiB (100.00%) used: 655.41 GiB (35.8%)
fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 612 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
used: 655.41 GiB (35.8%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-4: /var/log raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
used: 655.41 GiB (35.8%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-5: /var/tmp raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
used: 655.41 GiB (35.8%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.29 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 31.25 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
System Temperatures: cpu: 39.0 C pch: 63.0 C mobo: N/A gpu: nvidia
temp: 56 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 269 Uptime: 1h 7m wakeups: 0 Memory: 31.29 GiB
used: 3.46 GiB (11.1%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: 2100
pm: pacman pkgs: 2094 libs: 597 tools: octopi,paru pm: flatpak pkgs: 6
Shell: fish v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.26
Garuda (2.6.16-1):
System install date:     2023-03-23
Last full system update: 2023-04-16
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:            plymouth-start.service
2

usually nothing, since the os-prober is enabled by default to my knowledge.

In case it isn't, change GRUB_DISABLE_OS_PROBER to false in /etc/default/grub and run sudo update-grub

3

just perform

update-grub

That would make os-prober detect your distro and add it to your grub boot menu.

4

Also when you write a output from terminal include it in tilde like this:

~~~
Your output here
~~~

It makes the output more readable.

You can read more on here:

1 Like
5

hi, thank you very much for answer.
Its my bad, but I forgot to write that I tried update-grub already, but without any result

please look at the output:

╭─kris@kris in ~
╰─λ sudo update-grub
[sudo] password for kris:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme1n1p2@/efi/Microsoft/Boot/bootmgfw.efi
Found Fedora Linux 38 (KDE Plasma Prerelease) on /dev/sda3
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Snapshots goes here ...
Found 10 snapshot(s)
Unmount /tmp/grub-btrfs.Fqi6AXrqit .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
6

It looks like os prober found your fedora entry. try to reboot and see if it’s still not there in the boot menu?

7

No, there is nothing new in menu after reboot, as new user I can't attach an screenshot, but menu look exactly the same as before

8

Fedora uses a heavily modified version of Grub that is not compatible with upstream Grub (which Arch uses). See dalto's note from a couple years ago on the Fedora forum:

Try using the rEFInd boot manager instead, which will allow each installation to load their own version of Grub (or whatever bootloader is in use).

4 Likes
9

I'm not sure, but in my case the each system is installed on different HDD.

10

Thank you for help: rEFInd helped. I also had to change EFI boot device in PC-BIOS.

1 Like
11

This had me stumped for a few hours, recently!

12

You can also interact with the EFI boot entries from user space with efibootmgr. Changing the boot order, as well as adding or removing boot options, is pretty simple once you know the commands.

rEFInd also has a built-in tool which piggybacks off of efibootmgr to set itself as the primary boot option. It has to be run from the installation where you installed rEFInd of course:

sudo refind-mkdefault
1 Like
13

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