316
I don't think I'll continue using Arch, btw
(lemmy.ohaa.xyz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Aug 2024
316 points (87.6% liked)
linuxmemes
20707 readers
410 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
arch-chrootyour mounted root filesystem/bootmkinitcpio -p linuxSteps 1,2 and 3 are the entry way to solve all "unbootable Arch" problems by the way, presuming you know what needs to be changed to fix it of course.
I'd gladly take an Arch wiki article
https://wiki.archlinux.org/title/Chroot
+
https://wiki.archlinux.org/title/Mkinitcpio
For a while, I had to do this after every kernel update
Turns out, i accidentally had two
/bootfolders. One was is own partition, and the other was on the rootfs partition. When Arch booted, the separate partition was mounted over the rootfs/bootdir, "shadowing" itExcept, UEFI / GRUB was still pointing to the rootfs partition. So when pacman installed a kernel update, it wasn't able to update the kernel that UEFI was booting, but it was able to update the kernel modules
Kernel no likey when kernel modules are newer than the kernel itself