My suspicion is that if the EDID data got corrupted in the first place,
then it's not protected. I don't know about i2cset, or any other methods.
That's exactly what I'm thinking. I'm trying to overwrite the EEPROM using a
DVI cable (since it's the DVI EDID which is broken). I saw other
On 02/07/2013 08:37 PM, mwesten wrote:
I recently used a DOS program called ddcw.exe to fix the corrupted EDID
on one of my monitors.
I already tried to write the good EDID into the monitor but I failed. I
also tried to do that using i2cset with the same result. I suspect the
EEPROM is write
On 02/08/2013 03:23 AM, Flavio Castelli wrote:
On 02/07/2013 08:37 PM, mwesten wrote:
I recently used a DOS program called ddcw.exe to fix the corrupted EDID
on one of my monitors.
I already tried to write the good EDID into the monitor but I failed. I
also tried to do that using i2cset with
On 02/08/2013 11:44 AM, mwesten wrote:
My suspicion is that if the EDID data got corrupted in the first place,
then it's not protected. I don't know about i2cset, or any other methods.
That's exactly what I'm thinking. I'm trying to overwrite the EEPROM
using a DVI cable (since it's the DVI
For an unknown reason both my monitors ended up with a corrupted EDID.
They both provide VGA and DVI input. The VGA input works fine, while
DVI is broken because of the EDID issue.
Using these [1] instructions I have been able to read the EDID and fix
it. Unfortunately I'm not able to write it
On Thu, Feb 07, 2013 at 04:16:54PM +0100, Flavio Castelli wrote:
For an unknown reason both my monitors ended up with a corrupted EDID.
They both provide VGA and DVI input. The VGA input works fine, while
DVI is broken because of the EDID issue.
Using these [1] instructions I have been able
On 02/07/2013 10:16 AM, Flavio Castelli wrote:
For an unknown reason both my monitors ended up with a corrupted EDID.
They both provide VGA and DVI input. The VGA input works fine, while
DVI is broken because of the EDID issue.
Using these [1] instructions I have been able to read the EDID and
