Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

I guess I'll try doing a fresh install this weekend on a spare drive and see if sleep starts to work then. BTW, does it matter what fan profile I set in the BIOS? Or does the MacOS always do its own thing after booting?
I wave the white flag of surrender. :banghead: I removed all my drives and did a fresh install on a 7200rpm hard drive. I used an unadulterated Opencore 0.6.1 EFI and it still can't sleep properly. So I wiped it and installed Windows 10. Guess what... it can't sleep properly either. It just shuts down like on MacOS. So, it is NOT an Opencore/EFI/Hackintosh issue. It has to be some combination of HW and motherboard configuration, possibly my power supply doesn't allow sleep somehow. I don't get it, since I'm using the same peripherals that everyone else is.

I don't regret moving over to a hackintosh because everything else is so much better than my previous mac. I'll miss the sleep ability. But since I don't get much sleep in real life, why should my computer be any different. :lol:

Thanks for all the advice. I really do appreciate what you guys have done to help a community like this. @CaseySJ I hope this is your full-time job, because you have definitely spent a lot of time making this great for people. I also hope you are well compensated for it. :thumbup:

Thanks again,
Ed
 
Good morning!
I just changed my MoBo because I had an hardware problem in my previous Asus ROG Maximus Hero XII Z490 wifi so I got in change a Gigabyte Z490 Vision D wifi. First of all... Thanks very much @CaseySJ for your work.
So Z490 Vision D + I7 10700K + Radeon 5700XT + 64 GB over 4 dimm G-skill Ripjaw @3200 + samsun nvme 970 pro 1GB. installed on M2P_SB connector for two reasons:
A) I don't use the PCIEX4 slot so I don't need to share bandwith or disable one or two SATA ports
B) M2M_SB and M2A_CPU connectors are placed just beside the PCIEX16 slot so just Under the video card so using one of this slot it is necessary to remove the video card to access the NVME HD; using M2P_SB this is not necessary.


First installation using only two dimm and 32GB of ram.
Upgraded the firmware from F3 original version to F5 then all flowed smooth, quick and easy without any problem.
After the installation of second couple dimm the system doesn't start. Simply boot stop at different error codes.
removed the last dimm put in the MB all goes again fine. so I downgraded the firmware to F4 put in again 3rd and 4th dimm then all worked fine.
Upgraded again firmware to F5 and now all works fine.
At first installation using CaseySJ OC61 EFI boh ETH worked fine but the 1Gb lan was working and displayed on the network panel of system preferences. The 2,5 Gb one was working but wasn't displayed in the network panel of system preferences.
After installing the wireless vision EFI from CaseySJ both lan port start to works fine and are displayed on the network panel.
SMBIOS as Imac 20.1

Bluetooth Seem active, in system report is correctly recognised but
A) I cannot pair any device. I tried to pair two Logitech mouse but the behaviour was the same: I can discover the mouse in the bluetooth panel, mouse in discover mode, so I can connect. after a few seconds the mouse disconnect from bluetooth then in the Bluetooth panel appear a second identical mouse at this point no connection
Airdrp doesn't works but in the system report I can read this about bluetooth ;
Services:
Bluetooth File Transfer:
Folder other devices can browse: ~/Public
When receiving items: Accept all without warning
State: Disabled

Bluetooth File Exchange:
Folder for accepted items: ~/Downloads
When other items are accepted: Save to location
When receiving items: Accept all without warning
State: Disabled

LAN speed
:
Wi-fi download speed 54MB/s upload speed 27MB/s (antenna 3 ft away from the router nothing between antenna and router connection made using 5G wireless network
2,5 Gb and 1Gb lan port average download speed 903Mb/s; average upload speed 103 MB/s

A little note about mainboard layout: usually PCIEX1 slot is placed between CPU andPCIEX16 slot. In this MB PCIEX16 is the first slot so installing a video card and a good CPU fan result in thermal problems. For example I use a noctua NHD15-S CPU fan and the distance between the radiator of the fan and video card is about half a centimetre so the heat from video card raise through the cpu fan.
 
Hi @CaseySJ,

I wrote a while ago in this thread that your excellent tutorial made me feel like building up a new Hackintosh configuration. A few weeks ago, I decided to take the step and here I am now writing you from my brand new (and awesome) Hackintosh. :thumbup:

The procedure did not go as smoothly as I hoped though. Therefore I wanted to give you a "little" feedback of what I've experienced so far. The tutorial that you have written and the close support you keep on providing to the members of this thread deserve it, I guess. Moreover if this could help other people to go through the same issues, I would be glad to help. Please note that regarding hardware components installation, BIOS update, OpenCore preparation (then the update to 0.6.1 version with last beta Intel AX201 driver) and boot up, I had absolutely no issue :thumbup: I indeed decided to give a chance to the WIFI/Bluetooth onboard Intel chip even though I already own a Fenvi-like card (from my previous Hackintosh configuration), so that I can save a PCI-E slot.

(I apologise in advance for my English... I am French but I will try to do my best)

This decision was taken after a while, because at the same time (in August) a new iMac was released and somehow troubled the game. The first and unofficial private benchmark about this iMac was talking about awesome and unexpectedly high CPU scores, making the tester think that the iMac had been especially optimised around the new 10th generation Intel CPUs in comparison with the competition. As you may know, next benchmarks showed then that it was actually NOT the case, that this machine was just a nice upgrade, with good but expected performance and no special game-changing hardware evolutions. This eventually killed the idea to possibly switch to iMac... So, I sticked to Hackintosh and your build. This was for me the best decision I could take.

Speaking about my experience now...

During the installation:

1. Mac installer could not detect my hard drive because of evil Intel Octane


Yes, I wanted to set up a Mac/Windows multi boot. Just to kill the suspense: it works perfectly fine now! ... but back in time I stumbled upon one obscure issue, which was surely the most time-consuming one along the entire Mac setup and installation procedure.

As you recommended, I installed Windows first from the USB Stick previously prepared with the official Microsoft's installation media creator. Everything went fine.

The next step was the installation of the drivers provided on Gigabyte motherboard support web page in order to clear out some "device unknown" messages I could see in the Window device manager... the usual stuff... Every driver installation ran fine and did its job, excepted one: The Intel Rapid Storage ****. Ok, I never asked myself the question whether a driver would be necessary for my basic (possibly gaming) usage of Window, and brainless installed everything... but I should have done it for this one... why? because during the driver installation, there was an especially important yes/no question about if I wanted to install the Intel Octane driver. There was a warning message which popped up along with the yes decision but I don't remember if the following was mentioned into it: This octane son-of-a-bitch actually change the SATA handling BIOS parameter from "AHCI" to "Intel Octane something" o_O This was an irreparable change (no possibility to go backward: uninstalling the driver does not help). Of course, at this moment I did not know yet that the BIOS was modified. The point is that I realised the aftermath of this change much much later on... after I spent half a day installing programs and fine tuning my Windows, so bad...

Then has started the long awaited moment of installing my Mac partition. Unfortunately I ran rapidly into troubles with the installer. At the step when I needed to create my os partition with the Mac disk utility tool, I could see that NONE of my internal disks were visible. For a short moment, I thought that it was due to my Corsair MP600 M.2 SSD drive which might be unsupported (because too recent or so), but none of the drives were actually visible. Of course, a few hours research session on Google was totally helpless. So, as a kinda desperate move, I decided to double check my BIOS settings and compared them with the ones from your thread... and I saw this Intel Octane thing. I of course immediately knew that it caused the issue! I switched back then to "AHCI" and great! ... the installer could finally see all my internal hard drives and start the installation procedure! :headbang:

Unfortunately (yes the story does not end here), the "AHCI" setting destroyed then my window partition, and booting up on it just ended up with a blue screen of death. I could not find any other way to repair it that reinstalling my Windows from scratch :cry: ... but this time, answering NO to the deadly "Do you want to install Intel Octane driver?" question while installing the Intel Rapid Storage driver. Please don't do the YES mistake like I did.

2. Mac installer issued the "An error occurred validating the installer data"

You wrote a dedicated spoiler for this problem in your post with the findings of @counterfactual, but it did not cover my build configuration, as I do not have four memory DIMMs installed. I then thought that is was a lack of luck, but the problem unfortunately respawned again and again after several installation attempts. Later on, I fortunately managed to find one thread somewhere on the web, which put forward an interesting explanation: it might be due to the USB Stick, which for some reasons, is not fully compliant with the installer. FYI, my USB Stick is a Sandisk Ultra Flair USB 3.0 128 GB. So, without any conviction, I gave a chance to my old external SSD USB drive and copied all the contents (including the EFI Partition) from my USB Stick to this drive, and restarted the installation procedure with it. Miracle! it solved the issue! The installation ran through properly till the Catalina login screen :D

After the installation (on Mac side):

1. Quite rare but repeating Bluetooth devices misdetection (with onboard intel chip)


It can happen (I would roughly say every tenth time) that my Bluetooth magic keyboard and trackpad are not detected by MacOS, starting from the login screen. In such case, after having plugged my keyboard to the USB port, entered the password, and unplugged it... I might wait for long minutes (probably 10, 15, or more) until the bluetooth functionality mysteriously activates itself and finally detects my devices. No special user activity seems to trigger this; you just have to wait. I have found no better solution than restarting the computer. Usually (in the great majority of cases) it solves the issue. It looks like this bug has been reported to OpenIntelWireless GitHub here: https://github.com/OpenIntelWireless/IntelBluetoothFirmware/issues/167, but as far as I can see, no fix has been provided yet. As for me, the issue appears much less frequently than in the description. No issue has been noticed after waking from sleep state as well.

At the beginning I followed the instructions of @counterfactual to active onboard Bluetooth. Since yesterday I have been using the EFI (with no further edits) from @CaseySJ bringing the last driver updates and WIFI support (yeah!) but could still reproduce the Bluetooth issue. WIFI is working well so far.

2. The computer cannot hold the sleep state

I have noticed that my computer cannot hold the sleep state after having entered into it. As recommended, I disabled the "Wake for network access" option in the Energy Saver window... but it unfortunately does not prevent the issue. Thinking that it might be due to PowerNap, I disabled it. But then, the effect is even worse: instantly after reaching the sleep state, the computer wakes up. As a brutal workaround, I could simply deactivate the energy saving, but on the other hand, I feel like I am very close to make it work (when PowerNap is enabled). The computer can stay in sleep state for a few minutes, but then something special wakes it up and I've never managed to know why.

May it be related to a special BIOS setting, or OpenCore setting? I precise that I use the BIOS and OpenCore settings provided in the post (yesterday updated with OpenCore 0.6.1 and Intel AX201 drivers).

3. Troubles installing Universal Audio Software due to MacOS security rules

The main reason why I opted for a thunderbolt 3 build setup is that I wanted to play around with the Universal Audio Apollo twin X sound card. HOWEVER, at the moment when I installed the Universal Audio software & drivers, my Apollo was not yet plugged in! The reason is that I actually already own a little Universal Audio UAD-2 one core PCI-E expansion card, which at this moment WAS plugged in. This helps to clear out any potential troubles related to thunderbolt 3 handling. I ran with the latest possible MacOS version and my UAD software was also up-to-date (it is still now the latest version available on their web site).

After the software (including Apollo drivers) installation, I stubbled upon the "Driver Not Installed Correctly" issue (already experienced by some users in this thread):
1601212334154.png


This problem is reported on the web site of Universal Audio here: https://help.uaudio.com/hc/en-us/articles/360033607311-macOS-10-15-Catalina-Compatibility-Info

But, even after having carefully followed the steps, I was not able to succeed the part "3: Allow UAD Software" because this window actually never popped up:
1601212658445.png


and the following message never appeared in my System Preferences -> Security & Privacy -> General tab in contrary to what is shown on Universal Audio web page:
1601212921179.png


I restarted the computer as they recommended, but still no change was noticed. Then, again as they recommended I uninstalled the software and reinstalled it, and again still no change... I repeated the procedure multiple times, even manually removed the UAD files hidden in Library/Preferences as they show it there: https://help.uaudio.com/hc/en-us/articles/360015775711--Mac-Apollo-X-Uninstall-Reinstall-Procedure

... no effect.

In a robotic way, I kept on repeating the same installation/uninstallation procedure again and again, desperately hoping that it would end up working... I finally managed to make it work! o_O honestly I have no idea why this ended up working after the tenth attempt (or so) and not before, because I exactly repeated the same steps again and again without changing anything, but well... it worked! I felt so happy and relieved to see the picture of my PCI-E card in the UAD Control Panel -> System Info tab up and running... So do not desperate guys, if by chance (or mischance) you stumbled upon the same troubles: obstinacy will set you free! ;)

Later on, my Apollo Twin X was immediately detected by the UAD software (together with the UAD-2 one core PCI-E), as soon as I plugged it in the thunderbolt 3 port. :thumbup:

4. Sizzling sound while recording my microphone plugged into the Apollo line input through the CoreAudio driver

The first time I wanted to try the recording capabilities of my Apollo Twin X with my studio microphone, I had a very bad feeling: There was indeed on Cubase (my Digital Audio Workstation) strange sizzling (kinda saturated) artefacts in the sound I recorded from my microphone onto my track in Cubase. My project and Console sample rate settings were both set at 96 kHz. I indeed had this bad feeling that it was probably due to the thunderbolt 3 port and that, contrary to what I could have read in this thread saying that the Apollo Twin X is fully compliant with the original stock version of the thunderbolt chip, a flashing of this chip would be eventually necessary...

But something reassured me: I found out that the sound coming out from the Apollo headphones output, processed in the meanwhile by a few plugins enabled in the UAD Console, was perfectly clear without any of these artefacts. Then, seized by a crisis of optimism (I still don't know if I was right), I thought that it could not be linked to the thunderbolt port, because the problem appeared ONLY when the sound was processed through Cubase, that's to say when it was processed through the UAD Core Audio driver... So, probably a pure software issue. Then I played around with the sample rate (on both Cubase and UAD Console) switching it to 44.1 kHz... and it worked! No more artefacts on Cubase! then I switched them both back to 96 kHz, it worked as well!! :headbang: ... there was probably a little bug hidden in the algorithmic complexity of this high-end product, I guess... :geek:

Up to now (I am touching wood), I do not experience the same issue anymore.

After the installation (on Windows side):

1. Still one "unknown device" visible in the device manager


With both MacOS and Windows installed, after having installed every possible driver on Windows (including the UAD Software), one device still remained unknown for Windows. After some research on the web, I have good reason to think that it might be due to OpenCore. As far as I understood it from the developers of OpenCore, this is a very minor bug which is somehow due to the fact that OpenCore renames one ACPI device identifier. As a result, Windows does not know this ID and is unable to find the correct driver for it. On my side, the unknown device has something to do with ACPI indeed. I could read it in the device details. No fix seems to be scheduled for it. It's not even sure if a fix would be possible, again as far as I understood. But, as this problem is really insignificant and does not affect Windows "stability" and performance, I don't care.

I am done! It was actually much longer than expected, wow. Anyway, I would be glad at least if it could help some potential lost souls with their hackintosh setup. ;)

Cheers!
 
@casey Thanks for the Wifi and BT EFI! Working fine here.
just for information, have you disabled a specific usb port like in this post or just added HS14 to the SSDT?
(I mean...are all the usb ports working with this EFI?)
The standard USB SSDT (SSDT-UIAC-VISION-D-V2.aml) did not include HS14 (Intel Bluetooth), hence the new SSDT-UIAC-VISION-D-V2-INTEL-BT.aml was added. The new SSDT simply adds HS14 without removing any pre-existing ports.
 
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"
    • Good lesson.
 
Last edited:
I wave the white flag of surrender. :banghead: I removed all my drives and did a fresh install on a 7200rpm hard drive. I used an unadulterated Opencore 0.6.1 EFI and it still can't sleep properly. So I wiped it and installed Windows 10. Guess what... it can't sleep properly either. It just shuts down like on MacOS. So, it is NOT an Opencore/EFI/Hackintosh issue. It has to be some combination of HW and motherboard configuration, possibly my power supply doesn't allow sleep somehow. I don't get it, since I'm using the same peripherals that everyone else is.

I don't regret moving over to a hackintosh because everything else is so much better than my previous mac. I'll miss the sleep ability. But since I don't get much sleep in real life, why should my computer be any different. :lol:

Thanks for all the advice. I really do appreciate what you guys have done to help a community like this. @CaseySJ I hope this is your full-time job, because you have definitely spent a lot of time making this great for people. I also hope you are well compensated for it. :thumbup:

Thanks again,
Ed
Hello @EdPayne,

If the system shuts down when attempting to sleep, it could be due to a hardware issue. Do you have a WiFi/BT PCIe card in the system? If so, remove it and try again.

Try to go through the Process of Elimination by removing as many PCIe cards, USB devices (including those connected to internal USB 2.0 header), etc. as possible. But keep the following installed:
  • AMD GPU
  • Wired keyboard
  • Wired mouse
 
...
Bluetooth Seem active, in system report is correctly recognised but
A) I cannot pair any device. I tried to pair two Logitech mouse but the behaviour was the same: I can discover the mouse in the bluetooth panel, mouse in discover mode, so I can connect. after a few seconds the mouse disconnect from bluetooth then in the Bluetooth panel appear a second identical mouse at this point no connection
Airdrp doesn't works but in the system report I can read this about bluetooth ;
Services:
Bluetooth File Transfer:
Folder other devices can browse: ~/Public
When receiving items: Accept all without warning
State: Disabled

Bluetooth File Exchange:
Folder for accepted items: ~/Downloads
When other items are accepted: Save to location
When receiving items: Accept all without warning
State: Disabled

LAN speed
:
Wi-fi download speed 54MB/s upload speed 27MB/s (antenna 3 ft away from the router nothing between antenna and router connection made using 5G wireless network
2,5 Gb and 1Gb lan port average download speed 903Mb/s; average upload speed 103 MB/s
...
Hello @Zottwalker,

Good job troubleshooting the installation issues (two DIMMs versus four; flashing BIOS; etc.)! Regarding Intel Bluetooth, you should be able to pair Bluetooth devices after Resetting the Bluetooth Module, as follows:
  • Press and hold SHIFT-OPTION and click the Bluetooth icon in menu bar.
  • If you're running Catalina, you will see a Debug menu item, and it will have a sub-menu item called Reset the Bluetooth module.
  • Select that and try removing and pairing your devices (don't forget to remove them first if they appear in the list of paired devices).
 
Hello @Zottwalker,

Good job troubleshooting the installation issues (two DIMMs versus four; flashing BIOS; etc.)! Regarding Intel Bluetooth, you should be able to pair Bluetooth devices after Resetting the Bluetooth Module, as follows:
  • Press and hold SHIFT-OPTION and click the Bluetooth icon in menu bar.
  • If you're running Catalina, you will see a Debug menu item, and it will have a sub-menu item called Reset the Bluetooth module.
  • Select that and try removing and pairing your devices (don't forget to remove them first if they appear in the list of paired devices).
Thanks @CaseySJ , I tried this at the beginning as basic operation but nothing changed; I can't connect any device using BT.
I tried also to enable bluetooth sharing in the system preference/sharing panel. now both BT file transfer and BT File exchanger services are enabled but airdrop stil doesn't works
I forgot... obviously "discovered by" is set to anyone
 
Hello @EdPayne,

If the system shuts down when attempting to sleep, it could be due to a hardware issue. Do you have a WiFi/BT PCIe card in the system? If so, remove it and try again.

Try to go through the Process of Elimination by removing as many PCIe cards, USB devices (including those connected to internal USB 2.0 header), etc. as possible. But keep the following installed:
  • AMD GPU
  • Wired keyboard
  • Wired mouse
Sadly, I have tried all of that. I'm an engineer and well versed in troubleshooting techniques. Though I'm not too familiar with how to play around with kexts, aml files, etc. To me HW is linear, SW is non-linear. :lol:

I tried a minimal system (no USB header connections, no Fenvi, no SSDs or drives except for the one I installed on). Just the RX580, SATA drive, wired mouse and wired keyboard as the only peripherals (and the base OC EFI). Both Windows and MacOS can't sleep properly. I wish I had multiple versions of hardware to try. But that would be cost prohibitive for me. It acts like the power supply, just can't handle low loads and shuts down completely. I'll see how the week goes with this new workflow. Thanks again for still thinking about my issues.

Ed
 
Back
Top