- Joined
- Mar 6, 2013
- Messages
- 266
- Motherboard
- Gigabyte X299X Designare 10G
- CPU
- i9-10980XE
- Graphics
- AMD 6900XT
- Mobile Phone
Sounds good - what loop kit have you got? I'm still running on my CoolerMaster 360mm AIO. I've spent nearly two weeks testing and tuning the overclock, and talking to the overclocking experts over at overclock.net. There's a 90+ page thread there on overclocking the 10980XE in which I've learnt a lot.Hey, I finally got my water cooling setup configured to a point where I can run it without the fear of drenching everything and am now embarking on the hackintosh journey for these parts as well.
Based on that I've now decided to take the plunge and go full custom loop. Never done it before, but I thought given I spent so much on the system, and am being limited by my AIO in terms of how much I can OC, I'd go the full distance. I'm hoping to get a large external radiator, the MO-RA3 420 (9 x 140mm fans!). CPU block I've not 100% decided yet; I'd really like the Optimus Signature V2 but it's very expensive and only available in the US. I just learned about a new company called TechN who are based in Europe and have a 2066-mount block that could be good.
Unfortunately I can somewhat corroborate beltzak's experience, though not entirely. I do encounter the BIOS "fake reset" bug quite often, but not consistently. I started out with your EFI @TheBloke because it was the only setup that was able to boot. I tried the original one, a custom one built from scratch and one from the german hackintosh-forum, neither of which got me past the OC init stage despite me fiddling with them for quite some time.
I currently observe some rather strange behavior in that if I even as much as sneeze in the wrong direction, OC will fail at the init stage. Sometimes however, it will boot normally and straight into a working macOS install (latest Catalina). I tried Big Sur as well, but no dice. Seems the APFS changes are screwing with things too much for the time being.
Either way, as soon as I do anything at all to the OC config, be that tweaking the config.plist in any way, removing, adding or even just updating an existing Kext or tweaking ACPI patches, I immediately get boot issues again.
These manifest in the sense that it will get right to the end of the OC init sequence and then hard reset. It will then show signs of the "fake reset" bug where the language switches to French and the XMP profile is maskedly reset.
I'd be really interested in what progress you've made on your EFI, to see what makes it work for you.
Huh, this is strange. I have to think it must be EFI related then, as for me booting is rock solid - normal booting anyway, when the BIOS menus aren't involved.
I do have those weird issues related to overclocking, where when overclock settings are applied I must never boot OpenCore from the BIOS, or after the BIOS has been opened. And when I do a shutdown in macOS, the BIOS resets my VCCSA voltage.
But aside from that, macOS is booting fine. Tested literally 30-40 times now. 30+ on BIOS F3B, about 10 on F3C.
Attached is my EFI. It's OpenCore 0.6.2. I don't yet have OpenCanopy installed, and this EFI doesn't yet have any settings changed related to dual-booting Windows. I removed my serial etc from PlatformDetails (marked with CHANGEME).
On your first boot with this EFI I recommend clearing your NVRAM - it's option 7 in the OpenCore boot menu (or option 8 if you have two bootable drives available, eg macOS + Windows).
In terms of SSDT and kexts it's the same as dolgarrenan's first post except I removed the SSDT related to the 5700XT GPU (I have the Vega 64), and I updated to the latest versions of Lilu, WhateverGreen, VirtualSMC and the SMC plugins.
I briefly tried adding SSDT-PLUG-DRTNIA as recommended by the Drtania guide for Skylake-X (and which I noted a couple of other people here are using), but I couldn't notice any difference, so I've disabled it. You'll find it's still installed, but disabled in the config.plist.
You've got the 10980XE right? If so this should hopefully be right as-is. If you've got a different CPU, the IOCPUNumber in Kexts/TSCAdjustReset.kext/Contents/Info.plist is meant to be changed to <num threads> - 1. To be honest I'm not actually sure what this does, because I just realised that I had it set wrong all this time. I had it set to 15 (ie appropriate for 16 threads) instead of 35 (for 36 threads). I just fixed it and re-benchmarked, and re-tested my booting-from-BIOS issues, and it doesn't appear to have changed a thing. Though I do remember seeing TSC errors in boot logs a while back, so maybe those are gone now; I've not yet checked.
Anyway, hopefully this EFI will help. In which case maybe do a diff on the config.plist and see what I had different to you - would be useful to know what settings can cause issues, to help us avoid them in future.