http://hardware.mcse.ms/archive53-2004-7-48432.html
So far, based on more than 20 hours of research, it's caused by VGA card encoding false EDID onto monitor's EDID header.
I do not understand why this 'my dvi is dead' is still an on-going issue when this problem has been around forever.
Anyway,
My problem is quite like the problem mentioned in above link. In addition, I know I have same problem as the my LCD's DVI EDID information shows that it is set as analog instead of digital.
Knowing that I can fix my LG L226WA's DVI problem as it's clear what's causing it, I followed the procedure mentioned in above link.
However, I can't input some of the EDID information. I guess it just isn't my lucky day.
In that situation, I know if I can get working EDID data file, the one that hasn't been currupted by VGA card,
I can just re-encode into LCD and it'd be fine.
Hence....It'd be great if someone who has working LG L226WA DVI monitor to post that EDID file.
Also, those who have working LCD DVI should make a backup as this problem seems to just happen out of nowhere.
So far, based on more than 20 hours of research, it's caused by VGA card encoding false EDID onto monitor's EDID header.
I do not understand why this 'my dvi is dead' is still an on-going issue when this problem has been around forever.
Anyway,
My problem is quite like the problem mentioned in above link. In addition, I know I have same problem as the my LCD's DVI EDID information shows that it is set as analog instead of digital.
Knowing that I can fix my LG L226WA's DVI problem as it's clear what's causing it, I followed the procedure mentioned in above link.
However, I can't input some of the EDID information. I guess it just isn't my lucky day.
In that situation, I know if I can get working EDID data file, the one that hasn't been currupted by VGA card,
I can just re-encode into LCD and it'd be fine.
Hence....It'd be great if someone who has working LG L226WA DVI monitor to post that EDID file.
Also, those who have working LCD DVI should make a backup as this problem seems to just happen out of nowhere.