Recent updates make GRUB erroneously probe own Garuda OS

[Duke187]

hi Nyrrion,

its late here so it remembered me on this Topic.

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 also have others de and so on please search in the forum too im out for today and wait for other Reply

i had the issues to with dual boot (also dev isos) but actually installed all on a other ssd so i dont mess with dualboot and hijacking windoof anymore other problems.