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:
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:
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:
>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.
Please attach the corresponding dmesg output.
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.
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.
Created attachment 140977 [details]
Gotcha. Log attached.
Also, I spoke with a friend using the same GPU, they are able to reproduce the issue.
sway users have reported this bug has been fixed in the latest kernel.