• Titou@feddit.de
    link
    fedilink
    arrow-up
    23
    arrow-down
    4
    ·
    10 months ago

    What did you edited ? Arch user here, never had this kind of issue. Also if you managed to install Arch, you should be able to fix it(maybe you switched from terminals, try ctrl+alt+1-9)

    • Nisaea@lemmy.sdf.org
      link
      fedilink
      arrow-up
      22
      arrow-down
      2
      ·
      10 months ago

      You were just lucky. For some of us ut was just about having the wrong hardware at the wrong time.

      Not complaining, I knew the risks going in and still love my distro, but arch updates totally can brick a PC with no PEBCAK involved. It does happen. :3

      • Titou@feddit.de
        link
        fedilink
        arrow-up
        8
        arrow-down
        25
        ·
        10 months ago

        Arch dosn’t break by itself, i’ve used bunch of Arch installations and every time it broke it was because of bad manipulation, not pacman -syu

          • Titou@feddit.de
            link
            fedilink
            arrow-up
            8
            arrow-down
            20
            ·
            10 months ago

            Have you tried it or are you just spreading misinformation ?

            • Skye@lemmy.world
              link
              fedilink
              arrow-up
              11
              ·
              10 months ago

              Arch breaking grub has happened to me twice. Second time I couldn’t even recover the install.

              You learn a lot of good practices by using arch, eg a separate home partitjon, git repositories for your config files, maintaining a clean package tree etc. Installing Arch is also really useful for noobs like me to learn some Linux basics.

              I use Fedora, btw.

              • CatLikeLemming@lemmy.blahaj.zone
                link
                fedilink
                English
                arrow-up
                3
                ·
                10 months ago

                maintaining a clean package tree

                What do you mean by that, specifically? I looked that up online and maybe I’m a bit dumb, but I didn’t find anything that made much sense

                • Skye@lemmy.world
                  link
                  fedilink
                  arrow-up
                  4
                  ·
                  10 months ago

                  I don’t know if that’s a widely recognized term.

                  Pacman used to be really bad at removing unneeded dependencies. I think pretty much every package manager has this facility now. For instant apt auto remove.

                  Suppose you installed gnome to try it out, gnome installs like 1000000 packages. The thing about some of those dependencies is that they’re really useful. It’s not uncommon for another package you have installed to use it as an optional dependency. In that case it doesn’t get flagged for autoremoval when you uninstall gnome.

                  When you apply this logic a couple layers deep they start to compound.

                  Also libraries and random python scripts tend to just exist forever in your system long after you used it lol.

                  I started developing the habit of checking what dependencies are being installed and to uninstall immediately when I realize I don’t need it.

                  This logic applies to language specific managers like cargo or pip too.

                  They all have really good tooling to figure out leaves, orphaned nodes etc. I just didn’t start using those until I got into the arch hype.

            • Nisaea@lemmy.sdf.org
              link
              fedilink
              arrow-up
              6
              ·
              edit-2
              10 months ago

              I was among one of the grub fiasco victims. Thank goodness they rolled it back pretty fast and I knew how to chroot.

            • ulterno@lemmy.kde.social
              link
              fedilink
              English
              arrow-up
              4
              ·
              edit-2
              10 months ago

              A grub breaking thingy happened to me too.
              I was saved by having multiboot, with every OS having their own GRUB version installed. (just selected one using the motherboard’s interface)

              The problem occurred when, after pacman -Syu, I read notes in the output, one of which hinted I would want to update GRUB and went - “Sure, I’ll try the new GRUB update” and ran GRUB update.

              When it didn’t startup after a restart, I just used the debian’s GRUB to login to the OS in question, downgraded GRUB, reinstalled GRUB and then ran pacman -Syu again.

              I feel like mine wasn’t the problem instance that goes on around the web, mostly because:

              1. None of the mentioned fixes worked in my case.
              2. I feel like people won’t go out of their way to update GRUB most of the time.
            • ☭ SaltyIceteaMaker ☭@iusearchlinux.fyi
              link
              fedilink
              arrow-up
              4
              ·
              10 months ago

              I have not experienced it but half of the arch users on reddit seem to have experienced it. Also it’s not a continuous problem but rather a problem with a certain arch and grub version. However the fact it happened once (to many people) means it can happen a second time

          • Titou@feddit.de
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            10 months ago

            How did you installed it ? Official arch repo or self compiled ? And what nvidia drivers are you using ? Nouveau or proprietary one ?

            • guskikalola :linux:@social.vivaldi.net
              link
              fedilink
              arrow-up
              4
              ·
              10 months ago

              @Titou proprietary drivers, dkms version.
              Official repos.

              Both my friend and I experienced this, a few minutes later pahole was reverted to previous version on the repos and the update was delayed until fixes were made.

              I migrated from nvidia to amd last summer and no issues since then ( a few crashes in Minecraft, its the only game capable of crashing the GPU, dont know why or how ).

              • Titou@feddit.de
                link
                fedilink
                arrow-up
                2
                ·
                10 months ago

                Conflict issues is not arch-exclusive(happenned to me on debian sid months ago) but glad to heard you switched to amd

    • Skye@lemmy.world
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      edit-2
      10 months ago

      Sounds like a skill issue. Some people just don’t know how to use Arch.

      Signed,

      Someone who has spent more days reinstalling Arch than using it.

      • yeehaw@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Yeah I dealt with that for a long while. Always used lynx or similar to go download the latest Linux driver from nvidias website, then manually install it lol. What a pain in the ass.

    • MyNamesNotRobert@lemmynsfw.com
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      10 months ago

      I use archinstall. I draw the line at having to use the command line to set up all your stupid partitions. That’s too complicated.