[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #5 from David Koppelman --- I meant that it's *not* likely I missed anything, due to the multi-second inactivity to suspend time. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #4 from David Koppelman --- (In reply to Nate Graham from comment #3) > Thanks. Out of curiosity, does the discrete GPU also render the logout > screen? The thing that appears when you click "Shut Down." If so, then I'm > guessing the shader-based blur effects they both use are triggering the > behavior. The discrete GPU remains suspended after selecting both shut-down and logout. When I select either of these I get a confirmation screen. The confirmation screen has a black background and no obvious blur effect. After selecting cancel I check the output a GPU status logger which had been checking every half second, and it shows that the GPU remained suspended. (After being used the discrete GPU remains active for several seconds before suspending, so it's likely I missed anything.) BTW, I have the wobbly windows effect active and composited window shadows, and neither results in the discrete GPU being activated. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #3 from Nate Graham --- Thanks. Out of curiosity, does the discrete GPU also render the logout screen? The thing that appears when you click "Shut Down." If so, then I'm guessing the shader-based blur effects they both use are triggering the behavior. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #2 from David Koppelman --- When a system is set up for what Nvidia calls prime render offload, applications by default will use the integrated GPU. In order to use the discrete GPU the application has to have certain environment variables set, usually __NV_PRIME_RENDER_OFFLOAD=1, though others need to be set for Vulkan applications. For details see Chapter 35 in the Nvidia driver readme: http://us.download.nvidia.com/XFree86/Linux-x86_64/530.41.03/README/primerenderoffload.html On my system I only want to use the discrete GPU for graphics intensive applications. I do that by starting these applications with a script that sets the environment variables before launching the application or by appropriate .gdbinit settings (if I'm debugging one of those applications). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 Nate Graham changed: What|Removed |Added Summary|kscreenlocker uses discrete |kscreenlocker uses discrete |GPU when integrated GPU is |GPU when integrated GPU is |available. |available CC||n...@kde.org --- Comment #1 from Nate Graham --- In general, how do you determine which GPU an app uses? I'm not very familiar with this type of hardware. -- You are receiving this mail because: You are watching all bug changes.
