Jump to content

[KEXT] Tired of low Geekbench scores? Use RadeonBoost!


135 posts in this topic

Recommended Posts

2 hours ago, BRONNER said:

It won't panic if you use named framebuffer B).

Nice find my man. Works like a charm. Scores were ~48k and are now ~67k :thumbsup_anim:

 

Here's the complete entry for the lazy:

<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
			<dict>
				<key>@0,name</key>
				<string>ATY,Adder</string>
				<key>@1,name</key>
				<string>ATY,Adder</string>
				<key>@2,name</key>
				<string>ATY,Adder</string>
				<key>@3,name</key>
				<string>ATY,Adder</string>
				<key>ATY,Rom#</key>
				<string>113-D1820501-101</string>
				<key>Force_Load_FalconSMUFW</key>
				<data>
				AQ==
				</data>
				<key>PP_WorkLoadPolicyMask</key>
				<data>
				IA==
				</data>
				<key>device_type</key>
				<string>ATY,AdderParent</string>
				<key>name</key>
				<string>ATY,AdderParent</string>
			</dict>

ROM version will likely differ between all the cards (I have the reference XT) so make sure you add your correct one.

  • Like 2
1 hour ago, Tiem said:

Nice find my man. Works like a charm. Scores were ~48k and are now ~67k :thumbsup_anim:

 

Here's the complete entry for the lazy:

ROM version will likely differ between all the cards (I have the reference XT) so make sure you add your correct one.

The "ATY,Rom#" is not required at all and you have to remove it unless your GPU's ROM provides correct value. It's an MSI-specific solution to avoid installer crash issue.

Edited by BRONNER

<key>Force_Load_FalconSMUFW</key>

Is the only part that gives the score boost. As for the Adder framebuffer fixing the kernel panic on 10.15.5 when SMU Firmware is loaded, that is an interesting find. Anyhow, I cannot implement this in my kext since this framebuffer is not intended to be used with PC cards. It could kill some outputs on various custom designs of Navi cards.

  • Like 1

Injecting anything else than EFI Bios or Flacon SMUFW is useless for performance.

I think could be useful for next Mac OS release have an AMDRadeonX6000Framebuffer.kext/Contents/Info.plist to check and compare with 10.15.4

Hi, thanks for your great work.

 

I have the following entries in my clover plist:

 

<key>PciRoot(0x0)/Pci(0x3,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
			<dict>
				<key>@2,AAPL,boot-display</key>
				<integer>1</integer>
				<key>ATY,EFIVersion</key>
				<data>MDEuMDAuMzE4MA==</data>
				<key>CFG_NVV</key>
				<integer>2</integer>
				<key>CFG_PTPL2_CNT</key>
				<integer>16</integer>
				<key>CFG_PTPL2_MAX</key>
				<integer>300</integer>
				<key>CFG_PTPL2_MIN</key>
				<integer>90</integer>
				<key>CFG_TPS1S</key>
				<integer>1</integer>
				<key>PP_ACDCGpioDisabled</key>
				<integer>0</integer>
				<key>PP_DiDtSQPatternWidthOverride</key>
				<integer>14</integer>
				<key>PP_DiDtSQStallPatternOverride</key>
				<integer>16383</integer>
				<key>PP_DisableDIDT</key>
				<integer>1</integer>
				<key>PP_DisablePCCLimitControl</key>
				<integer>1</integer>
				<key>PP_DisableULV</key>
				<integer>0</integer>
				<key>PP_FclkGfxClkRatio</key>
				<integer>1036831949</integer>
				<key>PP_PhmSoftPowerPlayTable</key>
				<data>wgYLAALCBjQIAACkNQAAfAAJAAAAGvoA+gD6AAAAAAB2AAELAAAACQcAAG4EAADMAwAAzAMAAMwDAADoAwAAyQQAAG4EAABuBAAANAQAACoDAAAAAAAAAAAAAAAAAAAAAAAAAAAAALwCAABmAQAANgEAADYBAAA2AQAAXgEAACYCAABmAQAAZgEAAJMAAAAOAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAABDgAAAAEBAQEBAQEBAQEBAQEBAAAAAAAAAAAAAAAAAAAAAAAAHQAAAJgIAACYCAAAmAgAAAYEAACYCAAABgQAAJgIAAAGBAAAsAQAABQAAAAoCgAAKAoAAF8AAABuAAAAAgAAAAAAAAABAAAAAQAAAAEAAABfAAAAZAAAAF8AAABkAAAAXwAAAGQAAABfAAAAZAAAAF8AAABkAAAAAAAAAAAAAAAAAAAAKAMAACgDAAAoAwAA4gIAACgDAADiAgAAKAMAAOICAABeAQAAFAAAAMIBAADCAQAAGQAAADIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABkAAAAUAAAAGQAAABQAAAAZAAAAFAAAABkAAAAUAAAAGQAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwAAAP/v9DkAAAAA+gAAAAAAAAAAAAAAAAAAAPoAAAAyAAAASgEAAGQAbgBeAHMAcwD///////8AAAAAAAAAAAEAcwAAAAAAAAAAACgKIAsYEDARJgAAAAEBCQAAAAAAAAAAAFuxvz7sUfi+ZRlSPwABCABkO58/Ft6lvQAAAAAAAAAAAAAAAAABCAA1Xpo/jzYuPgAAAAAAAAAAAAAAAAABCABpb7A/SDMWPQAAAAAAAAAAAAAAAAABCADlYaE/EvdYvQAAAAAAAAAAAAAAAAABAwC1FYM/wt0ZPgAAAAAAAAAAAAAAAAABCACGOIY/Dr4wPgAAAAAAAAAAAAAAAAABCACDwFo/TaHzPQAAAAAAAAAAAAAAAAIBCAAAAAAAAAAAAKRwjT/kFIW/1ecyPwIBAwAAAAAAAAAAAAAAAAAAAAAA1ecyPwEBCAAAAIA/AAAAANGR/D4fhSu/Mnd1P7wCKANuBFwFCgaTBtUG7QYKBwAAAAAAAAAAAAAAAAAAZgHmAWsC9AJSA8wDbgRuBDYBkAEMAmsCqAL0AlIDzAM2AZABDAJrAqgC9AJSA8wDNgEMAjcCawKoAvQCUgPMA14BIANMBEwEJgJiArIC+AJmA8ADOATJBGYBxgE3AqgC9AJSA8wDbgRmAcYBNwKoAvQCUgPMA24EkwDyAFgB5AEVAqoDEwQ0BA4BHAIqAwAAAAAAAAAAAAAJB24EzAPMA8wD6ANuBG4ENAQqA8kEAADIACwBYAnwCigDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoHAQAAAAAAAAIGBlAANAEAAAAAAAAAAAAAAACQAZABkAGQAZABkAGQARQAKAooCigKXwAAAAACAAAAAAAAAAAAAQAAAAAAAFCNlzwK16M7AAAAAOqymDyHokA9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAABAAAAAAAAAKAAAAAIEAIQGgRMBOgD6APoA+gDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACGCyILVAsAAJABkAE4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data>
				<key>PP_PhmUseDummyBackEnd</key>
				<integer>0</integer>
				<key>PP_WorkLoadPolicyMask</key>
				<integer>1</integer>
			</dict>

Do I need to remove anything as I'm guessing some of the values are passed on through the kext?

 

GPU is a Radeon VII, got a nice 8% boost in Luxmark with them, no difference with or without the kext but don't mind keeping it:)

 

On 5/2/2020 at 10:21 AM, CMMChris said:

 

With new bugs that will either never be fixed or with a delay of 1+ year(s)...

I'll take the delay over the bugs ;) 

 

what other choice do hackintoshers have?  obviously can't go geforce.

Uhm, so - im a bit on the slower end here, so please, a for dummies answer:

Which part do I use exclusively for AMD Radeon Vega 56 from the extra keys needed adding?

The line below is only for the XT 5xxx+ cards, right?

Force_Load_FalconSMUFW

Thanks in advance,

 

Don't use the kext. If you want to use the "hack" for your Vega 56 simply inject the Force_Load_FalconSMUFW device property as number with value 1 through your bootloader like you would with a PowerPlay Table. If you use OpenCore you need to inject to the PCI path of your GPU, on Clover you can use "PrimaryGPU" as device path.

  • Like 1

Hello, I am having difficulties, I tell you.
I have a 7900x with an asus tuf mark1 motherboard, I use smbios macpro7,1 along with a sapphire nitro + 5700xt with the bootflag agdpmod = pikera (using WEG).

I have tried several things always using WEG
1-using an ssdt for the 5700xt and I get a very high improvement but sometimes when I turn on the PC it freezes when I get to the desktop.
2 using RadeonBoost.kext v1.4, this gives me a little more punctuation but the same thing happens to me sometimes when I get to the desktop it freezes me.
3 I added various combinations to the properties of the devices, but they have no effect.

What is the best way for me to be stable and work better, what am I doing wrong? who could help me? , Thanks in advance.

I've seen the Radeon_RX_5700_XT_PowerPlayTable_Generator but I don't know how to use it :(

Don't use any kind of SMU firmware injector if you have problems with it, neither the SSDT from Tonymac (the user has stolen parts of my work) nor my RadeonBoost kext. Apple has stopped loading the SMU firmware for PC cards so they don't run any testing with it. Thus, functionality cannot be guaranteed and there is nothing I can do about it. Also, in 10.15.5 my Kext will stop working for all Navi GPUs. SMU firmware is not compatible anymore with any PC card in this release. It will just cause a kernel panic.

 

I'd suggest using a Windows if you are not satisfied with the performance of your GPU on macOS. Apple just doesn't care about macOS anymore. No issues get fixed and if they fix something it's usually just some dirty workaround. macOS is just a pile of garbage by now.

Edited by CMMChris
  • Like 1
  • Thanks 1
On 5/14/2020 at 4:24 PM, CMMChris said:

Don't use any kind of SMU firmware injector if you have problems with it, neither the SSDT from Tonymac (the user has stolen parts of my work) nor my RadeonBoost kext. Apple has stopped loading the SMU firmware for PC cards so they don't run any testing with it. Thus, functionality cannot be guaranteed and there is nothing I can do about it. Also, in 10.15.5 my Kext will stop working for all Navi GPUs. SMU firmware is not compatible anymore with any PC card in this release. It will just cause a kernel panic.

 

I'd suggest using a Windows if you are not satisfied with the performance of your GPU on macOS. Apple just doesn't care about macOS anymore. No issues get fixed and if they fix something it's usually just some dirty workaround. macOS is just a pile of garbage by now.

Shouldn't really be any talk of stealing. everyone should be figuring stuff out together. but just to say, the guy is claiming the same as you......

Screenshot 2020-05-15 at 18.06.07.png

On 5/15/2020 at 7:07 PM, Insanelyhack.com said:

but just to say, the guy is claiming the same as you......

 

I know

 

@Rocky12 This is for AMD CPUs and motherboards, not GPUs.

Edited by CMMChris

HI everyone
i've install it using propertree in opencore 0.5.8
i've copy RadeonBoost.kext to EFI/OC/Kexts
and command+R in propertree to update the config.plist
reset.
my hackintosh rx 5700 jumped in results

here are the results..
@CMMChris thanks you very much
do you if it possible to achieve same speed as in windows? (64,000 in my case) 

before radeonboost.kext

1787000540_Screenshot2020-05-18at11_32_21.thumb.png.fe3ec65e6431415d101b907cd14f01e2.png 

after radeonboost.kext

1553081135_Screenshot2020-05-18at13_35_32.thumb.png.6422eac30ec367e989112c86115e519d.png

 

Edited by Ericine
  • 2 weeks later...

Yeah, it is not working.
 

panic(cpu 2 caller 0xffffff7fa1dbf778): "PowerPlay Failed to Initialize.
"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/GPUDriversAMD/GPUDriversAMD-3.9.15/Common/IONDRV/ATI/AMDUniversalFramebuffer/AMDUniversalFramebuffer/Controller/Controllers/AmdRadeonController.cpp:1668
Backtrace (CPU 2), Frame : Return Address
0xffffff82048a3550 : 0xffffff801ef1f5cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff82048a35a0 : 0xffffff801f058b05 mach_kernel : _kdp_i386_trap + 0x155
0xffffff82048a35e0 : 0xffffff801f04a68e mach_kernel : _kernel_trap + 0x4ee
0xffffff82048a3630 : 0xffffff801eec5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff82048a3650 : 0xffffff801ef1ec97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff82048a3750 : 0xffffff801ef1f087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff82048a37a0 : 0xffffff801f6c27ec mach_kernel : _panic + 0x54
0xffffff82048a3810 : 0xffffff7fa1dbf778 com.apple.kext.AMDRadeonX6000Framebuffer : __ZN34AMDRadeonX6000_AmdRadeonController10doGPUPanicEPKcz.cold.1 + 0x15
0xffffff82048a3820 : 0xffffff7fa1c6f3ac com.apple.kext.AMDRadeonX6000Framebuffer : __ZNK34AMDRadeonX6000_AmdRadeonController12getAttributeE22AmdControllerAttributePm
0xffffff82048a3aa0 : 0xffffff7fa1c3af10 com.apple.kext.AMDRadeonX6000Framebuffer : __ZN33AMDRadeonX6000_AmdPowerPlayHelper7powerUpEv + 0xec
0xffffff82048a3ae0 : 0xffffff7fa1c6e457 com.apple.kext.AMDRadeonX6000Framebuffer : __ZN34AMDRadeonX6000_AmdRadeonController7powerUpEv + 0x133
0xffffff82048a3b30 : 0xffffff7fa1c3f16e com.apple.kext.AMDRadeonX6000Framebuffer : __ZN35AMDRadeonX6000_AmdRadeonFramebuffer16enableControllerEv + 0x42
0xffffff82048a3b90 : 0xffffff7fa189316c com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer4openEv + 0x618
0xffffff82048a3c10 : 0xffffff7fa18899ac com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer13newUserClientEP4taskPvjPP12IOUserClient + 0x264
0xffffff82048a3ca0 : 0xffffff801f601e69 mach_kernel : __ZN9IOService13newUserClientEP4taskPvjP12OSDictionaryPP12IOUserClient + 0x69
0xffffff82048a3d00 : 0xffffff801f65cd19 mach_kernel : _is_io_service_open_extended + 0x129
0xffffff82048a3d60 : 0xffffff801f007d71 mach_kernel : _iokit_server_routine + 0x4931
0xffffff82048a3db0 : 0xffffff801ef25328 mach_kernel : _ipc_kobject_server + 0x238
0xffffff82048a3e10 : 0xffffff801eefbcc5 mach_kernel : _ipc_kmsg_send + 0x135
0xffffff82048a3e70 : 0xffffff801ef12aa2 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffff82048a3f00 : 0xffffff801f030d05 mach_kernel : _mach_call_munger64 + 0x205
0xffffff82048a3fa0 : 0xffffff801eec6226 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(576.1)[B1C0006F-E1F5-37D9-9548-5F918E92B422]@0xffffff7fa187a000->0xffffff7fa18cafff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[3C56BB73-D149-3E84-A2EB-DF806779B96C]@0xffffff7f9fb01000
         com.apple.kext.AMDRadeonX6000Framebuffer(3.0.9)[E9880F7F-25D3-340E-9F59-0FB58854EF20]@0xffffff7fa1c2e000->0xffffff7fa205ffff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[0A7D7382-66FE-391B-9F93-97A996256C25]@0xffffff7f9faef000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[3C56BB73-D149-3E84-A2EB-DF806779B96C]@0xffffff7f9fb01000
            dependency: com.apple.iokit.IOGraphicsFamily(576.1)[B1C0006F-E1F5-37D9-9548-5F918E92B422]@0xffffff7fa187a000
            dependency: com.apple.AppleGraphicsDeviceControl(5.2.4)[CD6E2942-2A23-3CE8-9BCA-D5A772667EB8]@0xffffff7fa18cb000

BSD process name corresponding to current thread: WindowServer
Boot args: -v debug=0x100 keepsyms=1 npci=0x2000 agdpmod=pikera alcid=1 

Mac OS version:
19F96

Kernel version:
Darwin Kernel Version 19.5.0: Thu Apr 30 18:25:59 PDT 2020; root:xnu-6153.121.1~7/RELEASE_X86_64
Kernel UUID: 7B7F06EE-1B75-345E-B898-2FD4FEC20F0D
Kernel slide:     0x000000001ec00000
Kernel text base: 0xffffff801ee00000
__HIB  text base: 0xffffff801ed00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 15832357934

 

I struggled with this error:

OS staling on glOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0

Seems disabling kext helped system to boot (lost a while to reboot into Windows and disable kext via Explorer++).
No certain clean improvement over 10.15.4, maybe 2%.

22 hours ago, CMMChris said:

New version 1.6 added to first post. Navi10/14 SMU firmware upload has been disabled for now due to broken firmware in macOS 10.15.5.

Thanks for this new version.

No more kernel panic at 10.15.5 release (19F96), but no significant boost for RX-580 & RX-560 now.

Edited by jsl2000

Polaris never was affected by Kernel Panic. Only Navi / RDNA is.

What's your RX580 metal score in Geekbench? If it is between 47k and 52k everything is fine. RX580 can't score higher except you overclock it.

  • Like 1

i had a freeze and shut down the system with the button and had karnel panic until the boot didn't recognized the drive

the nvme died, i'll go to the store and rma it but for now i've reinstall and i'm back on and everything is running well except that now my card radeon rx 5700 is having a  very very low score... what actually happened? is it the 10.15.5? or that i've change to imacpro1,1 from imac19,1? i really like this kext it worked like magic what can i do? there is another way to set it manually? thanks.
yours. Eric.

968214062_ScreenShot2020-05-29at19_41_35.png.a95ca1ebd125b0f585fe6eccaaff431c.png825867019_ScreenShot2020-05-29at19_42_09.thumb.png.3b8ef9acf5335ac08743ad70a5dd2705.png

13 hours ago, CMMChris said:

Polaris never was affected by Kernel Panic. Only Navi / RDNA is.

What's your RX580 metal score in Geekbench? If it is between 47k and 52k everything is fine. RX580 can't score higher except you overclock it.

1. My Z87 hackintosh with RX-580 got Kernel Panic at 10.15.5 beta2/3, but no such an issue at 10.15.5 release. I don't know why.

2. It got minimal improvement from 44K to 45K only by GB5 Metal test.

Thanks again !

Edited by jsl2000
  • Like 1

@Ericine

I got low score too with RX580 after update to Catalina 10.15.5, I was using Mojave 10.14.6 before the update, got no idea before 10.15.5

on mojave opencl always 40-41k, and metal 47-48k with RadeonBoost or without

but now with 10.15.5 OpenCL always 29-30k, and metal 34-35k

 

is somebody else experience the same issue?

can someone confirm the score with previous Catalina releases?

On my RX 590 system, the kext ruins the GeekBench 5 score which is already pretty low. I use OpenCore 0.5.9 on Catalina 10.15.5

Without RadeonBoost the RX 590 scores about 26k. Also the screen turns off on boot until I hit any key.

Snímek obrazovky 2020-06-05 v 16.26.22.png

On my RX 590 system, the kext ruins the GeekBench 5 score which is already pretty low. I use OpenCore 0.5.9 on Catalina 10.15.5

Without RadeonBoost the RX 590 scores about 26k. Also the screen turns off on boot until I hit any key.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...