Jump to content

AGPM Injector kext generator app!!


Pavo
145 posts in this topic

Recommended Posts

12 minutes ago, telepati said:

@Pavo  app does not recognize SMBIOS 19,1 will you add this? When I open it shows my board ID I choosing it but it does not generate anything.

 

1581993306_ScreenShot2019-05-17at15_36_41.png.1eeed9ad28e0f934a435e3331cbcdfaa.png

The app list whatever machines that AGPM supports, if its showing a board number instead that means there were new machines added to AGPM. If you know the SMBIOS of the added board numbers I can update the app to reflect the SMBIOS instead.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Pavo there is something wrong but I don't get it. When I open your app it is auto selected MacPro4,1 and I can create a kext to desktop. But I am using 19,1 SMBIOS and when I change to 19,1 it never generates anything. is it a bug or something wrong on my system?

 

1200769349_ScreenShot2019-05-25at20_43_53.png.bfb92df896c981a3a9e9bbbff0271494.png

 

1165961232_ScreenShot2019-05-25at20_44_43.png.cef9ef51ed4ced84e5a80a267deecef3.png

Link to comment
Share on other sites

3 hours ago, telepati said:

Pavo there is something wrong but I don't get it. When I open your app it is auto selected MacPro4,1 and I can create a kext to desktop. But I am using 19,1 SMBIOS and when I change to 19,1 it never generates anything. is it a bug or something wrong on my system?

 

1200769349_ScreenShot2019-05-25at20_43_53.png.bfb92df896c981a3a9e9bbbff0271494.png

 

1165961232_ScreenShot2019-05-25at20_44_43.png.cef9ef51ed4ced84e5a80a267deecef3.png

The reason it auto selects MacPro4,1 is because it’s the first in the list, I don’t have the app checking against system SMBIOS that the app is being ran off of, but it’s not a bad idea.I will look into that, thanks for the report. You can always open a issue on github under the app repo.

Edited by Pavo
  • Thanks 1
Link to comment
Share on other sites

2 hours ago, Pavo said:

The reason it auto selects MacPro4,1 is because it’s the first in the list, I don’t have the app checking against system SMBIOS that the app is being ran off of, but it’s not a bad idea.I will look into that, thanks for the report. You can always open a issue on github under the app repo. 

 

It is a bug then? I will wait for the next release then.

 

Also from now on, I will open an issue on GitHub.  :wink_anim:

 

Thank you.

 

Edit: You have already released the new version, I will test tomorrow. :superman:

Edited by telepati
Link to comment
Share on other sites

4 hours ago, telepati said:

 

It is a bug then? I will wait for the next release then.

 

Also from now on, I will open an issue on GitHub.  :wink_anim:

 

Thank you.

 

Edit: You have already released the new version, I will test tomorrow. :superman:

Should be fixed now, just update from within the app to download the latest release.

  • Thanks 1
Link to comment
Share on other sites

7 hours ago, Pavo said:

Should be fixed now, just update from within the app to download the latest release.

Just updated to the latest release. For some reason the app with not create an AGPMInjector kext for SMBIOS iMac 19,1 or 19,2. All other SMBIOS work perfectly fine. 

Link to comment
Share on other sites

2 hours ago, tikizondo94 said:

Just updated to the latest release. For some reason the app with not create an AGPMInjector kext for SMBIOS iMac 19,1 or 19,2. All other SMBIOS work perfectly fine. 

 

1 hour ago, telepati said:

 

I tested either and still didn't work for 19,1 and 19,2, just like the @tikizondo94 said.

Hmmm, will look into it again. Thanks for the feedback.

  • Thanks 1
Link to comment
Share on other sites

3 hours ago, tikizondo94 said:

Just updated to the latest release. For some reason the app with not create an AGPMInjector kext for SMBIOS iMac 19,1 or 19,2. All other SMBIOS work perfectly fine. 

 

2 hours ago, telepati said:

 

I tested either and still didn't work for 19,1 and 19,2, just like the @tikizondo94 said.

Ok should be fixed now, Also I have switched to a better versioning scheme. Please download the latest release from Github because the auto update inside the app will not except the new version with earlier versions.

https://github.com/Pavo-IM/AGPMInjector/releases

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

Hi @Pavo

 

Tested your app and everything works well in Clover but not in OC.

This is the result in clover without your kext:

 

clopver_AGPMkext.thumb.png.28775c66e22f8fc512f36a1b070b3082.png

 

And tis is the result with your kext injected in Clover:

 

OC_AGPMkext.thumb.png.0bcf10c820963eed9565691a04e6062b.png

 

In OC I have the same result as in Clover without the kext injected.

Any ideas?

Link to comment
Share on other sites

17 minutes ago, obus said:

Hi @Pavo

 

Tested your app and everything works well in Clover but not in OC.

This is the result in clover without your kext:

 

clopver_AGPMkext.thumb.png.28775c66e22f8fc512f36a1b070b3082.png

 

And tis is the result with your kext injected in Clover:

 

OC_AGPMkext.thumb.png.0bcf10c820963eed9565691a04e6062b.png

 

In OC I have the same result as in Clover without the kext injected.

Any ideas?

Your screenshots are backwards, the first one shows it being injected, the second shows it not being injected. The reason I know this is because the second on shows the VendorxxxDevicexxx also, my injection takes those out and only has GFX0 and if you selected IGPU.

Link to comment
Share on other sites

Sorry @Pavo my bad. 

Of course you are right the second screenshot shows the injected and working kext in Clover. But the problem is still there with OC. The first screenshot is the result after injecting (?) your kext in OC.

Any thoughts?

I have no integrated Graphics so I presume I shouldn't check select IGPU?

 

Edited by obus
Link to comment
Share on other sites

13 minutes ago, obus said:

Sorry @Pavo my bad. 

Of course you are right the second screenshot shows the injected and working kext in Clover. But the problem is still there with OC. The first screenshot is the result after injecting (?) your kext in OC.

Any thoughts?

I have no integrated Graphics so I presume I shouldn't check select IGPU?

 

Show me a screenshot of the Kernel section of your OC config on the AGPMInjector.kext part.

Link to comment
Share on other sites

7 minutes ago, obus said:

Here we go.imageproxy.php?img=&key=c17464ef1b1b51c7

 

1677894678_Screenshot2019-05-28at17_46_49.thumb.png.bfe6a46097bfce29e31a85f2af160d4d.png

Remove the ExecutablePath, the kext doesn’t have a executable binary, it just has a Info.plist path.

  • Like 2
Link to comment
Share on other sites

  • 5 weeks later...

Hello @Pavo, I have tried your app and works to create the desired .kext, but unfortunately It dones't seem to work on my build... On both instances (have created one with iGPU and one without it) the result is 0x11 on GFX0 dev.. I'm not sure what am I doing wrong here.. I changed the value inside .plist and nothing, just sits at 0x11 ¿?¿?343870681_Screenshot2019-06-27at16_47_58.png.bf6571bece981824bca17afe050f05be.png

Link to comment
Share on other sites

6 hours ago, dolgarrenan said:

Hello @Pavo, I have tried your app and works to create the desired .kext, but unfortunately It dones't seem to work on my build... On both instances (have created one with iGPU and one without it) the result is 0x11 on GFX0 dev.. I'm not sure what am I doing wrong here.. I changed the value inside .plist and nothing, just sits at 0x11 ¿?¿?343870681_Screenshot2019-06-27at16_47_58.png.bf6571bece981824bca17afe050f05be.png

I'm confused on what the issue or question is? AGPM is being loaded for both the iGPU and GFX0 devices.

Link to comment
Share on other sites

12 hours ago, dolgarrenan said:

Thanks for your reply! Wasn't it supposed to have control ID 0x12 for better PM for GFX0??

After multiple test with a array of different dGPUs we have came to a conclusion that the best value is a integer of 17, which converts to 0x11 hex.

  • Like 1
Link to comment
Share on other sites

On 6/28/2019 at 9:30 PM, Pavo said:

After multiple test with a array of different dGPUs we have came to a conclusion that the best value is a integer of 17, which converts to 0x11 hex.

Cool!, I'll modify the .plist no more and leave it as is. Thanks!

Link to comment
Share on other sites

×
×
  • Create New...