this post was submitted on 04 Aug 2024
319 points (87.7% liked)

linuxmemes

20750 readers
296 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith
zephyr
319
I don't think I'll continue using Arch, btw (lemmy.ohaa.xyz)
submitted 1 month ago by [email protected] to c/linuxmemes
114 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 33 points 1 month ago* (last edited 1 month ago) (2 children)
  • Boot to usb
  • Mount your root filesystem
  • arch-chroot your mounted root filesystem
  • mount /boot
  • mkinitcpio -p linux

Steps 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.

[–] [email protected] 3 points 1 month ago* (last edited 1 month ago)

For a while, I had to do this after every kernel update

Turns out, i accidentally had two /boot folders. One was is own partition, and the other was on the rootfs partition. When Arch booted, the separate partition was mounted over the rootfs /boot dir, "shadowing" it

Except, 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