# 580 release feedback & discussion **URL:** \ **Category:** Linux\ **Created:** [August 4, 2025, 2:15pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205 "2025-08-04T14:15:05Z")\ **Posts on this page:** 20\ **Page:** 38
**Author:** ![BlueGoliath](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@BlueGoliath](https://forums.developer.nvidia.com/u/BlueGoliath)\ **Post date:** [November 9, 2025, 3:38pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/770 "2025-11-09T15:38:55Z")
After turning on the display, it showed an image for a second or two then went black and then showed an image at the desktop. I sent a bug report via PM. ---
**Author:** ![kentooo](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kentooo/32/437426_2.png) [@kentooo](https://forums.developer.nvidia.com/u/kentooo)\ **Post date:** [November 9, 2025, 4:31pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/771 "2025-11-09T16:31:03Z")
Some CachyOS users and I have encountered issues after updating to the NVIDIA 580.105.08 driver, which seem similar to the problems you described. The core problem appears to be that the graphics card fails to correctly detect the resolution and refresh rate of monitors connected via HDMI. The issues reported in the forum threads are as follows: 1. Inability to set the correct resolution, [After updating linux-cachyos-nvidia/linux-cachyos-rc-nvidia/linux-cachyos-lts-nvidia(NVIDIA driver version 580.105.08), the dual-screen display resolution is incorrect - #10 by kentooo - Issues & Assistance - CachyOS Forum](https://discuss.cachyos.org/t/after-updating-linux-cachyos-nvidia-linux-cachyos-rc-nvidia-linux-cachyos-lts-nvidia-nvidia-driver-version-580-105-08-the-dual-screen-display-resolution-is-incorrect/18057/10) and [SUddenly missing higher resolution on second monitor - Issues & Assistance - CachyOS Forum](https://discuss.cachyos.org/t/suddenly-missing-higher-resolution-on-second-monitor/18101) 2. Inability to set the correct refresh rate, [After a nvidia graphic driver change I'm stuck at 60 Hz or lower (both in moniter info and on the pc), I should be able to get 144 Hz - Issues & Assistance - CachyOS Forum](https://discuss.cachyos.org/t/after-a-nvidia-graphic-driver-change-im-stuck-at-60-hz-or-lower-both-in-moniter-info-and-on-the-pc-i-should-be-able-to-get-144-hz/18192) The hardware currently reported with these issues on CachyOS includes the GTX 10xx Series and RTX 20/30/40 Series. In the display settings, the correct resolutions and refresh rates are unavailable, and they cannot be forced using `xrandr` either. It has been confirmed that this is not a Desktop Environment issue, as the incorrect resolution is noticeable as early as the system boot splash screen. Furthermore, after rolling back to the 580.95 driver version, these issues no longer occur. ---
**Author:** ![forbyta](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@forbyta](https://forums.developer.nvidia.com/u/forbyta)\ **Post date:** [November 9, 2025, 7:49pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/772 "2025-11-09T19:49:53Z")
I guess it’s encouraging it’s not just me… although in my case I see the problem with all versions of the 580 driver that I’ve tested. I have a multi-boot system with a partition I use just for testing, so it’s easy for me to install any OS, wipe it and reinstall another OS. Maybe I’ll try CachyOS. Since I’ve seen the problem with all versions of 580 is there a way to initially install the 580.95.05 version and then upgrade to 580.105.08? ---
**Author:** ![agarplayerarlon](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@agarplayerarlon](https://forums.developer.nvidia.com/u/agarplayerarlon)\ **Post date:** [November 9, 2025, 11:24pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/773 "2025-11-09T23:24:16Z")
does anyone experience a stutter once in a while when gaming? ---
**Author:** ![vrachatte](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/vrachatte/32/382649_2.png) [@vrachatte](https://forums.developer.nvidia.com/u/vrachatte)\ **Post date:** [November 10, 2025, 5:20am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/774 "2025-11-10T05:20:35Z")
> [@gtschemer](#): > > 5556719 Hello, Engineering team is still working on it, I shall update here once that is fixed. ---
**Author:** ![vrachatte](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/vrachatte/32/382649_2.png) [@vrachatte](https://forums.developer.nvidia.com/u/vrachatte)\ **Post date:** [November 10, 2025, 6:58am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/775 "2025-11-10T06:58:41Z")
Hello, I am archiving this case 5547471 as this is not reproducible at our end. Please check with latest driver and report if you still facing this issue. ---
**Author:** ![amrits](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/amrits/32/14043_2.png) [@amrits](https://forums.developer.nvidia.com/u/amrits)\ **Post date:** [November 10, 2025, 6:58am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/776 "2025-11-10T06:58:58Z")
Hi @BlueGoliath Thanks for sharing logs. ---
**Author:** ![amrits](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/amrits/32/14043_2.png) [@amrits](https://forums.developer.nvidia.com/u/amrits)\ **Post date:** [November 10, 2025, 7:29am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/777 "2025-11-10T07:29:25Z")
Hi @dinosaur We have a bug 5649065 filed internally for corrupted meshes in Second Life viewers. If possible, could you please help to share game save file where you see the corruption. Also please confirm if you are still experiencing GPU idling issue with latest released drivers. ---
**Author:** ![BlueGoliath](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@BlueGoliath](https://forums.developer.nvidia.com/u/BlueGoliath)\ **Post date:** [November 10, 2025, 12:45pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/778 "2025-11-10T12:45:48Z")
I think I found something: if I wiggle my type-c connector to a powered dock sometimes the screen goes black and the same weird graphical static appears partially on the screen despite no displays being connected to it. Is electrical noise causing the issues? ---
**Author:** ![meinertreu74](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@meinertreu74](https://forums.developer.nvidia.com/u/meinertreu74)\ **Post date:** [November 10, 2025, 2:23pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/779 "2025-11-10T14:23:58Z")
Hello, for me “Wayland” (xwayland) is a complete disaster. I can’t even access the login console after restarting the computer, even though the Nvidia driver should be active after installation. I don’t even know the reason or what’s causing it. I’ve put the configuration with two monitors connected to the RTX 5060 via DisplayPort on hold. First, I need to get the main monitor, a Dell U2410, working with the driver, or even just the driver itself working… [nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/g9Dwe6U55QokHnTuHu8msG9fN8W.gz) (364.9 KB) ---
**Author:** ![dinosaur](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@dinosaur](https://forums.developer.nvidia.com/u/dinosaur)\ **Post date:** [November 10, 2025, 4:37pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/780 "2025-11-10T16:37:16Z")
> [@amrits](#): > > We have a bug 5649065 filed internally for corrupted meshes in Second Life viewers. Good… > [@amrits](#): > > If possible, could you please help to share game save file where you see the corruption. Second Life is not a game and does not have “save files”. Second Life is a virtual world: just download a Linux viewer (such as the [Cool VL Viewer](http://sldev.free.fr/)), log into SL (you’ll need to [create an avatar account](https://join.secondlife.com/) if you don’t have one), and find a busy place (in the cited viewer, click the “Search” button to open the search window, “Web search” tab, “Showcase” radio button, and from there find the busiest place for the quickest bug repro: the more avatars around, the fastest the bug will occur). > [@amrits](#): > > Also please confirm if you are still experiencing GPU idling issue with latest released drivers. I did not verify… I now have a workaround via an _/etc/xinit.d/nvidia_ script that takes care of bounding the GPU frequency with _nvidia-smi -lgc 2500,3000_ when it detects a v580 NVIDIA driver… And I have since reverted to the 575.64.05 version which works quite well (but will likely not work any more with Linux 6.18, or at least not without yet another patch over the one I got for 6.17). Has there been any code change in 580.105.08 that could hint that this issue could be solved (I did not see anything even remotely related in the change log) ? ---
**Author:** ![thesword53](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@thesword53](https://forums.developer.nvidia.com/u/thesword53)\ **Post date:** [November 10, 2025, 5:53pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/781 "2025-11-10T17:53:44Z")
> [@Bobovi88](#): > > Added a new environment variable, CUDA\_DISABLE\_PERF\_BOOST, to allow for disabling the default behavior of boosting the GPU to a higher power state when running CUDA applications. Setting this environment variable to ‘1’ will disable the boost. The issue is not fully solved. `CUDA_DISABLE_PERF_BOOST` allows GPU to go below P2 state but the GPU is still limited to P2 state at 100% usage, so we still have performance loss when using NVENC and NVDEC. Is it possible to have another environment variable to also disable this behavior in future versions @amrits? ---
**Author:** ![n7v321](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@n7v321](https://forums.developer.nvidia.com/u/n7v321)\ **Post date:** [November 10, 2025, 11:30pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/782 "2025-11-10T23:30:09Z")
Submitted a bug report /w logs to [linux-bugs@nvidia.com](mailto:linux-bugs@nvidia.com). NVIDIA driver 580.105.08 fails to expose the native 2560x1080 resolution for LG Ultrawide monitors on RTX 5090, despite correctly reading the EDID; downgrading to 580.95.05 resolves the issue. ---
**Author:** ![opisalwaysgreat](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@opisalwaysgreat](https://forums.developer.nvidia.com/u/opisalwaysgreat)\ **Post date:** [November 11, 2025, 3:12am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/783 "2025-11-11T03:12:49Z")
Are there any news on bug 5622970? As it’s still a thing on 580.105.08 (logs here, [No HDMI output on Nobara Linux 42, from Lenovo Legion 7i w/ RTX 3080 - #16 by opisalwaysgreat](https://forums.developer.nvidia.com/t/no-hdmi-output-on-nobara-linux-42-from-lenovo-legion-7i-w-rtx-3080/347774/16) ) ---
**Author:** ![pbo](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/pbo/32/157952_2.png) [@pbo](https://forums.developer.nvidia.com/u/pbo)\ **Post date:** [November 11, 2025, 9:06am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/784 "2025-11-11T09:06:00Z")
Hello, experiencing the issue with the monitor resolution not able to go higher than 1920x1080, like other people reported. Made a thread in the arch testing forum, tested both xorg and wayland. The first link is my thread where you can find with both driver versions: - ```bash xrandr --verbose ``` - ```bash for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done ``` - ```bash eglinfo -B ``` and other links about people experiencing the same results. > **[nvidia-dkms/nvidia-utils 580.105.08-1 / \[testing\] Repo Forum / Arch Linux Forums](https://bbs.archlinux.org/viewtopic.php?id=310035)** > **[After updating...](https://discuss.cachyos.org/t/after-updating-linux-cachyos-nvidia-linux-cachyos-rc-nvidia-linux-cachyos-lts-nvidia-nvidia-driver-version-580-105-08-the-dual-screen-display-resolution-is-incorrect/18057)** > > I am using an RTX 2070 graphics card, with one monitor connected to the DisplayPort interface and another to the HDMI interface. The primary monitor is a PHL 275M1RZ (connected via DP), and the secondary monitor is a DELL P2418D (connected via... > **[Reddit - The heart of the internet](https://www.reddit.com/r/linux_gaming/comments/1othkm9/second_monitor_stuck_to_60hz_after_updating_to/)** ---
**Author:** ![eyerust](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@eyerust](https://forums.developer.nvidia.com/u/eyerust)\ **Post date:** [November 11, 2025, 9:11am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/785 "2025-11-11T09:11:16Z")
Hello there has been an issue with multiple monitors for a few driver releases now. At least when using GNOME. One of the screens randomly freezes up and one has to restart to fix it. Very annoying. This is with version 580.95.05 and a RTX 4090. ```auto Nov 08 16:10:50 mpc kernel: NVRM: GPU at PCI:0000:01:00: GPU-f26ddcc8-c533-52da-a0ce-e7d54c25fcc3 Nov 08 16:10:50 mpc kernel: NVRM: GPU Board Serial Number: 1322123021630 Nov 08 16:10:50 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100ae 00000007 00000000 Nov 08 16:10:50 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000208c 000100ae 00000007 00000000 Nov 08 16:10:50 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002488 000100ae 00000007 00000000 Nov 08 16:10:50 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000248c 000100ae 00000007 00000000 Nov 08 16:18:58 mpc kernel: SELinux: Context system_u:object_r:invalid_bootcinstall_testlabel_t:s0 is not valid (left unmapped). Nov 08 16:19:18 mpc kernel: BTRFS info (device dm-1): scrub: finished on devid 1 with status: 0 Nov 08 16:19:19 mpc kernel: BTRFS info (device dm-1): scrub: finished on devid 2 with status: 0 Nov 08 16:26:30 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100ae 00000007 00000000 Nov 08 16:26:30 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 16:26:30 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 16:28:35 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100a5 00000007 00000000 Nov 08 16:28:35 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000208c 000100a5 00000007 00000000 Nov 08 16:28:35 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002488 000100a5 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100b7 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000208c 000100b7 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002488 000100b7 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000248c 000100b7 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100b7 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000208c 000100b7 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002488 000100b7 00000007 00000000 Nov 08 17:07:22 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000248c 000100b7 00000007 00000000 Nov 08 17:45:34 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 0001009e 00000007 00000000 Nov 08 17:45:34 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:45:34 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:45:34 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100b6 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000208c 000100b6 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002488 000100b6 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000248c 000100b6 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000208c 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002488 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000248c 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100ad 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002088 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000208c 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00002488 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 0000248c 000100af 00000007 00000000 Nov 08 17:57:49 mpc kernel: NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000200 00000001 00000005 0000001a ``` ---
**Author:** ![BlueGoliath](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@BlueGoliath](https://forums.developer.nvidia.com/u/BlueGoliath)\ **Post date:** [November 11, 2025, 10:20am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/786 "2025-11-11T10:20:24Z")
I keep seeing these static noise glitches on my screen. I can’t be the only one seeing these? ---
**Author:** ![Bobovi88](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Bobovi88](https://forums.developer.nvidia.com/u/Bobovi88)\ **Post date:** [November 11, 2025, 10:31am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/787 "2025-11-11T10:31:19Z")
Doesnt happen to me with a 4090 + PG32UCDP connected via DP. Maybe try another cable or underclock the vram? ---
**Author:** ![BlueGoliath](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@BlueGoliath](https://forums.developer.nvidia.com/u/BlueGoliath)\ **Post date:** [November 11, 2025, 11:47am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/788 "2025-11-11T11:47:18Z")
Did a VRAM test: ![occt_memory](https://global.discourse-cdn.com/nvidia/original/4X/7/8/e/78e474afc807468d50de2c656a0b3e0b5facd038.png) I’ve done about 8 hours at this point of OCCT stability tests. Everything passes. Maybe it’s an HDMI cable issue? Funny thing I noticed: if VRAM is near full, GTK applications can sometimes fail to start with a “failed to get graphics context” error. ---
**Author:** ![shelter](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shelter/32/405595_2.png) [@shelter](https://forums.developer.nvidia.com/u/shelter)\ **Post date:** [November 11, 2025, 12:57pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/789 "2025-11-11T12:57:47Z")
> [@BlueGoliath](#): > > Funny thing I noticed: if VRAM is near full, GTK applications can sometimes crash with a “failed to get graphics context” error. GTK4 got a pretty severe Vulkan bug that may cause apps to crash. Probably not the cause of your crash but might be good to know. The GTK devs are aware of it. [Previous page](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205.md?page=37) [Next page](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205.md?page=39)