AMD/ATI Pixel Clock Patcher

[ToastyX]

(11-28-2016 03:17 PM)Altberta Wrote:  I did attach configuration files. Default/Patched DVI/DP export bin files and Patched DVI/DP screenshots.

Your DP_Patched.png screenshot does not match the DP_Patched.bin file. It should not say "Default extension block" unless CRU could not read the extension block, which can happen if you edited it with the monitor disconnected, but the DP_Patched.bin file shows CRU was able to read the extension block. You can import the file to see it. You need to edit the extension block and delete the HDMI support data block because there's no reason to have that with DisplayPort. See if that helps.

[Altberta]

(11-28-2016 08:23 PM)ToastyX Wrote:  

(11-28-2016 03:17 PM)Altberta Wrote:  I did attach configuration files. Default/Patched DVI/DP export bin files and Patched DVI/DP screenshots.

Your DP_Patched.png screenshot does not match the DP_Patched.bin file. It should not say "Default extension block" unless CRU could not read the extension block, which can happen if you edited it with the monitor disconnected, but the DP_Patched.bin file shows CRU was able to read the extension block. You can import the file to see it. You need to edit the extension block and delete the HDMI support data block because there's no reason to have that with DisplayPort. See if that helps.

As a result, I got some help. However, I couldn't set over 89hz. I did attach new bin file and screenshot.

[ToastyX]

(11-28-2016 09:34 PM)Altberta Wrote:  As a result, I got some help. However, I couldn't set over 89hz. I did attach new bin file and screenshot.

I checked the EDID and the monitor does not properly identify itself as a DisplayPort monitor. There's no way to fix this with CRU directly, but it can import changes to the EDID.

Import this file using the "Import complete EDID" option:
  27100Q-DP.bin (Size: 256 bytes / Downloads: 685)

I fixed the video input definition and put 100 Hz in the extension block. You shouldn't need the pixel clock patch with this.

[Altberta]

(11-28-2016 10:26 PM)ToastyX Wrote:  I checked the EDID and the monitor does not properly identify itself as a DisplayPort monitor. There's no way to fix this with CRU directly, but it can import changes to the EDID.

Import this file using the "Import complete EDID" option:

I fixed the video input definition and put 100 Hz in the extension block. You shouldn't need the pixel clock patch with this.

OK. It's works now without clock patch, but color depth is fixed on 6 bpc at 100hz. 75hz can set 8 bpc.
Also, I have another problem. With FreeSync, my desktop screen bezel is get some truncation. You have fix solution? I did attach screenshots. (FreeSync on/off)

I posted same post on CRU thread. Please help.

[traycer]

Hi, ToastyX! Thanks for all your hard work with this tool and CRU!

I recently replaced an 11-year old Dell 3007WFP 2560x1600 display with a BenQ BL3201PH 3840x2160. My PC is running Windows 10 Pro with a Radeon HD4800 of some sort. I had two Dells hooked up to it, each via dual-link DVI @ 2560x1600. I unplugged one of them and plugged in the BenQ, without shutting down Windows first. The new display was recognized, and I was able to select the 3840x2160 resolution in Display Settings. Tried out Photoshop and a few other things, and I was satisfied things were working correctly.

I reboot the machine just to make sure everything is happy, but now Windows will not let me select anything higher than 2560x1440. I run atikmdag, and initially it patches everything except "low-resolution limit". I run CRU 1.3 anyway, and sees that it already knows about 3840x2160 @ 30 Hz. Reboot, still no change. Run atikmdag again just to be sure, add the 3840x2160 entry into the extension block with CRU, run atikmdag again, notice that "low-resolution limit" has now been patched.... reboot again. Still no go. Windows does not seem to want to go above 2560x1440.

Checked the monitor tab in the display driver, and it only shows 59 Hz and 60 Hz, even with "hide modes" unchecked. Is this the root of the issue, that the driver will not do a 30 Hz refresh rate? It is clearly able to do so, since it was happy with that resolution before I rebooted the PC for the first time. Any thoughts on this?

---

Replying to my own post...

Downloaded the latest monitor driver from BenQ's site, attempted to install it, but Windows claims what it has is already the latest. I was thinking this was the problem because the monitor shows up just as "BenQ LCD" in Device Manager, rather than with a more detailed model number. Rebooted again, but still nothing.

Poked around a bit more on BenQ's site, downloaded their "Display Pilot" utility (manages monitor settings from Windows, etc.). While that was installing, I did a "scan for hardware changes" in Device Manager... displays blinked off and then on, BenQ comes back on but with _massive_ windows and icons, like it was running at 1024x768 on a 32" display. Looked closer, and discovered Windows was now running it at 3840x2160 but with 300% desktop scaling.

Checked the display adapter drivers, and it now shows 30 Hz as the only supported refresh rate, and 3840x2160 now appears in the list of supported resolutions. I don't think the Display Pilot software had anything to do with it, but it was forcing a hardware rescan (which I thought was done on boot) that did it.

[DaLy]

(11-20-2016 02:13 AM)ToastyX Wrote:  

(11-18-2016 08:27 AM)DaLy Wrote:  So... finally I bought a Sony GDM-5411 (which is very, very, very good CRT) I can have 145Hz at 1024x768, that is so f*cking good.
But I have a problem, I can't calibrate colors very good... I have a green "overlay" on black background, what I can do ?
I tried so many combinations of RGB Dias and Gain but the final result is same... I can't have clear black background, can you help me with some idea please?

That's a common problem with Trinitron monitors. You'll need a special cable and WinDAS to adjust the G2 voltage: https://www.google.com/search?q=crt+windas

Hi, so, I opened the case from monitor and I found few adjustments... But I can't find the brightness and RGB Adjusments, can you help me please ?
Here are the adjusments:




Here is the book from the monitor.

P.S I adjusted these ads little bit and now it's more better but the colours are the same, I still need to found the RGB and brightness adjustments...

[ToastyX]

(12-04-2016 11:41 AM)DaLy Wrote:  Hi, so, I opened the case from monitor and I found few adjustments... But I can't find the brightness and RGB Adjusments, can you help me please ?

You need a special cable and WinDAS software to do those adjustments. The manual shows where the DAS port is for the cable.

[ToastyX]

(12-01-2016 09:57 PM)traycer Wrote:  I recently replaced an 11-year old Dell 3007WFP 2560x1600 display with a BenQ BL3201PH 3840x2160. My PC is running Windows 10 Pro with a Radeon HD4800 of some sort. I had two Dells hooked up to it, each via dual-link DVI @ 2560x1600. I unplugged one of them and plugged in the BenQ, without shutting down Windows first. The new display was recognized, and I was able to select the 3840x2160 resolution in Display Settings. Tried out Photoshop and a few other things, and I was satisfied things were working correctly.

I reboot the machine just to make sure everything is happy, but now Windows will not let me select anything higher than 2560x1440. I run atikmdag, and initially it patches everything except "low-resolution limit". I run CRU 1.3 anyway, and sees that it already knows about 3840x2160 @ 30 Hz. Reboot, still no change. Run atikmdag again just to be sure, add the 3840x2160 entry into the extension block with CRU, run atikmdag again, notice that "low-resolution limit" has now been patched.... reboot again. Still no go. Windows does not seem to want to go above 2560x1440.

None of this makes any sense. You shouldn't need the patch for 3840x2160 @ 30 Hz with dual-link DVI, and the patch is meant for 5000-series and newer cards anyway. I don't see how the low-resolution limit would not be patched the first time unless you used an older version of the patcher first, but you don't need the low-resolution limit anyway. You shouldn't need to add 3840x2160 @ 30 Hz with CRU because it's already there. Adding it again in the extension block should not make a difference. I don't see how forcing a hardware rescan would change anything unless there's a driver bug, but then you'd have to do that every time you reboot. Does 3840x2160 @ 30 Hz still work after rebooting?

[Vennto]

Nice tool!!! I test it on the last drivers (16.12.1) and "HBlank limit" could not be found, I used anyway cuz I needed it to load a modded atikmdag to bypass modded bios check (new drivers have the check again) without disabling windows driver signature enforcement at every boot (basically I followed this steps: http://www.overclock.net/t/1604567/polar...25699216).

Since I'd like to create a program to disable bios check automatically for the next drivers, I'd like (if possible) to know the process (or simply a small copy of the code) that this tool use to avoid conflict with windows driver signature enforcement.

I do not want to steal code, I just want a driver that allows modded bios.

[ToastyX]

(12-10-2016 10:30 AM)Vennto Wrote:  Since I'd like to create a program to disable bios check automatically for the next drivers, I'd like (if possible) to know the process (or simply a small copy of the code) that this tool use to avoid conflict with windows driver signature enforcement.

Do you have a kernel-mode code signing certificate?