Hello, I just updated to mga9 and my script to correct colour saturation, which rely on libvibrant is broken. After some investigation, I observed the absence of this properties (displayed by xrandr --prop) : GAMMA_LUT_SIZE: 4096 range: (0, -1) DEGAMMA_LUT_SIZE: 4096 range: (0, -1) GAMMA_LUT: 0 range: (0, 65535) CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 DEGAMMA_LUT: 0 range: (0, 65535) I managed to pinpoint the issue to this commit in kernel : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0e444a4de6b38c4593a07e4cfb5bf54c40cc79b6 https://lists.freedesktop.org/archives/dri-devel/2022-November/378252.html Reversing the patch restore the previous behaviour, the aforementioned properties are present and I can correct colour saturation. I'm using an AMD radeon RX570 (codename POLARIS) which is DCE 11.2 ( https://wiki.gentoo.org/wiki/AMDGPU ) Can we reverse this in mageia ? thanks Julien
CC: (none) => julien.moragny
Thank you for this report, and learned investigation: identifying the kernel patch which caused the problem! Formidable. As such, assigning to the kernel maintainer.
Assignee: bugsquad => kernel
Summary: Kernel > 6.0.9 disable color saturation (vibrancy) correction => Kernel > 6.0.9 disable color saturation (vibrancy) correction on some amd gpu
Hello, the problem is still present in latest kernel 6.4.16 thanks.
Does kernel-6.5.9-1.mga9 showing the same in backports_testing?
CC: (none) => ghibomgx
Hello, it's the same with the kernel 6.5.9-1 ; the properties are absent and I can't change vibrancy: [jules@tue-amour ~]$ uname -a Linux tue-amour 6.5.9-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Tue Oct 31 03:01:01 UTC 2023 x86_64 GNU/Linux [jules@tue-amour ~]$ $HOME/devel/libvibrant-legacy/build/vibrant-cli/vibrant-cli HDMI-A-0 libvibrant version 1.0.2 Cannot find output HDMI-A-0 in the list of supported outputs, it either does not exist or is not supported [jules@tue-amour ~]$ xrandr --prop |grep LUT [jules@tue-amour ~]$ thanks
Hello, The last update of kernel (6.5.11-5) carrys the revert and fix my problem. Thanks alot. Regard julien FWIW, here is the upstream bug https://gitlab.freedesktop.org/drm/amd/-/issues/2974
Status: NEW => RESOLVEDResolution: (none) => FIXED