You are only browsing one thread in the discussion! All comments are available on the post page.

Return

Rustmilian , (edited )
@Rustmilian@lemmy.world avatar

kscreen-doctor -o
Then adjust the below command accordingly :
kscreen-doctor output.1.hdr.disable

Make sure you go open a bug report.
When you do, you can use hw-probe and run :
sudo -E hw-probe -all -upload -dump-acpi -decode-acpi
And use the given link in your BR.

ByteBovine OP ,

The monitor does not display with kscreen-doctor -o as it's disconnected.

I will create a bug report.

Rustmilian , (edited )
@Rustmilian@lemmy.world avatar

I see you got it fixed.
When you run hw-prope make sure your offending monitor is connected. hw-prope will help identify the monitor by hardware ID which is used in various areas like kernel space and will help with identifying the exact model of the problem monitor hopefully allowing for devs to reproduce the bug in a lab environment.

ByteBovine OP ,

Added the hw-probe link

Rustmilian ,
@Rustmilian@lemmy.world avatar

Which one of these is the problem monitor?
benq or gigabyte ?

Edit : nvm, I see you already said Gigabyte.

Rustmilian ,
@Rustmilian@lemmy.world avatar

Looking through the probe logs, and seeing that your monitor is using EISA bus and works fine without HDR, there doesn't appear to be any issues on the Linux side of things. My guess is that they didn't implement HDR on the monitors side exactly to spec and that's where the problem resides. So, in this sense some monitor specific quirk fixup code is needed on the Linux side of things to get it working properly. If the devs ask any additional steps from you, be sure to do it and provide feedback.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • [email protected]
  • All magazines