Changing names of boot entries and boot order

Hello…

I have two versions of Garuda installed on different drives on the same desktop (Garuda Dragonized on /dev/nvme0n1 and Garuda Sway on /dev/nvme1n1) and so I have two entries named “Garuda” in the grub boot menu. I use the Dragonized version most often. It isn’t a very descriptive name, unfortunately, and it seems like since the Sway version is what I installed last, that’s always what boots, even if I change the boot order in the Garuda Boot Options app in the Dragonized installation.

I’ve looked at these topics and there seem to be varying degrees of success changing the boot order, but unfortunately setting GRUB_DEFAULT=2 nor GRUB_SAVEDEFAULT=true seems to work after a sudo update-grub, and none of them seem to talk about changing the names:

https://forum.garudalinux.org/t/garuda-boot-options-not-applying/2681/26

I also saw this, but I don’t know that I need to change it from UEFI since technically grub can boot both of them:

And then there’s this, but when I look at the files in /etc/grub.d in Dragonized, they all seem to be generated with variables which are defined somewhere, and I can’t figure out where it’s getting the names.

https://wiki.archlinux.org/title/GRUB

So, how do I change at least the names of the entries in the grub menu?

Following is the garuda-inxi output:

System:
  Kernel: 6.12.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=79bebd74-6c02-4148-b1e5-1bed3e4c4274 rw rootflags=subvol=@
    quiet resume=UUID=03ba1005-a576-46de-bba3-38f9d149082e loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.9.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: B550 Taichi Razer Edition
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: L3.46 date: 08/20/2024
CPU:
  Info: model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 96 MiB desc: 1x96 MiB
  Speed (MHz): avg: 3595 min/max: 550/4550 boost: enabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 3595 2: 3595 3: 3595
    4: 3595 5: 3595 6: 3595 7: 3595 8: 3595 9: 3595 10: 3595 11: 3595 12: 3595
    13: 3595 14: 3595 15: 3595 16: 3595 bogomips: 108588
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel DG2 [Arc A770] vendor: ASRock driver: i915 v: kernel
    alternate: xe arch: Gen-12.7 code: Alchemist process: TSMC n6 (7nm)
    built: 2022+ pcie: gen: 1 speed: 2.5 GT/s lanes: 1 ports: active: DP-1
    off: HDMI-A-4 empty: DP-2, DP-3, DP-4, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 0e:00.0 chip-ID: 8086:56a0 class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900
    XT/7900 XTX/7900 GRE/7900M] vendor: Yeston driver: amdgpu v: kernel
    arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: none off: DP-5,HDMI-A-5
    empty: DP-6,DP-7,Writeback-1 bus-ID: 12:00.0 chip-ID: 1002:744c
    class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: amdgpu,modesetting
    unloaded: radeon alternate: fbdev,intel,vesa dri: iris,radeonsi
    gpu: i915,amdgpu display-ID: 0
  Monitor-1: DP-1 res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: intel iris drv: amd radeonsi platforms: device: 0
    drv: iris device: 1 drv: radeonsi device: 2 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: 24.3.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Arc A770 Graphics (DG2)
    device-ID: 8086:56a0 memory: 15.53 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.303 layers: 14 device: 0 type: discrete-gpu name: Intel
    Arc A770 Graphics (DG2) driver: N/A device-ID: 8086:56a0
    surfaces: xcb,xlib,wayland device: 1 type: discrete-gpu name: AMD Radeon
    RX 7900 XTX (RADV NAVI31) driver: N/A device-ID: 1002:744c
    surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
    18.1.8 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel DG2 Audio vendor: ASRock driver: snd_hda_intel v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 0f:00.0 chip-ID: 8086:4f90
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 12:00.1 chip-ID: 1002:ab30 class-ID: 0403
  Device-3: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 14:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.12.7-zen1-1-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.2.7 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 driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    port: N/A bus-ID: 05:00.0 chip-ID: 8086:3102 class-ID: 0200
  IF: enp5s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 vendor: Rivet Networks Killer
    driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp8s0 state: up mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:5 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 3.68 TiB used: 407.99 GiB (10.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 model: NX-2TB 2280 size: 1.86 TiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
    tech: SSD serial: <filter> fw-rev: H240129a temp: 41.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: SanDisk model: Extreme 2TB X3N
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 731100WD temp: 42.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 1.8 TiB size: 1.8 TiB (100.00%) used: 407.99 GiB (22.2%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
    used: 407.99 GiB (22.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
    used: 407.99 GiB (22.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 1.8 TiB size: 1.8 TiB (100.00%)
    used: 407.99 GiB (22.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 62.72 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 68.99 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 45.6 C mobo: N/A gpu: amdgpu temp: 32.0 C
    mem: 60.0 C
  Fan Speeds (rpm): fan-1: 366 gpu: amdgpu fan: 0
Info:
  Memory: total: 64 GiB note: est. available: 62.72 GiB used: 7.94 GiB (12.7%)
  Processes: 443 Power: uptime: 20h 38m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 25.08 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1952 libs: 578 tools: octopi,paru,pikaur
    Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 13 Shell: garuda-inxi
    default: fish v: 3.7.1 running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
  System install date:     2024-12-03
  Last full system update: 2025-01-03 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            

uname -a:

Linux purple 6.12.7-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 27 Dec 2024 14:24:32 +0000 x86_64 GNU/Linux

The contents of /etc/default/grub:

File: /etc/default/grub
# GRUB boot loader configuration

GRUB_DEFAULT="2"
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR='Garuda'
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=03ba1005-a576-46de-bba3-38f9d149082e 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=5

# 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 `videoinfo'
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

# This config file imports drop-in files from /etc/default/grub.d/.
for garuda_grub_d in ${sysconfdir}/default/grub.d/*.cfg ; do if [ -e "${garuda_grub_d}" ]; then source "${garu
da_grub_d}"; fi; done
GRUB_EARLY_INITRD_LINUX_STOCK=''

inxi --recommends:

inxi will now begin checking for the programs it needs to operate.

Check inxi --help or the man page (man inxi) to see what options are
available.
------------------------------------------------------------------------------
Test: core tools:

Perl version:  5.040000
Current shell: fish 3.7.1
Default shell: fish
sh links to: /usr/bin/bash
Package manager: pacman
------------------------------------------------------------------------------
Test: required system directories:

/proc: ........................................................... Present
/sys: ............................................................ Present

All required system directories are present
------------------------------------------------------------------------------
Test: recommended system programs:

Note: IPMI sensors are generally only found on servers. To access that data,
you only need one of the ipmi items.

blockdev: --admin -p/-P (filesystem blocksize).................... Present
bt-adapter: -E bluetooth data (if no hciconfig, btmgmt)........... Present
btmgmt: -E bluetooth data (if no hciconfig)....................... Present
dig: -i wlan IP................................................... Present
dmidecode: -M if no sys machine data; -m.......................... Present
doas: -Dx hddtemp-user; -o file-user (alt for sudo)............... Missing
fdisk: -D partition scheme (fallback)............................. Present
file: -o unmounted file system (if no lsblk)...................... Present
fruid_print: -M machine data, Elbrus only......................... Missing
hciconfig: -E bluetooth data (deprecated, good report)............ Missing
hddtemp: -Dx show hdd temp, if no drivetemp module................ Missing
ifconfig: -i ip LAN (deprecated, ip preferred).................... Present
ip: -i ip LAN..................................................... Present
ipmitool: -s IPMI sensors (servers)............................... Missing
ipmi-sensors: -s IPMI sensors (servers)........................... Missing
lsblk: -L LUKS/bcache; -o unmounted file system (best option)..... Present
lspci: -A,-E,-G,-N,-R PCI Device data (/sys supplies much)........ Present
lsusb: -A,-E,-G,-J,-N USB Device data (/sys supplies much)........ Present
lvs: -L LVM data.................................................. Present
mdadm: -Ra advanced mdraid data................................... Present
modinfo: Ax; -Nx module version................................... Present
ps: -G,-I,-n,-S,-t process/programs............................... Present
runlevel: -I fallback to Perl..................................... Missing
sensors: -s sensors output (optional, /sys supplies most)......... Present
smartctl: -Da advanced data....................................... Present
strings: -I sysvinit version...................................... Present
sudo: -Dx hddtemp-user; -o file-user (try doas!).................. Present
tree: --debugger 20,21 /sys tree.................................. Missing
udevadm: -m ram data for non-root, or no dmidecode................ Present
upower: -sx attached device battery info.......................... Present
uptime: -I uptime................................................. Present

The following recommended system programs are missing:
doas
pacman: doas
fruid_print
pacman: N/A
hciconfig
pacman: bluez-utils-compat (frugalware: bluez-utils)
hddtemp
pacman: hddtemp
ipmitool
pacman: ipmitool
ipmi-sensors
pacman: freeipmi
runlevel
pacman: systemd
tree
pacman: tree
------------------------------------------------------------------------------
Test: recommended display information programs:

eglinfo: -G X11/Wayland EGL info.................................. Present
glxinfo: -G X11 GLX info.......................................... Present
vulkaninfo: -G Vulkan API info.................................... Present
wayland-info: -G Wayland data (not for X)......................... Present
wmctrl: -S active window manager (fallback)....................... Missing
xdpyinfo: -G (X) Screen resolution, dpi; -Ga Screen size.......... Present
xprop: -S (X) desktop data........................................ Present
xdriinfo: -G (X) DRI driver (if missing, fallback to Xorg log).... Missing
xrandr: -G (X) monitors(s) resolution; -Ga monitor data........... Present

The following recommended display information programs are missing:
wmctrl
pacman: wmctrl
xdriinfo
pacman: xorg-xdriinfo
------------------------------------------------------------------------------
Test: recommended downloader programs (You only need one of these):

Perl HTTP::Tiny is the default downloader tool if IO::Socket::SSL is present.
See --help --alt 40-44 options for how to override default downloader(s) in
case of issues.

If dig is installed, it is the default for WAN IP data. Strongly recommended.
Dig is fast and accurate.

curl: -i (if no dig); -w,-W; -U................................... Present
dig: -i wlan IP................................................... Present
wget: -i (if no dig); -w,-W; -U................................... Present

All recommended downloader programs are present
------------------------------------------------------------------------------
Test: recommended kernel modules:

GPU modules are only needed if applicable. NVMe drives do not need drivetemp
but other types do.

To load a module: modprobe <module-name> - To permanently load add to
/etc/modules or /etc/modules-load.d/modules.conf (check your system paths for
exact file/directory names).

amdgpu: -s, -G AMD GPU sensor data (newer GPUs)................... Present
drivetemp: -Dx drive temperature (kernel >= 5.6).................. Missing
nouveau: -s, -G Nvidia GPU sensor data (if using free driver)..... Missing
radeon: -s, -G AMD GPU sensor data (older GPUs)................... Missing

The following recommended kernel modules are missing:
drivetemp
nouveau
radeon
------------------------------------------------------------------------------
Test: recommended Perl modules (Optional):

None of these are strictly required, but if you have them all, you can
eliminate some recommended non Perl programs from the install.

HTTP::Tiny and IO::Socket::SSL must both be present to use as a downloader
option. For json export Cpanel::JSON::XS is preferred over JSON::XS, but
JSON::PP is in core modules. To run --debug 20-22 File::Copy, File::Find, and
File::Spec::Functions must be present (most distros have these in Core
Modules).

File::Copy: --debug 20-22 - required for debugger................. Present
File::Find: --debug 20-22 - required for debugger................. Present
File::Spec::Functions: --debug 20-22 - required for debugger...... Present
HTTP::Tiny: -U; -w,-W; -i (if dig not installed).................. Present
IO::Socket::SSL: -U; -w,-W; -i (if dig not installed)............. Missing
Time::HiRes: -C cpu sleep (not required); --debug timers.......... Present
JSON::PP: -G wayland, --output json (in CoreModules, slower)...... Present
Cpanel::JSON::XS: -G wayland, --output json (faster).............. Missing
JSON::XS: -G wayland, --output json (legacy)...................... Missing
XML::Dumper: --output xml - Crude and raw......................... Missing
Net::FTP: --debug 21,22........................................... Present

The following recommended Perl modules are missing:
IO::Socket::SSL
pacman: perl-io-socket-ssl
Cpanel::JSON::XS
pacman: perl-cpanel-json-xs
JSON::XS
pacman: perl-json-xs
XML::Dumper
pacman: perl-xml-dumper
------------------------------------------------------------------------------
Test: recommended directories:

/dev: -l,-u,-o,-p,-P,-D disk partition data....................... Present
/dev/disk/by-id: -D serial numbers................................ Present
/dev/disk/by-label: -l,-o,-p,-P partition labels.................. Present
/dev/disk/by-path: -D extra data.................................. Present
/dev/disk/by-uuid: -u,-o,-p,-P partition uuid..................... Present
/sys/class/dmi/id: -M system, motherboard, bios................... Present
/sys/class/hwmon: -s sensor data (fallback if no lm-sensors)...... Present

All recommended directories are present
------------------------------------------------------------------------------
Test: recommended files:

Note that not all of these are used by every system, so if one is missing it's
usually not a big deal.

/etc/lsb-release: -S distro version data (older version).......... Present
/etc/os-release: -S distro version data (newer version)........... Present
/proc/asound/cards: -A sound card data............................ Present
/proc/asound/version: -A ALSA data................................ Present
/proc/cpuinfo: -C cpu data........................................ Present
/proc/mdstat: -R mdraid data (if you use dm-raid)................. Missing
/proc/meminfo: -I,-tm, -m memory data............................. Present
/proc/modules: -G module data (sometimes)......................... Present
/proc/mounts: -P,-p partition advanced data....................... Present
/proc/scsi/scsi: -D Advanced hard disk data (used rarely)......... Present
/var/log/Xorg.0.log: -G graphics driver load status............... Present

The following recommended files are missing:
/proc/mdstat
------------------------------------------------------------------------------
Ok, all done with the checks. Have a nice day.

Hi there, welcome to the forum.
Give a look at the update GRUB section of this Wiki page:

4 Likes

It turns out that if I use the Garuda Boot Options on the Sway installation, it changes the boot order, but I still haven’t figured out how to change the name.

The link you sent me mentions changing the names of EFI directories in the boot partition, which seems dangerous. Back in the old days, we’d update /boot/grub.cfg for just the labels - does grub now use the directory names to name the entries in the menu?

can you check this file an post here the output?

open in terminal this command

sudo nano /etc/default/grub

maybe this work i dont know i never did names but i found this guide. Please do a Backup or Snapshot before do changes.im not in charge for it.i dont know that those work for Garuda too.So maybe wait for some other responds.

Changing Arch Linux Boot Entries

To change the names of boot entries on Arch Linux, you can follow these steps:

  1. Edit GRUB Configuration:
  • Open the GRUB configuration file /etc/default/grub using a text editor like nano or vim:
sudo nano /etc/default/grub
  • Modify the GRUB_DISTRIBUTOR variable to change the name of the boot entry. For example, to change it to “My OS”, you can set:
GRUB_DISTRIBUTOR="My OS"
  • Save the changes and exit the editor.
  1. Update GRUB:
  • Run the command to update the GRUB configuration:
sudo update-grub
  1. Edit Systemd-boot Entries:
  • If you are using systemd-boot, you can edit the boot entries in /boot/loader/entries/. For example, to rename the Arch Linux entry, you can edit /boot/loader/entries/arch.conf:
sudo nano /boot/loader/entries/arch.conf
  • Change the title line to reflect the new name you want:
title My OS
  1. Update Systemd-boot:
  • After editing the entries, you may need to regenerate the boot loader configuration:
sudo bootctl update

These steps should allow you to change the names of your boot entries to reflect your desired names.

Please do a Backup or Snapshot before do changes.im not in charge for it.i dont know that those work for Garuda too.So maybe wait for some other responds.

It’s not, if you make the changes correctly.
The point of the issue here is in my opinion that every time you install a new Garuda spin on an existing EFI system partition, the installer (actually the GRUB installation step) creates a new Garuda folder there, which overwrites the existing one. So the old bootloader is lost.
You change both the existing folder name and the GRUB_DISTRIBUTOR and the new installation won’t cause troubles.
Or if you already have two systems but one bootloader (the one of the last installation), you make the change for that second one, chroot into the first installation and reinstall the GRUB, possibly, but not necessarily, following that procedure again after, to use also in this case a different name (or you’ll have a normal Garuda name).
Of course it’s a critical step and a somewhat complex process; that’s why multibooting is discouraged and not supported here. We can’t spend much time solving user-created problems for something we suggest not to do.
But I’ve done it more than once with no issues, and for sure i’m not the only one.

PS:
You may want to forgive me. I thought I was responding to a similar topic opened that same day here !!! :rofl: :rofl:
If your systems are bootable you don’t need to chroot. Just login and apply the procedure in both. The concept applies anyway, in my opinion.

4 Likes

It’s not, if you make the changes correctly.

Never underestimate the power of an idiot.

That idiot being, namely, me.

I think what we’ll try is changing GRUB_DISTRIBUTOR on the second partition. I don’t know if that will work or not, but we can try. As for changing EFI directories… yeah, I’m too scared for that, and if it’s isn’t supported anyway, I’ll just leave things alone.

Let me ask this - is there a way to have some sort of persistent config on the live USB version? The sway version I don’t use as often as I do Dragonized, and maybe I can just mount the second drive for my Steam library.

OK, so after rebooting into Sway, changing the GRUB_DISTRIBUTOR name in /etc/default/grub, and then running update-grub, I can now see that the Sway installation name has changed, and the boot order is persisted from Garuda Boot Options. The other name didn’t change even though I changed GRUB_DISTRIBUTOR in /etc/default/grub in Dragonized, but two out of three ain’t bad. That’s about as far as I want to take this experiment. Even with a backup, I have them set up just the way I need them, so I don’t want to rock the boat.

Well, the issue with grub+btrfs+snaphot can you handle also simple.
Your default boot is dragonized. Then change inside bios the boot order. (F2)
Reboot in os dragonized.
Insert in /etc/grud.d/40_custom your sway.
Example like this

What you type inside
menuentry ‘xxx’ → ‘Garuda Sway’ or what you like.
The correct uuid and all the options you can see if you take a look inside the grub.conf from your sway (nvme1) folder /boot/grub/grub.cfg
(copy&paste)
then
the option GRUB_DISABLE_OS_PROBER=false to =true (/etc/default/grub/)
→ run inside console sudo update-grub
or
if you have knowledge about the scripts 10_linux & 30_os-prober (/etc/grub.d) change it to what you prefer.

1 Like

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