Please describe the issue in as much detail as possible, including any errors and traces.
I run a laptop which has both an intel iGPU and an NVIDIA GPU. I use suse-prime to offload the NVIDIA GPU, so that my monitors are run by the iGPU and any heavy calculations are put on to the NVIDIA GPU. It only turns on the NVIDIA GPU when it needs to, in order to save battery.
My issue is that howdy is turning on that GPU, and I would rather it just stick to the iGPU to avoid high battery consumption. The only settings I have changed in howdy's config is setting my device path and raising the dark threshold to 80. It should not be using open_cnn, so I expected howdy to use my iGPU instead.
Important note: I know that suse-prime recommends to change some environment variables when I wish to run an application with my dGPU, but I have not needed to. It seems to automatically detect when it needs to run to play games, so I suspect that the software is somehow "asking" to use my dGPU, which is why I suspect this may be an issue with howdy.
I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): openSUSE Tumbleweed
That is going to be dlib deciding to use the much faster GPU. I'm not sure what the fix is there, but you could try to dig into why and when it decides that
Please describe the issue in as much detail as possible, including any errors and traces.
I run a laptop which has both an intel iGPU and an NVIDIA GPU. I use suse-prime to offload the NVIDIA GPU, so that my monitors are run by the iGPU and any heavy calculations are put on to the NVIDIA GPU. It only turns on the NVIDIA GPU when it needs to, in order to save battery.
My issue is that howdy is turning on that GPU, and I would rather it just stick to the iGPU to avoid high battery consumption. The only settings I have changed in howdy's config is setting my device path and raising the dark threshold to 80. It should not be using open_cnn, so I expected howdy to use my iGPU instead.
Important note: I know that suse-prime recommends to change some environment variables when I wish to run an application with my dGPU, but I have not needed to. It seems to automatically detect when it needs to run to play games, so I suspect that the software is somehow "asking" to use my dGPU, which is why I suspect this may be an issue with howdy.
I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): openSUSE Tumbleweed
Howdy version (
sudo howdy version
): Howdy 2.6.1