- Feb 21, 2016
- Gigabyte Z370 Aorus Gaming 7
- RX 5700
- Mobile Phone
I don't think so! I have installed F13, and it fails with the same errors as previously. I have even tried booting of my Mojave boot USB, same errors. The one that really worries me is one that occurs before the last errors.Another new one so soon? wonder if they fixed ACPI errors
[ 1.992433] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) [ 1.992455] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20180810/psparse-516) [ 1.995390] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) [ 1.995411] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20180810/psparse-516)
Hello @MysticalOS Any chance of sharing that new BIOS with the secret sauce? Please and thank you!And done. On a modded F11 with all latest CPU microcode updates that patch all latest meltdown and spectre and Retpoline variants and what nots. I wonder if macOS is smart enough to disable the CPU eating work arounds or not though when it's mitigated at cpu level.
After searching for and reading about the programming tools needed to alter BIOS code I am certain that the witchcraft involved in changing microcode in an existing BIOS build is way beyond my ken. I was wondering if your modded F11 was working for you and if you would be willing to share it. See enclosed gift.My understanding is you CAN make F12 and even 13 work with a custom DSDT to remove the bad nonsense. But I prefer clover hot patching myself. I wonder what an ACPI hot patch would look like to remove/fix the PCIO stuff