Contribute
Register

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

Ive got the kexts in the clover folder and my extensions folder is clean.
got my cable hookd Up! it works in clover when booting, but when I reach the os, it goes bye-bye.
are there any usb enabling differences between your Mojave and Catalina guides? I cant seem to see any.
@CaseySJ Figured it out, sorry for the bother. For some reason the latest version of usbinjectall.kext didn't work for me on 10.14.6, so I rolled back to version 0.7.3 and all the USB ports started working, and then of course, so did the bluetooth on the FUSB header. Took me a while to figure out out the USB wasn't working as I was looking for bluetooth related clues. Party.
 
** Micro-Guide: Radeon Speed Boost **
for Vega 56/64, Radeon VII, RX 5500/XT, RX 5700/XT
Please do not quote this micro-guide in its entirely. Post a link instead.​

I take it there are not going to be any powerplay table enhancements made for RX580. The post about the kext says RX570-590 are supported alongside WEG, so I used it.
 
Last edited:
Just rename the current config.plist something else but ending in .plist, eg oldconfig.plist.
If the new config.plist gives you problems then you can boot with oldconfig.plist from the Clover menu to get back to where you were.
So I finished the rest and tried booting via: F12>UEFI partition Corsair USB drive BUT then when it pre-selects my SSD it shows the "White" Do Not enter- Boot error sign
Macs booting error.png


Could this be possibly from Not deleting drivers etc in Number #10 of the Micro guide: Mojave to Catalina?
 
So I finished the rest and tried booting via: F12>UEFI partition Corsair USB drive BUT then when it pre-selects my SSD it shows the "White" Do Not enter- Boot error sign View attachment 464762

Could this be possibly from Not deleting drivers etc in Number #10 of the Micro guide: Mojave to Catalina?
Please enable verbose by adding -v to Boot Arguments. Then boot again so detailed logs appear on the screen.
 
I take it there are not going to be any powerplay table enhancements made for RX580. The post about the kext says RX570-590 are supported alongside WEG, so I used it.
I know it's tempting, but please:
Screen Shot 2020-04-24 at 4.41.12 PM.png
 
Definitely not on the top side, it must be below. Try taking a picture of this two from the side with phone to see if any is a "winbond" chip.
View attachment 464589
If non is, you will have to lift cooler, look for some inscriptions near the smd chip "THU" or "THU3", that might tell which one is it.

EDIT: You are looking for a chip like the top one in terms of size and form factor, could be near the TB3 port.
sorry for the delay in responding.
first--I deserve no credit for producing the firmware. that is all thanks to Elias/caseysj and a host of others.

it's been a couple of weeks, but IIRC it is the chip on the back side (fan side) at the very bottom of the your picture, right next to the metal housing that covers the back side of the SDcard slot. it doesn't say Winbond on it but it does have a model number--along the lines of 25Q80DV... the letter after V on the designer mobo is S but I think the one on the NUC is N.

I used the "low-priced" SOIC clip and it interfered with the SDcard metal housing. so I recruited one of my wife's nail files and sanded off the square edge of the clip where it interfered. there is quite a bit of plastic before you risk getting into the metal part of the contacts so don't fear, but remove just a bit then try it, then remove a bit more if necessary. you can tell visually when you've removed enough and the clip seats firmly on the chip's contacts.

in my experience I didn't need to use a resistor or capacitor to read the chip. I just connected the wires between my RPi2B and the clip and followed the rest of the guide.

good luck!
First look for any chip with 8 pins (four on one side, four on the other). Then look closely at the label on the chip. Does it say:
  • Winbond / W25Q80DV...
  • MXIC / MX25L8006E...
The chip should be in close proximity to the Thunderbolt controller (Intel JHL 6xxx or 7xxx). It could even be behind the Thunderbolt chip (i.e. on the other side of the board).

Thank you @dolgarrenan @faithie999 @CaseySJ => I'm going to pop my NUC open again tonight and flash the modded firmware :)

@faithie999 Thanks for the tip. Will keep that in mind!

For the NUC8, instead of externally flashing the chip, you might be better off running "Thunderbolt Patcher" after installing MacOS using the guide at osy86/HaC-Mini. This GitHub repository has a complete installer as well as instructions how to get TB working using an app created by the developer. The basic instructions there (copied from 'Installation.md') are to:

1. Download the installer and run **HaCMini.pkg**
2. Run the installer to completion
3. If you've selected to install _Native Thunderbolt_ support, run **Thunderbolt Patcher** from Applications after rebooting and patch your Thunderbolt controller.

@rj510 I actually tried running this within MacOS (tried a bunch of combinations and ensured I was running it as root) but neither the CLI nor the GUI could find any TB3 devices/controllers. IOReg shows they exist though and the TB3 devices (OWC TB3 Dock + Flash Drive) themselves work fine too (as long as they're plugged in before bootup) I'm guessing osy86's scripts only work with Hades Canyon i.e. NUC8i7HVK and not the model I have i.e. NUC8i3BEH
 

Thanks Casey! I had a few questions regarding the above linked Radeon guide (apologies in advance for all the questions, I like to try and think ahead):

1. As this is a new SSDT is this likely to break sleep? The reason I ask is because the only way for me to get 100% fully working sleep (with the machine not awakening randomly and going to sleep after 3 mins) was to apply your power management fix straight after a fresh install. The fix was in the first page of this thread:

Code:
cd /Library/Preferences
ls -l com.apple.PowerManagement.*

Code:
sudo rm com.apple.PowerManagement.*

2. I’m guessing as a worst case, if I apply the aforementioned Radeon SSDT in the Radeon mini guide, as well as the new kext, I can just run the above power management command again?

3. As we’re already on version 1.4 of this fix, assuming some time down the line there’s V1.x, if we find that has broken sleep, or something else, is there a simple procedure to roll back to the previous SSDT/kext, or do we have to restore from our Casey mandated backups? :D

4. How will a noob like me know when to upgrade from V1.4 of the kext to say V1.5 etc? Should I follow the thread you’ve mentioned on MacRumors and TonyMac?

5. Lastly, I haven’t got Netflix working on Safari yet and am going to run the fixes. Should I do that after or before I apply the new Radeon mini guide changes?

P.S. I’ll also run some Geekbench 4, cinebench and brute tests before and after so we can get some metrics going! I’ve also seen reference to OpenCL, Metal an GFXbenchmark tests that can be carried out. Is there any other tests yourself or anyone else would like me to try? I’m dual booting windows so don’t mind doing them there too to compare
 
Last edited:
I take it there are not going to be any powerplay table enhancements made for RX580. The post about the kext says RX570-590 are supported alongside WEG, so I used it.
@rj510 -- any comments? Seems I'm passing the buck! :)
 
...I actually tried running this within MacOS (tried a bunch of combinations and ensured I was running it as root) but neither the CLI nor the GUI could find any TB3 devices/controllers. IOReg shows they exist though and the TB3 devices (OWC TB3 Dock + Flash Drive) themselves work fine too (as long as they're plugged in before bootup) I'm guessing osy86's scripts only work with Hades Canyon i.e. NUC8i7HVK and not the model I have i.e. NUC8i3BEH
Osy86's Thunderbolt patcher (tbpatch) tool is awesome, but it won't work out of the box. We first need to configure and install the TbtOnPch SSDT, reboot, ensure that Thunderbolt Bus appears, and then run the patcher to modify the Thunderbolt chip. On an Alpine Ridge system, you might wonder why it's even necessary to flash the firmware when an SSDT will do the job! @Elias64Fr has a fully working Thunderbolt Bus on his Asus Maximus X Hero Maximus IX Extreme (with on-board Alpine Ridge). Firmware flashing is not necessarily required for on-board Alpine Ridge controllers.

Correction: Elias has Maximus IX Extreme.
 
Last edited:
Back
Top