- Joined
- Dec 31, 2013
- Messages
- 811
- Motherboard
- Huawei Matebook D
- CPU
- i5-8250U
- Graphics
- UHD 620
- Mobile Phone
Thanks for the effort...!!Nothing about graphics jumps out at me in your IOReg dump. Could it be that Big Sur is treating an Intel i3 differently than Catalina did? I see you're spoofing device-id 0x3e92 (same as my i7-8700). The IOReg dump from my rig running Catalina (with i7-8700) is attached. Maybe this will offer some clues. You might want to carefully examine your IOReg dumps from Catalina and Big Sur to see if you notice any differences. I'm still running Catalina as my baseline and only "visit" Big Sur for occasional testing. If you haven't solved this and I run Big Sur again, I'll post my IOReg dump with Big Sur. Sorry I don't have more to offer.
@zzmadd One other thing that I didn't inspect too closely, but you may want to examine. Your OC config.plist enables an ACPI rename of PPMC->PMCR. If you examined your extracted ACPI and found that you do indeed have a PPMC that can simply be renamed to PMCR - that's a clever solution; however, your config.plist also enables injection of SSDT-PMC.aml which also defines Device (PMCR). Are you getting any ACPI errors at boot that indicate that you have conflicting definitions of PMCR?
@zzmadd Take a close look at your IOReg dump. You'll see that you have two instances of PMCR. I only have one instance of PMCR in my IOReg, so something's not right with your PMCR patching. Without seeing your extracted ACPI, I am not sure of the proper PPMC/PMCR patching for you, but I suspect that you don't need the PPMC->PMCR rename.
Indeed another error. I dropped the PPMC->PMCR rename.
Now it shows just one instance of PMCR.
Still no H265 acceleration though.
I'll look into your IOReg and compare to mine to see if anything comes up.
If you have a chance and remember please drop the Big Sur one as well.
Thanks a lot!!