❯ ls -al /boot
Permission denied: /boot - code: 13
Skipped 1 directories due to permission denied:
/boot
~
❯ sudo ls -al /boot
[sudo] password for wombat:
total 420972
drwx------ 6 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Nov 15 15:57 ..
drwx------ 4 root root 4096 Nov 15 10:02 76c04ffb82cd4f5b85f7fb454c06fde1
drwx------ 5 root root 4096 Nov 14 23:43 dbb9dd44f7dd4296a394b1cef921ff63
drwx------ 5 root root 4096 Apr 23 2025 EFI
-rwx------ 1 root root 225256521 Nov 15 10:02 initramfs-linux-cachyos.img
-rwx------ 1 root root 159550021 Nov 15 10:02 initramfs-linux-cachyos-lts.img
-rwx------ 1 root root 14934016 Nov 11 06:07 intel-ucode.img
drwx------ 4 root root 4096 Nov 15 17:38 loader
-rwx------ 1 root root 16339135 Nov 15 10:00 vmlinuz-linux-cachyos
-rwx------ 1 root root 14963200 Nov 15 10:00 vmlinuz-linux-cachyos-lts
~
❯
1 Like
if he reboots and taps F12 while it comes up…and it sees two distinct bootable operating systems then what would that mean? that’s an ‘if’ though
1 Like
Well, as I ALWAYS have every important file, image, document, and config backed up on both Mega, and 2 external SSDs, I may just go ahead and start fresh with new installs. Experiment a bit. I have the rest of the weekend to nerd out.
Your EOS’ kernels seem to be there so that’s fine.
I am suspecting that perhaps something has gone wrong with the loader/entries/ conf files. But I am not sure. Could you check for the sake of ruling out the eventuality?
This should be easy to fix, follow the arch-chroot instructions from the EOS wiki. You can do it right from within cachyos. Then run reinstall-kernels from within the chroot.
1 Like
I am not sure if he would see two operating system there either.
He would see one option for “Linux Boot Manager” and that one seemingly only shows the entries in the screenshot in
Interesting…
❯ sudo bootctl status
[sudo] password for wombat:
System:
Firmware: UEFI 2.70 (American Megatrends 5.12)
Firmware Arch: x64
Secure Boot: disabled (setup)
TPM2 Support: yes
Measured UKI: no
Boot into FW: supported
Current Boot Loader:
Product: systemd-boot 257.8-2-arch
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Load drop-in drivers
✓ Support Type #1 sort-key field
✓ Support @saved pseudo-entry
✓ Support Type #1 devicetree field
✓ Enroll SecureBoot keys
✓ Retain SHIM protocols
✓ Menu can be disabled
✓ Multi-Profile UKIs are supported
✗ Loader reports network boot URL
✗ Support Type #1 uki field
✗ Support Type #1 uki-url field
✗ Loader reports TPM2 active PCR banks
Partition: /dev/disk/by-partuuid/0126c0d9-6b98-4089-a481-b341966ac38c
Loader: └─/boot//EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI
Current Entry: linux-cachyos.conf
Random Seed:
System Token: set
Exists: yes
Available Boot Loaders on ESP:
ESP: /boot (/dev/disk/by-partuuid/0126c0d9-6b98-4089-a481-b341966ac38c)
File: ├─/boot//EFI/systemd/systemd-bootx64.efi (systemd-boot 257.8-2-arch)
└─/boot//EFI/BOOT/BOOTX64.EFI (systemd-boot 257.8-2-arch)
Boot Loaders Listed in EFI Variables:
Title: Linux Boot Manager
ID: 0x0005
Status: active, boot-order
Partition: /dev/disk/by-partuuid/0126c0d9-6b98-4089-a481-b341966ac38c
File: └─/boot//EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI
Title: UEFI OS
ID: 0x0006
Status: active, boot-order
Partition: /dev/disk/by-partuuid/0126c0d9-6b98-4089-a481-b341966ac38c
File: └─/boot//EFI/BOOT/BOOTX64.EFI
Boot Loader Entry Locations:
ESP: /boot (/dev/disk/by-partuuid/0126c0d9-6b98-4089-a481-b341966ac38c, $BOOT)
config: /boot//loader/loader.conf
token: cachyos
Default Boot Loader Entry:
type: Boot Loader Specification Type #1 (.conf)
title: Linux Zen
id: linux-zen.conf
source: /boot//loader/entries/linux-zen.conf (on the EFI System Partition)
linux: /boot//vmlinuz-linux-zen (No such file or directory)
initrd: /boot//initramfs-linux-zen.img (No such file or directory)
options: root=UUID=83ff6666-4c45-4c25-b23a-037c57cecb10 rw rootflags=subvol=/@ zswap.enabled=0 nowatchdog splash
WARNING: default boot entry is broken
lines 40-70/70 (END)
1 Like
the F12 screen doesn’t always duplicate the normal boot screen in my experience. sometimes yeah, sometimes no.
that’s why I mentioned it as a booting variable
Yeah, your entries are missing. Solution is the same as I mentioned above a couple of times already.
1 Like
Well, according to this your EOS’ loader entries seem to be gone. That is why they don’t show in the boot menu screen.
reinstall-kernels in chroot as advised by @dalto should regenerate them.
1 Like
I went with the BIG DADDY. Installing Arch on the PC. I’ll get back to EOS on the laptop.
whole new gameplan. nice
1 Like
When finally the cause of the issue was found and a solution presented you chose to nuke CachyOS and install Arch instead?
Funny thing is I also tried to install Cachyos last night, it was against better judgement .
Because I have a multi boot environment with Refind as bootloader, I tried to install it with Refind as bootloader .
It already threw some errors during install, and got hung on 38%, so after waiting sometime I decided to go on with other things.
In the past had it crashing during usage, once, than twice, so I thought third time lucky.
Well I could swear that I heard somebody laughing in the background when it crashed on me the third time.
This is just about the only distro that gave me so much troubles, and I have installed a lot of Distros in the past. So from now on I call it Crashy.
Perhaps you should have installed it without a boot -loader/-manager and used the refind you have already installed to creat new boot stanzas for Cashy. After all that is the point of refind, I think, isn’t it?
Obvious case of YMMV, it seems.
I have CachyOS on different multiboot constellations. No problem on my end installing, booting and running. I maintain it as I would any Arch-based distros and that’s about it. Not a Single crash so far for months.
Well I would have installed it without a bootloader, but that option was not available if I recall it correctly, because otherwise I always do that this way if possible.
Also there was another distro that gave me the Refind option that behaved just like it should and gave me no problem at all. Think it was either reborn or bluestar.
1 Like
In that case systemd or even Grub would have been the better option for not interfering with your already installed refind. I guess after creating manual boot stanzas for Cashy with your refind you could remove Grub. Though I have never tried such constellation myself.
Pretty much. As I was attempting to address the situation, I wasn’t paying close enough attention and ended up making things worse. I just didn’t feel like tinkering and “un-messing” things any further. So, I just opted for a fresh install of Arch. My laptop, previously a test machine for other distros, will be my dedicated EndeavourOS install.
3 Likes