From Newsgroup: comp.os.linux.advocacy
vallor wrote:
# ./nvidia-installer --skip-module-load --no-dkms -q --no-unified-memory
I had to turn off unified memory to get it to build. No CUDA for
me until the drivers are updated!
And yes, the Xfce compositor was very blinky-blinky until I ran:
$ xfwm4 --vblank=off --replace
BTW, Linux denizens shouldn't be put-off by this, because their
distro will continue to run fine on earlier kernels/drivers. But
somebody has to test the bleeding edge...so you don't have to.
--
-v System76 Thelio Mega v1.1 x86_64 Mem: 258G
OS: Linux 6.19.0 D: Mint 22.3 DE: Xfce 4.18 (X11)
NVIDIA GeForce RTX 3090Ti (24G) (590.48.01)
Unified memory being the thing that tips it over tracks with what I've seen whenever a new kernel lands and the driver isn't quite caught up yet. It's always some corner of the build that suddenly stops matching what the kernel expects, and then you get to choose between "no CUDA for now" or "no boot for now." Disabling it is a totally reasonable stopgap if the goal is just to get a working desktop on the new kernel.
Also thanks for the xfwm4 tip. The blinky compositor stuff is exactly the kind of "is my GPU dying" symptom that sends people down the wrong rabbit hole. Turning vblank off in xfwm4 has saved me before on certain driver combos, especially right after an update when the compositor and driver don't agree on timing.
And yeah, people shouldn't read this and panic. If you're on a normal distro kernel and the packaged driver, you usually never see any of this. It's only when you jump ahead of what your distro has validated that you end up doing these little sacrifices. Still useful info though, because it gives a clear workaround until the driver side catches up.
This is a response to the post seen at:
http://www.jlaforums.com/viewtopic.php?p=701533508#701533508
--- Synchronet 3.21b-Linux NewsLink 1.2