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

[Robertyu]

Thank you for following up on the XFX Radeon. I may have to remove or otherwise reword NOTE 4 from the guide, which currently reads:

NOTE 4: The XFX Radeon RX 580 graphics card is known to cause kernel panics during installation, and is strongly discouraged. Use a different brand (Sapphire, MSI, PowerColor, etc.).

Please let me know if the statements below are accurate from your experience:

• The HDMI port works?
• Each of the DisplayPort connectors works. If you iterate the DP cable through each of the DP ports, do they all work?
• I don’t care about DVI-D , but if you got a chance to test that, does it also work?
• If you set BIOS —> Initial Display Output —> PCIe 1 Slot, can you see the BIOS splash screen, the Clover Boot Menu, and the Mojave login screen through the XFX Radeon 580?
• In BIOS, CSM Support is disabled?
• On the older Asus motherboard, did you perform a clean installation of Mojave with the XFX Radeon plugged in and connected to the primary display monitor?

And finally, if you happen to have Windows installed and a copy of ATI Win Flash or GPUZ, it can identify the firmware version on the card. That might be useful to post.

Sorry for such a late response, have been busy...

• The HDMI port does not work on either machine.
• Only the two DP ports at the top of the card work, same on both machines. The third DP port down from top of backplane works right up until the display driver in MacOS takes over during final stage of boot, then blank screen.
• I've got nothing to test the DVI-D port with at the moment.
• On boot, I see the motherboard bios splash screen (when turned on in bios), the Clover boot screen, and the Mojave logon screen.
• I'll need to check the bios settings for the CSM support as I forget what I had set that to.
• I have not had the XFX RX-580 plugged in during setup of either system, not have a tested that. I always introduced the card after Mojave install, and port installation steps of the guide.

I do not have Windows installed except on a Parallels VM, so no CPUz or ATI Win Flash have been used.

 

[3Dman]

@zoomlenz @CaseySJ @luckyal

Just catching up on a couple days worth of posts/following along. If we're successfully able to unlock MSR 0xE2 on the Gigabyte Z390 Designare, what would be the immediate benefit?

If I understand correctly, we could then enable VT-d and remove dart=0? Which kexts could we remove as well after the unlock? I'd like to possibly try it, but my system is running great right now and I don't want to mess with it.

It's possible to boot without KernelPM clover patch which patches AppleIntelCPUPowerManagement.kext to prevent it from writing to that register, so more vanilla, better power management maybe?

As for VT-d, I fixed it by using VirtualSMC as the panic was related to FakeSMC.

 

[monarchx94]

I'm doing this build with an i9-9900K and a GTX 1080 Ti. I'm trying to run High Sierra for the GTX 1080 Ti.

- the 2 Kernel and Kext Patches lines weren't in or available in Clover Config - I went ahead to install and got to 75% before hitting the No Entry Symbol,

If there's any advice out there, it would be deeply appreciated! - this is my first build

 

[faithie999]

Thanks a lot for your reply.

I hope I'm not too much off topic ,but am I wrong to think that Windows would add the same folder (/ Microsoft) if I had a third SSD with a Linux distribution in a triple boot UEFI mode (macOS / Windows 10 / Linux)?

After lots of trial and error, I successfully installed Ubuntu on a separate HD, and now am able to boot Mojave, Windows 10, and Ubuntu from the Clover boot screen. I know very little about Linux, and the only prior experience I had was with a Ubuntu Live CD. So I went with Ubuntu rather than another flavor of Linux. If I don't get some of the Linux lingo right, my apologies.

First, I learned that the most recent long-term support release of Ubuntu, (which I had planned to install), 18.04, doesn't include drivers for RX 590 (and perhaps not RX 580 either), or HD630. while there may be a distribution of same out there somewhere with "safe graphics mode" as a boot option, I couldn't find it, so I went with the most recent release, 19.04.

I didn't want to remove my M.2 Mojave drive since I would have had to remove the CPU cooler which I didn't want to do. Removing the M.2 would make Ubuntu post-install easier but that would spoil the fun!

Note: you will need to know the "UNIX name" of your Ubuntu target drive. There is probably a way to determine that from macOS but I have no idea how to do so. A good assumption is that if you only have your M.2 and your Ubuntu target, it will be SDA. If you already have a Windows HD installed, then your Ubuntu drive may be sdb, depending on which SATA ports your Windows and Ubuntu drives are attached to. If both your Mojave drive and Windows drive are in M.2 slots, then your Ubuntu HD will be SDA.
To be absolutely sure, it is best to choose the "try Ubuntu safe graphics" (rather than "Install Ubuntu safe graphics") mode from the installer, and then run a terminal session and run the command

sudo fdisk -l (lower case L)

which will list all your drives in Linux lingo.

Most important: make sure you have a working USB boot drive. Test yours to make sure you can boot from it to the Clover screen.

So:
1) download and create install media for Ubuntu 19.04
2) install drive on which Ubuntu will be installed
3) boot from the Ubuntu install media. choose Install with safe graphics.
4) at the "Installation Type" screen, I chose "something else"
5) choose the drive that you want to install to and choose the partition that you want the boot loader installed to (your Ubuntu drive).
6) assuming you have wired Ethernet connectivity (I say wired since I have no idea if the Ubuntu installer contains drivers for your WiFi card), Ubuntu will download updated drivers during installation that will enable the RX590 card after reboot.
7) restart. It will boot into Ubuntu, but don't panic (yet!).

Despite the fact that you instructed the installer to put the boot loader on your Ubuntu drive, it also puts a Ubuntu folder/boot loader on your Mojave drive, which is why you computer will boot straight to Ubuntu at step 7. This is fine because I would advise a belt-and-suspender approach and from Ubuntu install the boot loader on your Ubuntu drive.

Once again from terminal run the fdisk command to verify the name of your Ubuntu drive.

Then type "sudo grub-install /dev/sdX" where X=the letter of your Ubuntu drive. if it complains re-run with --force added to the command (sudo grub-install /dev/sdX --force)

Plug in your USB boot drive and boot from it. Select your Mojave drive, and, when at the desktop, mount the EFI partition.

In /EFI remove the Ubuntu folder. But removing this folder doesn't completely remove the work the Ubuntu installer did to install grub on your Mojave drive.

Download and run Clover installer, just selecting the first two entries, for UEFI booting. That is needed to not have Ubuntu try to boot Ubuntu from your Mojave drive.

Remove your USB drive and reboot. If successful, you will see the Clover screen which now has an icon for Linux.

good luck!

ken

 

[CaseySJ]

I'm doing this build with an i9-9900K and a GTX 1080 Ti. I'm trying to run High Sierra for the GTX 1080 Ti.

- the 2 Kernel and Kext Patches lines weren't in or available in Clover Config - I went ahead to install and got to 75% before hitting the No Entry Symbol,

If there's any advice out there, it would be deeply appreciated! - this is my first build

Couple of suggestions:

• Are you booting with the verbose flag enabled (-v in Boot Arguments)? If not, please try that and capture a screenshot of the final log messages.
• It might be a good idea to see this and subsequent posts by @avtor.

 

[CaseySJ]

@faithie999, that’s a good guide for Linux installation. I’d like to link that post to Contributed Files and Tips in the build guide. Recently installed Ubuntu 19.04 on a separate dual-boot PC with Windows and an Nvidia GPU. Fractional scaling for 4K was enabled with this simple command. Quite impressed with Ubuntu 19.04 so far.

 

[RuleBreaker01]

One of the many nice things about Thunderbolt is the ability of two Macs to share devices over a local Thunderbolt connection. This is achieved through a Thunderbolt Local Node which enables Target Disk Mode and Target Display Mode. In both cases, one Mac acts as a donor and the other acts as a host. The donor Mac donates its boot drive or its LCD display to the host.

Unfortunately, we have not been able to make this work on a Hackintosh. So for the time being Target Disk Mode and Target Display Mode do not work. Target Disk Mode also works over FireWire, so as long as two machines have FireWire either with a PCIe FireWire card or Thunderbolt-to-FireWire adapter, it might be worth trying...

Regarding the M.2 device in the second slot (M2P), what is the make and model of the drive? Are you certain it’s a PCIe x4 NVMe SSD? The two M.2 slots share bandwidth with SATA, but because you have no SATA devices attached, you certainly should get full x4 bandwidth out of each slot. I would also suggest going into the BIOS peripherals page and checking the NVMe information. Feel free to post any relevant screenshots if you’d like to follow-up.

Edit: I just came across your thread here. Have you fixed the issue that prevented your from booting Mojave after updating the driver on the Chelsio NIC?

Thanks for the info! I was hoping to find out I wasn’t dreaming. I assume if target disk bootia a no-go, so is booting from an external TB3 drive. Use case Is to achieve a singular experience in MacOS environment. I want my MacBook Pro to completely sync to Desktop to work completely seamlessly through both. It’s possible to get halfway there, but not all the way. TDM would allow for me achieve similar result, in that I would be able to use the power of the desktop with my MacBook Pro NVMe. I’ve got a quad NVMe external TB3 Enclosure I could boot from, if possible, that would be satisfactory, but not psyched about carrying it around, even though it’s small. I could accept NVMe over USB 3.1 -> Performance is OK and it’s much smaller. Of course for those two, if the TB boot is possible.

The other option, which is showing a lot of potential is vitalized macOS with AMD GPU virtualization. This way, access to power singular experience. Access from literally anywhere. That’s the future. Running on one of my Xeon NVMe servers I can do that. A few issues to work out like handoff, performance of virtualized 10GbE, and a few other things. Otherwise it is a feasible option.

I finally got my install to boot. Booted in safe mode, then went single user, deleted the new Kext, reboot was still a panic. Then I booted without the Ethernet and Audio kexts and I was good. Not sure what the deal was, but it’s good for now.

Per the NVMe’s they are both new model WD Black. It’s weird, maybe just a BIOS reporting issue, because it shows my Chelsio NIC in slot one, and doesn’t show the GPU in slot 2. I’ll have to run a speed test to see if it’s really running x1.

Another peculiarity to note. Thunderbolt is disabled in BIOS, but Thunderbolt devices are there and working.

 

[CaseySJ]

...I’ve got a quad NVMe external TB3 Enclosure I could boot from, if possible, that would be satisfactory, but not psyched about carrying it around, even though it’s small. I could accept NVMe over USB 3.1 -> Performance is OK and it’s much smaller. Of course for those two, if the TB boot is possible.

Have you tried installing something simple on the external TB3 enclosure (maybe Windows or Linux) to see whether it appears as a boot disk in BIOS or when pressing F12 during boot? There is a Thunderbolt boot option in BIOS, which we normally disable because in my experience it led to BIOS corruption. But with F6 BIOS it might be worth trying. In the worse case, just re-flash the BIOS and reapply the parameters.

• Thunderbolt(TM) Configuration
  • TBT Vt-d Base Security → Disabled
  • Thunderbolt Boot Support → Disabled
  • Security Level → No Security

...
Per the NVMe’s they are both new model WD Black. It’s weird, maybe just a BIOS reporting issue, because it shows my Chelsio NIC in slot one, and doesn’t show the GPU in slot 2. I’ll have to run a speed test to see if it’s really running x1.

Yes that's a good idea. BlackMagic's Disk Speed Test (among others) should show READ speeds in excess of 2000MB/s.

Another peculiarity to note. Thunderbolt is disabled in BIOS, but Thunderbolt devices are there and working.

Thunderbolt is enabled by default. Are you sure you explicitly disabled it? Or perhaps a different Thunderbolt parameter is disabled...

 

[SardusX]

After lots of trial and error, I successfully installed Ubuntu on a separate HD, and now am able to boot Mojave, Windows 10, and Ubuntu from the Clover boot screen. I know very little about Linux, and the only prior experience I had was with a Ubuntu Live CD. So I went with Ubuntu rather than another flavor of Linux. If I don't get some of the Linux lingo right, my apologies.

First, I learned that the most recent long-term support release of Ubuntu, (which I had planned to install), 18.04, doesn't include drivers for RX 590 (and perhaps not RX 580 either), or HD630. while there may be a distribution of same out there somewhere with "safe graphics mode" as a boot option, I couldn't find it, so I went with the most recent release, 19.04.

I didn't want to remove my M.2 Mojave drive since I would have had to remove the CPU cooler which I didn't want to do. Removing the M.2 would make Ubuntu post-install easier but that would spoil the fun!

Note: you will need to know the "UNIX name" of your Ubuntu target drive. There is probably a way to determine that from macOS but I have no idea how to do so. A good assumption is that if you only have your M.2 and your Ubuntu target, it will be SDA. If you already have a Windows HD installed, then your Ubuntu drive may be sdb, depending on which SATA ports your Windows and Ubuntu drives are attached to. If both your Mojave drive and Windows drive are in M.2 slots, then your Ubuntu HD will be SDA.
To be absolutely sure, it is best to choose the "try Ubuntu safe graphics" (rather than "Install Ubuntu safe graphics") mode from the installer, and then run a terminal session and run the command

sudo fdisk -l (lower case L)

which will list all your drives in Linux lingo.

Most important: make sure you have a working USB boot drive. Test yours to make sure you can boot from it to the Clover screen.

So:
1) download and create install media for Ubuntu 19.04
2) install drive on which Ubuntu will be installed
3) boot from the Ubuntu install media. choose Install with safe graphics.
4) at the "Installation Type" screen, I chose "something else"
5) choose the drive that you want to install to and choose the partition that you want the boot loader installed to (your Ubuntu drive).
6) assuming you have wired Ethernet connectivity (I say wired since I have no idea if the Ubuntu installer contains drivers for your WiFi card), Ubuntu will download updated drivers during installation that will enable the RX590 card after reboot.
7) restart. It will boot into Ubuntu, but don't panic (yet!).

Despite the fact that you instructed the installer to put the boot loader on your Ubuntu drive, it also puts a Ubuntu folder/boot loader on your Mojave drive, which is why you computer will boot straight to Ubuntu at step 7. This is fine because I would advise a belt-and-suspender approach and from Ubuntu install the boot loader on your Ubuntu drive.

Once again from terminal run the fdisk command to verify the name of your Ubuntu drive.

Then type "sudo grub-install /dev/sdX" where X=the letter of your Ubuntu drive. if it complains re-run with --force added to the command (sudo grub-install /dev/sdX --force)

Plug in your USB boot drive and boot from it. Select your Mojave drive, and, when at the desktop, mount the EFI partition.

In /EFI remove the Ubuntu folder. But removing this folder doesn't completely remove the work the Ubuntu installer did to install grub on your Mojave drive.

Download and run Clover installer, just selecting the first two entries, for UEFI booting. That is needed to not have Ubuntu try to boot Ubuntu from your Mojave drive.

Remove your USB drive and reboot. If successful, you will see the Clover screen which now has an icon for Linux.

good luck!

ken

Thank you very much for taking the time to clarify this problem.
Have you experienced in your multi boot system the behavior described in this post?

macOS 10.14.X/WIN10/Linux UEFI Multiboot on separate 2 x nvme pcie SSD + 1 x Sata SSD

Hi All, I installed my current triple boot system (macOS 10.13.6/WIN10/Linux Clover Legacy) on a 1 x Sata SSD + 2 x Sata HDD connecting each time only the drive affected by each O.S. installation and installing Clover boot loader on the masOS Sata SSD. Now in my new build (Gigabyte Z390...

www.tonymacx86.com

 

[faithie999]

Thank you very much for taking the time to clarify this problem.
Have you experienced in your multi boot system the behavior described in this post?

macOS 10.14.X/WIN10/Linux UEFI Multiboot on separate 2 x nvme pcie SSD + 1 x Sata SSD

Hi All, I installed my current triple boot system (macOS 10.13.6/WIN10/Linux Clover Legacy) on a 1 x Sata SSD + 2 x Sata HDD connecting each time only the drive affected by each O.S. installation and installing Clover boot loader on the masOS Sata SSD. Now in my new build (Gigabyte Z390...

www.tonymacx86.com

Yes.

As I explained in my post about installing Ubuntu after having installed Mojave, the Ubuntu installer does the same thing that the post you referenced says that Windows does--it installs boot information onto the first drive in the tree which in my case is OS X Mojave.

I described how to eliminate the Ubuntu boot stuff from the OS X drive so you can boot directly to the Clover screen and choose your desired startup drive.

if you install Windows after having installed Mojave, the Windows installer creates a folder called Microsoft in the EFI folder on the OS X drive. Fixing that issue is much easier than the process for fixing the Ubuntu boot issue.

After you install Windows, it will reboot straight to Windows. you need to reboot with your USB boot drive installed, booting from the USB drive. Rrom the Clover screen, boot your Mojave drive. Once at the Desktop, mount your EFI partition. Open the EFI folder and you will see /Microsoft along with /Clover and /Boot. Open /Microsoft/Boot and you will see a file called bootmgfw.efi. Rename it to bootmgfw-orig.efi, so the Windows startup manager can't find it. When you reboot, you'll be back to "normal" with the boot going straight to your Clover screen.

If Windows does a "major" update, it may create a new bootmgfw.efi file. if you start up your computer some day and it boots to Windows, repeat the process described above.

Note: after installing Windows and fixing the boot issue, you may see several Windows icons on your clover boot screen. Choose the one that says something like "boot windows from Microsoft EFI". There are guides that tell you how to remove unwanted boot icons from the Clover screen.

ken