scrambled screen with nvidia driver

After upgrading from pkg latest I get a scrambled screen

I am on FreeBSD 15.0-RELEASE-p9 FreeBSD 15.0-RELEASE-p9 GENERIC amd64
Video card is NVIDIA Quadro P2000

Installed packages
libva-nvidia-driver-0.0.17 NVDEC-based backend for VAAPI
linux-nvidia-libs-580-580.159.04 NVIDIA graphics libraries and programs (Linux)
nvidia-driver-580-580.159.04 NVIDIA graphics driver userland
nvidia-drm-66-kmod-580-580.159.04.1500068 NVIDIA DRM Kernel Module
nvidia-drm-kmod-580-580.159.04_1 NVIDIA DRM kernel module
nvidia-kmod-580-580.159.04.1500068 NVIDIA graphics driver kernel module
drm-66-kmod-6.6.25.1500068_9 Direct Rendering Manager GPU drivers
drm-kmod-20260508 Direct Rendering Manager (DRM) GPU drivers metaport
drm_info-2.9.0 Dump info about DRM devices
gpu-firmware-kmod-20250109,1 Firmware modules for the drm-kmod drivers
libdrm-2.4.133,1 Direct Rendering Manager library and headers
linux-rl9-libdrm-2.4.123 Rocky Linux Direct Rendering Manager runtime

Xorg.0.log does not show any errors.

Any help is very much appreciated to solve this issue.
 
kld_list: nvidia-drm fusefs coretemp sem cpuctl ichsmb cuse libiconv cd9660_iconv msdosfs_iconv udf_iconv linux64 fdescfs linprocfs linsysfs
 
linux64 fdescfs linprocfs linsysfs
Don't need to load these (don't need to mount them in /etc/fstab either). Just put linux_enable="YES" in rc.conf, it will get automagically done.

Not related to your issue though.
 
Are you hellbent on the DRM driver? Or doesn't matter, as long as it works?

You could try the 'traditional' NVidia driver instead (nvidia-modeset and Driver "nvidia" for Xorg.

Is there an option to go back to the old versions?
Not through packages, unless you still have that older version lingering in /var/cache/pkg/.
 
I am also on latest for packages, and I don't have this problem. I have found that when I have issues with Nvidia, they've almost always been fixed by me first updating ports to latest, then using ports and building nvidia-drm-kmod from ports. (Maybe nvidia-drm-kmod-580 as I have an older Nvdia card). This usually pulls in any needed dependencies and has fixed upgrade problems for me every time save once. I think that what happens is whether you use quarterly or latest, the nvidia modules can get out of sync. (I'm not sure that's the cause--it just seems likely to me).

Secondly, if you're on ZFS, I always do a bectl create working-(date) before an nvidia upgrade--I'm lying, I should say I try to remember to do that, and do, most of the time. This way, if an Nvidia upgrade messes me up, I can go back to the boot environment I had before the upgrade.
 
Thanks, I just assumed that if I built the nvidia kmod it would pull in drm-66 if needed. I just learned somethng.
If it's the fresh installation of graphics drivers, yes.
But if there're already drivers installed via pkg and try forcibly building graphics/nvidia-drm-*-kmod* ports alone, corresponding graphics/drm-*-kmod wouldn't be rebuilt/reinstalled automatically, as there's already the matching one installed via pkg.
 
I just went back to the old packages from pkg quarterly and experience the same problem. Could it also be a hardware issue of the graphics card?
If so, how could I check that?
 
Can you take a photo of you "scrambled video screen" ?
I have an old Kaby-Lake machine with a P2000 , it can start X-windows on it , but when I terminate the X session its not able to return
to the VT screen but shows jumbled blocks of colour on the display.

Its of importance that the SCREEN is powered and connected to the computer when the computer is powered up
so that the SCREENs EDID data is transfered to the graphics card so it can select the proper mode .
 
Can you take a photo of you "scrambled video screen" ?
I have an old Kaby-Lake machine with a P2000 , it can start X-windows on it , but when I terminate the X session its not able to return
to the VT screen but shows jumbled blocks of colour on the display.

Its of importance that the SCREEN is powered and connected to the computer when the computer is powered up
so that the SCREENs EDID data is transfered to the graphics card so it can select the proper mode .
Prior to my actual problem I had the same behavior as you describe when terminating the X session.
Now I see these jumbled blocks of color when trying to start up the X session. The Xorg server terminates immediately after startup.
 
I am running 15-stable on a machine with GT-1030 but just use nvidia-driver and nvidia-kmod packages (not built locally). 580.159.04. As per Nvidia your board NVIDIA Quadro P2000 is supported by the same driver on freebsd. If it helps in my nvidia.conf file I just have the Identifier and Driver lines, no BusID or Option. You certainly don't need nvidia-drm-66-kmod-580-580.159.04.1500068
 
Prior to my actual problem I had the same behavior as you describe when terminating the X session.
Now I see these jumbled blocks of color when trying to start up the X session. The Xorg server terminates immediately after startup.

I think the X session fails to start and when it shuts down directly after failure, you see this P2000 colored blobs on the screen.
As said before in this thread ,try it without the DRM driver

cleanup the installation first .
pkg remove the whole list of packages you listed above.
reinstall nvidia-driver , nvidia-kmod, nvidia-settings nvidia-xconfig
remove nvidia-modeset from /boot/loader.conf
and have only " kld_list: nvidia-modeset " in /etc/rc.conf

I dont think the P2000 will be automatically detected , mine isn't. so it will need an /etc/X11/xorg.conf
or config snippet in /usr/local/etc/X11/xorg.conf.d


Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce RTX 3060"
EndSection

Is what im using in my presently active desktop.
 
I think the X session fails to start and when it shuts down directly after failure, you see this P2000 colored blobs on the screen.
As said before in this thread ,try it without the DRM driver

cleanup the installation first .
pkg remove the whole list of packages you listed above.
reinstall nvidia-driver , nvidia-kmod, nvidia-settings nvidia-xconfig
remove nvidia-modeset from /boot/loader.conf
and have only " kld_list: nvidia-modeset " in /etc/rc.conf

I dont think the P2000 will be automatically detected , mine isn't. so it will need an /etc/X11/xorg.conf
or config snippet in /usr/local/etc/X11/xorg.conf.d


Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce RTX 3060"
EndSection

Is what im using in my presently active desktop.
No success with this minimal configuration. The X Server will terminate immediately after startup
 
If you show us the output of
Code:
kldstat | grep nvidia
sysrc kld_list
grep nvidia /boot/loader.conf
pkg info | grep nvidia
sysctl hw.nvidia
may be we can debug this further...
 
I think the X session fails to start and when it shuts down directly after failure, you see this P2000 colored blobs on the screen.
As said before in this thread ,try it without the DRM driver

cleanup the installation first .
pkg remove the whole list of packages you listed above.
reinstall nvidia-driver , nvidia-kmod, nvidia-settings nvidia-xconfig
remove nvidia-modeset from /boot/loader.conf
and have only " kld_list: nvidia-modeset " in /etc/rc.conf

I dont think the P2000 will be automatically detected , mine isn't. so it will need an /etc/X11/xorg.conf
or config snippet in /usr/local/etc/X11/xorg.conf.d


Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce RTX 3060"
EndSection

Is what im using in my presently active desktop.
The X Server will terminate immediately after startup
This means there's probably some useful information in the Xorg log file. With exactly this minimal configuration after a failed startup of X (in addition to bakul's request), please post:
  • cat /var/log/Xorg.0.log | nc termbin.com 9999 and post the resulting link here.
  • pkg query -x '[%R] %o %n %v' '^drm-(510-|515-|61-|66-)?kmod|(^nvidia-(d|k))' | column -t
 
Back
Top