Hacking the LG Monitor's EDID
gist.github.com
Hacking the LG Monitor's EDID
1–10 of 146 posts
Re: Hacking the LG Monitor's EDID
#2LG monitors get firmware updates, I wonder if one of them contained this fix.
Re: Hacking the LG Monitor's EDID
#3I was expecting a tale of how the author managed to overwrite whatever part of the monitor's firmware was responsible for spitting out the EDID. While interesting, the title is a bit misleading: it's an ugly but effective hack to inject a custom EDID.
Re: Hacking the LG Monitor's EDID
#41. This is impressive debugging work by the author. No individual step is rocket science - especially when the story is the success path and not the forking paths of possible failures - but they kept their eyes on the prize and figured it out.
2. This reminds me why I no longer use linux on the desktop
Re: Hacking the LG Monitor's EDID
#5Very interesting report. I'm not sure I understand what the root cause of the issue is though - is it a Linux bug or a problem with the monitor itself?
Re: Hacking the LG Monitor's EDID
#6I was expecting a tale of how the author managed to overwrite whatever part of the monitor's firmware was responsible for spitting out the EDID. While interesting, the title is a bit misleading: it's an ugly but effective hack to inject a custom EDID.
In the last paragraph: "One last thing I might consider doing at some point would be to try to overwrite the EDID on the monitor itself."
Re: Hacking the LG Monitor's EDID
#71. This is impressive debugging work by the author. No individual step is rocket science - especially when the story is the success path and not the forking paths of possible failures - but they kept their eyes on the prize and figured it out. 2. This reminds me why I no longer use linux on the desktop
[deleted]
Re: Hacking the LG Monitor's EDID
#8Very interesting report. I'm not sure I understand what the root cause of the issue is though - is it a Linux bug or a problem with the monitor itself?
There are many cases where hardware is not up to spec and other operating systems ignore it more or less but Linux can be a stickler.
Windows is generally most forgiving, then Mac, finally Linux.
Re: Hacking the LG Monitor's EDID
#9Very interesting report. I'm not sure I understand what the root cause of the issue is though - is it a Linux bug or a problem with the monitor itself?
The monitor reports an EDID resolution/refresh value to the system that is incorrect for the actual monitor's capabilities. Linux happens to be choosing to use that invalid EDID resolution/refresh value and the default result is no picture on the monitor.
The bug is with the EDID values LG programmed into the monitor.
Re: Hacking the LG Monitor's EDID
#101. This is impressive debugging work by the author. No individual step is rocket science - especially when the story is the success path and not the forking paths of possible failures - but they kept their eyes on the prize and figured it out. 2. This reminds me why I no longer use linux on the desktop
Huh. This reminds me of why the world so needs Linux. That they could just take off the shelf tools & plug around for a bit, learning & understanding a complex situation with crude & fast debugging, knowing only a little of the internals, and in the end improve their own situation clearly. And then they could share that knowledge with others in such a clear manner.
Nothing else in computing is like this. We just cannot help ourselves & each other in most realms of computing: we must be content with what we are given, as it is.
In almost all probability the linux system either doesn't have a GPU capable of running this high pixel clock or the cable/connector can't handle it. I'd love to know what the Mac & windows machines do; do they run 60Hz too or are they pushing all 144Hz here successfully? This seems very likely to be a cable issue, one I don't expect windows nor Mac deal with particularly excellently.