AGPM Injector kext generator app!!

[Pavo]

On 7/5/2019 at 2:26 AM, URBANsUNITED said:

So, means mine is ok too?

I am a bit lost, sorry...

Looking for possiblities why my system is under Catalina not waking up properly, but it does on Mojave.

 

Thanks URBANsUNITED

 

AGPM has nothing to do with Wake/Sleep

[innerd]

I know that the injector needs a proper cpu with x86platformplugin loaded, but is it possible to inject that proprieties with a workaround? I really need to fix my Vega 64 power management

[Pavo]

34 minutes ago, innerd said:

I know that the injector needs a proper cpu with x86platformplugin loaded, but is it possible to inject that proprieties with a workaround? I really need to fix my Vega 64 power management

You might wanna look into https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Radeon.en.md, there are multiple ways to inject properties for the GPU. It seems you are wanting to change PowerPlay or "Wattsman" type settings, which is not Power Management is about.

How could I tune my GPU configuration?
ATI/AMD GPUs could be configured by aty_config, aty_properties parameters that one could find in AMDxxxxController.kext Info.plist files. Different framebuffers have overrides for these preferences for lower energy consumption, higher performance, or other reasons. Unfortunately in such combinations they often are unsuitable for different GPUs.
WhateverGreen allows to specify your own preferred parameters via GPU controller properties to achieve best GPU configuration. Use CFG, prefix for aty_config properties, PP, prefix for aty_properties, and CAIL, prefix for cail_properties from AMDRadeonXxxxx.kext Info.plist files. For example, to override CFG_FB_LIMIT value in aty_config you should use CFG,CFG_FB_LIMIT property.
Further details are available in SSDT sample to get the general idea.

 

Edited July 7, 2019 by Pavo

[innerd]

Already changed those type of settings, with vgtab or PyVega. As I said in another topic I have a strange behavior with my vega64, the p-states probably don't work as they should, under load (like valley benchmark) i can see the core frequency around 500-1000 with fluctuant fps (Geekbench is even worse, the core can't raise over 100). It seems that the gpu doesn't receive the right instruction (just a guess) in those type of scenarios while for example in LuxMark the gpu can maximize correctly its core/memory frequency with more than decent results. Can it be a lack of power management? Any advises will be really appreciated

Edited July 7, 2019 by innerd

[real3x]

Just a little clarification since i've lost track of what happen with AGPM, specially on AMD, i always had nvidia card since 10.5 :)

 

On older sandy bridge which load ACPI_SMC_PlateformPlugin, there is no way to load x86PlateformPlugin so there is no way to activate AGPM (RX 580) ?

[ianxpluto]

Hi Pavo. Thank you for your app for us. I have a question, what's different between AGPMInjector and Whatevergreen boot arg agdpmod=ignore ?

Edited October 26, 2019 by ianxpluto

[Pavo]

41 minutes ago, ianxpluto said:

Hi Pavo. Thank you for your app for us. I have a question, what's different between AGPMInjector and Whatevergreen boot arg agdpmod=ignore ?

AGPM = AppleGraphicPowerManagement. AGDP = AppleGraphicsDevicePolicy

[ianxpluto]

7 minutes ago, Pavo said:

AGPM = AppleGraphicPowerManagement. AGDP = AppleGraphicsDevicePolicy

Sorry for bother you.

I thought AGPM & AGDP are linked, because they will unload together and loaded together.

[ianxpluto]

As iMac 19,1 did I inject it right ? 

[Pavo]

4 minutes ago, ianxpluto said:

As iMac 19,1 did I inject it right ? 

Yeah looks correct.

[ianxpluto]

1 minute ago, Pavo said:

Yeah looks correct.

Awesome, thank you.

[Pavo]

Found a HUGE bug in the the app on version 2.7.7, if you generated a injector kext using this version please update to the latest (2.7.8) and re-generate your injector kext. 

[Pavo]

AGPMInjector 2.8.0 Released

- Fixed MacPro7,1 crashing

[telepati]

@Pavo I downloaded the new version and try to create a new one but no Enable IGPU option? Did you remove this? 

 

I think this is a bug; No IGPU after; Also it shows vendor and device ID instead of GFX0

 

Before;

 

 

After

 

Edited November 18, 2019 by telepati

[Pavo]

2 hours ago, telepati said:

@Pavo I downloaded the new version and try to create a new one but no Enable IGPU option? Did you remove this? 

 

I think this is a bug; No IGPU after; Also it shows vendor and device ID instead of GFX0

 

Before;

 

 

After

 

Yes I removed IGPU option and working on adding them back again. Yes only the dGPU Vendor and Device IDs will be used now for dGPUs.

[jinbingmao]

Edited November 20, 2019 by jinbingmao
add

[theoriginalmagneto]

I just discovered this, thanks! However, since I'm using the iGPU for encoding/decoding HEVC, I don't think I can use the kext...yet. Hope you re-add the iGPU support soon  

[ghost8282]

Thanks for this Pavo!

Is it possible to add the GTX Titan Black?

Vendor: 10de

Device id: 100c

 

I added a pull request in github.

 

I generated the kext by using the 'GTX Titan' and then I manually edited the device id into the kext, everthing seems ok.

I'm running catalina inside kvm/qemu.

 

 

Edited January 2, 2020 by ghost8282

[Paksman]

2 hours ago, ghost8282 said:

Thanks for this Pavo!

Is it possible to add the GTX Titan Black?

Vendor: 10de

Device id: 100c

 

I added a pull request in github.

 

I generated the kext by using the 'GTX Titan' and then I manually edited the device id into the kext, everthing seems ok.

I'm running catalina inside kvm/qemu.

 

 

I'm not 100% shure but according to toleda, heuristic id for Nvidia gpu should be 4, not ffffffff

[ghost8282]

3 hours ago, Paksman said:

I'm not 100% shure but according to toleda, heuristic id for Nvidia gpu should be 4, not ffffffff

Not sure 100% me too

The generated kext for 'Titan' with the Pavo app 2.8.8 has -1 (0xffffffff).

However I found an older kext and the toleda's post with a value of 4 for nvidia.

I switched yesterday from 4 to -1 and I didn't notice any change in the behaviour.

 

Moreover, I saw around different templates for the AGPM injector kext, with additional entries, such as Threshold_High and Threshold_Low..Also for the structure: Pavo's app generates the VendorXXXXDevice1234 tree, other templates, such as that of toleda have also the GFX0 tree...but maybe things are changed, so there's some confusion in my mind, maybe someone can explain it a bit.

 

Thanks

Edited January 2, 2020 by ghost8282

[Pavo]

@ghost8282 Added.

[cclark170]

I'm having a hard time getting this to work.  My setup is:

• Catalina 10.15.2
• SMBIOS set as iMac19,1
• MSI Vega56 dGPU
• UHD630 iGPU (i7-9700k CPU)

The generated kext has the following Info.plist:

 

But in IORegistry Explorer, I see this:

 

It seems like the injector is just not doing what it is supposed to.

 

I did notice the following in my Console log:

 

Quote

2020-01-06 22:13:28.794386-0600  localhost kernel[0]: (AppleGraphicsPowerManagement) <AppleGraphicsPowerManagement`AGPMLogString(AGPMLogLevel, AGPMLogModule, char const*, unsigned int, char const*, char const*, ...)> [AGPM][WARN ][CONTROLLER  ][createAGPMClass         ] GPU = GFX0 unknownPlatform (no matching vendor_id+device_id or GPU name); don't create AGPM class

 

I don't know if it could be related or not.

 

Thanks in advanced!

[Pavo]

26 minutes ago, cclark170 said:

I'm having a hard time getting this to work.  My setup is:

• Catalina 10.15.2
• SMBIOS set as iMac19,1
• MSI Vega56 dGPU
• UHD630 iGPU (i7-9700k CPU)

The generated kext has the following Info.plist:

 

But in IORegistry Explorer, I see this:

 

It seems like the injector is just not doing what it is supposed to.

 

I did notice the following in my Console log:

 

 

I don't know if it could be related or not.

 

Thanks in advanced!

The log error has nothing to do with my kext injector, because it doesn't match against GPU device name, it matches against the Vendor and Device-ID. I dunno why its not working for you unless whatever boot loader you are using isn't injecting kext correctly. It is working fine for multiple other users right now.

[theoriginalmagneto]

On 1/20/2019 at 6:12 PM, Pavo said:

Added user notification if there is an update on Github

AGPMInjector_2.3.4

Any chance to add Intel IG support?

[telepati]

@Pavo did you remove 19,1 I don't see it in the latest version?

 

Edited January 16, 2020 by telepati