3 ms·
Yes, plugging the monitor into a Linux box would have be easier. In my case the edid is exposed under /sys, and edid-decode is from the xorg-x11-utils Fedora pa
by jburgess777 9y ago
Yes, plugging the monitor into a Linux box would have be easier. In my case the edid is exposed under /sys, and edid-decode is from the xorg-x11-utils Fedora package
$ edid-decode < /sys/devices/pci0000:00/0000:00:03.0/0000:0f:00.0/drm/card0/card0-HDMI-A-1/edid
Extracted contents:
header: 00 ff ff ff ff ff ff 00
serial number: 00 b3 00 37 00 00 00 00 01 19
... [ followed by more data and the decoded output ] ...
- kens 9y ago> plugging the monitor into a Linux box would have be easier As JFK said, we do these things not because they are easy, but because they are hard :-)
- jburgess777 9y agoEven on Linux things don't always work as intended. The reason I am familiar with the EDID information is that my display stopped working after a kernel update and I tried to figure out why. It turned out that my AV receiver didn't like the VIC field being sent in the HDMI infoframes[1]. There is a surprising amount of communication which goes on between the graphics card and the monitor in a modern system. 1: Bug 50371 - [BISECTED] HDMI display blank unless VIC set in AVI infoframe https://bugzilla.kernel.org/show_bug.cgi?id=50371 https://bugzilla.kernel.org/show_bug.cgi?id=50371
- pmorici 9y agomodprobe i2c-dev and you can access the i2c bus your monitor is on in the same way described in this post w/o hacking up your cable.