It looks like there might be some other log entries that give a clue about the SSDT-GPRW loading error. Without seeing the supporting lines, it does appear that there's an error injecting GPRW (which is what would be expected without the patch). If you still want your SSDT-GPRW replacement, be sure to include the patch in your config.plist. See full documentation
here.
@deeveedee I'll keep that in mind for the future. Thanks a lot for sharing.
@Css13 you already mentioned me in your post so that's enough
- no need to turn off vt-d
if vt-d is off in windows 10 it will be impossible to enable the sandbox or any other virtualisation software. vt-d works fine in mac os
- CSM - disabled
- C States Support: Auto
about ACPI tables
Open Core works only with .aml
- SSDT-PM.aml - I don't know where you got it but this table is for Intel 100 chipset. we use 300 serises chipset. All tables in OC folder must be have code if OSI darwin - otherwise wil be affected windows and we get BSOD
- SSDT-USBX must be obligatory for corect power menegment usb ports otherwise charging iphone /ipad is not possible, possible shutdowns portable external harddrives, sticks
- xhci unsoported kext- This kext was developed when Intel released 300 chipset at that time in apples kext were absent some ID for usb controllers but after a few months later, Apple released new mac with a 300 chipset (imac 19.1, macmini8.1) that ID present in apples kexts
@viorel78 Got it. Thank you for explaining, makes sense to me, but I can ensure you that I've been trying my setup for days and I didn't have any BSOD on Windows or USB power management issues (tried USB pen drives and hard drives only) so far. Anyway, your setup looks cleaner than mine and it requires less kexts, so probably it is also more stable.
Ok - I think you'll find that Css13's SSDT-PM works fine (it's what I use) and I think you will find that USBPorts.kext is able to inject USB Power properties just fine. I have had success with both SSDT-USBX and USBPorts - they both work fine. There is more than one "right" way to hack. Be careful about claiming that any one solution is "wrong."
When you said "I'm sorry friend, I don't want to offend you, but you made a lot of wrong decisions" - he didn't make wrong decisions - he just made different decisions.
I would agree with you, but I am still unexperienced about the Hackintosh topic and I'm more than happy to learn different (and eventually, better) ways to do things. I really appreciate your suggestions and the time you took for explaining me.
That said, I just updated my EFI.zip attachment on this thread using viorel78's one with some minor adjustments (like replacing the Generic section in config.plist file with my data and the background color of the OpenCore boot picker). It works good so far on my hardware and maybe it's a bit less "hacky" than mine.
