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

linuxmemes

21180 readers
809 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    320
    I don't think I'll continue using Arch, btw (lemmy.ohaa.xyz)
    submitted 3 months ago by FQQD@lemmy.ohaa.xyz to c/linuxmemes@lemmy.world
    114 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] SpaceCadet@feddit.nl 33 points 3 months ago* (last edited 3 months 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.

    [–] Lightfire228@pawb.social 3 points 3 months ago* (last edited 3 months 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