Pete's Asus ROG Strix Z370-G Gaming (WI-FI AC) i5-8600K Build
- Thread starter PeteStewardson
- Start date
- Status
pastrychef
Moderator
- Joined
- May 29, 2013
- Messages
- 19,458
- Motherboard
- Mac Studio - Mac13,1
- CPU
- M1 Max
- Graphics
- 32 Core
- Mac
- Classic Mac
- Mobile Phone
I'm pretty sure I used DisplayPort. Apple only has 4K@60Hz support over DisplayPort.
- Joined
- Mar 7, 2018
- Messages
- 71
- Motherboard
- Asus ROG Strix Z370-G Gaming ( Wifi AC )
- CPU
- i5-8600K
- Graphics
- Vega 56
- Mac
- Mobile Phone
Yes I use the DP output on the motherboard. Works fine for me, but I'm using a 2k monitor.
- Joined
- Mar 7, 2018
- Messages
- 71
- Motherboard
- Asus ROG Strix Z370-G Gaming ( Wifi AC )
- CPU
- i5-8600K
- Graphics
- Vega 56
- Mac
- Mobile Phone
I remembered I've not updated this thread since I built this machine.
Following the original build, I didn't do much with the machine. However, on going to use it, I discovered it had auto-update to either Mojave or Catalina and was effectively dead in a set of boot loops. I've not updated Clover or anything since the build. So I suspect it was just not compatible somehow.
As I'm doing a little bit more on the machine now, and I have a dual monitor setup which I couldn't use with it with the iGPU setup, I went and bought myself a new 1TB Samsung 970EVO NVMe and a MSI Radeon RX Vega 56 Air Boost 8G OC graphics card.
I then started the process to get the machine up to Catalina 10.15.3. This took a bit of effort as for some reason, even using @pastrychef's latest Clover setup, the Catalina installer would not complete. After a bit of faffing about, I tried his OpenCore boot loader, and, low and behold, the install completed. I had a Catalina setup working with dual monitor, etc. To get both monitors working on DP connection, I did have to factory reset both monitors. No idea why but after that everything has worked perfectly as a dual monitor setup.
The next day I start to install software. Davinci was fine. But, as soon as I went to install PS, everything stopped as it would not install in a case sensitive file system. Somehow, and I don't remember selecting it, I had reformatted the NVMe as a case sensitive volume. So back to the drawing board.
After many tries, I discovered that the OpenCore boot loader will not boot/install my High Sierra install USB, so I had to go back to Clover for that. Then switch to Opencore, and then install Catalina. No idea why however doing this got me back up and running with a fully working install again.
There are two things I've noticed that still need to be looked into.
Sleep - The system goes to sleep and wakes up from a keyboard/mouse input. However, when the system is asleep, it seems like the system is in some way powering back up and down in the background as the fans spin back up, then go off, then back up after a minute or so. Need to see what that is but I tend to power down when not in use so not a big deal.
Unlock with Apple Watch - I have enabled this, it enables perfectly fine, but doesn't unlock on wake. Could be related to the sleep issue above as I get requests for access approval to a drive on the watch so I think it's working but not unlocking.
Other than that it looks good so far. And works with my twin 2K monitor setup.
Following the original build, I didn't do much with the machine. However, on going to use it, I discovered it had auto-update to either Mojave or Catalina and was effectively dead in a set of boot loops. I've not updated Clover or anything since the build. So I suspect it was just not compatible somehow.
As I'm doing a little bit more on the machine now, and I have a dual monitor setup which I couldn't use with it with the iGPU setup, I went and bought myself a new 1TB Samsung 970EVO NVMe and a MSI Radeon RX Vega 56 Air Boost 8G OC graphics card.
I then started the process to get the machine up to Catalina 10.15.3. This took a bit of effort as for some reason, even using @pastrychef's latest Clover setup, the Catalina installer would not complete. After a bit of faffing about, I tried his OpenCore boot loader, and, low and behold, the install completed. I had a Catalina setup working with dual monitor, etc. To get both monitors working on DP connection, I did have to factory reset both monitors. No idea why but after that everything has worked perfectly as a dual monitor setup.
The next day I start to install software. Davinci was fine. But, as soon as I went to install PS, everything stopped as it would not install in a case sensitive file system. Somehow, and I don't remember selecting it, I had reformatted the NVMe as a case sensitive volume. So back to the drawing board.
After many tries, I discovered that the OpenCore boot loader will not boot/install my High Sierra install USB, so I had to go back to Clover for that. Then switch to Opencore, and then install Catalina. No idea why however doing this got me back up and running with a fully working install again.
There are two things I've noticed that still need to be looked into.
Sleep - The system goes to sleep and wakes up from a keyboard/mouse input. However, when the system is asleep, it seems like the system is in some way powering back up and down in the background as the fans spin back up, then go off, then back up after a minute or so. Need to see what that is but I tend to power down when not in use so not a big deal.
Unlock with Apple Watch - I have enabled this, it enables perfectly fine, but doesn't unlock on wake. Could be related to the sleep issue above as I get requests for access approval to a drive on the watch so I think it's working but not unlocking.
Other than that it looks good so far. And works with my twin 2K monitor setup.
- Joined
- Nov 19, 2011
- Messages
- 72
- Motherboard
- ASUS STRIX Z370-g mATX (Clover)
- CPU
- I5-8400
- Graphics
- ASUS Radeon RX 580 8G
- Mac
- Classic Mac
- Mobile Phone
My PC wouldn't sleep...
I typed "pmset -g assertions" in the Terminal, and it showed "NetworkClientActive named: "org.cups.cupsd"
Someone mentioned that it could be a printer issue. So I reset printer settings ,and now we're asleep.
I typed "pmset -g assertions" in the Terminal, and it showed "NetworkClientActive named: "org.cups.cupsd"
Someone mentioned that it could be a printer issue. So I reset printer settings ,and now we're asleep.
- Status