A nub and his grub. Grub not showing other linux OS in menu

Fairly new to Garuda and just want to say I love the OS. So far everythingg has been working near perfectly. I do notice that when I add something to latte dock on a dual monitor system and move a icon on one monitor the latte dock on the second monitor goes crazy and all the icons move back and fourth. Its a easy fix though. I just close out latte dock and reload it. i would personally prefer to get rid of latte off the secondary monitor. I'll figure that out another day. The reason I am here though is because I really enjoy Gardua's grub set up. However, I can't seem to get it to show Nobara (Fedora) in the boot menu. If you notice in my posts below it certainly sees it and says it adds it to the menu, but when it boots it doesn't show up in the menu. It's not an emergency I can get in all of my systems. I can switch between refind, and my two grubs in bios so not a a big deal. But I would just prefer to use Garuda strictly because I love the way it works and looks. I did search for a answer in the forums and couldn't find one. So I copied some of the requested postings from other questions and included in my post to help speed things up and hopefully give you everything you need to help me out without having to ask a lot of questions. Thank you in advance for your help and time.

garuda-inxi
─λ sudo garuda-in
[sudo] password for jj78:
System:
Kernel: 5.19.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: root=UUID=7c0035c0-6c1b-480f-b5b0-020c0884e8da rw
[email protected] quiet quiet splash rd.udev.log_priority=3
vt.global_cursor_default=0
resume=UUID=ab7b1e7a-eba8-4439-8cbe-c82aadb79203 loglevel=3
[email protected]\boot\initramfs-linux-zen.img
Console: pty pts/0 wm: kwin_x11 DM: SDDM Distro: Garuda Linux
base: Arch Linux
Machine:
Type: Desktop System: Dell product: XPS 8940 v: N/A serial: <filter>
Chassis: type: 3 serial: <filter>
Mobo: Dell model: 0K3CM7 v: A00 serial: <filter> UEFI: Dell v: 2.9.0
date: 07/13/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech K850 Performance Wireless
Keyboard serial: <filter> charge: 100% (should be ignored)
rechargeable: yes status: discharging
CPU:
Info: model: 11th Gen Intel Core i7-11700 socket: LGA1151 (U3E1)
note: check bits: 64 type: MT MCP arch: Rocket Lake gen: core 11
built: 2021+ process: Intel 14nm family: 6 model-id: 0xA7 (167)
stepping: 1 microcode: 0x53
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1582 high: 2500 min/max: 800/4800:4900
base/boost: 2500/4200 scaling: driver: intel_pstate governor: powersave
volts: 0.8 V ext-clock: 100 MHz cores: 1: 800 2: 800 3: 2500 4: 2500
5: 800 6: 801 7: 801 8: 800 9: 800 10: 2500 11: 2500 12: 2500 13: 2500
14: 800 15: 1420 16: 2500 bogomips: 79872
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced IBRS
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 750] vendor: Dell
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: none empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3
bus-ID: 0000:00:02.0 chip-ID: 8086:4c8a class-ID: 0300
Device-2: NVIDIA GA104 [GeForce RTX 3060 Ti] vendor: Dell driver: nvidia
v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+ status: current
(as of 2022-07) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
built: 2020-22 bus-ID: 0000:02:00.0 chip-ID: 10de:2486 class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
unloaded: nouveau alternate: fbdev,intel,nv,vesa gpu: i915,nvidia
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 82 s-size: 1189x331mm (46.81x13.03")
s-diag: 1234mm (48.59")
Monitor-1: DP-5 pos: primary,right res: 1920x1080 hz: 60 dpi: 82
size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 75 dpi: 93
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
OpenGL: renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA
515.65.01 direct render: Yes
Audio:
Device-1: Intel vendor: Dell driver: snd_hda_intel v: kernel
bus-ID: 0000:00:1f.3 chip-ID: 8086:f1c8 class-ID: 0403
Device-2: NVIDIA GA104 High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus-ID: 0000:02:00.1 chip-ID: 10de:228b
class-ID: 0403
Sound Server-1: ALSA v: k5.19.8-zen1-1-zen running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: PulseAudio v: 16.1 running: no
Sound Server-4: PipeWire v: 0.3.57 running: yes
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi vendor: Rivet Networks
driver: iwlwifi v: kernel bus-ID: 0000:00:14.3 chip-ID: 8086:06f0
class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek vendor: Rivet Networks driver: r8169 v: kernel
port: 3000 bus-ID: 0000:03:00.0 chip-ID: 10ec:2600 class-ID: 0200
IF: enp3s0 state: down mac: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-14:5 chip-ID: 8087:0026 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:
Hardware-1: Intel Comet Lake PCH-H RAID driver: intel_nvme_remap v: N/A
port: 5060 bus-ID: 0000:00:17.0 chip-ID: 8086:06d6 rev: class-ID: 0104
Drives:
Local Storage: total: 3.24 TiB used: 99.41 GiB (3.0%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Toshiba model: KBG40ZNS512G
NVMe KIOXIA 512GB size: 476.94 GiB block-size: physical: 512 B
logical: 512 B type: SSD serial: <filter> rev: 10410106 temp: 53.9 C
scheme: GPT
SMART: yes health: PASSED on: 116d 21h cycles: 255 read-units: 9,177,199
[4.69 TB] written-units: 7,466,591 [3.82 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-75WN4A1 family: Blue size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD
rpm: 7200 serial: <filter> rev: 7113 temp: 34 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 116d 1h cycles: 256
read: 189.65 GiB written: 247.57 GiB
ID-3: /dev/sdb maj-min: 8:16 model: SSD size: 953.87 GiB block-size:
physical: 512 B logical: 512 B sata: 3.2 speed: 6.0 Gb/s type: SSD
serial: <filter> rev: 8A0 temp: 40 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 43 hrs cycles: 134
read: 5.9 MiB written: 3.8 MiB
ID-4: /dev/sdc maj-min: 8:32 vendor: Silicon Power model: SPCC Solid
State Disk size: 953.87 GiB block-size: physical: 512 B logical: 512 B
sata: 3.2 speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4A0 temp: 40 C
scheme: GPT
SMART: yes state: enabled health: PASSED on: 27 hrs cycles: 32
read: 491 KiB written: 1.8 MiB
Partition:
ID-1: / raw-size: 292.97 GiB size: 292.97 GiB (100.00%) used: 21.42 GiB
(7.3%) fs: btrfs block-size: 4096 B dev: /dev/sdc1 maj-min: 8:33
ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%) used: 2 MiB
(0.2%) fs: vfat block-size: 512 B dev: /dev/sdc4 maj-min: 8:36
ID-3: /home raw-size: 627.89 GiB size: 627.89 GiB (100.00%) used: 78 GiB
(12.4%) fs: btrfs block-size: 4096 B dev: /dev/sdc3 maj-min: 8:35
ID-4: /var/log raw-size: 292.97 GiB size: 292.97 GiB (100.00%) used: 21.42
GiB (7.3%) fs: btrfs block-size: 4096 B dev: /dev/sdc1 maj-min: 8:33
ID-5: /var/tmp raw-size: 292.97 GiB size: 292.97 GiB (100.00%) used: 21.42
GiB (7.3%) fs: btrfs block-size: 4096 B dev: /dev/sdc1 maj-min: 8:33
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.02 GiB used: 84.2 MiB (0.3%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sdc2 maj-min: 8:34
Sensors:
System Temperatures: cpu: 50.0 C pch: 49.0 C mobo: 41.0 C gpu: nvidia
temp: 42 C
Fan Speeds (RPM): cpu: 996 fan-1: 811 gpu: nvidia fan: 0%
Info:
Processes: 393 Uptime: 1h 0m wakeups: 38 Memory: 31.02 GiB used: 4.68 GiB
(15.1%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pacman: 1626 lib: 387
Shell: garuda-inxi (sudo) default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.20
Garuda (2.6.7-1):
System install date:     2022-09-12
Last full system update: 2022-09-14 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Yes
Snapshots:               Snapper
Failed units:            systemd-networkd-wait-online. Service

efibootmgr -v

efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0006,0001,0000,0002,0003
Boot0000* Windows Boot Manager  HD(1,GPT,83820e4d-d48b-4b6c-bd35-dd670c446ace,0x800,0x4b000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 b0 04 00 00 00 00 00 4d 0e 82 83 8b d4 6c 4b bd 35 dd 67 0c 44 6a ce 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 3400 37 00 39 00 35 00 7d 00 00 00 00 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* Nobara        HD(1,MBR,0x51c82198,0x800,0x200000)/File(\EFI\fedora\shimx64.efi)
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 98 21 c8 51 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0002* Onboard NIC(IPV4)     PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(b04f1303ebf2,0)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 1c / 01 01 06 00 00 00 / 03 0b 25 00 b0 4f 13 03 eb f2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0c 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0003* Onboard NIC(IPV6)     PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(b04f1303ebf2,0)/IPv6([::]:<->[::]:,0,0)0000424f
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 1c / 01 01 06 00 00 00 / 03 0b 25 00 b0 4f 13 03 eb f2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0d 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0004* rEFInd Boot Manager   HD(4,GPT,4aee34ae-7c26-6740-9592-16d19fb725bc,0x800,0x200000)/File(\EFI\refind\refind_x64.efi)
dp: 04 01 2a 00 04 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 ae 34 ee 4a 26 7c 40 67 95 92 16 d1 9f b7 25 bc 02 02 / 04 04 3a 00 5c 00 45 00 46 00 49 00 5c 00 72 00 65 00 66 00 69 00 6e 00 64 00 5c 00 72 00 65 00 66 00 69 00 6e 00 64 00 5f 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0006* Garuda        HD(4,GPT,4aee34ae-7c26-6740-9592-16d19fb725bc,0x800,0x200000)/File(\EFI\Garuda\grubx64.efi)
dp: 04 01 2a 00 04 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 ae 34 ee 4a 26 7c 40 67 95 92 16 d1 9f b7 25 bc 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 47 00 61 00 72 00 75 00 64 00 61 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00

sudo os-prober

╰─λ sudo os-prober
/dev/[email protected]/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sdb3:Nobara Linux 36 (KDE Plasma):Nobara:linux:btrfs:UUID=b81ff9f2-215e-428b-bd22-064507cef543:subvol=roo
t

sudo update-grub

╭─[email protected] in ~ as 🧙 took 4s
╰─λ sudo update-grub
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
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-lts-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
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/[email protected]/efi/Microsoft/Boot/bootmgfw.efi
Found Nobara Linux 36 (KDE Plasma) on /dev/sdb3
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2022-09-14 16:02:28 | @/.snapshots/32/snapshot | post | bluemail                              |
Found snapshot: 2022-09-14 16:02:26 | @/.snapshots/31/snapshot | pre  | /usr/bin/pacman -S --noconfirm chaotic-aur/bluemail                      |
Found snapshot: 2022-09-14 16:02:07 | @/.snapshots/30/snapshot | post | ufw-extras                            |
Found snapshot: 2022-09-14 16:02:06 | @/.snapshots/29/snapshot | pre  | /usr/bin/pacman -S --noconfirm --asdeps community/ufw-extras             |
Found snapshot: 2022-09-14 16:02:04 | @/.snapshots/28/snapshot | post | dropbox                               |
Found snapshot: 2022-09-14 16:02:03 | @/.snapshots/27/snapshot | pre  | /usr/bin/pacman -S --noconfirm chaotic-aur/dropbox                       |
Found snapshot: 2022-09-14 15:55:15 | @/.snapshots/26/snapshot | post | embree expect kdsoap python-idna whois|
Found snapshot: 2022-09-14 15:55:14 | @/.snapshots/25/snapshot | pre  | pacman -Su --config /tmp/tmp.idTNkK1bin                                  |
Found snapshot: 2022-09-14 07:58:12 | @/.snapshots/24/snapshot | post | curl plasma-integration plasma-workspace ttf-iosevka-nerd wayland-utils  |
Found snapshot: 2022-09-14 07:58:06 | @/.snapshots/23/snapshot | pre  | pacman -Su                            |
Found 10 snapshot(s)
Unmount /tmp/grub-btrfs.84YYPlRnc9 .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

/etc/default/grub.conf

# GRUB boot loader configuration

GRUB_DEFAULT="0"
GRUB_TIMEOUT=30
GRUB_DISTRIBUTOR="Garuda"
GRUB_CMDLINE_LINUX_DEFAULT="quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 resume=UUID=ab7b1e7a-eba8-4439-8cbe-c82aadb79203 loglevel=3"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT=30

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME="/usr/share/grub/themes/garuda-dr460nized/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
GRUB_DISABLE_SUBMENU=y

# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
GRUB_DISABLE_OS_PROBER=false
1 Like

Welcome @jj78. :slightly_smiling_face:

Fedora's grub is not standard and requires special configuration if you want it to play nicely with others. I don't know the exact way to fix your issue, but maybe these resources can be helpful:

https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault#Upgrade.2Fcompatibility_impact

3 Likes

That's really unusual (at least for me :blush:): os-prober / detection seems OK but the menu entry is not displayed...
Since this is Garuda (Arch) to detect/display Fedora (not the other way round), I'd rather try in the manual way, adding entries to /boot/grub/custom.cfg like here:
https://wiki.archlinux.org/title/GRUB#Dual-booting
Edit: I noticed only now that Fedora has Secure Boot (shimx64.efi). I have no experience on that and how this might play a role in the procedure above (maybe it is necessary to "load Fedora's grub.cfg files on-the-fly during boot"? or maybe something can be done chainloading (see the chapter above).
Also maybe it's worth reading?
https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot

5 Likes

Yeah the more I read the more I learn certain distros just don't get along. My luck I chose two that don't agree lol. I am still trying a few of those options in the links you provided. I will update if I have any luck. I spent a few hrs today on it with no luck. Thank you for the info. I think the fact that they are both btrfs is making the manual entry tricky. I'm not sure if I should be using /@/ or not. Anyways I'll keep plugging away at it. I'm pretty devoted to figuring stuff out.

1 Like

Thanks for the link. Definitely helpful, I am trying different things to see if I have any luck.

I must say I did get it to work one time but duplicating what I saw in the nobara grub when I hit e, the only problem with that is I don't think the kernel updates automatically. It had a old kernel when I did it that way.

1 Like

You may want to give a look at this long thread.
There is a solution but I'm not sure it was confirmed.

Grub related help
Good luck!

EDIT: Just disregard, it goes to the same link provided by @BluishHumility :slight_smile:

@jj78 I'm about to do the same thing, but maybe I'll stop by Fedora first. Do share if you figured out how to dual-boot them as I'll do some research as well.

This depends on how Fedora works.
If it was Garuda it could have been something like

menuentry "Nobara on /dev/sdb3" {
   insmod btrfs
   search --no-floppy --fs-uuid --set=root XXXXXXXXXX
   configfile /@/boot/grub/grub.cfg
   }

Where of course XXXXXXXX is the UUID of /dev/sdb3
This should go into /boot/grub/custom.cfg which does not require any update-grub.

You mean you copied that into the /boot/grub/grub.cfg of Garuda? That one of course will be regenerated at every update-grub in Garuda, so your changes will be also overwritten.
That's why my idea was to link Garuda GRUB to Fedora /boot/grub/grub.cfg as shown above, so when you update Fedora, you get to the updated configuration from Garuda.

Given these ideas, I must admit that I've been completely displaced by the first Fedora link above, since things seems quite different there, so maybe my suggestion won't work :frowning:

2 Likes

No actually I was trying different methods in the grub edit mode for the custom 40 entry I started for fedora in the grub.cfg(garuda). Just to see what works and didn't work. The only one I could get to work was duplicating what I found in edit mode from the fedora grub. I have a few ideas I just need to get to to try in combination with some of the suggestions made so far. Doing it that way like I said, I don't think will update the kernel to the latest for fedora.

Actually, I think I will try that one first. I can always set the fedora timeout to 0 or 1 so i don't have to make a selection to speed up the process. And you're right fedora will update on its own. It wasn't quite clicking at first when you said that originally lol.

I will, and i might know something today. My calendar is kind of mixed on stuff to do today. I think Filo might have the best method though.

Fedora uses a heavily modified grub, which is not compatible to upstream (grub, or Arch). They use a different configuration method, so they call standard grub as "Legacy-deprecated" or similar.
A long time ago, when we were investigated a similar case, there was a possibility to revert to the old method. I am not sure if this is still possible.

I would suggest trying the rEFInd method, not that it would be OOTB ready, but I guess it would be more straightforward to configure manually. Archwiki has detailed instructions on this.

I have also seen your Fedora root is on MBR disk, but since it works in some way, it may not matter.

Confirm with Fedora documentation/support, that there is no issue with using shim with SecureBoot disabled, or any requirements. Was Fedora installed with SecureBoot enabled?

Are Fedora entries completely absent in Garuda grub menu, or just not working?

I also recommend you ask Fedora support, as they surely know their systems better.

1 Like