https://bugs.freedesktop.org/show_bug.cgi?id=107459
Bug ID: 107459 Summary: Atomically set gamma ramps are not applied until TTY switch Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: sir@cmpwn.com
When atomically setting gamma ramps on AMDGPU (specifically ), the changes don't take effect until switching to another TTY and back again. Using the legacy DRM interface works as expected.
To reproduce, build and run the rootston Wayland compositor:
https://github.com/swaywm/wlroots
We will shortly be merging this patch for a new gamma control protocol extension, which you will need to apply if we haven't merged it by the time you attempt it:
https://github.com/swaywm/wlroots/pull/1157
An sample program will be available in the build directory, ./examples/gamma-control, which can adjust gamma. By default this will use the atomic interface, set WLR_DRM_NO_ATOMIC=1 before starting rootston to use the legacy interface. Our atomic gamma code is here:
https://github.com/swaywm/wlroots/blob/master/backend/drm/atomic.c#L199-L230
https://bugs.freedesktop.org/show_bug.cgi?id=107459
--- Comment #1 from Drew DeVault sir@cmpwn.com ---
When atomically setting gamma ramps on AMDGPU (specifically ), the changes don't take effect until switching to another TTY and back again. Using the legacy DRM interface works as expected.
Specifically the RX 550, that is.
https://bugs.freedesktop.org/show_bug.cgi?id=107459
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |harry.wentland@amd.com
--- Comment #2 from Michel Dänzer michel@daenzer.net --- Please attach the corresponding dmesg output.
https://bugs.freedesktop.org/show_bug.cgi?id=107459
--- Comment #3 from Drew DeVault sir@cmpwn.com --- Sorry for the delay. I did the following:
dmesg -n debug # Reproduce problem dmesg -n info # Examine dmesg
There was nothing new written to the log.
https://bugs.freedesktop.org/show_bug.cgi?id=107459
--- Comment #4 from Michel Dänzer michel@daenzer.net --- I mean just the output of dmesg without any arguments, to see various information about the initialization of the driver and the kernel in general.
https://bugs.freedesktop.org/show_bug.cgi?id=107459
--- Comment #5 from Drew DeVault sir@cmpwn.com --- Created attachment 140977 --> https://bugs.freedesktop.org/attachment.cgi?id=140977&action=edit dmesg.log
Gotcha. Log attached.
Also, I spoke with a friend using the same GPU, they are able to reproduce the issue.
https://bugs.freedesktop.org/show_bug.cgi?id=107459
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #140977|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=107459
--- Comment #6 from emersion contact@emersion.fr --- sway users have reported this bug has been fixed in the latest kernel.
https://bugs.freedesktop.org/show_bug.cgi?id=107459
emersion contact@emersion.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org