Over the last 6 months I switched 3 machines to EndeavourOS. So far so good… until this Dell Laptop.
The laptop had Ubuntu on it. I just moved the root filesystem with ubuntu to a subfolder, and installed EOS into the same partition. The first time I chose “online update” and grub. The online update failed. So I did the offline one. Then grub failed. So then I did the offline one with systemd.
It booted perfectly! With Secure Boot on! I am not sure which boot option it used, but I suspect it was the systemd one.
Then came the first update. It complained about not being able to overwrite BOOTX64.EFI. (So I renamed it. It wrote a BOOTX64.EFI that’s almost 10x bigger. But only after I figured out that the command to run is not the dracut rebuild command,. which I ran, but that I just needed to reinstall “linux” (the kernel package))
Reboot. Nope. It had the systemd boot and grub, and Ubuntu’s systemd and grub options. Nothing worked. The only error I could see was one about virtual console setup
that failed. (Did I make the mistake of not choosing EN-US in the installer?! The one time I think… okay lets try the suggested default.) Sometimes it came to “Enter password for maintenance” - but I couldn’t type! Sometimes it would just have a lot more failures, starting with “Failed to start D-Bus System Message Bus”. But I could still boot with init=/bin/bash
and look around…
Then I made the first real mistake. I turned off secure boot. I tried every iteration, similar failures. When I got to “Enter password for mainenance” I just couldn’t type.
Then I turned back on Secure boot. Now nothing worked anymore.
So I turned it back off, and tried Legacy boot. Nope no legacy boot options even got to a bootloader.
UEFI with Secure Boot Off again.
After going though several “Enter password for maintenance” with me not being able to type, I finally figured out that if I boot with Grub, and type in:
root=(hd0,1) # my EFI partition
linux /b84d666250124276b26f1eabb362ceb8/6.8.7-arch1-1/linux root=/dev/sda2 rw
initrd /b84d666250124276b26f1eabb362ceb8/6.8.7-arch1-1/initrd
boot
Then it would boot.
I couldn’t find a grub.cfg
so I suppose its embedded in one of the other files. (Which one?)
Now it boots, still shows the “virtual console setup” error, but I get lightdm! (Hurray!)
But when I log into lightdm, the screen goes black, and keyboard dies. (Ctrl+alt+del doesn’t shut down or reboot) - Power button once (not forced) shuts it down, so it’s not completely non-responsive.
If I follow the same, and open a virtual console, manually run Xorg, xterm, mate-session, everything works.
Mysteries:
- Why doesn’t any input works after grub or systemd boot, on some of the sessions?
- Why would lightdm login do that? Running things manually without lightdm, work?
(There are more but I have to go now… :-()