Rarely something breaks my system (other than me messing with it), but this update was one of them. At first I thought it was the kernel upgrade that also came by today, but downgrading this pkg to 530 ~ made X and gdm work again

  • g7s@lemmy.mlEnglish
    3·
    1 year ago

    Had a maybe similar issue with steam and nvidia. Enabling multilib-testing and updateing lib32-nvidia-utils fixed it for me

    • shadowintheday@beehaw.orgOPEnglish
      1·
      1 year ago

      Nope, I tried mkinitcpio -P and bootctl in arch-croot with a live usb, reinstalling kernels, installing normal linux kernel instead of zen, only downgrading nvidia worked

  • UrbenLegend@lemmy.mlEnglish
    2·
    1 year ago

    I was able to boot just fine with 535, but Steam couldn’t launch because lib32-nvidia-utils didn’t make it out of multilib-testing yet. Temporarily enabling it and installing that package seemed to fix things for me. I’d check if that’s related to your issue.

  • EccTM@lemmy.mlEnglish
    1·
    1 year ago

    I’m still waiting for the nvidia-beta-dkms package to be updated in the AUR, but I was checking to see if nvidia had left extra-staging earlier today, guess that happened right after I checked.

    • linkbattosai@lemmy.oneEnglish
      1·
      1 year ago

      I noticed this recently myself. I’m growing tired of the Nvidia Proprietary drivers. I just picked up an Arc A770 to see if it suits my need better. Most of the games that I play are older and non triple A anyway so I don’t mind a performance dip

  • CaptainJack42@discuss.tchncs.deEnglish
    1·
    1 year ago

    Oh man not again, I was so glad to get an AMD GPU on my home desktop and not have to bother with this crap anymore and than my boss gave me a work laptop with a 3050…

  • rossome!@lemmy.mlEnglish
    1·
    1 year ago

    I have been using the Frogging-Family Nvidia PKGBUILD for ages now. Easiest way I have seen to stay on the latest versions of the proprietary drivers with the least amount of headaches.