|
16 | 16 | # management for Turing generation mobile cards, allowing the dGPU to be |
17 | 17 | # powered down during idle time. |
18 | 18 | # |
19 | | -# NVreg_RegistryDwords=RMIntrLockingMode=1 (default 0) - enables experimental |
20 | | -# switch for better frame-pacing this mainly improves it for high refresh rate |
21 | | -# monitors with VRR or VR headsets. |
22 | | -# |
23 | | -# Note: This only works for PRIME configurations if your dGPU is controlling an |
24 | | -# external monitor. |
25 | | -# |
26 | | -# For example: At 240Hz each frame is expected every 4ms. But if a 1ms |
27 | | -# task—say, in the kernel or on the GSP — runs when a frame is about to be |
28 | | -# displayed, it can delay the rendering. Instead of a neat sequence at T+4ms, |
29 | | -# T+8ms, T+12ms, the frames might appear at T+4ms, T+9ms, T+12ms, etc. This |
30 | | -# shows how even small delays can shift frame timing, potentially impacting |
31 | | -# smooth display output. |
32 | | -# |
33 | | -# NVreg_EnableS0ixPowerManagement=1 (default 0) Enables S0ix for the NVIDIA GPU: |
34 | | -# lets the device enter deep, |
35 | | -# low-power idle states while the system uses s2idle (the S0 low-power idle path), |
36 | | -# reducing battery drain—especially on laptops with recent Intel/AMD |
37 | | -# platforms and Turing/Ampere/Ada GPUs |
38 | | -# |
39 | 19 | options nvidia NVreg_UsePageAttributeTable=1 \ |
40 | 20 | NVreg_InitializeSystemMemoryAllocations=0 \ |
41 | | - NVreg_DynamicPowerManagement=0x02 \ |
42 | | - NVreg_RegistryDwords=RMIntrLockingMode=1 \ |
43 | | - NVreg_EnableS0ixPowerManagement=1 |
44 | | - |
| 21 | + NVreg_DynamicPowerManagement=0x02 |
0 commit comments