Contribute
Register

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

Some issues on my Hackintosh:
  1. I have a M2 Samsung 970 Evo 1 TB, with new version Monterey 12.0.1 is affected by the boot soooo slow (I have only MacOS partition, only Mac, no Windows), the entire disk is in APFS (this issue I don't have it with my second hackintosh because I have installed a M2 of Crucial 500 GB).
  2. I have update the BIOS to from F20d to F21a (for support Windows 11, no need it but I did); not a issue this or maybe...
  3. After 4 reboots to update Monterey, the sound don't works, so I remembered that I must to get a "#" before "device-id" in the DeviceProperties (pic), and now working fine (for my second hackintosh too) - (then this issue is resolved ;))
In this moment that's all. Please help me to resolve the issue with M2.
Thank you.
 

Attachments

  • Mac di Gianni  2021-10-26 alle 15.22.03.png
    Mac di Gianni 2021-10-26 alle 15.22.03.png
    194 KB · Views: 28
Looks like a lot of people are reporting slow boot times with Samsung 970 Evo / Evo Plus. Also with WD SN 550.

I have had no problems in Monterey with:
  • Silicon Power
  • ADATA SX series
  • Sabrent Rocket
  • Crucial
 
Well, I really, really do wish that people would stop repeating that you must use the legacy approach with CCC. I have been using CCC for well over 10 years. I know how to use it, and how to use the "legacy" approach. I'm just saying its not reliable, and is not going to be around much longer.

A quote from Mike Bombich of CCC: "....APFS replication utility completed the task, but then failed to remount the destination. CCC tried to remount the destination as well, but also failed. The backup is whole, but CCC was unable to wrap up the final details of renaming the destination back to "imacProBkUp", and restoring a custom icon, if applicable. This is why CCC recommended that you erase the destination and try again."

Which I did, and it failed again, on a different disk. So clearly, it failed.

Furthermore, Mike pushes hard to not use the legacy approach "I agree! Please, stop doing it this way! Don't make bootable backups, make Standard Backups instead (i.e. the "default settings")".

And my final point is: soon, you will have no choice, you will not be able to use CCC to make bootable clones. I believe in preparation, and so I have taken steps to protect myself and my data.

What you, or Casey chooses to do, that's your choice. All the best.
I think I can act as devil's advocate saying that Mike has in mind real Mac users. We, hackintosh users, are more prone to render the system useless because are constantly tweaking and experimenting on hardware that is not officially supported. Should an issue occur on a real Mac user, system reinstall is in many cases the standard procedure anyway. Is that right?
 
Hi Juan, my issue with Ethernet is this: no network! the driver is installed but don't works correctly! see the pictures.
Thanks
I read is some forum that "HP NC360T Intel PRO/1000 PT LP Gigabit Dual Port = Intel 82571EB" is natively supported.
That could be a possible workaround for z490 vision g users.
 
Last edited:
I think I can act as devil's advocate saying that Mike has in mind real Mac users. We, hackintosh users, are more prone to render the system useless because are constantly tweaking and experimenting on hardware that is not officially supported. Should an issue occur on a real Mac user, system reinstall is in many cases the standard procedure anyway. Is that right?

This was all done on a "real" mac, not a hack.

But you are right that hacks need that bootable backup, at least that's my opinion. However, for now, for hacks, the good news is that they are typically Intel based (maybe AMD too) and are in a case that you can open.

So, on my two hacks (which are Intel based and are beta machines only) I can boot my Clonezilla USB and clone on my hacks (and I think you could do this with an Acronis USB as well). Once booted to Clonezilla, I can clone to another USB attached drive or I can clone to an internal drive that I can install. So, that works.

For now...

And Mike is a truly good guy, at least in his interactions wth me. We had another dialogue this morning. He clearly would prefer Apple would not have made the changes they have made, but he's doing his best to make this all work.
 
Last edited:
Some issues on my Hackintosh:
  1. I have a M2 Samsung 970 Evo 1 TB, with new version Monterey 12.0.1 is affected by the boot soooo slow (I have only MacOS partition, only Mac, no Windows), the entire disk is in APFS (this issue I don't have it with my second hackintosh because I have installed a M2 of Crucial 500 GB).
  2. I have update the BIOS to from F20d to F21a (for support Windows 11, no need it but I did); not a issue this or maybe...
  3. After 4 reboots to update Monterey, the sound don't works, so I remembered that I must to get a "#" before "device-id" in the DeviceProperties (pic), and now working fine (for my second hackintosh too) - (then this issue is resolved ;))
In this moment that's all. Please help me to resolve the issue with M2.
Thank you.
For issue 1, try setting SetApfsTrimTimeout to 999 and reboot.

Screen Shot 2021-10-26 at 6.53.40 AM.png

Also, if you're using Intel WiFi/BT, it's necessary to use new BlueToolFixup kext and disable IntelBluetoothInjector.
 
Last edited:
For issue 1, try setting SetApfsTrimTimeout to 999 and reboot.

View attachment 532078
Also, if you're using Intel WiFi/BT, it's necessary to use new BlueToolFixup kext and disable IntelBluetoothInjector.
Thank you @CaseySJ I try your tip, but don't works :| I have see the previous post about this issue... and now I try... I don't have any issue with Wi-Fi/BT, all works fine.
Thank you
 
I think I can act as devil's advocate saying that Mike has in mind real Mac users. We, hackintosh users, are more prone to render the system useless because are constantly tweaking and experimenting on hardware that is not officially supported. Should an issue occur on a real Mac user, system reinstall is in many cases the standard procedure anyway. Is that right?
It’s not wrong, but in my circle of professionals, we all keep bootable clones of our system installs because of the time it takes to install our individual software packages and libraries, and as @mm2margaret pointed out, our deadlines can be tight enough that a day of downtime to reinstall can sink a project. So, without bootable backup, we’re forced into having backup machines.
 
Yeah, I have a feeling this is the culprit, will confirm later


What ports are you experiencing the ejecting on if I may ask?

OK, so I just installed 11.6.1, and my computer is no longer giving me the disk ejection warning on wake-from-sleep,
but in 11.6 and 11.6.1, my streamdeck does not wake to it's original state either, and wake-from sleep is significantly longer than in 11.5. Since I now have appleVTD disabled, I'm inclined to assume this is a fundamental OS USB behaviour change from 11.6+
 
Looks like a lot of people are reporting slow boot times with Samsung 970 Evo / Evo Plus. Also with WD SN 550.

Are we talking hacks in general or the Vision D and slow boot times. I have 2 970 Evo Plus drives, only one is being used with mac os but it is on my Z390 Designaire build on 10.15.7. I have not had any problems that I am aware of using the 970 though I have read and can see there could be several.

On a side note, on this Vision D build I'm using a Samsung 860Pro SSD and boot time is ~20 secs (starting after the opencore chooser), so I can see a boot on NVMe over 30 seconds doesn't sound right...

I'm considering buying a NVMe for the Vision D. Is there a favorable controller we should be looking for?
 
Back
Top