linux4noobs

1386 readers

1 users here now

linux4noobs

Noob Friendly, Expert Enabling

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.

Seeking Support?

Mention your Linux distro and relevant system details.
Describe what you've tried so far.
Share your solution even if you found it yourself.
Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
Properly format any scripts, code, logs, or error messages.
Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.

Community Rules

Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
Posts must be Linux oriented
Spam or affiliate links will not be tolerated.

founded 1 year ago

MODERATORS

PlutoParty

How to find out what bootloader I'm using and then disable the 5 seconds delay? (lemmy.ml)

submitted 6 months ago by [email protected] to c/linux4noobs

8 comments fedilink hide all child comments

I never booted into more than one OS, I only have one. I've no use for the 5 seconds for selection.

I've no clue what bootloader I have... I think not grub, because I cannot find any grub files besides

/etc/grub.d/ with 2 files: 15_ostree 35_fwupd

and grub-mkconfig -o /boot/grub/grub.cfg results in bash: grub-mkconfig: command not found

I remember in the past turning off the 5 seconds, but I reinstalled my system after Plasma 6 release.

I use EndeavourOS with KDE if that matters/helps.

top 8 comments

sorted by: hot top controversial new old

[–] [email protected] 10 points 6 months ago* (last edited 6 months ago) (2 children)

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!

[–] [email protected] 5 points 6 months ago (1 children)

And it worked. Thank you so so so so much. <3 🥰 ❤️‍🔥

[–] [email protected] -3 points 6 months ago* (last edited 6 months ago) (1 children)

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

[–] [email protected] 4 points 6 months ago (1 children)

sudo nano efi/loader/loader.conf

[insert password]

and edit the timeout to =0 (or whatever your preference may be)

[–] [email protected] 2 points 6 months ago

Awesome, thanks. I wonder how the config file got changed in the first place

[–] [email protected] 1 points 6 months ago

This file exists! Now I need to figure out how to make it work. Thank you!~ 🥰

[–] fourwd 2 points 6 months ago (1 children)

EndeavorOS offers a choice of systemd-boot and GRUB. So, if you don't have GRUB, you probably have systemd-boot.

[–] [email protected] 3 points 6 months ago

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.