IONDRVFramebuffer/AGPM or NVDA/AGPM

[ezsolt]

Post your 3 ssdts.

Likely: if your third non-CPU related SSDT references the graphics card device (renamed/defined in ssdt-gpu) it will have to be parsed after the one you uploaded. I don't think the naming of the device PEGP/GFX0/GFX1 is relevant.

Please note, that I use either SSDTs or PEGP to GFX0, HDAS to HDEF remaing via clover,
but I use them not at the same time.

Here are my ssdt-s

thanks a lot for your help

 

[vulgo]

Turns out the order of the SSDTs is irrelevant. hda-gfx 'onboard' number should be different for HDEF and HDAU. Won't hurt to inject a few more properties, device_type and some ports on the display device.

You might try this. Install the attached SSDT, clean up io display preferences

$ sudo rm /private/var/db/.com.apple.iokit.graphics

Reboot, and at this point, whether or not the web driver seems to be working, re-install the web drivers then reboot a second time.

 

[ezsolt]

Turns out the order of the SSDTs is irrelevant. hda-gfx 'onboard' number should be different for HDEF and HDAU. Won't hurt to inject a few more properties, device_type and some ports on the display device.

You might try this. Install the attached SSDT, clean up io display preferences

$ sudo rm /private/var/db/.com.apple.iokit.graphics

Reboot, and at this point, whether or not the web driver seems to be working, re-install the web drivers then reboot a second time.

I have an error with your ssdt, don't know why, the ssdt looks good. I attached a screenshot.

The good news is, that based on your ssdt and one of my older ssdts I managed to get my GPU working.
Here I also post my ssdt. Basically all I have done is to put the device-id and the @1,AAPL,boot-display things in them.

Also a good hint was to delete the .com.apple.iokit.graphics plist, when fiddeling with PEGP GXF-x device names

Now my hack is working correctly, for the last five boots I had not one issue., hope it will last.

Thanks a lot vulgo, now hopefully I can grow my hair back, because I have pulled them out in the last days

 

[toleda]

Here are my ssdt-s

SSDT-HDEF: Original, ssdt_hdef-1-100-hdas.zip; why did you modify?
SSDT-CPU: ssdtPRGEN.sh is not needed for Skylake CPU PM, try ssdt_xcpm.zip. See
macOS Native CPU/IGPU Power Management
SSDT-GPU: GFX0 the only discrete device name AGPM recognizes. All injected values are already stored in the graphics card ROM, ignored (except HDMI audio properties).

device/Name (_STA, Zero) may not work for a device if native dsdt/device/_STA exists

 

[toleda]

I also post my ssdt

Attach an IOReg with your ssdt installed.

 

[vulgo]

Some device properties are managed by the web driver, but only when it is loaded.

 

[ezsolt]

Attach an IOReg with your ssdt installed.

Thanks Toleda,
here is the ioreg

Withoult using ssdtPRGEN.sh I had my CPU running always at the highest, around 4000 MHZ.
I thought ssdtPRGEN.sh is the way to go.

 

[toleda]

Some device properties are managed by the web driver

Which properties?

 

[toleda]

here is the ioreg

OK, remove ssdt-gpu, restart, reply with new IOReg
Install ssdt-gpu, restart

thought ssdtPRGEN.sh is the way to go

Only required for Ivy Bridge, see linked thread, Post #14

 

[ezsolt]

OK, remove ssdt-gpu, restart, reply with new IOReg
Install ssdt-gpu, restart

Only required for Ivy Bridge, see linked thread, Post #14

I think there is an issue with the nvram emulation (clover / EmuVariableUEFI)

At the boot sometimes I have

NvidiaStartup: Web

and sometimes

NvidiaStartup: ERROR failed to find NVRAM registry entry

I check the nvram in every boot for the nvda_drv = 1%00 variable, and it is there.

I attachet three ioregs, one with removed ssdt-gpu, one with ssdt-gpu with working webdrivers, and one with ssdt-gpu and failed webdrivers.

Also my EFI folder is there

I hope you can catch the error