Jump to content
71 posts in this topic

Recommended Posts

Nice, great job. Well done  👏

It doesn't work in my case with device ID 0x3E92  ( black screen )

 

Spoiler

Screenshot2025-09-17alle19_59_01.thumb.png.4810b069b2e8b266ea14830a17fb2c04.png


I'm using device ID 0x3E98 ( I only have the integrated one ).

 

https://www.intel.com/content/www/us/en/products/sku/191792/intel-core-i79700-processor-12m-cache-up-to-4-70-ghz/specifications.html

 

I will continue to explore the app 😋

  • Like 4

@Anto65

Thanks for the feedback, There are several UHD 630 with different device IDs, find the one with the same device ID as you mentioned and use that to generate the config.

Can you try that one and see if that works please?

  • Like 1

Yes, I've already tried it in the proposed device IDs, but mine isn't there. I tried inserting mine into the generated plist (same black screen).
I think it might work with Mobile ID, but I want to use the desktop one.
ID 0x3E98 is the one for the i7 9700.

... I will try again

  • Like 1
1 minute ago, Anto65 said:

Yes, I've already tried it in the proposed device IDs, but mine isn't there. I tried inserting mine into the generated plist (same black screen).
I think it might work with Mobile ID, but I want to use the desktop one.
ID 0x3E98 is the one for the i7 9700.

... I will try again

Ok thanks, I will check that out and find out whats' going on, thanks for the feedback. I guess I need to be more focused on the Intel iGPUs I was testing it with AMD GPUs mostly.

If that failed to work again wait for the next revision don't spend any more time on it.

  • Like 1

@Oyecomova

Hi, let's continue our previous conversation about GPU device properties here.

I created a dedicated topic for GPU device properties and I'm referring to your post at:

 

@Anto65

can you try this please:

 

config.plist

  • Like 2
4 hours ago, Max.1974 said:

@Cyberdevs oh my gosh so wonderful tool!! My brother congrats !!! You are the best!! :thumbsup_anim:

Thanks man :)

This is a work in progress and it needs to be refined until it's completely finished.

  • Like 2

Amazing app from an amazing guy.

i tested it and it’s working. I was getting a black screen, at least i thought i was. 
The thing is, it takes a bit longer to get to the lock screen. 

I got the black screen and before i rebooted i went to get me a beer. When i came back the lock screen showed up.

@Anto65, have you tried to wait a bit? Maybe you have the same “issue?”

  • Like 4
On 9/17/2025 at 6:40 PM, Cyberdevs said:

Please test the app and check the benchmarks before and after and share the results if you like so I can know how to improve the app.

 tryed your app works for me Stunning work. well done. I think you need to take out the boot argument in the Nvram its not needed

Screenshot 2025-09-19 at 05.54.26.png

Edited by BALDY_MAN
  • Like 3

Hi, @Cyberdevs

How the settings generated by this application interact with entries in DeviceProperties ---> Add ---> PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) ---> PP,PP_WorkLoadPolicyMask && PP_PhmSoftPowerPlayTable?

Is it possible (or makes sense) to use these settings together?

  • Like 1

@Cyberdevsinteresting utility :)

image.thumb.png.2354c4d835dc901ee31c624a960caa20.png

i have 2 6950xt both spoofed

One of them needs also of a SSDT bridge for its PCIE slot

Both are working well 

image.thumb.png.65a20660c5db6627802238ef2808d738.png

 

Why your app sees one as 6900xt? and your app could be usefull to improve my config.plist in your opinion?

Thanks

 

  • Like 2
5 minutes ago, fabiosun said:

@Cyberdevsinteresting utility :)

 

i have 2 6950xt both spoofed

One of them needs also of a SSDT bridge for its PCIE slot

Both are working well 

 

 

Why your app sees one as 6900xt? and your app could be usefull to improve my config.plist in your opinion?

Thanks

Hi, thanks, it's a work in progress and it's far from being a complete project. I just had the idea and started to play with this project.

You just need to select one GPU to generate the config, based on the screenshot you've selected all the GPUs, when you click a GPU in the list it will be selected for generating the config. click Clear All button, select your RX 6950 GPU and generate the config. it will generate the device properties in a new config file, you can use the same settings for your second GPU but the device path needs to be edited manually. I didn't add the function for dual GPUs to the app.

 

1 hour ago, verdazil said:

Hi, @Cyberdevs

How the settings generated by this application interact with entries in DeviceProperties ---> Add ---> PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) ---> PP,PP_WorkLoadPolicyMask && PP_PhmSoftPowerPlayTable?

Is it possible (or makes sense) to use these settings together?

Hi

If I understand your question the app will generate the device properties based on the selected GPU then it add's the to the config.plist based on the device path. you can either save it in a new config or add them to your existing config this part is the obvious part if I get your question right.
About the PP,PP_WorkLoadPolicyMask && PP_PhmSoftPowerPlayTable I'm not sure what you mean exactly. Can you please explain a bit more or attach the config generated for your system so I can take a look?

 

1 hour ago, BALDY_MAN said:

 tryed your app works for me Stunning work. well done. I think you need to take out the boot argument in the Nvram its not needed

 

It doesn't hurt to have it enabled, you can remove it if your GPU doesn't require it.

  • Like 1

@Cyberdevs,

The settings for my video card were made according to this description:

https://github.com/perez987/6600XT-on-macOS-with-softPowerPlayTable

 

One more thing. If I'm wrong, please correct me.

As far as I know, in OpenCore, device properties must be assigned to the actual device, not to intermediate PCI bridges.
For example:

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) → PCI Bridge (not suitable for injecting GPU properties)

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) → VGA compatible controller (this is the correct path for GPU properties)

Therefore, to inject properties such as device-id, model, or AAPL,slot-name, the full device path of the VGA controller must be used.

my-worked-config.plist.zip your-app-config.plist.zip

  • Like 2

@verdazil

Thanks for the reply, since generating power play tables are a very complex and GPU specific procedure I'm not sure if using PP,PP_WorkLoadPolicyMask && PP_PhmSoftPowerPlayTable both will affect the system. maybe @miliuco can explain this question better.
 

24 minutes ago, verdazil said:

One more thing. If I'm wrong, please correct me.

As far as I know, in OpenCore, device properties must be assigned to the actual device, not to intermediate PCI bridges.
For example:

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) → PCI Bridge (not suitable for injecting GPU properties)

PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) → VGA compatible controller (this is the correct path for GPU properties)

I'm not entirely sure about this but the app detects the device path and uses it to inject the properties, but I guess the device path can be edited if that's wrong.
On my Z690 the device path is PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) but on my Z270 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) so if it detects the wrong path I guess I need to fix it.

  • Like 1
Just now, Cyberdevs said:

When using the new device properties do you see any differences in temperatures or the performance?  

I haven't tested with the settings from this app, as I was hoping to get information about their compatibility with my current settings. However, I can test it and share the results.

  • Like 1

@verdazil

To be honest I wan't sure about the whole project and the benefits of it because WEG does a great job for the most part, but since it has issues with Tahoe until the devs update WEG I decided to give it a try and see how the system performs with these setting and it worked on my RX 580 which many users had issues with theirs and Tahoe.

So the whole project is in limbo for now and I'm not sure whether to move forward or abandon it if it doesn't prove much effective.

@Cyberdevs,

Finished testing. When I configured my graphics card according to the project https://github.com/perez987/6600XT-on-macOS-with-softPowerPlayTable I had two goals: zero RPM during idle time and slight limitation of maximum performance to reduce chip heating.

After merging (the right way) my settings and the app's settings, there was a slight performance boost. However, temperatures didn't increase and the zero RPM level remained unchanged.

On the negative side, there's a 15-second black screen pause before the desktop appears during system boot.

I can't say whether I benefit from using the app's settings. Perhaps, in my case, everything was configured correctly according to the aforementioned project.

 

Spoiler

Tests.thumb.png.52587982f80162f3dce0fb4cab3c4b45.png

 

  • Like 2
×
×
  • Create New...