• einfach_orangensaft@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      38
      ·
      1 day ago

      If it where arch, but its manjaro. Somehow during the last kernel update the grub info was not changed to point to the current kernel names…still pointed at the old kernel…and that had been replaced. After figuring all that out in chroot, fix was as simple as changing a single line in that grub file

      • QuazarOmega@lemy.lol
        link
        fedilink
        arrow-up
        55
        arrow-down
        1
        ·
        1 day ago

        Yet another Majaro L? Not one to dunk on random distros, but I’ll always make an exception for Manjaro

      • Lucy :3@feddit.org
        link
        fedilink
        arrow-up
        14
        ·
        1 day ago

        The dangers of relying on a prebuilt system which is maintained … lets just say not state of the art.

        Also, would grub-hook be an option?

        • bzLem0n
          link
          fedilink
          arrow-up
          8
          ·
          1 day ago

          Grub-hook is what I use to prevent this exact situation.

          • Lucy :3@feddit.org
            link
            fedilink
            arrow-up
            9
            ·
            edit-2
            1 day ago

            GRUB-HOOK PACKAGE GIVES YOU STABILITY ON THE SYSTEM YOU LOVE

            THE KINDA STABILITY THAT MAKES YOU BOOGY

            *insert cringe dance*