Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SwayFX does not allow non-primary GPUs to suspend #274

Open
Sid127 opened this issue Feb 15, 2024 · 5 comments
Open

SwayFX does not allow non-primary GPUs to suspend #274

Sid127 opened this issue Feb 15, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@Sid127
Copy link

Sid127 commented Feb 15, 2024

Swayfx currently initializes its DRM backend for every card available on the system, as can be seen in the log I have attached. Yes, I know I'm on the proprietary drivers, but I have also reproduced this using nouveau. This causes the non-primary GPU to stay active, preventing it from engaging in a runtime power management routine (entering D3cold state), increasing power consumption.

Relevant log lines:

00:00:00.030 [INFO] [wlr] [backend/drm/backend.c:200] Initializing DRM backend for /dev/dri/card0 (i915)
00:00:00.030 [DEBUG] [wlr] [backend/drm/drm.c:88] Using atomic DRM interface
00:00:00.030 [DEBUG] [wlr] [backend/drm/drm.c:100] ADDFB2 modifiers supported
00:00:00.030 [INFO] [wlr] [backend/drm/drm.c:253] Found 3 DRM CRTCs
00:00:00.030 [INFO] [wlr] [backend/drm/drm.c:180] Found 9 DRM planes
00:00:00.030 [INFO] [wlr] [backend/drm/backend.c:200] Initializing DRM backend for /dev/dri/card1 (nvidia-drm)
00:00:00.031 [DEBUG] [wlr] [backend/drm/drm.c:88] Using atomic DRM interface
00:00:00.031 [DEBUG] [wlr] [backend/drm/drm.c:100] ADDFB2 modifiers supported
00:00:00.031 [INFO] [wlr] [backend/drm/drm.c:253] Found 4 DRM CRTCs
00:00:00.031 [INFO] [wlr] [backend/drm/drm.c:180] Found 12 DRM planes
@Sid127 Sid127 added the bug Something isn't working label Feb 15, 2024
@WillPower3309
Copy link
Owner

Thanks for raising the issue! I assume this isn't the case for upstream sway, but can you confirm?

@Sid127
Copy link
Author

Sid127 commented Feb 16, 2024

Yes, this is not an issue with upstream, whichever is the current version of sway in the arch repos. It is, however, also an issue on hyprland-git

@swwwee
Copy link

swwwee commented May 29, 2024

I have the same issue with regular sway-1.9, using a 3060M. It is most likely an underlying issue with the nvidia-drivers as a whole, or wlroots not wanting to playing nice (both are possible).

E.g., I have my main monitor plugged into the iGPU to get around nauseating, terrible flickering. And I use reverse-prime, to offload GPU intensive tasks. In theory, the iGPU should only be used, and it is, until a process is offloaded. This powers on the GPU, but it also moves sway onto the graphics stack, preventing the GPU from powering off.

It really sucks, but we cannot control NVIDIA drivers or the wlroots project's stance on said drivers.

@WillPower3309
Copy link
Owner

Yes, this is not an issue with upstream, whichever is the current version of sway in the arch repos. It is, however, also an issue on hyprland-git

To clarify, is this sway-git or was it 1.9?

@Sid127
Copy link
Author

Sid127 commented May 30, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants