Sleep works too?This has been one of the easiest hackintoshes I've put together. It took longer to assemble than to get the OS up and running. I went with a Z790 Proart as I got the board for $409.
My [summerized] 9 steps to boot.
- Switch my Win10 nvme from the Vision D to the new build to update bios to 0816 and the Intel ME to v16.1.25.2020.
- Loaded optimized defaults and went through the settings checklist.
- Replaced the EFI on my Z490 Vision D build with the one provided by @CaseySJ for the Proart build on page 1.
- Setup the Platforminfo with OCC.
- Changed Misc --> Boot --> LauncherOption to Full (to get OpenCore boot option at bios)
- Went to hackinDROM to create ssdt for TitanRidge addin card. Changed bus to 1, added UID from IOReg, and changed PCI0.RP21 to PC00.RP09.
- Added that to the EFI
- Put the drive in the new build.
- Boot new build. It just works. I haven't checked all the little stuff but this build is running and usable.
Thank you @CaseySJ once again for your time, expertise, and help with previous builds.
Also a thanks to @Inqnuam for hackinDROM.
When did the problem begin? In other words, was the system booting normally every time until suddenly it started requiring Reset NVRAM?BIOS Version 816 [latest]
Fresh clean install. 13.1
OC 0.8.9.
Thank you!!
I have written to Gigabyte support many times. This made me the only one who wrote BIOSes for Z690 Gaming X DDR4 and Z690 UD DDR5 with Titan Ridge support.Thank you etorix
...
I noticed it. Ori69 managed to get the latest BIOS for his Gaming X to have the support added back…
Just tried sleep. It didn’t sleep, but when I tried it didn’t crash and reboot.Sleep works too?
If you want 10 GbE, you need a supported 10 GbE NIC, but not necessarily the AQC 107s/113 which Apple uses in real Macs. DriverKit now includes Intel'sWhat do you mean?
ixgbe
driver, which supports the X500 series of NICs (but unfortunately not the latest X700 and X800 series: these are on ixl
and ice
drivers.) There are drivers for Chelsio and Solarflare cards.This sounds like a BIOS issue. Although the post below is from a Gigabyte board, it might be worth reading:After the full install, not during the install.