Messed update, fastfetch claims to run arch after kernel fix

I borked my system bootloader yesterday by not following the system update guide in here. Managed to get it fixed by using live usb and arch-chroot to reinstall the kernels in my EFI partition.

Mostly everything seems to have been fixed but I noticed that fastfetch now automatically shows Arch btw instead of Endeavour OS

So the question is, since I’m not coming up with any issues (for now) is this something that could lead to trouble later on and if so is there a way to fix without clean install of Endeavour?

Trouble? Unlikely.

You should be able to fix this by comparing the /etc/*-release files with standard EnOS contents:

emk2203@nuc10i3fnk:~$ ls /etc/*-release
 /etc/arch-release   /etc/lsb-release   /etc/os-release
emk2203@nuc10i3fnk:~$ cat /etc/arch-release

emk2203@nuc10i3fnk:~$ cat /etc/lsb-release
DISTRIB_ID="EndeavourOS"
DISTRIB_RELEASE="rolling"
DISTRIB_DESCRIPTION="EndeavourOS Linux"
DISTRIB_CODENAME="rolling"
emk2203@nuc10i3fnk:~$ cat /etc/os-release
NAME="EndeavourOS"
PRETTY_NAME="EndeavourOS"
ID="endeavouros"
ID_LIKE="arch"
BUILD_ID="2023.08.05"
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://endeavouros.com"
DOCUMENTATION_URL="https://discovery.endeavouros.com"
SUPPORT_URL="https://forum.endeavouros.com"
BUG_REPORT_URL="https://forum.endeavouros.com/c/general-system/endeavouros-installation"
PRIVACY_POLICY_URL="https://endeavouros.com/privacy-policy-2"
LOGO="endeavouros"

This is how it looks for me.

Cheers, I guess my worry was that if there had been some file link shenanigans that could affect some future updates. But seeing the only differences here are in the /etc/os-release. It looks to be okay to leave it be.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.