- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the EDID read with Linux contains a third block that also defines the 165 Hz video timing (with 777 MHz pixel clock). But I can't get it to appear on my Windows device either.
With a bit of fiddling around, I can say that there seems to be a pixel clock limit of 600 MHz with this configuration on the Intel Windows drivers.
If the Linux EDID is changed to take this into account, then you can run
- 2560 x 1600 @ 101 Hz RGB 10-bit (475.82 MHz) or
- 2560 x 1600 @ 127 Hz RGB 8-bit with dithering (598.31 MHz)
on Windows.
Please try this on yours:
- Download the EDID file attached
- Download Custom Resolution Utility (CRU)
- Run CRU.exe
- Make sure the active EDID is CSO1600 connected to your PC. If necessary, select from the drop down menu.
Please close CRU with OK and restart the computer.
Note:
All changes made with CRU can be undone if necessary by running "reset-all.exe" from the CRU download package and restarting the system. You can find more information about this tool on the linked page.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What happens when you enable Variable Refresh Rate Mode in Intel Graphics Software (if possible)?
Intel Graphics Software > Display > Scroll all the way down in the right pane:
The EDID only reports 60 Hz as the refresh rate. However, there is a FreeSync block that specifies 60 - 165 Hz.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It has no change no different whatever VRR and VRR Mode are. Just 60Hz.
VRR Fullscreen
VRR Fullscreen&Windowed
VRR Mode Disabled
VRR Disabled
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Obviously there are differences in how the Windows and Linux drivers process the monitor's EDID. The EDID that this device sends is not entirely consistent.
The panel is a CSOT T3 MNG007DA1-1, which is a laptop screen. What cable did you use to connect this panel to the Arc A750?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are right. I found the final blocks of EDID are different in Windows and Linux.
In Windows, Intel GCC Raw EDID:
00 FF FF FF FF FF FF 00 0E 6F 00 16 00 00 00 00
00 1E 01 04 B5 22 16 78 03 EE 95 A3 54 4C 99 26
0F 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 6E 6E 00 A0 A0 40 84 60 30 20
36 00 59 D7 10 00 00 18 00 00 00 FD 0C 3C A5 1F
1F 4E 01 0A 20 20 20 20 20 20 00 00 00 FE 00 43
53 4F 54 20 54 33 0A 20 20 20 20 20 00 00 00 FE
00 4D 4E 47 30 30 37 44 41 31 2D 31 0A 20 02 02
02 03 1D 00 E3 05 80 00 E6 06 05 01 6A 6A 24 6D
1A 00 00 02 03 3C A5 00 04 6A 24 6A 24 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF
02 03 1D 00 E3 05 80 00 E6 06 05 01 6A 6A 24 6D
1A 00 00 02 03 3C A5 00 04 6A 24 6A 24 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF
Linux is:
00 ff ff ff ff ff ff 00 0e 6f 00 16 00 00 00 00
00 1e 01 04 b5 22 16 78 03 ee 95 a3 54 4c 99 26
0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 6e 6e 00 a0 a0 40 84 60 30 20
36 00 59 d7 10 00 00 18 00 00 00 fd 0c 3c a5 1f
1f 4e 01 0a 20 20 20 20 20 20 00 00 00 fe 00 43
53 4f 54 20 54 33 0a 20 20 20 20 20 00 00 00 fe
00 4d 4e 47 30 30 37 44 41 31 2d 31 0a 20 02 02
02 03 1d 00 e3 05 80 00 e6 06 05 01 6a 6a 24 6d
1a 00 00 02 03 3c a5 00 04 6a 24 6a 24 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff
70 13 79 00 00 03 01 14 ac 2f 01 85 ff 09 9f 00
2f 00 1f 00 3f 06 83 00 02 00 05 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 37 90
I don't know why they are different. I just use a 16'' portable screen. There is an edp to minidp board inside it and using a minidp to DP cable connected to Arc A750.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the EDID read with Linux contains a third block that also defines the 165 Hz video timing (with 777 MHz pixel clock). But I can't get it to appear on my Windows device either.
With a bit of fiddling around, I can say that there seems to be a pixel clock limit of 600 MHz with this configuration on the Intel Windows drivers.
If the Linux EDID is changed to take this into account, then you can run
- 2560 x 1600 @ 101 Hz RGB 10-bit (475.82 MHz) or
- 2560 x 1600 @ 127 Hz RGB 8-bit with dithering (598.31 MHz)
on Windows.
Please try this on yours:
- Download the EDID file attached
- Download Custom Resolution Utility (CRU)
- Run CRU.exe
- Make sure the active EDID is CSO1600 connected to your PC. If necessary, select from the drop down menu.
Please close CRU with OK and restart the computer.
Note:
All changes made with CRU can be undone if necessary by running "reset-all.exe" from the CRU download package and restarting the system. You can find more information about this tool on the linked page.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you!🤗The EDID_mod you provided works well at 127Hz on Windows.😄
127HZ
Then I thought and tried to copy paste the EDID from Linux and import it with CRU on Windows, 165Hz comes out.😂
165HZ
So it can run at the same 165Hz on Windows as Linux. 👏But manually...🤣
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah, all the better! Then the pixel clock limit seems to be a phenomenon on my simulation environment only.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page