I have been playing with KDE Linux for a while now and am very impressed. However, it does exhibit a behaviour that some other distros do too, and that is to modify the boot order to put itself first after an update. For those of us who have more than one distro installed (possibly including Windows) this is not acceptable. Now, after I have done an update I have to open efibootmgr and put my boot system (Refind in my case) back on top. Perhaps it works correctly if grub is used as the bootloader, I don’t know, I haven’t tried it. I’ve never used grub. But Refind is becoming very popular, so it seems to me that an update should respect the existing boot options whatever they may be.
Just my two cents worth.
Thanks for trying out KDE Linux!
It’s not really designed right now to play well in a heterogenous environment where there’s already an EFI system partition and a bootloader. It very much wants to create the ESP itself and use sd-boot. So installing it in an environment where it can’t do that — or where those have to co-exist with pre-existing things — it kind of operating at cross-purposes.
It’s possible we’ll improve multi-boot support in the future. But this is one of those low reward-to-effort ratio projects, since it would require a ton of resources to get right, and only a very small fraction of users are sophisticated enough to maintain a multi-boot setup.
Thanks for the reply.
I didn’t know it would be hard. I don’t know anything about what’s under the hood, so please forgive my ignorance. I’ll just have to remember to reset every time I update!
1 Like