• Nisaea@lemmy.sdf.org
    link
    fedilink
    arrow-up
    0
    ·
    8 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
      0
      ·
      8 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
          0
          ·
          8 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
            0
            ·
            8 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
              0
              ·
              8 months ago

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