@c-o-pr hey guy. thanks for your detailed tutorial/guide for our board. helped me quiet a bit. even though for some reason I cannot boot with the driver openhfsplus.efi I was able to boot past the picker using hfsplus.efi only.
I have a question about your ssd's you have in your EFI folder that you posted and this is solely for self knowledge.
what are these for HPET and USB-Reset.
Also, is USBX the same as EC-USBX?
Thanks for your help.
Hey glad to hear my writeup made a diff!
Re HPET and USB-Reset, these are Dortania ACPI boilerplate made using SSDTTime on Linux to dump the system DSDT, then same utility converts into relevant ACPI.
- Strictly speaking, USB-Reset is for 400 series boards as mentioned in above docs.
- HPET is IRQ conflicts which may be legacy for this new stuff.
Re question on USBX, yes I think so... Here is a case were lore gets confusing because Dortania OpenCore guide offers some downloads which are hackintosh boilerplate but named a little diff (I think they are same in this case). Sorry to be a dork about this answer, but in strictest sense; IDK!
Something I love about Dortania write-up is they say "Hey it's important to learn by doing it yourself" and I agree, but there's too much to know and I also respect laziness of not reinventing good work of others unless there's a mosdef need.
When I ran into trouble with sleep, I figured I had better go thru every aspect of the ACPI guide and cover all bases. But this leads to paradox that this may be lore that's no longer relevant. Problem for us is if it's needed and we don't add, we are remiss for not being thorough, and if it's not necessary or even problematic, how do we know? So I agree with Dortania Guide that it's important to try and learn. OTOH, the combinatorials are ridiculous!
Re openhfsplus.efi vs hfsplus.efi, this is another case of guide lore. I've seen both work. I went with the one supplied in the Acidanthera OpenCore release area. It's pretty easy to slip up on config.plist changes so if you are having trouble look extra carefully at your basic config, like are you referring to the driver properly.
Note that the config.plist checker command (
ocvalidate) provided in the OC release Utilities folder is far more detailed that the on-line checker that's common cited. BTW—If if complains about "schema" this usually means that the spec for the release of OC requires config.plist entry details that are missing from your config; schema is the template for required fields in the plist. Older config examples may be missing fields for newer OC releases.
Also note that Dortania offers a complete spec for config.plist documented at
...See Configuration.pdf
For new OC releases, carefully read the release notes and do a config diff between the sample.plist in any future release of OC and your working config.plist. If you search for tools, there are several that help with doing this comparison. The one I like is
Python script to compare two plists and list missing keys in either. - corpnewt/OCConfigCompare
github.com
Regarding combinatorials and possible errors in my config: My build got stuck for a long while because I was just using iGPU and somehow got the installer to run in safe graphics, then I thought I could get full iGPU working and install Radeon later. The turned into a bugaboo because I didn't understand the importance of SMBIOS on graphics config. At the same time, I switched from OC 0.6.7 to 0.6.8 and was just learning ropes. I made some dumb mistakes and had some big setbacks too. What I am saying is I'm not even sure that the latest EFI I've posted will work from beginning to end of install. But now I sort of don't care because so many variables, there's only so much time in day
hth
