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

[manHands]

Just ordered it. Will report back after I try it out.

Thanks, really curious if it's in fact PCIe 3.0 X1. According to Marvell 88SE9215 product brief and datasheet, I'm not holding my breath. Everything points to PCIe 2.0 X1 or X2 capability...

Datasheet
Product Brief

Fingers crossed!

 

[FormerUser-594785]

Just Updated BIOS to F6 from F6c.
I can't import my old (F6c) profile saved to USB key. (not compatible).
So, after loading "Optimized Defaults", manually entered all Data from Casey guide.
So far so good.

 

[CaseySJ]

Thanks. I've made these changes. After a few times of going to sleep, it just stays on a black screen as if it's not awake, but you can hear the computer is running as normal. Nothing being displayed. I have to do a reboo,t and then I get stuck in the clover boot menu a few times. I need to turn off the computer and the power supply. Eventually, I get past the Clover menu and everything works fine until it does that sleep thing I said again at some point within the first 3/4 times it goes to sleep. Its making my build unusable ATM.

Arg, the dreaded wake-from-sleep that you've been reporting since the beginning...

Have you upgraded the power supply? Are all SATA drives working now after replacing the bad cable? Are the Vega fans under control? If you're a Final Cut user, have you switched to a headless platform ID?

If so, is wake-from-sleep the only remaining issue now?

 

[ZHENGQINLONG]

I don't know why the changes in config.plist are not taking effect...

Can you try to copy your entire EFI folder to the EFI partition of a USB flash drive and then boot from the USB flash drive to see if it takes effect?

I tried copying to the USB flash drive and updating config.plist. The device-id still does not change.

So I cleared EFI. Then reinstall all drivers with MultiBeast 11.0.1. Reload once.

This time I noticed it. When I changed the SMBIOS to imac18.3 without adding the Properties in Devices. The UHD 630 is working, although it still shows no work in iStat Menus and is displayed as "INTER UHD GRAPHICS 630". But the device-id is already shown as 923e0000. I opened the link video with QuickTime and its usage became around 10%. I used another player to open the 8K video in my computer and it played normally.

However, opening the FCPX in less than a minute will crash. Complete crash. The kind that must be forced to restart.

Then I started adding the values in the Properties in Devices. I found out that if I add and save all three data at once, the device-id will become 983e0000.

If I add framebuffer-patch-enable and AAPL, ig-platform-id first. After saving and restarting, add the device-id. Device-id will always be 923e0000. So I solved the current problem in this way. FCPX is also working fine.

It seems that everything seems normal right now. However, when I opened the link video with QuickTime, it started to be slightly stuck and then played normally. And iStat Menus still shows that the UHD 630 is not working.

 

[ZHENGQINLONG]

Because you have "Inject Kexts" set to "Detect" as shown in the screenshot below, it means you should install Lilu and WhateverGreen into /Library/Extensions and rebuild kernel cache by running Kext Utility. In your screenshot, we can see also that AppleIntelFramebuffer is not being attached. Instead, you have the default IONDRVFramebuffer. So please try again after installing Lilu/WhateverGreen into /L/E folder.

View attachment 394355

I tried it. But no effect.

Please take a look at #2568.
I am not sure if I solved the problem.

 

[CaseySJ]

I tried it. But no effect.

Please take a look at #2568.
I am not sure if I solved the problem.

Your CPU usage in post #2568 looks correct. iStat always shows Intel iGPU frequency as 0 MHz, so you can ignore it. As long as your device-id, ig-platform-id, and "AppleIntelFramebuffer" are appearing correctly, then the IGPU is working correctly.

 

[tholstro]

I've spent the last week reading this entire post. It's been like a good book and can't put it down!!

I've been struggling with what I'll call the "phantom display" as also mentioned in post #810. For some reason I'm showing to have two identical LG UltraFine displays. Not a big deal other than my dock sometimes moving to this phantom display.

LG UltraFine 5k is connected to the Thunderbolt port and the RX580 DisplayPort out is obviously going to the motherboards DisplayPort in.

Any recommendations???

Thanks!

Tom

Any thoughts?? Recommendations??

 

[1BConvery]

I've tried to recreate your install to the letter.I have a Z390 M gaming but would expect it to be close to the same. I get stuck at the "final" install. I've also seen some weird bios screen as well....it's attached.

Mobo updated to F5 and everything as you prescribed. 6 days in getting demoralized......

 

[ZHENGQINLONG]

Your CPU usage in post #2568 looks correct. iStat always shows Intel iGPU frequency as 0 MHz, so you can ignore it. As long as your device-id, ig-platform-id, and "AppleIntelFramebuffer" are appearing correctly, then the IGPU is working correctly.

View attachment 394450

I seem to be showing something wrong here?

 

[pastrychef]

I tried copying to the USB flash drive and updating config.plist. The device-id still does not change.

So I cleared EFI. Then reinstall all drivers with MultiBeast 11.0.1. Reload once.

This time I noticed it. When I changed the SMBIOS to imac18.3 without adding the Properties in Devices. The UHD 630 is working, although it still shows no work in iStat Menus and is displayed as "INTER UHD GRAPHICS 630". But the device-id is already shown as 923e0000. I opened the link video with QuickTime and its usage became around 10%. I used another player to open the 8K video in my computer and it played normally.

However, opening the FCPX in less than a minute will crash. Complete crash. The kind that must be forced to restart.

Then I started adding the values in the Properties in Devices. I found out that if I add and save all three data at once, the device-id will become 983e0000.

If I add framebuffer-patch-enable and AAPL, ig-platform-id first. After saving and restarting, add the device-id. Device-id will always be 923e0000. So I solved the current problem in this way. FCPX is also working fine.

It seems that everything seems normal right now. However, when I opened the link video with QuickTime, it started to be slightly stuck and then played normally. And iStat Menus still shows that the UHD 630 is not working.

View attachment 394441

That's weird. It doesn't make any sense that when you add 923E0000 device-id, it will change to 983E0000. 983E0000 should be a mobile IGPU, same as what's used in MacBookPro15,1.

Which build of macOS are you running? I'm running 10.14.3 (18D109).

I seem to be showing something wrong here?
View attachment 394455

This looks correct.