Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.
My google-foo leads to this:
https://discovery.endeavouros.com/installation/systemd-boot/2022/12/
where it looks like an edit to the 'timeout' variable in:
efi/loader/loader.conf
may be a possible solution.
DISCLAIMER: I use Slackware, and know nothing about systemd, etc....so tread carefully, backup, and research a bit before proceeding willy nilly!
And it worked. Thank you so so so so much. <3 ๐ฅฐ โค๏ธโ๐ฅ
Whoa, how did you stop the delay? I have not been able to stop it at all, and I thought it was just s***** computer stuff I didn't understand, which obviously it is, but I thought it was the computer's fault and not my dumb ignorance
sudo nano efi/loader/loader.conf
[insert password]
and edit the timeout to =0 (or whatever your preference may be)
Awesome, thanks. I wonder how the config file got changed in the first place
This file exists! Now I need to figure out how to make it work. Thank you!~ ๐ฅฐ
EndeavorOS offers a choice of systemd-boot and GRUB. So, if you don't have GRUB, you probably have systemd-boot.
The thing is, I don't seem to have systemd-boot files.
Under /boot/ I only have amd-ucode.img and nothing else. Tutorials for systemd-boot mention /boot/loader/loader.conf.
I also don't seem to have the file /ESP/loader/loader.conf anywhere.