Contribute
Register

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

A Hackintosh might actually wear a Samsung NVME out, at least. Apparently the TRIM support for that doesn't work as expected despite being listed as Yes.

I and several others have noticed they run hotter than they should on macOS, and this OC build guide describes why.

If macOS is not handling TRIM or the controller properly, and it runs hotter, it might wear it out faster.

I switched to a Sabrent Rocket 4.0 for these reasons. I figure even though I've ruled out the 970 Evo Plus as the faulty device on my machine, might as well trade for the Sabrent Rocket 4.0 now before the 980 comes out (which will also have a controller macOS probably doesn't like) and lowers the value of the 970. It runs a lot cooler and if/when I do a PCI 4 build (looking forward to Z590 Vision D build with Rocket Lake that actually supports PCI 4) it will get a speed boost the 970 wouldn't.
Good to know. I will link this to Post 1. I have never purchased a Samsung NVMe SSD only due to their significantly higher cost. But now we also have a functional reason to avoid those drives (i.e. macOS issues with Phoenix controller).
 
This is what I need to hear.
I think I shall start getting things on order and get cracking into this Hackintosh game.
I assume you have used OC 0.5.9 or 0.6.0?
You may get the odd query at some point

Thanks again for your response

Rob


@SpinRD,
We are all OC 0.6.0
 
So I just home and tried the following. When all the USB headers are plugged in and I put the system to sleep, monitor goes to sleep and after a few seconds the computer completely turns off. Tried removing the Kraken, removed the Fenvi, and got the same results.

I also installed Windows and when I set it to sleep the same thing is happening. Set it to sleep and it completely turns off.
When configuring BIOS parameters, did you start with Save & Exit --> Load Optimized Defaults?
 
10.15.16? Did you mean 10.15.6? I only ask because I ordered my 10900K last night along with my Vision D and plan on building it next week and the week after. I use Pro Tools as well and the Avid website says that Pro Tools 2020.5 is only compatible up to 10.15.5. I have the files for both versions of macOS ready and would love to clarify which if you've been fine running the latest version of macOS with Pro Tools

In case it matters the specs will be:
10900k
Z490 Vision D
32GB 3466MHz Corsair Dominator Platinum RGB
Gigabyte Gaming OC 5700XT
Kraken X73 AIO
1TB Intel 660p boot drive
500GB Samsung 850 EVO for PT session files (In current system)
3TB Seagate Barracuda for mas storage (In current system)
I'm also carrying over the fenvi and the PSU from my current hackintosh
Entho Evolve X case

I currently use and 2nd gen Focusrite 18i8 but I'm looking at the new Quantum 2626 with thunderbolt 3 once this system is up and running


@GMoney022 I stand corrected.
It is 10.15.6. (I have edited the response to reflect the correct OS version. Thank you.)

We have not implemented the latest macOS Catalina 10.15.6 Supplemental Update.

We are running PT 2020.5.

My apologies for the typo.

Tony
 
Good to know. I will link this to Post 1. I have never purchased a Samsung NVMe SSD only due to their significantly higher cost. But now we also have a functional reason to avoid those drives (i.e. macOS issues with Phoenix controller).

Interesting. I have a Samsung 970 Evo Plus that came with the 2B2Q firmware. So none of that crashing that occurred with the original firmware.

Temps seem fine on Mac. I’ve checked temps using HwSensors (using the associated Lilu Plugins) and my drive is usually between 48c to 51c. I don’t know if that is high or not, but temps are roughly in the same range in windows as well.

Any comment on what ‘normal temps’ for NVME SSDs should be?

Trim was enabled by default in Mac.
 
Interesting. I have a Samsung 970 Evo Plus that came with the 2B2Q firmware. So none of that crashing that occurred with the original firmware.

Temps seem fine on Mac. I’ve checked temps using HwSensors (using the associated Lilu Plugins) and my drive is usually between 48c to 51c. I don’t know if that is high or not, but temps are roughly in the same range in windows as well.

Any comment on what ‘normal temps’ for NVME SSDs should be?

Trim was enabled by default in Mac.
48-51C is still okay. My Sabrent Rocket has the best thermal performance, usually operating between 28C and 35C as shown below. My Silicon Power is currently around 46C even though Catalina is booted off the Sabrent Rocket and the Silicon Power is mostly idling.

I should mention that the Sabrent Rocket's M2P slot is currently operating at x2 because there's a PCIe card in the bottom long slot that splits the bandwidth.
Screen Shot 2020-08-23 at 5.09.36 AM.png
 
48-51C is still okay. My Sabrent Rocket has the best thermal performance, usually operating between 28C and 35C as shown below. My Silicon Power is currently around 46C even though Catalina is booted off the Sabrent Rocket and the Silicon Power is mostly idling.

I should mention that the Sabrent Rocket's M2P slot is currently operating at x2 because there's a PCIe card in the bottom long slot that splits the bandwidth.
View attachment 485409
Very Interesting. I’m gonna turn on NVMEFix.kext later and see what, if anything changes. I’m eyeing that Sabrent Rocket .
 
System boots from the selection of Catalina to the login prompt in about 12 seconds. I haven’t found anything that doesn’t work yet.

hello lcoff!
i have nearly exact the same setup as you (same RAM, GPU, Wifi+BT, only difference: my CPU is i9 10900K and I use Evo 970 SSD) and i wonder why you are able to boot so quick!
My board takes 25 seconds from opencore to login-screen and its stuck for about 3 seconds on something about USB "missing required descriptor" or "power supply unavailable: assuming successful power". the rest of the 25 seconds are just running text, not stopping or waiting anywhere...

I am really interested in your BIOS-Settings if you have anything special and I want to ask which method you use for USB (because that seems to slow down my boot a bit).
Do you use the latest BIOS? have you flashed the thunderbolt-chip or is it original?
How long does your board take from power on to BIOS / Opencore?
Would it be possible to get your BIOS-profile and your EFI so I could test if my boot-speed changes with exactly your setup?

Hey @CaseySJ, with your flashed NVM 50 on the Vision D, does your boot time increase? I noticed that on my Vision D, with the Flashed Thunderbolt NVM, the system post time increases by about 20 seconds or so. Seems that the motherboard is trying to communicate with the thunderbolt controller during post... On stock NVM, boot time is shortened significantly.

I experienced the same problem, but because flashing TB was the first thing I did, I don't know if it would have booted faster without flashing the chip. I got the board, made blind BIOS-Update to F5 over QFlash+ and than flashed the chip. My board then needed about 30 seconds from power on to BIOS. The display on the Board showed "80" for about 17 seconds of that time, and the VGA-LED was lighing most of that 30 seconds. As a side-note, I noticed that one of the network-adapters had MAC 00:00:00:00:00:00. I tried everything, resetting, CMOS-Reset, installing the firmware-Update again, remove all hardware...even with just CPU and RAM and with complete reset BIOS it still took 30 seconds to BIOS. I then decided to return the board.
Then I was more careful with the new one: I first made sure that it booted quicker with original TB-Firmware. Instead of 30 seconds, it now took about 8 seconds to BIOS, with the same BIOS-Version and -settings and the same hardware installed than I had on my old board. Then I flashed the TB-Chip, so now the config was exactly like on my old board, and it still needed only 8 seconds to BIOS.

I guess 8 seconds is still not really fast, but its better than waiting 30 seconds...and now the hex-codes on the board's display just run through, its not pausing anymore at "80", not even for a second.

I also noticed that a Diff between the TB-Firmware-BIN of my first (broken) board and the modified Firmware-BIN from here showed a lot more differences than a Diff between the original TB-FW of my second board and the modified Firmware-BIN from here. So overall, returning the first board was the right choice I guess.

Because you also seem to have slow boots: do you have a valid MAC on both of your network cards? is your board pausing at a specific code while it boots? how many differences do you see in your thunderbolt-firmware compared to the modified one? I attached my TB-Bins from my first and my second board for you, if you want to compare.

I don't know if this helps to get more knowledge about the slow boots, but it looks like there is the possibility that thunderbolt-flashing (or something else, maybe not directly related to TB) has an impact on POST/boot times.
 

Attachments

  • TB_FW.zip
    552.2 KB · Views: 77
just upgraded to z490 Vision-D (bios F5) + i9-10900k and installed latest Catalina and then Big Sur, so all looks great, but no luck with thunderbolt 3 and Apollo UAD2 "no device found!" I use Apple TB3 to TB2 adapter it works years with others boards, on Windows 10 is same situation just "no device found!"
Very strange because connection to Monitor using usb3.1(TB3) to DP cable work great. What can I do now, any advice please. Maybe the board has some issue and I should to replace it?
 
Back
Top