HomePLAYSTATIONNVIDIA reveal a list of issues with their driver and Wayland

NVIDIA reveal a list of issues with their driver and Wayland

Whereas the state of affairs has improved somewhat for NVIDIA and Wayland, they’re not likely there but and so NVIDIA at the moment are conserving a public listing of the problems cut up between drivers and both protocol or compositor limitations. This follows on from the large splash they made not too long ago with their new open supply Linux GPU kernel modules, which additionally improved Wayland help somewhat too with the 515.43.04 driver that went up on the identical time.

NVIDIA mentioned they anticipate the listing to get shorter over time as “lacking performance is carried out each within the driver and in upstream parts”.

So for these , here is issues as they stand proper now:


  • The VDPAU library, used for {hardware} accelerated video decoding and presentation, doesn’t have native Wayland help and doesn’t work with Xwayland.

  • The NvFBC desktop seize library doesn’t have native Wayland help and doesn’t work with Xwayland.

  • Variable show refresh charge capabilities comparable to G-Sync should not reported by nvidia-drm module, due to this fact this performance will not be accessible on Wayland.

  • Digital actuality shows, such because the SteamVR platform, require help for DRM show leasing which doesn’t at the moment work.

  • EGL_EXT_platform_x11 will not be supported with Xwayland.

  • The nvidia-drm module doesn’t help the GAMMA_LUT, DEGAMMA_LUT, CTM, COLOR_ENCODING, or COLOR_RANGE connector properties, which can affect some compositor options associated to paint correction.

  • The nvidia-settings configuration software has restricted performance on Wayland.

  • Entrance-buffer rendering in GLX doesn’t work with Xwayland.


  • The next workstation options should not supported by any Wayland compositors or the Wayland protocol. They will even seemingly require new EGL extensions or different means to reveal the associated {hardware} performance.

  • There is no such thing as a established public API by way of which Wayland compositors can energy off video reminiscence through RTD3.

  • Xwayland doesn’t present an acceptable mechanism for our driver to synchronize software rendering with presentation, which may trigger visible corruption in some circumstances.

  • Show multiplexers (muxes) are usually utilized in laptops with each built-in and discrete GPUs to offer a direct connection between the discrete GPU and the built-in show (inside mux) or an exterior show (exterior mux). On X11, the show mux will be mechanically switched when a full-screen software is operating on the discrete GPU, enabling enhanced show options and improved efficiency, however no Wayland compositors at the moment help this performance.

  • Oblique GLX doesn’t work with Xwayland as a result of the Glamor rendering engine will not be appropriate with our EGL implementation.

  • {Hardware} overlays can’t be utilized by GLX purposes with Xwayland.

Article taken from GamingOnLinux.com.

Source link



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments