As others here, I have to get a fresh install of EndeavouOS.
In first attempts, it won’t to install selecting grub as bootloader. Then, I tried the no bootloader option; it installs but then I’m not able to run properly the arch-root commands so I can’t iinstall any bootloader after installation.
Then, I tried to install EOS with the systemd-boot option; it installs but there’s no possibility to select EndeavourOS from UEFI and, maybe worst, Windows bootloader run from the ssd with EndeavourOS was installed!!! (Windows is installed on a nvme, and yes, I checked thousand times the partitions where I was installing EOS before runnig the install program!). I tried to install both with secure boot enabled and disabled and both online/offline installation, with Calamar’s auto-partitioning and partitioning with my own specs.
I read about a lot of people is having the same problem so, I’m wondering if the iso need a change on the bootloader side…
Please share the install log so we can see what is happening.
When you use systemd-boot, it isn’t called “EndeavourOS” but there should be an option for it.
I sent the log online after the failed installation program asked to do it…
I tried to download another iso from another mirror but nothing to do!
I miss EndeavourOS so much and I’m still having problems installing it. I also tried to enable/disable stuff from UEFI but it seems the bootloader is having the same problem.
can you share the url?
This is where your error is.
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
2024-11-17 - 13:35:21 [2]: WARNING: [PYTHON JOB]: "Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=endeavouros --force' returned non-zero exit status 1."
2024-11-17 - 13:35:21 [6]: [PYTHON JOB]: "stdout:Installing for x86_64-efi platform.\nCould not prepare Boot variable: No space left on device\ngrub-install: error: efibootmgr failed to register the boot entry: Input/output error."
No. I tried to install partitioning by my self (leaving 1024MiB for ESP and 1024 MiB for boot), either erasing the whole ssd leaving calamares do the job. I tried both enabling/disabling secure boot but the problem remain.
The only way to install EOSis as descripted above (see first post).
Ad
Selecting systemd-boot, the ssd with EOS appear in the UEFI as the Windows boot manager (indeed, then it boot windows installed on another ssd!)
Could other operating systems installed on other ssd break something about bootloader during the installation process (in particular, Win10)?
Being EndeavourOS a rolling release distro, I still have both Artemis and Artemis Neo isos. If I try to reinstall from that isos, Will I have the new Neo in all for all after upgrading with pacman -Syyu or I have to set something manually after that?
The Neo iso still gives me problem…
you should install with the latest ISO
while older ISO’s will boot and work its really not advisable to install from old ISO do to the fact that packages get updated and sometimes things change so what worked when the ISO was made isn’t guaranteed to work after getting updated.
IF you have an updated system then there is nothing you need to do.
So, I will wait for the next release with bug fixes because this one seems to be impossible to install on my system.
Now I’m using Devuan for general purpose use, but I heavily miss EndeavourOS as my first choice. I would try again to install without any bootloader, bit I find complicated installing it with arch-root.
Finally I came back home!!!
After a BIOS/UEFI update, installation get complete! I wonder why! Ok, I tried different settings to try to make my thunderbolt device work, but I turned on/off the same settings everytime! As a non-technical guy, I think that secretely something as changed in the BIOS under the hood without any permission by the user or maybe some iso changes that won’t “meet” the needs of the old version of my BIOS/UEFI.
Anyway, now I here again! The only aspect that I still had encoutered while installing is the long time to install EOS. I didn’t remember that long when I installed Artemis. But it doesn’t matter! I am really happy to have the possibility to use this OS again!
Glad to hear that it finally worked out! Updates to the UEFI firmware can iron out some bugs or introduce new ones. It might be helpful to read up on what’s being changed in the future 