https://bugs.kde.org/show_bug.cgi?id=496631
--- Comment #16 from Evert Vorster <evors...@protonmail.com> ---
OK, it has been a little adventure, but unfortunately I am back here with
nothing good to report.
I adopted the ddcutil-dev-git package in Arch Linux, then updated the dev
branch to the latest branch (2.2.0-dev), and then installed that into my
system.
The output of ddcutil detect has changed:
<code>
[evert@Evert ~]$ ddcutil detect
Invalid display
I2C bus: /dev/i2c-3
DRM connector: card1-eDP-1
EDID synopsis:
Mfg id: BOE - BOE
Model: NE173QHM-NZ2
Product code: 2921 (0x0b69)
Serial number:
Binary serial number: 0 (0x00000000)
Manufacture year: 2022, Week: 24
This monitor does not support DDC/CI. (I2C slave address x37 is
unresponsive.)
Invalid display
I2C bus: /dev/i2c-17
DRM connector: card0-HDMI-A-1
EDID synopsis:
Mfg id: BNQ - UNK
Model: BenQ EX3210U
Product code: 32678 (0x7fa6)
Serial number: ETW5N05026SL0
Binary serial number: 16843009 (0x01010101)
Manufacture year: 2022, Week: 21
This monitor does not support DDC/CI. (I2C slave address x37 is
unresponsive.)
</code>
So, ddcutil now sees the monitor, but claims that it is not supported.
I had a root around the monitor settings, and there is no DDC/CI setting to
mess with. The closest was HDMI-CEC, which was off. I turned it on, but still
no joy.
One thing I am noticing that is kind of weird to me, is that if I turn off or
unplug the external monitor, KDE does not detect this, and happily outputs to a
dead display. Once I unplug the HDMI cable, though, then it realizes the
monitor is gone and switches to the internal laptop panel only.
In my understanding, there are quite a few monitors that do not support DDC/CI,
and so it follows that this should not be relied upon exclusively to detect and
configure displays.
The monitor is fairly expensive and modern, being only made in 2022. Also, this
issue does not seem to be present in Windows, so there is a little room for
improvement here, I guess.
I tested with HDR on and off, and every single time it comes down to display
update rate.
When the display update rate is 30fps, it wakes up properly from sleep mode,
and when a higher update rate is used it does not.
When setting the display to 120fps and rebooting the computer, the first time I
log in there is a fairly good chance that the display works properly. If I take
a little long to type the login password, the monitor goes to sleep and then it
does not wake up properly.
On a related mode, the monitor does have an auto-power off mode, which has been
disabled. So, powersave and powered down are different modes. With that
HDMI-CEC on, it wakes up from powered down mode too, but still the same issue
persists, leading me to think that this is not due to the monitor.
--
You are receiving this mail because:
You are watching all bug changes.
