Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
An interesting finding:

By using lilu and whatevergreen and by altering nvram to enable HWaccel (sudo nvram boot-args="shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94"), geekbench scores drop in half. In my case metal from 47K+ dpopped into 23K. Resetting nvram corrects this.

Sorry if this has been mentioned
 
An interesting finding:

By using lilu and whatevergreen and by altering nvram to enable HWaccel (sudo nvram boot-args="shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94"), geekbench scores drop in half. In my case metal from 47K+ dpopped into 23K. Resetting nvram corrects this.

Sorry if this has been mentioned
AFAIK, this only happen on RX580 (may be other Polaris GPU as well) and in Catalina.
 
An interesting finding:

By using lilu and whatevergreen and by altering nvram to enable HWaccel (sudo nvram boot-args="shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94"), geekbench scores drop in half. In my case metal from 47K+ dpopped into 23K. Resetting nvram corrects this.

Sorry if this has been mentioned

This also happens on my system, but scores are usually back to normal after a sleep-wake cycle. I use AirOut 2 to quickly measure the performance; ideally, I want to see >3000 GFLOPS in FP32 performance.
 
Ah ok. You are the only one with that issue so far though. So I guess it is not directly related to RadeonBoost.
Then some conflicts between My config, OC0,57 and Radeonboost :(

@CMMChris do I need to repair permissions and rebuild kext cache if I'm using OC 0,57?
 
Last edited:
Please try version 1.5 from here: https://www.hackintosh-forum.de/for...res-wie-am-echten-mac-unter-windows/?pageNo=1
Haven't added it in this topic yet. Also please note that you need to use it along Whatevergreen for Polaris cards.

This version boosted my RX 580 (a little bit). Thank you.
[automerge]1589932879[/automerge]
An interesting finding:

By using lilu and whatevergreen and by altering nvram to enable HWaccel (sudo nvram boot-args="shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94"), geekbench scores drop in half. In my case metal from 47K+ dpopped into 23K. Resetting nvram corrects this.

Sorry if this has been mentioned
AFAIK, this only happen on RX580 (may be other Polaris GPU as well) and in Catalina.
This also happens on my system, but scores are usually back to normal after a sleep-wake cycle. I use AirOut 2 to quickly measure the performance; ideally, I want to see >3000 GFLOPS in FP32 performance.

This post solved in my case (rx580 + Catalina):

 
Last edited:
Recent GB5 Metal Compute Scores
  1. No RadeonBoost : 37154
  2. RadeonBoost v1.0 : 40565
  3. RadeonBoost v1.3 : 37740
  4. RadeonBoost v1.5 : 42946
 
  • Like
Reactions: CMMChris
Ah ok. You are the only one with that issue so far though. So I guess it is not directly related to RadeonBoost.
@CMMChris
I make new test with 1.5 and OC 0,57 NBK from @h9826790
Then
Lilu.kext 1.4.3 (but test with 1.4.4 same freeze and auto-reboot)
WhateverGreen.kext 1.3.8 (but test with 1.3.9 same freeze and auto-reboot)

It start and RadeonBoost enable
Capture d’écran 2020-05-20 à 09.52.56.png


I have still freeze and auto-reboot cMP with RadeonBoost installed
and I have these error in console
1589963890850.png
 
@CMMChris
I make new test with 1.5 and OC 0,57 NBK from @h9826790
Then
Lilu.kext 1.4.3 (but test with 1.4.4 same freeze and auto-reboot)
WhateverGreen.kext 1.3.8 (but test with 1.3.9 same freeze and auto-reboot)

It start and RadeonBoost enable
View attachment 916902

I have still freeze and auto-reboot cMP with RadeonBoost installed
and I have these error in console
View attachment 916900
Rather than figure out what’s wrong, it may be easier and quicker to install a new clean MacOS.

Since you are the only person reported this issue so far. Most likely it’s your OS has problem.

To perform a clean installation, we can know if that’s software / hardware issue straight away.

The idea is simple. Install a clean Mojave on a spare drive, then install OC (by using cdf’s config, or my package) and RadeonBoost. Don’t do anything else.

If still freeze, then 99% you have some hardware issue that we can’t fix.
 
  • Like
Reactions: startergo
Rather than figure out what’s wrong, it may be easier and quicker to install a new clean MacOS.

Since you are the only person reported this issue so far. Most likely it’s your OS has problem.

To perform a clean installation, we can know if that’s software / hardware issue straight away.

The idea is simple. Install a clean Mojave on a spare drive, then install OC (by using cdf’s config, or my package) and RadeonBoost. Don’t do anything else.

If still freeze, then 99% you have some hardware issue that we can’t fix.
OK but it wasn't freeze with the first Radeonboost but without improvement
and now with last RadeonBoost (1.4 and 1.5) it freeze
then impact is clearly based between Radeonboost version and hardware/software of course
but ktext is common with

@CMMChris have you old version of Radeonboost for me I can make several tests

thank you
 
OK but it wasn't freeze with the first Radeonboost but without improvement
and now with last RadeonBoost (1.4 and 1.5) it freeze
then impact is clearly based between Radeonboost version and hardware/software of course
but ktext is common with

@CMMChris have you old version of Radeonboost for me I can make several tests

thank you
Are you sure you are not running multiple instances of LILU/WEG in different folders? kexstat loaded kexts.
 
  • Like
Reactions: leoaf79
By more than standard deviation?
I haven't scrupulously collected the data and put it to proper analysis and my conclusion might not stand up to proper review but in general, I am seeing 43xxx for Scenario 5 and 41xxx Scenario 6.

Was hoping others would have a go to confirm.
 
Last edited:
10.15.5 OC device properties injection even with VMM flag on. Excellent results:
Code:
<dict>
    <key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>@0,name</key>
                <data>
                QVRZLE9yaW5vY28=
                </data>
                <key>ATY,EFIVersion</key>
                <data>
                MDEuMDEuMTgz
                </data>
                <key>CFG,CFG_FB_LIMIT</key>
                <data>
                BA==
                </data>
                <key>CFG,CFG_PTPL2_TBL</key>
                <data>
                ggAAAHwAAAB2AAAAcAAAAGoAAABkAAAAXgAAAFgAAABS
                AAAATAAAAEYAAABAAAAAOgAAADQAAAAuAAAAKAAAAA==
                </data>
                <key>PP,PP_PowerPlayEnabled</key>
                <data>
                AQAAAA==
                </data>
                <key>PP,PP_WorkLoadPolicyMask</key>
                <data>
                IA==
                </data>
                <key>agdpmod</key>
                <data>
                cGlrZXJhAA==
                </data>
                <key>model</key>
                <data>
                QU1EIFJhZGVvbiBSWCA1ODA=
                </data>
                <key>rebuild-device-tree</key>
                <data>
                AA==
                </data>
                <key>shikigva</key>
                <data>
                kA==
                </data>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
            <array>
                <string>ATY,EFIVersion</string>
            </array>
        </dict>
    </dict>
</dict>
 
  • Like
Reactions: h9826790 and cdf
What is this? Most of those properties are useless. Why are you specifying a framebuffer which is not intended to be used on a PC card? What is "<key>ATY,EFIVersion</key>" supposed to do on a Polaris card?
 
What is this? Most of those properties are useless. Why are you specifying a framebuffer which is not intended to be used on a PC card? What is "<key>ATY,EFIVersion</key>" supposed to do on a Polaris card?
That framebuffer thing may actually valid for PULSE RX580 (if that's not purely cosmetic with that injection).

Apple do apply Orinoco framebuffer for the PULSE RX580 8GB card that use in the BlackMagic eGPU kit.

Nowadays, I don't think there is any difference anymore. But in the old days, having Orinoco framebuffer can avoid few bugs (e.g. the GPU can't display after wake from sleep).

The VBIOS mod to achieve that was discuss at here
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.