I know there’s a handful of these posts already in the forum, but so far I’ve had no luck with any of the solutions. Maybe I did something incorrectly along the way, but I’ll list off what I’ve attempted so far. I’m not opposed to trying things again, so if you think I’ve done something incorrectly feel free to just tell me to do it again.
I want to say there’s more, but currently it’s 2 AM and I’ve honestly forgotten at this point. I am running GRUB. I’m not sure if that’s an issue since I seem to see a mix of systemd-boot and grub directions when looking around, but leaning towards systemd-boot.
I also have three exports that I managed to pass through to this Windows install via a shared mounted drive. I do dual-boot Windows on this machine, but Endeavour and Windows have their own separate drives. I tried to paste them below, but they were much too long. If you want me to pass them along as screenshots or a specific section, let me know. I have the output for:
journalctl -xb
systemctl status boot-efi.mount
dmesg
If this is a totally lost cause I should have the means to clean reinstall, but I’d like to save that as a last resort. Thank you for your help.
One thing that was happening before this occurred that might be of interest? I was having some really weird issues with the ffmpeg package. I installed obs-studio-browser from the AUR via yay some time ago. obs-studio-browser requires a variation of ffmpeg called ffmpeg-obs.
I’ve never had issues with these being conflicting packages and I know I’ve done at least a handful of full system upgrades since installing obs-studio-browser (using sudo pacman -Syu followed by yay -Syu and usually a system reboot). So this really threw me off.
I didn’t do anything too crazy I don’t think. I started to periodically uninstall packages, and right as I was about to make a post to these forums I tried sudo pacman -Syu one more time. Somehow the system upgrade just went through and then I went ahead and attempted to reinstall obs-browser-studio. I wasn’t able to build it for whatever reason, but after I gave up on that I rebooted and ended up in the current situation I’m in.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=CD8D-9DDF /boot/efi vfat fmask=0137,dmask=0027 0 2
UUID=824b4841-9e5e-4fd6-ae2c-4153a5c43b41 / ext4 noatime 0 1
UUID=04e1699c-9411-4b24-bb0c-871fc6a89857 swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
# Game SSD
UUID=94383BAF383B8EEC /mnt/SteamGames ntfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
# Backup HDD
UUID=ffd1c3b8-7b11-41f9-882f-cc5ebb37f378 /mnt/Backups ext4 rw,relatime 0 0
In this case you need to reinstall the kernel packages. If the OP has kernel-install-for-dracut installed, they probably don’t have the latest kernels in /boot
This combined with pacman -S linux linux-headers linux-zen linux-zen-headers and grub-mkconfig -o /boot/grub/grub.cfg did the trick!
So at some point before this all happened (like weeks ago roughly) I believe I uninstalled eos-dracut in favor of kernel-install-for-dracut. I can’t recall why this was the case / what tutorial I had ended up blindly following that made me do this, but I’m fairly certain not having eos-dracut was my doing.
Thank you both for your help, I greatly appreciate it.
