Hi Everyone.While reading recently about these problems with Grub booting in uefi mode, I came across information about yet another loader, which is the system itself. I tried using uefi on my laptop and ran the Arch installer, choosing the system-boot option instead of GRUB. Unfortunately, Arch dumps to bios after booting and from there I can only boot from the efi manager menu. It seems to me that something went wrong, and I’m wondering if maybe it’s a mistake that I chose to boot from Grub 2 when starting the installer. I’m not sure if anything of what I’ve written here is clear to you
not everything … but i see you try to install archlinux not EndeavourOS… and posting it on the EndeavourOS newbie forum
It should not matter if you boot the installer with grub as long as you install the systemd-bootloader properly and indeed the OS
Yes indeed. My apologies and please move to the appropriate place, unless my predicament cannot be addressed here at all. I installed Arch using the archinstall script.
Contents of loader.conf file
# Created by: archinstall # Created on: 2023-01-24_19-16-07 title Arch Linux (linux-lts) linux /vmlinuz-linux-lts initrd /intel-ucode.img initrd /initramfs-linux-lts.img options root=PARTUUID=d8ba104b-35f0-4ec6-ad26-c102546c196c rw intel_pstate=no_hwp rootfstype=ext4
I wanted to practice it on a different system.
As a heads up, the way archinstall handles systemd-boot and the way EOS does are completely different.
another heads up is the archinstall system saves your passwords for user and encryption in plain text
youre gonna wanna delete the archinstall logs
sounds like somehow you dont have a kernel installed after running the archinstall system. Thats the only reason i can think systemd wouldnt work for you is if it cant find the kernel/initramfs
Ive used archinstall a few dozen times on different systems and never encountered that issue. Where did you mount your efi partiton? archinstall assumes
/boot and doesnt support anything else afaik
So that explains a lot. Most likely EOS will not cause such a problem. @Echoa The kernel is installed. The location is /boot
is it really the case that unencrypted passwords remain in the logs?
if the partition layout is correct and the kernel/initramfs is in /boot then im not sure. The drop to EFI ususally means systemd-boot cant find the system.
What sort of partition layout do you have and what formats are your partitions?
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 238,5G 0 disk └─sda1 8:1 0 238,5G 0 part sdb 8:16 0 119,2G 0 disk ├─sdb1 8:17 0 511M 0 part /boot ├─sdb2 8:18 0 19,5G 0 part / └─sdb3 8:19 0 99,2G 0 part /home sdc 8:32 1 28,8G 0 disk ├─sdc1 8:33 1 28,8G 0 part └─sdc2 8:34 1 32M 0 part
Im assuming /boot is FAT32 correct?
Numer Początek Koniec Rozmiar System plików Nazwa Flaga 17,4kB 1049kB 1031kB Wolne miejsce 1 1049kB 537MB 536MB fat32 primary ładowalna, esp 537MB 538MB 1049kB Wolne miejsce 2 538MB 21,5GB 20,9GB ext4 primary 3 21,5GB 128GB 107GB ext4 primary 128GB 128GB 335kB Wolne miejsce
hmmm…yeah thats bizarre
Honestly, not really sure why systemd-boot cant see your system. It seems like you have it all formatted correctly so it is supposed to just work.
have you tried running archinstall again to see if its repeatable?
I checked the archinstall log file and except for the message that the password is weak, I did not find it. Although I didn’t encrypt the partition, but I didn’t find any user passwords either
Yes, it happened every time. In addition, wanting to use GRUB, the system quite refused to boot, going into grub resuce. Could Ventoy, from which I run the installer, have something to do with all this?
Well hopefully that means they fixed it recently as it was a thing for most of the past year+
Possibly, I know the latest EOS iso has a fuss with Ventoy and i had to put it on its own USB Drive.
I start installer Cassini on Ventoy and it is all good
not on my end it just refuses to boot the iso, but why not give it a try if you have the option to not use Ventoy to see if it helps?
Generally, this was to see how it would work and whether Endeavour Os would survive it. However, if the differences in the use of system-boot are large between the two systems, this whole exercise was pointless. Arch boots, but only from the bios level. Tomorrow I will put together a new installation of Endeavour with the hope that all will be well if I give up grub. Thank you all for your help!
So indeed Endeavour Os has not the slightest trouble with system-boot. However, due to the fact that I don’t quite know how to figure it out yet, I’m having trouble with another kernel showing up in the entries. How can I make the newly added kernel visible in the boot menu?