open-gpu-kernel-modules

tested on 3060, debian 13. freeing 300 megs is easy, just disable gsp. 50 megs is thanks to an undocumented NVReg key, which may or may not work on different cards. (there are similar NVReg keys that didn't work well on my card, however could be useful on others: https://github.com/NVIDIA/open-gpu-kernel-modules/blob/main/... ) the other 50MiB is nvidia kernel module patching, 39 of which was a worst case memory reserve (32 general, and 7 for copy engine stuff). 9mb was reducing page table entry budget (12GB/4KB * 8bytes per PTE is 24megs, i couldnt go lower since it started breaking haha.). and there was around 4.5 megs of old legacy code. i only tested llama.cpp since it's my only usecase.

It is indeed the explanation: https://github.com/NVIDIA/open-gpu-kernel-modules/pull/1014

Wow, someone in the github comments[1] noticed that one of the bug numbers assigned internally for the issue matches to the day the number of days the driver would stay up. 1: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/971...

HDR still doesn't really work on Linux w/ nVidia GPUs. 1. 10bpp color depth is not supported on RGB monitors, which are the majority of LCD displays on the market. Concretely, ARGB2101010 and XRGB2101010 modes are not supported by current nVidia Linux drivers - the drivers only offer ABGR2101010 and XBGR2101010 (See: https://github.com/NVIDIA/open-gpu-kernel-modules/blob/main/...). 2. Common browsers like Chrome and Firefox has no real support for HDR video playback on nVidia Linux drivers. The "HDR" option appears on YouTube, but no HDR color can be displayed with an nVidia GPU. Also, video backgrounds in Google Meet on Chrome are broken with nVidia GPUs and Wayland. Ironically it works on Firefox. This has been broken for a few years and no fix is in sight. The "HDR" toggle you get on Plasma or Mutter is hiding a ton of problems behind