Post Reply
AMD/ATI Pixel Clock Patcher
05-30-2021, 09:53 AM
Post: #1071
RE: AMD/ATI Pixel Clock Patcher
(05-29-2021 10:24 PM)ToastyX Wrote:  
(05-29-2021 07:33 PM)D1stRU3T0R Wrote:  Hello @ToastyX

Newer kernel from the 21.4.1 has changed and now we can't extend official overclock limit on mobile GPU-s (like RX550) and now we can't use Wattman, nor anything else to OC, could you make a patch as it was before so we can use newer drivers(and wattman, but that's unlockable with MSI Afterburner's Extended OC feature)?
Update for 21.4.1 came out a month ago.

I know, but it is unlocking the new OC "limit"? I don't remember seeing it back when I last used it. If yes, then I'm sorry, didn't knew that it can unlock OC too, I though only Pixel Clock stuff.
Find all posts by this user
Quote this message in a reply
06-04-2021, 12:27 PM
Post: #1072
RE: AMD/ATI Pixel Clock Patcher
(09-07-2012 09:07 PM)ToastyX Wrote:  AMD/ATI Pixel Clock Patcher modifies the AMD/ATI video driver to allow higher resolutions and refresh rates by removing the 165 MHz pixel clock limit for single-link DVI and HDMI, the 330 MHz limit for dual-link DVI, and the 400 MHz limit for VGA.

Download: atikmdag-patcher-1.4.10.zip - Source: atikmdag-patcher-1.4.10-src.zip

A message from ToastyX:

Creating and maintaining software is a lot of work, and I have provided updates and support for free over the years. I would like to continue providing updates and work on new ideas, but I need your support. If you find my software useful, please consider supporting me through Patreon:

[Image: patreon.png]

Requirements:
  • Windows Vista or later
  • 5000-series GPU or newer
  • CrossFire requirements:
    • R9 285/290/290X/295X2 and newer cards can handle higher pixel clocks without CrossFire bridges.
    • Older cards require two CrossFire bridges if the pixel clock is greater than 300 MHz. This is only possible with cards that have two connectors. It will not work properly with more than two cards. Dual-GPU cards such as the 7990 will not work properly at higher pixel clocks.
Compatibility:
  • Version 1.4.10 is compatible with Catalyst 11.9 to Adrenalin 21.4.1. It can be used with future versions if it finds the limits you need.
Getting started:
  1. Run atikmdag-patcher.exe. (If you only need the BIOS signature patch, rename it to atikmdag-patcher-bios.exe first.)
  2. If all limits are found, click "Yes" to patch and sign. If a limit is not found or if multiple matches are found, the patcher needs to be updated.
  3. Reboot.
You can then add higher refresh rates using Custom Resolution Utility (CRU).

To restore the unpatched driver, run the patcher again and click "Yes" to restore from backup.

Unpatching is not required before upgrading drivers. Simply run the patcher again after installing the new driver.

Known issues:
  • Legacy drivers may have issues with HDCP and video acceleration with the patch.
  • Workarounds for video playback issues with legacy drivers:
    • Disable hardware acceleration in the Flash Player settings (right-click on any Flash video and click "Settings...").
    • Use the Codec Tweak Tool to disable DXVA hardware acceleration under "Various Tweaks" (in the "Miscellaneous" section).
  • Older cards require the "LCD standard" vertical blanking/total to reduce the memory clock when idle. Horizontal values can still be reduced if necessary. Newer cards can handle some lower values depending on the resolution and refresh rate.
  • Older cards have a design limitation unrelated to the patch that causes video acceleration to scramble the screen if the vertical blanking/total is below standard with the video card's memory overclocked or with multiple monitors connected. Skype is known to trigger this problem. Either don't overclock the video card's memory, or use the "LCD standard" vertical blanking/total in CRU.
Recent changes:
  • 1.4.10: Updated for 21.4.1.
  • 1.4.9: Fixed HDMI-DVI limit for 20.11.2 and HBlank limit for 20.5.1.
  • 1.4.8: Updated for 20.5.1.
  • 1.4.7: Find new SL-DVI/HDMI limit.
  • 1.4.6: Find new HDMI-DVI limit.
  • 1.4.5: Updated for 17.4.1. Find new DP-DVI/HDMI limit.
  • 1.4.4: Find BIOS signature check.
  • 1.4.3: Fixed HBlank limit for 16.12.1.
  • 1.4.2: Find 56 horizontal blanking (HBlank) limit.
  • 1.4.1: Fixed an issue that prevented the driver from loading correctly with earlier versions of Windows 10. This does not affect the anniversary update.
  • 1.4.0: Updated for 16.9.1. Changed the way the driver is located and patched. Replaced 640x480 limit with low-resolution limit. Fixed VGA limit for 32-bit.
  • 1.3.6: Find 10-resolution limit for Radeon Settings.
  • 1.3.5: Updated for 15.11 Crimson. Find 640x480 limit for Radeon Settings.
  • 1.3.4: Try to improve finding DVI/HDMI limit for newer drivers. Removed blue screen workaround for 14.6/14.7.
  • 1.3.3: Updated for 15.3. Fixed DVI/HDMI limit for 32-bit.
  • 1.3.2: Updated for 15.2. Fixed DVI/HDMI limit for 64-bit.
  • 1.3.1: Find 297 MHz HDMI 1.3+ limits. Run 3 times to properly repatch an existing installation.
  • 1.3: Removed blue screen workaround for 14.9. Fall back to self-signing if signing fails.
  • 1.2.7: Attempt to work around some antivirus false positives. Repatching is not necessary.
  • 1.2.6: Fixed AMD APP encoding for 14.6.
  • 1.2.5: Updated for 14.6. Fixed TMDS and VGA limits. Implemented workaround for SYSTEM_SERVICE_EXCEPTION blue screens.
  • 1.2.4: Updated for 14.4. Fixed SL limit on DL-DVI.
  • 1.2.3: Updated for 13.30 and upcoming 14.x releases.
  • 1.2.2: Find new HDMI limit for 12.9+.
  • 1.2.1: Find 400 MHz VGA limit.
  • 1.2: Test mode no longer required.

Hi! I’m working on app for rebuilding modules in vbios. And early method working file. But I stuck with vbios signature verification. I compare all modules of four vbioses and find out that PowerPlayInfo includes some different two bytes 3125, 3025, 4626, 6326... etc... so possibly they are signatures.

If you know the location of signature in vbios and driver, it could be very useful, thanks!

   
Find all posts by this user
Quote this message in a reply
06-13-2021, 09:31 AM
Post: #1073
RE: AMD/ATI Pixel Clock Patcher
(05-30-2021 09:53 AM)D1stRU3T0R Wrote:  
(05-29-2021 10:24 PM)ToastyX Wrote:  
(05-29-2021 07:33 PM)D1stRU3T0R Wrote:  Hello @ToastyX

Newer kernel from the 21.4.1 has changed and now we can't extend official overclock limit on mobile GPU-s (like RX550) and now we can't use Wattman, nor anything else to OC, could you make a patch as it was before so we can use newer drivers(and wattman, but that's unlockable with MSI Afterburner's Extended OC feature)?
Update for 21.4.1 came out a month ago.

I know, but it is unlocking the new OC "limit"? I don't remember seeing it back when I last used it. If yes, then I'm sorry, didn't knew that it can unlock OC too, I though only Pixel Clock stuff.

Anyone who has a laptop GPU, can you please test if this is unlocking the unofficial overclock for laptops?
Find all posts by this user
Quote this message in a reply
06-15-2021, 06:09 PM
Post: #1074
RE: AMD/ATI Pixel Clock Patcher
GPU overclocking is outside the scope of the patcher and is not my area of expertise. I only have the Polaris BIOS signature workaround.
Find all posts by this user
Quote this message in a reply
06-15-2021, 07:43 PM
Post: #1075
RE: AMD/ATI Pixel Clock Patcher
(06-15-2021 06:09 PM)ToastyX Wrote:  GPU overclocking is outside the scope of the patcher and is not my area of expertise. I only have the Polaris BIOS signature workaround.

Well the RX550 is a Polaris chip, and it's not about overclock, it would be about unlocking the limiter from the newer kernels (I'm talking about wattman, since it was locked since the 21.4.1). Some laptops really need underclock to work well (like RX550, 560X and the rests), and now we can't do anything. If you have time, could you please check what's up with this lock, and a way to bypass it? Thanks!
Find all posts by this user
Quote this message in a reply
06-15-2021, 08:54 PM
Post: #1076
RE: AMD/ATI Pixel Clock Patcher
(06-15-2021 07:43 PM)D1stRU3T0R Wrote:  Well the RX550 is a Polaris chip, and it's not about overclock, it would be about unlocking the limiter from the newer kernels (I'm talking about wattman, since it was locked since the 21.4.1). Some laptops really need underclock to work well (like RX550, 560X and the rests), and now we can't do anything. If you have time, could you please check what's up with this lock, and a way to bypass it? Thanks!
I can't do that.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 12 Guest(s)