Today, I did an online XFCE install of EndeavourOS_Artemis_neo_22_8.iso.
It uses grub version 2:2.06.rxxx.xxxxxxxxxxx-1.
Installation method: Bios, ext4 on baremetal:
Calamares-Installer towards the end got stuck in a loop of grub-mkconfig -o /boot/grub/grub.cfg with no way to finish the installation:
The python-script was always trying to include /dev/sdb1 (my USB-Installer) into grub.cfg but of course couldn’t do it.
The BIG QUESTION: WHY?!
So I exited calamares and did an arch-chroot into the installed system.
There, I first did grub-install --target=i386-pc /dev/sda, then sudo grub-mkconfig -o /boot/grub/grub.cfg.
When I wanted to update, I found NetworkManager.service wasn’t enabled and startet yet.
Next thing, displaymanager service needed to be enabled before being able to boot into the XFCE-GUI.
First update via yay went fine.
Then, installing another kernel (zen) gave more problems… so sudo mkinitcpio -P before the next grub-install, and the subsequent grub-update… long story.
The result, with much tinkering:
P.S. - I wonder, was it the USB-stick, I created with Fedora image writer? It had done the job before well, a week or so ago (with a newer ISO from GitHub).
P.S.S. - Post Editor isn’t giving me the option to summarize some text. The function seems gone.
EDIT:
As @joekampradshowed in his post down below, it could not have been the python-script, but rather the grub-install, or the grub-update strangely breaking into a loop, not allowing calamares to finish the installation successfully.
grub-install runs right before the script to finish EndeavourOS-specific settings and changes (chrooted_cleaner_script) so everything from that is not getting applied to the installed system.
Yeah, I realized that too late. After going through the installer-script searching for potential errors there, I discovered lots things that weren’t finished during install. So I deleted cache and journals all to receive a clean system… oh well.