Choppy external monitor performance (<20 FPS) when using Wayland and the nvidia GPU mode
Herschenglime opened this issue · 1 comments
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
nvidia-driver-530:
Installed: 530.41.03-0ubuntu0.22.04.2
Candidate: 530.41.03-0ubuntu0.22.04.2
Version table:
*** 530.41.03-0ubuntu0.22.04.2 500
500 http://apt.pop-os.org/ubuntu jammy-security/restricted amd64 Packages
500 http://apt.pop-os.org/ubuntu jammy-updates/restricted amd64 Packages
100 /var/lib/dpkg/status
Issue/Bug Description:
After an update, the NVIDIA GTX 1650 Ti in my HP Spectre eb000 seems as if it is no longer being used even in nvidia-only mode, resulting in choppy rendering of the desktop on my external monitor while the laptop lid is closed. It's as if the laptop is still in hybrid mode - nvidia-smi shows gpu utilization of 0%. In settings under the About tab, grapics are shown as "Mesa Intel® UHD Graphics (CML GT2) / Mesa Intel® UHD Graphics (CML GT2)".
I'm not sure if this was caused by updating the nvidia drivers or something else, but the last version of the nvidia drivers that I recall working were 525.85.05. I updated to 530 to see if that might have fixed the issue, but it seems to not have.
Expected behavior:
nvidia GPU is used exclusively for rendering, smoother animations and mouse movement on external monitor.
Other Notes:
I am using a Wayland session.
After rolling back to a snapshot from before the suspected updates went through to test, I realized that Wayland also seems to have had that issue before and that the "smooth" performance I noticed was probably a result of me using Xorg without realizing it. I'm editing the name of the bug to better reflect what I now see to be the issue.