Secondary Monitor colours too dark with 7.2 kernel

[koeshi]

On Kernel 7.2 my secondary monitor has the colours far too dark. Going back to 7.1 and 7.0 the issue is not present. As I have not updated in a while I wasn’t sure where the issue came in and at first thought it might be related to this:

@discobot

Graphical artifacts after the update

Probably only affects some combination of amd gpu and monitors.

Workaround: change the “Color accuracy” setting from efficiency to color accuracy. In KDE, this option can be configured under “System Settings → Display & Monitor”

Note that this in theory can increase latency, especially in games.

Which then led me to find that I do not have that colour accuracy option in KDE settings. Searching for it in settings tells me that it is present under Display Configuration, but I cannot actually see that setting.

Any ideas on why kernel 7.2 is causing this issue or why the colour accuracy option is missing for me in KDE settings?

[soundofthunder]

@koeshi

Going back to 7.1 and 7.0

Both of these kernels have reached EOL.

Linux Kernel

I suggest kernel 6.18 (LTS) instead, and perhaps 6.12 (LTS) as your fallback. When kernel 7.3 in more mature, you might try that for size.

@koeshi

Any ideas on why kernel 7.2 is causing this issue

None, but I’m aware there have been a few similar reports - the general resolve seems to be reverting to the LTS kernel, for the time being until more information is known.

Regards.

[koeshi]

Well I’ll just stick with 7.1 for now, its only just EOL. I have the LTS kernels installed as a fallback.

Honestly more concerned right now about the fact that I appear to be missing a setting that should supposedly be there as that issue is present regardless of what kernel version I am on.

[stephane]

you will have to wait for drm - amdgpu

[datamoose]

Do not use EOL, you won’t have any security updates.

You can install the 7.2 kernel with mhwd-kernel -i linux72, or linux618 if you want LTS.

Having security updates is absolutely necessary, your system will be subject to vulnerabilities running on EOL.

[koeshi]

@stephane

you will have to wait for drm - amdgpu

Was that in response to me? If so what do you mean?

@datamoose

Do not use EOL, you won’t have any security updates

I know what I am doing, 7.1 only just went EOL in this release, most likely by the next release 7.3 will be available. I won’t be getting any updates in between anyway. If 7.3 is not out by then I will adjust my active kernel at that time.

[stephane]

check on report issues

Work items · drm / amd · GitLab

[BG405]

@koeshi

I’ve moved your post and its replies to this dedicated Topic for individual attention.

[soundofthunder]

@koeshi

I won’t be getting any updates in between anyway.

@stephane is correct that no updates will be forthcoming for kernel 7.1 now that it’s EOL (two weeks ago). You should also be aware that continuing to use an EOL kernel technically places you in an unsupported state.

Just two of the reasons 6.18 (LTS) was recommended.

@koeshi

most likely by the next release 7.3 will be available

Well, kernel 7.3 RC3 (a release candidate only) was released almost a week ago and is available in Unstable branch. If you wanted to try it now you would need to make the switch from Stable to Unstable.

Switching Branches

Linus Torvalds has announced the third release candidate (RC3) for the upcoming Linux Kernel 7.3 version on September 13, 2026. This release lands right on schedule as the testing phase for Linux 7.3 gains momentum.

Linux Kernel 7.3 RC3 is Officially Released: Here's What's New - OSTechNix

[koeshi]

@soundofthunder

I understand all of that, however it isn’t really EOL until a release cycle goes by without it getting updated. Also even in Manjaro Settings Manager while 7.0 is marked Unsupported 7.1 isn’t.

@stephane

Sorry if I am just being stupid, but I am not sure what you want me to do here. Are you saying that the issue is already reported or that I should raise it there?

---

Mod edit:- Please avoid consecutive posts. Leverage the @mentions feature instead to address different members from the same post.

[scotty65]

@koeshi

Which then led me to find that I do not have that colour accuracy option in KDE settings. Searching for it in settings tells me that it is present under Display Configuration, but I cannot actually see that setting.

Is there any chance you could provide some system information, so that this thread can (hopefully) progress towards a resolution of the issue?

Please provide the output of:

inxi --filter --verbosity=8

or the short form (preferred):

inxi -zv8

• inxi man pages (Arch Manual)

Running `inxi` in `chroot`

@Running `inxi` in `chroot`

If you need to run inxi from within a chroot environment, and find the output is laced with unexpected 12’s, please try again with:

• Add to the long form command: --color=0
• or, change the short form to: inxi -zv8c0

Providing `inxi` when you cannot access your desktop environment

@Providing `inxi` when you cannot access your desktop environment

If you are unable to copy and paste the inxi output due to being unable to access your desktop, but can still access a TTY text session, then you can send the inxi output to a pastebin service:

inxi -zv8c0 | nc termbin.com 9999

Note: the nc command may require installation of the openbsd-netcat package:

pamac install openbsd-netcat

or

sudo pacman -Syu openbsd-netcat

After the output is sent, a link to the inxi output will be provided, which you can then add to your forum post.

If you are not allowed to post links in the forum due to being a new member, you can still paste the link as code by typing 3 backticks ``` on empty lines above and below the pasted URL.

@Your privacy is respected

When inxi is run using the --filter or -z parameters, any personally identifiable information is filtered from the resulting output.

Any code or command output (such as inxi output) should be placed within a scrollable pre-formatted text enclosure according to forum guidelines.

See here for instructions

---

[Mini How-To] format code or command output

Select and copy all the text in the Terminal window (minus the prompt, if you are using zsh).

Then paste the output in between two lines containing three backticks:
```
or three tildes:
~~~

Or:

Copy & paste, then highlight the pasted text and click the </> button at the top of the reply window (easier for smaller outputs).

---

[soundofthunder]

@koeshi

in Manjaro Settings Manager while 7.0 is marked Unsupported 7.1 isn’t.

…and for a very different reason – kernel information in MSM is only updated when the package itself is updated, and that happens less regularly than packages inherited from Arch.

Of course, now there is manjaro-settings-manager-qt6 as well; I’m uncertain whether the infrequent updates hold true for that.

In any case, my comments regarding kernel 7.1 were ancillary and clarifying by nature – the main takeaway which may have been of interest was that you could try kernel 7.3 (rc3) even now, if you wished.