• MildlyArdvark@feddit.dk
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I never understood these. Arch has always been rock solid for me and in 10 years or so I have never had to chroot to fix an issue. The most annoying issues have been related to PGP signatures or old certificates but those have been easily fixed.

    What is it you people do to your arch installs that fucks them up so much?

    • Eavolution@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      The only time is during setup once I forgot to download iwd so I had to chroot back in to install that from within the installer.

    • s4if@lemmy.my.id
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago
      • Nvidia driver (not me, I’m poor)
      • dubious/niche AUR packages
      • Wrong settings on BIOS/UEFI
      • Windows Update on dual-boot setup (sometimes)

      I don’t know why, but my archlinux bootloader always disappear if I connet bootable disk when my computer is booting, lol…

        • s4if@lemmy.my.id
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Some custom or git version of application. Once a time I need to use sddm git to fix bug with my hylrland.

      • Tb0n3@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        It’s possible your uefi has a thing about default EFI boot names. I ended up changing mine to just boot because if I update the bios it clears everything and doesn’t automatically pick up any EFI except boot.

        • MonsiuerPatEBrown@reddthat.com
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          My advice is that you make sure you use a full unblemished calf for sacrifice with gilded horns of gold.

          If you don’t gild the horns and burn the fatty thigh parts in the fire then it will never boot.