Just a heads up, Nvidia 535.54.03-1 broke my system
Just a heads up, Nvidia 535.54.03-1 broke my system
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
Had a maybe similar issue with steam and nvidia. Enabling multilib-testing and updateing lib32-nvidia-utils fixed it for me
My first linux fix find on Lemmy rather than Reddit. Keep it up!
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.
Mkinitcpio -P didnt work?
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
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...
It causes my laptop to freeze randomly. A complete hard lock requiring long pressing the power button to shut down. I rolled back to the previous version.
I'm still waiting for the
nvidia-beta-dkmspackage to be updated in the AUR, but I was checking to see ifnvidiahad left extra-staging earlier today, guess that happened right after I checked.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
me too, I had to downgrade to 525. 530 made the top 3rd of my screen flicker quite a bit, it was honestly unbearable. 535 has the same problem, I think it's specific to some of the gtx 1660 cards
They had nvidia and lib32-nvidia-utils out of synch with lib32-nvidia-utils not updated to the new version yet. That's been fixed, although I don't know if that'll fix this particular issue.