Installing Hyprland Alongside Dr460nized Edition

[mrdhobbs]

Hi,

I'd like to install this Hyprland Edition alongside my existing KDE Dr460nized Edition. I have my drive split into mulitple partitions, so the Editions will remain seperate from each other. My concern is, what will happen to GRUB, having two "Garuda" entries? If I end up with two Garuda entries in GRUB, how will I be able to identify which is KDE and which is Hyprland?

Many thanks!

garuda-inxi, if necessary:

System:
Kernel: 6.1.51-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=4c53965d-52cb-489d-aab3-ae07a0ff2075 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7B51 v: 1.0
serial: <superuser required>
Mobo: Micro-Star model: MPG Z390 GAMING PLUS (MS-7B51) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 1.80
date: 12/26/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: Intel Core i5-9600KF 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: 0xFA
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB
desc: 1x9 MiB
Speed (MHz): avg: 4465 high: 4487 min/max: 800/4600:4700 scaling:
driver: intel_pstate governor: performance cores: 1: 4486 2: 4487 3: 4400
4: 4486 5: 4487 6: 4449 bogomips: 44412
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: Micro-Star MSI
driver: nvidia v: 535.104.05 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-08) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.0 chip-ID: 10de:2182 class-ID: 0300
Device-2: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2:3 chip-ID: 046d:0825
class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.0
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 110 s-size: 794x333mm (31.26x13.11")
s-diag: 861mm (33.9")
Monitor-1: HDMI-0 res: 3440x1440 dpi: 110 size: 797x333mm (31.38x13.11")
diag: 864mm (34.01") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 535.104.05 renderer: NVIDIA GeForce GTX 1660
Ti/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA TU116 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403
Device-3: C-Media Blue Snowball driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2
chip-ID: 0d8c:0005 class-ID: 0300 serial: <filter>
Device-4: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2:3 chip-ID: 046d:0825
class-ID: 0102 serial: <filter>
API: ALSA v: k6.1.51-1-lts status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.79 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: 3.64 TiB used: 3.19 TiB (87.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Crucial model: CT1000P2SSD8
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: P2CR033 temp: 42.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Crucial model: CT1000P1SSD8
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: P3CR013 temp: 38.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZRX-00L4HB0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 1A01 scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD110
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: A8J0 scheme: MBR
Partition:
ID-1: / raw-size: 46.57 GiB size: 46.57 GiB (100.00%)
used: 36.96 GiB (79.4%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:6
ID-2: /boot/efi raw-size: 619 MiB size: 617.8 MiB (99.80%)
used: 222.3 MiB (36.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3
ID-3: /home raw-size: 46.57 GiB size: 46.57 GiB (100.00%)
used: 36.96 GiB (79.4%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:6
ID-4: /var/log raw-size: 46.57 GiB size: 46.57 GiB (100.00%)
used: 36.96 GiB (79.4%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:6
ID-5: /var/tmp raw-size: 46.57 GiB size: 46.57 GiB (100.00%)
used: 36.96 GiB (79.4%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.28 GiB used: 1.2 MiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 6 dev: /dev/zram0
ID-2: swap-2 type: partition size: 3.91 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 42.0 C pch: 51.0 C mobo: 34.0 C gpu: nvidia
temp: 42 C
Fan Speeds (rpm): fan-1: 0 fan-2: 828 fan-3: 956 fan-4: 760 fan-5: 783
fan-6: 825 fan-7: 0 gpu: nvidia fan: 47%
Info:
Processes: 301 Uptime: 52m wakeups: 4 Memory: total: 32 GiB
available: 31.28 GiB used: 8.67 GiB (27.7%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 2162 libs: 560 tools: octopi,paru Shell: fish
v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.29
Garuda (2.6.16-1):
System install date:     2023-08-07
Last full system update: 2023-09-07 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

[filo]

There are several options.
Personally, I’d reinstall the grub from your current system but giving the entry a different name, e.g. Garuda-Dr460nized. So the new installation will create a new entry called by default Garuda, and that will be Hyprland.
Or you could do like in this solution:

Two Garuda install on two different drives

GRUB - ArchWiki You can add additional custom menu entries by editing /etc/grub.d/40_custom and re-generating /boot/grub/grub.cfg. Or you can create /boot/grub/custom.cfg and add them there. Changes to /boot/grub/custom.cfg do not require re-running grub-mkconfig, since /etc/grub.d/41_custom adds the necessary source statement to the generated configuration file.

But in that thread, I would have gone also for the custom.cfg suggestion in post #5.

[BluishHumility]

You can rename the boot directory and change the GRUB_DISTRIBUTOR= line to be whatever you’d like as described in this guide: Multiple installations on one partition | Garuda Linux wiki

Update Grub

Change the name of the boot directory from “Garuda” to something else so it won’t create a conflict when you install the next ISO. The next installation will also name the boot directory “Garuda”, which will simply overwrite any directory with the same name (this would make our first installation unbootable).

sudo mv /boot/efi/EFI/Garuda /boot/efi/EFI/Gnome

Change the GRUB_DISTRIBUTOR= line in /etc/default/grub to match whatever you just named the boot directory in /boot/efi/EFI/.

sudo micro /etc/default/grub

GRUB_DISTRIBUTOR="Gnome"

If this line does not match the name of a directory in /boot/efi/EFI (the one we just changed above), when you run the grub-install script it will automatically make a completely new directory.

Next, run the Grub installation script.

sudo grub-install ...

I have put “...” to mean “add whatever options are specifically relevant for your Grub installation”. In some cases, grub-install or grub-install --no-nvram is enough. If you are not sure, refer to the document here: GRUB - ArchWiki

Regenerate the Grub configuration file.

sudo update-grub