Hello
@maeluse,
It is wonderful to see that you handled every challenge with such competence! You searched for answers, you performed experiments (even repetitively), and you persevered throughout the long process. Your post is a shining example of what I mean when I say that, as Hackintosh owners, we must learn to be our own first line of defense. There is no tech support with Hackintosh, no Genius Bar, no satisfaction guarantee, no promise of compatibility with the components we use, no promise that future software updates will work, and the list goes on. The way you handled
adversity is exemplary.
Some comments:
- I will modify Post #1 with a reference to your post. It can indeed be very helpful to others.
- Issue 1: Intel Octane Driver and setting SATA ports to AHCI in BIOS.
- Good lessons here for everyone.
- Issue 2: Sleep.
- If the computer comes out of sleep quickly, first try
sudo pmset -a proximitywake 0
.
- If this does not work, please try disconnecting any devices that are plugged into the two USB 2.0 headers on the motherboard.
- If that also does not help, let us know. There is a Sleep Aid guide here.
- Issue 3: UAD devices did not appear until 10 install/re-install cycles.
- Please check if you have this enabled:
- BIOS --> Thunderbolt Boot Support --> Boot Once.
- Issue 4: Sizzling sound
- Good lessons here as well.
- Issue 5:"An error occurred validating the installer data"
Hi
@CaseySJ and everyone,
First, very sorry for the late reply and thanks a lot for your encouraging words and (last but not least) for referring my post in the FAQ section!
Knowing the perfect quality of your tutorial, I feel like honoured to be somehow part of it! I hope this could at least help a few people.
Yes, to be honest I actually have a quite superficial picture of the general functioning of OpenCore, together with the drivers/ktexts/patchs and how they articulate around the boot process, and I am really sorry for that. I wish I could know much more about it, but unfortunately my desperately busy schedule does not give me enough time to go as deep as I would like into this obscure (for me) universe. And, as long as everything works fine, I don't see any reason for me to do it...
Anyway, in the "real life" I am a software engineer. So, as a professional quirk I am kinda stubborn, and when I face a problem I like to get to know it and investigate until everything looks clear, how little my knowledge about the topic can be.
I solved the
Issue 2! thanks for your help on this too! the "Sleep Aid" really made things easier! It is not clear though which specific option really cleared out the issue, as I sometimes tried several options at the same time. I will anyway detail each step. Hopefully it can also help people having the same configuration and facing the same issues.
First, I must maybe shortly describe the symptoms: my computer used to regularly enter into a
dark wake state. It happened every 1-2 hours. The behaviour was usually always the following: it spontaneously woke up, then stayed awake about 30 seconds (in average), and finally fell back into a deep sleep. As it was logged by the system as a "dark waking up", I started to proceed that way:
- I disabled PowerNap (no effect: but it's important to note here that it was a part of the final solution)
- I re-enabled PowerNap
- I unplugged every USB devices (not only the ones plugged on the USB Header through the computer case) and my Thunderbolt cable. Basically then, only my HDMI monitor cable was plugged in the motherboard. (no effect)
- As I am using a Bluetooth Magic Keyboard and Magic Trackpad AND as I read somewhere that it might be caused by a Bluetooth intermittent signal, I then unchecked the following option in [System Preferences -> Bluetooth -> Advanced] (sorry for the French) (no effect):
- I gave a try to your suggested command:
sudo pmset -a proximitywake 0
(no effect)
Before I continue with the last steps, it may be useful to share you the
wake reason that I could identify in the log (dumped with the following command:
pmset -g log
):
0 kernel: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: RTC PEG1 PEG2 RP04 (Alarm)
Always the same message appeared, showing
PEG1 and
PEG2. I guess that
PEG1 and
PEG2 ids refer to the PCI Express Graphic card. In addition to that, I read in the "Sleep Aid" that
AMD RX 5700 series GPUs may trouble the sleep. I own a
RX 5700XT, so there were already two hints that the cause could be my graphic card. On the other hand, I did not want to isolate this issue. I could indeed unplug the card and activate the intel graphics chip... however as I was satisfied with how I arranged the hardware components and cables inside my case, I did not want to touch it anymore... and yes, I am kind of lazy
... anyway I went on with the next steps:
- I tried then the following command:
sudo pmset -a tcpkeepalive 0
(no effect)
- I re-disabled PowerNap (in the Power Settings)... and tadaaa --> it worked!!! <--
For your information, here is how my
Power Settings window
now looks like (sorry again for the French):
So, as I said, it is not clear which precise setting made it... maybe the combination of all of them is necessary. As for me, as I don't need the
proximitywake feature and
tcpkeepalive either (the latter is only needed for
Find My Mac localisation service, which I will never use), I will leave the options like they are now. That's totally fine!
I can confirm now, after several days of testing with these settings, that my computer can
endlessly remain in the deep sleep state, and this with
all my USB and
Thunderbolt plugged in and bluetooth magic things turned on.
Now I can finally say that my Hackintosh is perfectly healthy and fully functional (if I omit some rare boot issues... but they are so rare that I don't even care
)
Just a little remark about Issue 3:
The boot option:
BIOS --> Thunderbolt Boot Support --> Boot Once was already enabled. Moreover, as I said, at the point when I installed the UAD Drivers, my Thunderbolt Apollo sound card was
not plugged in yet. I experienced these issues when I tried to make the UAD driver detect my
UAD-2 Solo PCI-E card... So, if you are unlucky like me, you might face the same issues, even though your BIOS is correctly configured. However, I would vote for a UAD installer bug maybe in association with a specific version of MacOS. IMO, it is likely to be fixed in a next update of the UAD software.
This completes my experience with this build. Thanks again
@CaseySJ for bringing this awesome build to my home studio experience. I am already enjoying it beyond my expectations!
Cheers!