Closed StayBlue closed 1 week ago
Sorry, I am not a maintainer of the Nvidia drivers. I only made some very minor changes to the Nvidia NixOS module that have since been reverted.
When setting open = false;, it should disable the GSP firmware.
This definitely is wrong, if using the open driver the firmware is required, but in theory using the GSP with the proprietary driver will free up resources that the CPU/driver would normally handle.
What I can see happening is adding an option to enable/disable the gsp firmware, with additional defaults/validation for the open driver.
When setting open = false;, it should disable the GSP firmware.
This definitely is wrong, if using the open driver the firmware is required, but in theory using the GSP with the proprietary driver will free up resources that the CPU/driver would normally handle.
What I can see happening is adding an option to enable/disable the gsp firmware, with additional defaults/validation for the open driver.
I only considered this a bug because the open = false;
option did what I expected it to do on the 550 series. Setting the kernel parameter as described in the changelog disables the GSP firmware. I can close this issue if this is expected behavior.
Describe the bug
When using the
production
driver instead oflatest
, settingopen = false;
inhardware.nvidia
in my nixOS configuration. I use this command to check if GSP is being used or not.On
latest
, it prints out the driver version, and onproduction
, it prints out N/A. This likely has to do with this change in the 555 series of drivers (source):Steps To Reproduce
Steps to reproduce the behavior:
package
inhardware.nvidia
tolatest
.open = false;
inhardware.nvidia
.nvidia-smi -q | grep "GSP"
and see that it says N/A.Expected behavior
When setting
open = false;
, it should disable the GSP firmware.Screenshots
N/A
Additional context
N/A
Notify maintainers
@abbradar @aidalgol @NickCao @Kiskae
Metadata
Add a :+1: reaction to issues you find important.