NVIDIA
Missing ' conceal_vrr_caps ' kernel parameter in nvidia-modeset.
NVIDIA Open GPU Kernel Modules Version
570.86.16
Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
- [ ] I confirm that this does not happen with the proprietary driver package.
Operating System and Version
Linux Fedora rawhide
Kernel Release
6.12.11-200.fc42.x86_64
Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
- [ ] I am running on a stable kernel release.
Hardware: GPU
RTX 4070 SUPER TI
Describe the bug
Nvidia wrote : Added a new kernel module parameter, 'conceal_vrr_caps', to the nvidia-modeset kernel module. This parameter may be used to enable usage of features on some displays such as ULMB (Ultra Low Motion Blur) which are incompatible with VRR. See the "Direct Rendering Manager Kernel Modesetting" (DRM KMS) chapter of the README for further information.
But this parameter is missing.
$ modinfo nvidia-modeset filename: /lib/modules/6.12.11-200.fc42.x86_64/extra/nvidia-open/nvidia-modeset.ko.xz version: 570.86.16 supported: external license: Dual MIT/GPL srcversion: CEEC263CC157BE95D120625 depends: nvidia,video name: nvidia_modeset retpoline: Y vermagic: 6.12.11-200.fc42.x86_64 SMP preempt mod_unload
parm: output_rounding_fix:bool parm: disable_hdmi_frl:bool parm: disable_vrr_memclk_switch:bool parm: hdmi_deepcolor:bool parm: vblank_sem_control:bool parm: opportunistic_display_sync:bool parm: debug_force_color_space:uint parm: enable_overlay_layers:bool parm: fail_malloc:Fail the Nth call to nvkms_alloc (int) parm: malloc_verbose:Report information about malloc calls on module unload (bool) parm: fail_alloc_core_channel:Control testing for hardware core channel allocation failure (int) parm: config_file:Path to the nvidia-modeset configuration file (default: disabled) (charp)
To Reproduce
Use modinfo .
Bug Incidence
Once
nvidia-bug-report.log.gz
No report
More Info
No response
@edpil02 Thank you for reporting this. The changelog entry is inaccurate, and the feature is missing in this release. We will work on getting the feature into a future release and have a clarification changelog entry in the release in the future.
