Hello.
I’m trying to install the NVIDIA proprietary driver on Debian 12 with MSI GeForce GTX 1660 Super Gaming X, but I’m having a problem with colors and resolution (throughout the system, not just in TTY). This occurs both when installing the driver from the repositories and when installing the driver from the site. This issue has already been raised, but it has not yet been resolved.
Is there any way to fix this bug?
What version of the video driver and the kernel do you use? 6.11 kernel is not fully compatible with 560 at this time. Need to update from nvidia or apply fixes.
On Debian I tested with kernel version 6.1 and drivers versions 535.183 and 550.120. I also installed Arch, where kernel version is 6.11, and driver version is 560.35. Now this abnormal behavior remains only on the login screen, in TTY and KDE Plasma everything is fine, but I would like to solve the problem once and for all and return to Debian.
Where can I see the progress of the error resolution, does Nvidia have a bug tracker for example? How long will it take to fix it? Is there anything I can do right now, maybe apply a patch? And is there any way to make sure that Nvidia knows about this bug and is working on it?
don’t know. At the moment nvidia has a lot of problems with video driver and when releasing a new version should include these fixes as they already exist in branch 500.
Probably internal. In fact this forum and repository on github are the only places where you can report bugs.
But as you can see they don’t care about such not mass errors. My questions were not answered, except by me.
Given that you are currently using version 535.183 it will probably be an eternity before the version reaches the current at this moment. Try asking on the debian forum if they can use newer video driver and kernel. Fix that I gave the reference to only fits for driver 560
Try to install archlinux with 6.10 kernel and 560 driver, to make sure the problem completely disappear.
But as you can see they don’t care about such not mass errors. My questions were not answered, except by me.
It’s very sad to see such an attitude, but there’s nothing we can do. Either way, I’ll write an issue on their GitHub repository. It’s worth a try.
Try asking on the debian forum if they can use newer video driver and kernel.
The maximum kernel version that can be installed is 6.10 from backports, along with the latest driver version from the site.
Try to install archlinux with 6.10 kernel and 560 driver, to make sure the problem completely disappear.
I have Arch installed now, only the current kernel version is 6.11, I understand that this has an effect. How can I understand whether the patch you specified has been applied or not?
I also noticed that the problem only appears when using X11 (i.e. with SDDM or when running an X11 session of KDE Plasma), on Wayland and in TTY everything works.
UPD 1: I’ll try to get rid of X11 in SDDM.
UPD 2: I was able to work around this problem. I wrote the following in /etc/sddm.conf.d/nvidia-fix.conf:
[General]
DisplayServer=wayland
[Wayland]
CompositorCommand=weston --shell=kiosk
Having previously installed the weston package. There are still issues with the two keyboard layouts, but I might get to that later (I’ll update the post).
However, the issue is not completely resolved, so I will not mark it as such, hoping that this will influence the appearance of a fix.
Video driver package version must be at least 560.35.03-14, this should be enough in archlinux. If not, add kernel parameters nvidia_drm.modeset=1 nvidia_drm.fbdev=1
I can’t tell you how the fixes are applied in debian packages, because I haven’t worked with it
Yes, it is
If I remember correctly I updated to 560.35.03-16 on Arch today, so the patch should be applied, but it still doesn’t fix the bug :(
Hi all,
Thank you for reporting the issue. This is being tracked internally at NVBug #4932437. I will provide an update when a fix is available.
Thank you
1 Like
So, it’s been more than two months, is there any progress?
Hi @greatdng ,
Sorry, we do not have an update yet. Can you please capture the EDID (binary format) from the failing display and attach it to this thread.
The instructions are available here - Managing a Display EDID on Linux | NVIDIA under Saving EDID to file.
Too bad. Anyway, here’s the EDID - edid.bin.zip (321 Bytes).
1 Like
Thank you. I have attached it to the internal bug for Engineering review.
Does your monitor OSD settings have a Color menu? Can you please share the input color format value if available?
If I understand correctly, yes, such a menu exists. All colors are set to 50 percent, Low Blue Light is disabled.
Hi @greatdng ,
What we are trying to understand is if/why the display may be interpreting an RGB signal as YUV, which could explain the color shift. Some displays have a setting that allows overriding RGB/YUV, which can produce similar results if set incorrectly.
The report from TTY green screen on nvidia geforce gtx1650 HDMI Display proprietary driver and TTY green screen on Linux 6.11 indicated that the problem was limited to the TTY (not X / Wayland), and went away when nvidia-drm was loaded with parameters modeset=1 and fbdev=1.
In Green TTY Bug - #7 by greatdng , you mention that you are only encountering the issue in X11 now, not in a TTY or Wayland session, which seems like a slightly different issue. Could you capture a bug report when X is running and the issue is reproducing? Run ‘sudo nvidia-bug-report.sh’ and attach the resulting ‘nvidia-bug-report.log.gz’.
Thanks!
Never heard of YUV, didn’t find it mentioned in the documentation or in the OSD of the display. By the way, the monitor is DEXP DF24H1, maybe this will help debug the problem.
Perhaps the problems are indeed somewhat different. In Debian I had this bug in both TTY and X11 (Wayland not tested). On Arch the problem only appears in X11. I’m not sure, but it may be the effect of this patch. Boot parameters had no effect.
I logged into a KDE X11 session and executed the script from Konsole. The bug was there. Here is the generated archive - nvidia-bug-report.log.gz (548.7 KB).
Sorry about the long delay. It appears that something about your display’s EDID is telling the driver that the 1080p@60Hz mode requires YUV420, but the display is failing to go into YUV420 mode. The former issue may or may not be a driver bug, currently being looked into, but the latter issue is almost certainly a problem with the display.
In the meantime you may be able to work around it by setting this in xorg.conf:
Option “ModeValidation” “HDMI-0: NoEdidHDMI2Check”