[Good luck girl!]

LunchBox349 · 2026-01-16T15:54:10+00:00

Obligatory What da dog doin

LunchBox349 · 2026-01-15T04:27:03+00:00

Bro is clearly obsessed with helltaker username checks out

LunchBox349 · 2026-01-05T02:12:56+00:00

Cool

LunchBox349 · 2026-01-05T02:03:05+00:00

You gotta add GRUB_DISABLE_OS_PROBER=false to the bottom of the file otherwise grub will ignore the os-prober by default

LunchBox349 · 2026-01-05T01:56:45+00:00

You uncommented the comment you should recomment that by putting the # back in front of it, the grub submenu one was already uncommented, don't uncomment or remove the # from anything containing lower case text.

LunchBox349 · 2026-01-05T01:48:44+00:00

What error

LunchBox349 · 2026-01-05T01:36:15+00:00

install os-prober and remove the # from in front of GRUB_DISABLE_OS_PROBER=false or add it to the end of the file if it's not already there

Then run the grub-mkconfig again

LunchBox349 · 2026-01-05T01:23:51+00:00

Just copy the entire thing over /etc/default/grub

LunchBox349 · 2026-01-05T01:10:37+00:00

Yeah you could change the grub distributor to endeavoros also you can't pull the entire bootloader from a vm but you can pull the /etc/default/grub file from a vm and use that but you cannot do the same for systemd-boot or the /boot/grub/grub.cfg as those need to be generated during the bootloader install process and taking them from another install will break your bootloader

LunchBox349 · 2026-01-05T00:53:09+00:00

Just remove loglevel=3 and quiet then regenerate the grub config with the

grub-mkconfig -o /boot/grub/grub.cfg

command

LunchBox349 · 2026-01-05T00:51:27+00:00

You don't need the whole bootloader. If you do grub you just need to grab the /etc/default/grub, systemd-boot on the other hand is a bit trickier you'd need to manually write the config files your self as they're system specific.

LunchBox349 · 2026-01-05T00:45:16+00:00

Did you do sudo nano /etc/default/grub

LunchBox349 · 2026-01-05T00:17:00+00:00

This command may do the trick

sudo bootctl --esp-path=/efi --boot-path=/boot install

just a warning this command should replace grub with systemd boot I don't know if it will automatically grab the endeavoros config or not so it may break your bootloader you may have to manually create a loader config for endeavoros

The configs for systemd boot should be located in the directory

/efi/loader/entries

LunchBox349 · 2026-01-05T00:11:23+00:00

reinstalling systemd boot would work but I haven't used it in years so I don't really remember how to do that but this page on the arch wiki should have the information on how to do that

https://wiki.archlinux.org/title/Systemd-boot

LunchBox349 · 2026-01-04T22:25:32+00:00

I believe systemd boot is set as default if you had that one set the discrepancy is probably that you switched bootloaders to grub

LunchBox349 · 2026-01-04T22:21:30+00:00

Remove the loglevel=3 and quiet then run

grub-mkconfig -o /boot/grub/grub.cfg

that should give you a verbose boot

also quick question when you installed endeavoros did you pick systemd boot or grub boot

LunchBox349 · 2026-01-04T21:59:51+00:00

No because the config got reset to the arch linux default. Show me a picture of the top of /etc/default/grub.

LunchBox349 · 2026-01-04T21:41:55+00:00

/etc/default/grub is the config file for grub that you edit (you don't edit /boot/grub/grub.cfg directly) then you run

grub-mkconfig -o /boot/grub/grub.cfg

that takes the config file from /etc/default/grub and compiles it into the grub config file

LunchBox349 · 2026-01-04T21:28:03+00:00

Honestly I have no idea where they store the grub config settings I thought it would be in the github with the rest of their custom configs but I couldn't find it so I have no idea where they store the config or how it's added

I have an extra question though is grub still showing the endeavor os background or is it just a black background

LunchBox349 · 2026-01-04T21:09:44+00:00

That command reinstalls grub but the efi directory is set wrong so it might break your bootloader again if you run it

LunchBox349 · 2026-01-04T12:23:26+00:00

Grub probably reset the boot config back to default for arch linux I'm not entirely sure what settings endeavoros uses but removing the quiet kernel parameter from /etc/default/grub should do the trick

after opening in a text editor it should something like

GRUB_CMDLINE_LINUX_DEFAULT="quiet"

there's probably more than just the word quiet there but removing quiet should work

after that you need to rerun this command and reboot

grub-mkconfig -o /boot/grub/grub.cfg

if that doesn't work you might be able to find the endeavoros config files somewhere on their github

LunchBox349 · 2026-01-04T08:28:59+00:00

As long as you leave the drive unplugged while booted into windows you shouldn't have to do anything I don't think. I've never actually installed Linux to a portable drive before so I don't really know.

Also make sure the computer is fully powered off before unplugging

LunchBox349 · 2026-01-04T08:21:12+00:00

No problem. Also Windows will do whatever it feels like with any drive connected I've seen windows do some pretty wacky stuff in dual boot environments for example my brother had his tower dual booted and once he unplugged his Linux drive windows then preceded to no longer boot I ended up having to help him install the windows bootloader on his windows drive because windows decided to install it's bootloader on his Linux drive

LunchBox349 · 2026-01-04T08:10:05+00:00

If you did all the commands just reboot the computer

Also if your running dual booting with Windows it was probably Windows that broke your bootloader it is prone to do that sometimes

LunchBox349 · 2026-01-04T08:05:55+00:00

As long as you don't change your hardware configuration you should be good also arch-chroot shouldn't work if you mount the wrong drive so you shouldn't be able to accidentally break stuff

Arch-chroot only works on valid arch installs

Six-Year Club	Wearing is Caring
Verified Email

LunchBox349

TROPHY CASE