[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[oopsmybad]

Yes it seems HWMonitorSMC2 v2.4.9 is not functioning correctly in Catalina (AMD GPU Info is not correct). Here's what I see:

Your CPU stats also (correctly) show up in HWMonitorSMC2 -- and mine don't. (I'm missing Utilization under the CPU chevron, and don't have a chevron for "Intel(R) Core(TM) i9-9900K CPU" like I do in Mojave.)

I noticed that my CPU shows up differently in the About screen and System Information. Could that cause HWMonitorSMC2 to misidentify it?

 

[CaseySJ]

Sooooo 10.15.2 has finally been released, I hope we can get a cleaner way to install it on our builds than we have to do on 10.15.1.

Woohoo! That's because the new modular Mac Pro was released today. Fortunately we can laugh all the way to the bank where our balances are safe from the gravitational pull of this thing's price tag.

I'll attempt a fresh install with 10.15.2 soon.

 

[CaseySJ]

OK!!! I borrowed an 8GB stick of RAM from the office...I'm in the installer!!! Does this mean that I wont be able to use the 64GB RAM going forward as well, or just for setup? (This might be useful for some folks in the future... don't use 32GB RAM.)

Use of 32GB modules may require specifying them in the Memory section at the bottom of SMBIOS. If you search this thread for 128GB you'll find a handful of relevant posts.

But for now, let's just focus on getting the basic system fully operational -- and backed up. We can come back to 32GB modules afterwards.

 

[CaseySJ]

@CaseySJ I do not have the H510i Elite, just the H510i. That's why I have a 140mm Aer RGB 2 on the top and a 120mm on the back And no, I do not have any Aer 1 device.

Spoiler: liquidctl --debug -d 1 initialize

[DEBUG] liquidctl.cli: running liquidctl v1.3.1 (homebrew; jonasmalacofilho/liquidctl/liquidctl 1.3.1)

[DEBUG] liquidctl.driver.usb: searching GenericHidBus (api=hid, drivers=[CommonSmartDeviceDriver, CorsairHidPsuDriver, KrakenTwoDriver, SeasonicEDriver, SmartDeviceDriver, SmartDeviceV2Driver])

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc086

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc086

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xa66

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x170e

[DEBUG] liquidctl.driver.usb: instanced driver for NZXT Kraken X (X42, X52, X62 or X72)

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x2006

[DEBUG] liquidctl.driver.usb: instanced driver for NZXT Smart Device V2 (experimental)

[DEBUG] liquidctl.driver.usb: searching PyUsbBus (drivers=[AsetekDriver, CommonAsetekDriver, CorsairAsetekDriver, LegacyAsetekDriver])

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x170e

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xa66

[DEBUG] liquidctl.driver.usb: probing drivers for device 0xbda:0x411

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x2006

[DEBUG] liquidctl.driver.usb: probing drivers for device 0xbda:0x5411

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc086

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x5e3:0x608

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x5e3:0x608

[DEBUG] liquidctl.cli: device: NZXT Smart Device V2 (experimental)

[DEBUG] liquidctl.driver.nzxt_smart_device: write 60 02 01 e8 03 01 e8 03 (and 56 padding bytes)

[DEBUG] liquidctl.driver.nzxt_smart_device: write 60 03 (and 62 padding bytes)

[DEBUG] liquidctl.driver.nzxt_smart_device: write 10 01 (and 62 padding bytes)

[DEBUG] liquidctl.driver.nzxt_smart_device: write 20 03 (and 62 padding bytes)

[DEBUG] liquidctl.driver.nzxt_smart_device: received 11 01 20 00 47 00 08 51 56 53 34 37 34 20 06 20 01 01 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[DEBUG] liquidctl.driver.nzxt_smart_device: received 61 03 20 00 47 00 08 51 56 53 34 37 34 20 03 00 02 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[DEBUG] liquidctl.driver.nzxt_smart_device: received 21 03 20 00 47 00 08 51 56 53 34 37 34 20 02 04 04 00 00 00 00 0c 0b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

NZXT Smart Device V2 (experimental)

├── Firmware version 1.5.0

├── LED 1 accessory 1 HUE 2 LED Strip 300 mm

├── LED 1 accessory 2 HUE 2 LED Strip 300 mm

├── LED 2 accessory 1 AER RGB 2 140 mm

└── LED 2 accessory 2 AER RGB 2 120 mm

Spoiler: liquidctl --debug -d 1 status

[DEBUG] liquidctl.cli: running liquidctl v1.3.1 (homebrew; jonasmalacofilho/liquidctl/liquidctl 1.3.1)

[DEBUG] liquidctl.driver.usb: searching GenericHidBus (api=hid, drivers=[CommonSmartDeviceDriver, CorsairHidPsuDriver, KrakenTwoDriver, SeasonicEDriver, SmartDeviceDriver, SmartDeviceV2Driver])

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc086

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc086

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xa66

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x170e

[DEBUG] liquidctl.driver.usb: instanced driver for NZXT Kraken X (X42, X52, X62 or X72)

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x2006

[DEBUG] liquidctl.driver.usb: instanced driver for NZXT Smart Device V2 (experimental)

[DEBUG] liquidctl.driver.usb: searching PyUsbBus (drivers=[AsetekDriver, CommonAsetekDriver, CorsairAsetekDriver, LegacyAsetekDriver])

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc539

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x4d9:0x8009

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x170e

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xa66

[DEBUG] liquidctl.driver.usb: probing drivers for device 0xbda:0x411

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x1e71:0x2006

[DEBUG] liquidctl.driver.usb: probing drivers for device 0xbda:0x5411

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x46d:0xc086

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x5e3:0x608

[DEBUG] liquidctl.driver.usb: probing drivers for device 0x5e3:0x608

[DEBUG] liquidctl.cli: device: NZXT Smart Device V2 (experimental)

[DEBUG] liquidctl.driver.nzxt_smart_device: received 67 02 20 00 47 00 08 51 56 53 34 37 34 20 03 00 02 02 00 00 00 00 00 00 ff 03 9f 03 00 00 00 00 00 00 00 00 00 00 00 00 32 32 32 00 00 00 00 00 32 32 32 00 00 00 00 00 4e 00 00 00 00 00 00 00

[DEBUG] liquidctl.driver.nzxt_smart_device: received 67 04 20 00 47 00 08 51 56 53 34 37 34 20 03 00 02 02 00 00 00 00 00 00 a1 2f 62 2f 7d 2f 00 00 00 00 00 00 00 00 00 00 27 00 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

NZXT Smart Device V2 (experimental)

├── Fan 1 duty 39 %

├── Fan 1 speed 12193 rpm

├── Fan 2 duty 0 %

├── Fan 2 speed 12130 rpm

├── Fan 3 duty 55 %

├── Fan 3 speed 12157 rpm

└── Noise level 0 dB

• Which 3 fans do you have connected to the Smart Device V2?
  • Aer RGB 2 140mm
  • Aer RGB 2 120mm
  • What is the mystery third fan?
• If there is no third fan, it means that the Smart Device V2 is sending a slightly different byte stream than expected by the driver.
  • I can look into this later in the evening.
• Are the LED accessories correctly listed?

 

[JayShay]

Sooooo 10.15.2 has finally been released, I hope we can get a cleaner way to install it on our builds than we have to do on 10.15.1.

I tried to do an upgrade but failed. The mini guide for Catalina fresh install is really easy - like 1/4 of the work from the previous guide. I would recommend a fresh install

 

[JayShay]

Woohoo! That's because the new modular Mac Pro was released today. Fortunately we can laugh all the way to the bank where our balances are safe from the gravitational pull of this thing's price tag.

I'll attempt a fresh install with 10.15.2 soon.

I might be getting that Pro Display XDR but I'm waiting for the new Radeon Pro w5700 to be released in the wild (has USB-C Port). If it works getting that damn display!

 

[CaseySJ]

I might be getting that Pro Display XDR but I'm waiting for the new Radeon Pro w5700 to be released in the wild (has USB-C Port). If it works getting that damn display!

I have only one thing to say to that: With the $tand or without?

• It only takes Thunderbolt 3 input.
• Will it work with one DP-In from AMD GPU to motherboard?
• Or do I recall correctly that you have the Gigabyte GC-Alpine Ridge and hence you can connect two DP-inputs to obtain a bonafide 6K output stream?

 

[CaseySJ]

Your CPU stats also (correctly) show up in HWMonitorSMC2 -- and mine don't. (I'm missing Utilization under the CPU chevron, and don't have a chevron for "Intel(R) Core(TM) i9-9900K CPU" like I do in Mojave.)

I noticed that my CPU shows up differently in the About screen and System Information. Could that cause HWMonitorSMC2 to misidentify it?

It should use CPU-ID instead of a text string to identify the CPU. Let me check my system later this evening.

 

[novation]

Hi, I'm also in the process of installing macOS on my new system: Z390, RX 580 with 32GB RAM G.Skill Ripjaws, be quiet power supply and Samsung 860 Pro 256GB SSD. Now my problem is that phase 2 keeps rebooting. I read the thread and discovered firmware issues with the SSD. But this is about the 970 SSD. Not the 860 SSD. Is this correct? And if not can someone tell me why it doesn't complete the installation? Thanks in advance and for this great tutorial.

Edit: Went back to BIOS and reverted to basic BIOS settings. Made the necessary changes in BIOS. Done. Problem solved. Got the extra apfs in Clover bootloader now. Thanks!

 

[pljucasdvakurca]

OK. So I did some testing with the Thunderbolt and my Apollo Twin Mk2. The regular Thunderbolt ports don't work when I try to connect... but with the USB-C adapter that I luckily have works fine. I'm also wondering if it is possible to run my old Firewire audio interface with the Firewire-Thunderbolt converter cable.