Bad time to find out my timeshift snapshots have not been getting created since Dec. 13 due to some corruption with exclude/include lists. Found this out when trying to manually create a snapshot before replacing my Nvidia drivers, and the snapshot failed.
While the path to replacement is clear, I’d like to have me a failsafe. Now I gotta wait to create a new snapshot that needs to capture everything from scratch. Would be done in a few seconds if I was on BTRFS, but with EXT4 on a system running for 3 years?
That seems normal. If you had installed the 580xx drivers from AUR you would have already removed the nvidia driver so it would not be part of your update.
I have heard of Vulcan, but pretty much only in the gaming context, which is something I don’t do other than the occasional very simple scroll shooter so I can mindlessly just KILL , KILL , KILLLLLLLLLLL alien scum!!
I’m sure if I tried running one of the more modern flagship games with my 1050, it would go up in flames! It would also leave me without my main workstation, because my Ryzen 7 5700X is not an APU, just a PCU, and the only other GPU I have is a much older AGP one I cannot put in any of my PC’s but the Athlon one it’s in.
On the other hand, if it’s not only a Steam , Vulcan … thing, and has any advantages over, or in addition to Nouveau for other applications, like graphics editors, FreeCad, Kdenlive… than I’m interested.
Cool ,and thanks ddnn (whatever that stands for) ! Now I have to dive in and figure out what all I need to install and configure, without causing any problems and get the best use of it all.
After upgrading to EndeavourOS Ganymede, my NVIDIA stack got caught in the driver transition (Arch moving to the nvidia-open* packages). On my RTX 2060 12GB (Turing), I initially ended up with severe window flicker / compositor-related glitches under Xfce on X11.
Disabling the Xfce compositor immediately improved stability.
What I tried (worked):
Updated to the current repo driver (590.x on my system now) so all NVIDIA packages are consistent again (nvidia-open-dkms, nvidia-utils, lib32-nvidia-utils all same series).
Then re-enabled compositor safely by setting Xfce vblank mode to xpresent:
After moving to 590 and using xpresent, the compositor appears stable again. Gaming was also fine with compositor disabled (acceptable workaround while troubleshooting).
just for your info
there is no flicking windows with mate , Xfce have not changed in december , only driver nvidia and they have introduced many bug in the serie 119 version.
version 105 was working , and they have not revert for 580-dkms , with your 20xx video card you can use 590 but they have not fixed trouble on flicking windows.
asking on other ( this is no us , this is compositor xfce ) is not a good future for theses drivers series , and remember how much nvidia have in money and what team dev Xfce have in the money.
nvidia-inst is currently not very useful because of the changes in Nvidia packages. But it will be modified to support the existing situation. This will happen likely after the Christmas holidays.
Note that nvidia-inst does not support AUR packages, so for GPUs older than the Turing family it will choose the nouveau kernel driver.
So it is up to the user to install packages from the AUR.
There’s also nvidia-all github site that may be helpful in such cases.
AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.
Yeah but it’s more about that Arch Linux only officially supports the packages from their own repos but than do the exact opposite with this and then advise to use an AUR PKGBUILD. It’s more about that than about using a corporate supported distribution.