Custom Resolution Utility (CRU)

[ToastyX]

(12-31-2015 05:53 AM)MightyUnit Wrote:  What would you do if you were me? Flash the display with the EDID after removing the empty extension block (if I understood that correctly) or try to tell Nvidia about this?

Why not both? Flash the EDID to check if that's the problem, and then report it to NVIDIA.

Does the monitor support 1280x800? I assume it does since you're able to see the boot screens. The monitor defines 1280x800 as the native resolution, probably for compatibility with single-link DVI, which could cause a black screen if the monitor didn't support it, but that shouldn't prevent the monitor from being detected. I've seen other 2560x1600 monitors do the same thing. You can make 2560x1600 the first detailed resolution if you want it to be the native resolution. Then GPU scaling should scale to 2560x1600 instead of 1280x800.

(12-31-2015 05:53 AM)MightyUnit Wrote:  EDIT: concerning EDID programming what about software called EDID programmer? I used it to flash an LG L245WP from within windows the other day. Here is a link to it: http://pg-anatolich.narod.ru/EDIDProgrammer_v1.2.1.zip

Where did you find this? I can't run it. It says it uses a demo version of the WinI2C/DDC component and that the 30-day trial period expired. I don't know anything about it since it's not documented anywhere, but if you got it to work with the LG, then it might work with any monitor.

(12-31-2015 05:53 AM)MightyUnit Wrote:  EDIT: can .bin files be renamed .edid? EDIDprogrammer can read and write .edid and CRU exports in .bin

No, the included .edid files look like the raw data as tab-separated hex values. I can't run the program, so I can't see if it will accept other types. Most EDID programs support the .bin format.

I manually converted the raw data with the extension block removed and with 2560x1600 as the first detailed resolution:

  dnd9220.edid (Size: 400 bytes / Downloads: 642)
  dnd9220-2560x1600.edid (Size: 400 bytes / Downloads: 654)