telepati Posted May 17, 2019 Share Posted May 17, 2019 @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. 1 Link to comment Share on other sites More sharing options...
Pavo Posted May 17, 2019 Author Share Posted May 17, 2019 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. 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. 1 1 Link to comment Share on other sites More sharing options...
tikizondo94 Posted May 22, 2019 Share Posted May 22, 2019 Awesome app! Can you update with SmBIOS 19,1? Will this info help? Mac-AA95B1DDAB278B95.plist Link to comment Share on other sites More sharing options...
telepati Posted May 25, 2019 Share Posted May 25, 2019 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? Link to comment Share on other sites More sharing options...
Pavo Posted May 25, 2019 Author Share Posted May 25, 2019 (edited) 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? 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 May 25, 2019 by Pavo 1 Link to comment Share on other sites More sharing options...
telepati Posted May 25, 2019 Share Posted May 25, 2019 (edited) 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. Thank you. Edit: You have already released the new version, I will test tomorrow. Edited May 25, 2019 by telepati Link to comment Share on other sites More sharing options...
Pavo Posted May 26, 2019 Author Share Posted May 26, 2019 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. Thank you. Edit: You have already released the new version, I will test tomorrow. Should be fixed now, just update from within the app to download the latest release. 1 Link to comment Share on other sites More sharing options...
tikizondo94 Posted May 26, 2019 Share Posted May 26, 2019 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 More sharing options...
telepati Posted May 26, 2019 Share Posted May 26, 2019 8 hours ago, Pavo said: Should be fixed now, just update from within the app to download the latest release. I tested either and still didn't work for 19,1 and 19,2, just like the @tikizondo94 said. Link to comment Share on other sites More sharing options...
Pavo Posted May 26, 2019 Author Share Posted May 26, 2019 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. 1 Link to comment Share on other sites More sharing options...
Pavo Posted May 26, 2019 Author Share Posted May 26, 2019 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 2 1 Link to comment Share on other sites More sharing options...
telepati Posted May 26, 2019 Share Posted May 26, 2019 1 hour ago, Pavo 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 Tested it all works now. Great job. Thank you. Link to comment Share on other sites More sharing options...
obus Posted May 28, 2019 Share Posted May 28, 2019 Hi @Pavo Tested your app and everything works well in Clover but not in OC. This is the result in clover without your kext: And tis is the result with your kext injected in Clover: In OC I have the same result as in Clover without the kext injected. Any ideas? Link to comment Share on other sites More sharing options...
Pavo Posted May 28, 2019 Author Share Posted May 28, 2019 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: And tis is the result with your kext injected in Clover: 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 More sharing options...
obus Posted May 28, 2019 Share Posted May 28, 2019 (edited) 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 May 28, 2019 by obus Link to comment Share on other sites More sharing options...
Pavo Posted May 28, 2019 Author Share Posted May 28, 2019 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 More sharing options...
obus Posted May 28, 2019 Share Posted May 28, 2019 30 minutes ago, Pavo said: Show me a screenshot of the Kernel section of your OC config on the AGPMInjector.kext part. Here we go. Link to comment Share on other sites More sharing options...
Pavo Posted May 28, 2019 Author Share Posted May 28, 2019 7 minutes ago, obus said: Here we go. Remove the ExecutablePath, the kext doesn’t have a executable binary, it just has a Info.plist path. 2 Link to comment Share on other sites More sharing options...
obus Posted May 28, 2019 Share Posted May 28, 2019 Works like a charm after removing ExecutablePath path Thank's for your good work @Pavo Link to comment Share on other sites More sharing options...
dolgarrenan Posted June 27, 2019 Share Posted June 27, 2019 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 ¿?¿? Link to comment Share on other sites More sharing options...
Pavo Posted June 27, 2019 Author Share Posted June 27, 2019 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 ¿?¿? 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 More sharing options...
dolgarrenan Posted June 28, 2019 Share Posted June 28, 2019 9 hours ago, Pavo said: I'm confused on what the issue or question is? AGPM is being loaded for both the iGPU and GFX0 devices. Thanks for your reply! Wasn't it supposed to have control ID 0x12 for better PM for GFX0?? Link to comment Share on other sites More sharing options...
Pavo Posted June 28, 2019 Author Share Posted June 28, 2019 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. 1 Link to comment Share on other sites More sharing options...
dolgarrenan Posted July 1, 2019 Share Posted July 1, 2019 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 More sharing options...
URBANsUNITED Posted July 5, 2019 Share Posted July 5, 2019 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 Link to comment Share on other sites More sharing options...
Recommended Posts