You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

NVIDIA 550.54.14 driver released as stable

By - | Views: 32,506

NVIDIA today launched the 550.54.14 Linux driver as stable coming with a whole bunch of fixes and improvements, so here's all that's changed.

Seems NVIDIA took on what I said to them about their recent changelogs being confusing for end-users (noted in the previous NVIDIA Beta article), so now they're including a note on changes between this version and the last in the same series. 

So the changes from the previous 550.40.07 Beta to this stable version are:

  • Fixed a bug that caused HDMI FRL displays to flicker or blank when enabling VRR with 8 bits per color channel.
  • Fixed a regression introduced with the 550.40.07 beta driver which caused corrupted window decorations in some applications when running on GNOME.
  • Fixed a bug where vkAcquireNextImageKHR() was not returning VK_ERROR_OUT_OF_DATE_KHR when it should with WSI X11 swapchains.
  • Fixed a bug where fences passed to VkSwapchainPresentFenceInfoEXT could signal earlier than expected when a WSI X11 swap chain becomes out of date.
  • Fixed Xid errors on Hogwarts Legacy and Forza Horizon 4.
  • Added support for the VK_KHR_video_encode_queue, VK_KHR_video_encode_h264, VK_KHR_video_encode_h265 and VK_KHR_video_maintenance1 extensions.
  • Fixed a regression which prevented some Vulkan applications from receiving VK_DEVICE_LOST upon a VT switch, which could lead to the application hanging or behaving incorrectly.
  • Fixed a bug that prevented nvidia-installer from honoring the --gbm-backend-dir command line option.

Meanwhile the changes on top of that when going from the 545.29.06 driver to this version are:

  • Fixed an issue that sometimes caused Wayland applications to run at less than one frame per second on Maxwell, Volta, and Pascal series GPUs.
  • Fixed a bug that caused an intermittent drop in desktop framerate.
  • Fixed a bug that caused “Flip event timeout” messages to be printed to the system log when displays are hotplugged when nvidia-drm is loaded with the fbdev=1 kernel module parameter.
  • Fixed intermittent Xid errors on Horizon Zero Dawn, Metro Exodus, Forza Horizon 5, and Halo Infinite.
  • Fixed a bug which prevented the “NoMaxPClkCheck” mode validation token from working on single-link TMDS (e.g. DVI, HDMI) outputs.
  • Fixed a bug that allowed VRR displays to be driven below their minimum refresh rate, resulting in a blank or flickering image.
  • Added an application profile to improve Kwin performance on hybrid GPU systems by setting OGL_DEDICATED_HW_STATE_PER_CONTEXT=ENABLE_ROBUST.
  • Updated the build process for NVIDIA kernel modules to honor the INSTALL_MOD_DIR Kbuild environment variable.
  • Added support for R8, GR88 and YCbCr GBM formats.
  • Optimized the X driver headless framerate limiter to more closely mimic upstream behavior and prevent it from activating in inconvenient situations. Added a new X config option LimitFrameRateWhenHeadless to disable the headless framerate limiter.
  • Fixed a bug that prevented Gamescope from running when using the NVIDIA Open GPU Kernel modules.
  • Fixed a bug that prevented the installer package from being unpacked on systems where zstd is not installed, when /tmp is mounted noexec.
  • Use transparent huge pages when available for the .text section. This is done through madvise() calls, and requires CONFIG_READ_ONLY_THP_FOR_FS.
  • Changed the name visible in /proc/devices of NVIDIA devices and the NVIDIA control device from “nvidia-frontend” to “nvidia” and “nvidiactl”. Scripts which parse /proc/devices (such as udev rules) may need to be updated. Note that the conventional /dev device paths like /dev/nvidia0 and /dev/nvidiactl remain unchanged.
  • Fixed a bug that could cause some multi-GPU systems to crash on suspend.
  • Fixed a bug that could cause the system to crash when an application is run with __NV_PRIME_RENDER_OFFLOAD=1.
  • Fixed a bug which prevented application profiles from getting applied to PRIME Render Offloaded applications running via Wine.
  • Disabled PRIME Display Offload Sink support for virtual displays on datacenter GPUs. This prevents unusable desktop layouts from getting automatically configured on systems with a mix of physical and virtual displays.
  • Fixed a bug that caused high CPU usage during system suspend, which could lead to the system not entering s2idle in some cases.
  • Fixed a bug that caused the nvidia-settings control panel to crash when running on Wayland with newer versions of libwayland-client.

There's more listed on the official changelog, but a bunch of those were available in older NVIDIA driver releases, as NVIDIA list all changes since the previous Production release.

See the full changelog here.

Article taken from GamingOnLinux.com.
10 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
5 comments

Linux_Rocks Feb 23
I think that screen flicker bug that got fixed was the same one that I was seeing in GZDoom while in the Doom menu. I was wondering WTF was up, cause I hadn't seen it like that before. lol

Yes, I play Doom and Chex Quest on a 4090. 👀
TheRiddick Feb 24
All good.

What I would like NVIDIA to be doing is release a update o NVReflex and Frame Generation support, that be neat.
Xpander Feb 24
Quoting: TheRiddickAll good.

What I would like NVIDIA to be doing is release a update o NVReflex and Frame Generation support, that be neat.

afaik reflex will work once that gets merged:
https://github.com/HansKristian-Work/vkd3d-proton/pull/1739
Quoting: Linux_RocksI think that screen flicker bug that got fixed was the same one that I was seeing in GZDoom while in the Doom menu. I was wondering WTF was up, cause I hadn't seen it like that before. lol

Yes, I play Doom and Chex Quest on a 4090. 👀

Perfectly good game choices, I am more curious about the heavy investment of a 4090, and yet running it on Linux.
Linux_Rocks Feb 25
Quoting: ElamanOpiskelija
Quoting: Linux_RocksI think that screen flicker bug that got fixed was the same one that I was seeing in GZDoom while in the Doom menu. I was wondering WTF was up, cause I hadn't seen it like that before. lol

Yes, I play Doom and Chex Quest on a 4090. 👀

Perfectly good game choices, I am more curious about the heavy investment of a 4090, and yet running it on Linux.
So far great actually. Only issue was needing to set "prefer high performance" and very high image quality in the Nvidia control panel. As the defaults are stupid, and held back the card.

Quake II RTX runs amazing natively. So does everything else that I throw at it in Linux. I multi-boot, so I don't really use Proton all that much. But everything in Linux has been fine outside of this screen flicker thing. At least the menus are still useable, and it does go away in game. Quake II RTX is locked at 144Hz at 4K max settings, and playing GZDoom games at a locked 4K 144Hz is really fast and awesome. lol
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register


Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.