I’m having problems to propely install the system, the install always fails when trying to install the bootloader and because of that the installation isn’t finished properly and even if i use a different bootloader (in my case rEFInd) the system will come missing some important configurations (https://forum.endeavouros.com/t/systemctl-enable-not-working-no-login-screen-and-no-internet-by-default )
installer log from live session:
Hardware information:
Boot log:
Yes. If it fails to load the bootloader, the installation is stopped in the middle.
You could choose the no bootloader option. That would let the install finish properly.
Then you could install the bootloader after.
I tried to do that but then rEFInd won’t recognize the system
Oh and it’s normal that when i select this no bootloader option, the install gives me some sort of “error” on the end? Like, it doesn’t say successfully installed, it gives me some bootloader related error, different from this one tho
Yeah, that is known issue if you select no bootloader on an offline install. It is fixed in our next ISO which is currently in testing.
Oooh, so i should just wait? rEFInd will be able to recognize the system once this is fixed?
I am not sure about refind, but it will fix the error you are getting when selecting no bootloader on an offline install.
In the meantime, it should work if you use an online install.
Online install doesn’t work on my machine, it has too little ram (https://forum.endeavouros.com/t/cant-install-the-sistem-on-online-mode/ )
There are 2 typos:
Cant should be Can't.
Sistem should be System.
Oh, that’s true sorry…
But that influences something? Like, i know its wrong but like, would it affect my post directly? Asking for curiosity
Sadly i cant fix it since the topic has already been closed
No, it is no problem. Your meaning was understood.
Regarding this:
If you want rEFInd to automatically generate a boot entry for you, you need to mount the EFI partition and run refind-install from within the booted OS (even though rEFInd is already on the EFI from the Windows installation). That is what generates the EFI stub that rEFInd boots off of.
The other option is to create a manual boot stanza in your refind.conf, however running refind-install and automatically generating the bootable EFI stub is much easier. Take a look at this part of the ArchWiki article about writing the stanza and you’ll see what I mean: https://wiki.archlinux.org/title/REFInd#For_manual_boot_stanzas
Ooh, but would i need to remove my current refind installation first, or refind-install would just update it?
It will automatically detect that it is already installed and will leave everything as-is, including your refind.conf and any themes or other setting you have set up. The only thing it will do is generate the EFI stub based on the kernel, path to the kernel, and kernel parameters in use at the time you run it.
Hmm, nice! Will try it later, thanks!