Contribute
Register

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

CaseySJ said:
There are two versions of the Fenvi:
  • FV-T919 (more expensive, but more advanced version)
  • FV-HB1200 (cheaper, but a little slower -- still a very good choice)
Other choices are compatible too:
  • ABWB (check product description to make sure it's Hackintosh compatible)
And even more choices:
  • You can buy a PCIe to Mini-PCIe adapter and a Broadcom 93460CD or 94360CD module to insert into the adapter. Two choices are mentioned in the Componentssection at the top of post #1.
    • This is not the preferred choice but it will work if other choices are too expensive or unavailable.
Click to expand...
I'll check it. Thanks.
 
CaseySJ said:
Hello @KidCertified,

On-board audio is controlled by AppleALC, which in turn is a Lilu plug-in. This means we need Lilu, which I don't see in your screenshot. Simply copy it to the /Library/Extensions folder in Mojave and run Kext Utility to rebuild the kernel cache. Then reboot and try again.

I also noticed that your config.plist does not have slide=0, but Mojave is booting anyway (w/OsxAptioFix2Drv-free2000)?
Click to expand...

@CaseySJ THANK YOU SO MUCH FOR THE RESPONSE! EVERYTHING WORKS NOW!


Currently, I am on Catalina. But, when I first did the build, I did installed Mojave.

Yes, it boots up most time with no problem. But on occasions I have to restart the computer several times before it boots. This happened even when I had Mojave installed. That might have been what was causing that issue. I input the boot arg that you suggest will let you know if my occasional boot issue reoccurs. Again, thank you so much!
 
CaseySJ said:
Just captured these Radeon Performance Boost results are from my main Designare Z390 system with PowerColor Red Dragon RX 5700 XT:
View attachment 464785
Click to expand...

@CaseySJ Reporting in with my own personal increase. Don't have Geekbench 5 and only running the trial of 4 on OpenCL. Still running Mojave. Running Radeon VII. Note: Installing only into EFI -> kexts/Other didn't load it. Had to install into /L/E and rebuild to get it working. Sorry if someone reported this already. I've not been able to keep us with the thread as much.

Still trying to find the time to flash my TB. Got the Pi and other parts, just need the time.
 

Attachments

  • Radeon Boost Result.png
    Radeon Boost Result.png
    577.4 KB · Views: 90
  • Hackintool Installed Kexts.png
    Hackintool Installed Kexts.png
    533.7 KB · Views: 109
CaseySJ said:
If checksums match then contents will match as well. This is very interesting...please post a screenshot of System Information --> Thunderbolt when you get a chance.
Click to expand...
I verified contents (just to make sure it wasn't filled with just garbage) and they seem identical.

Here is a screenshot of my System Information > Thunderbolt:
SystemInformation-Thunderbolt--reflashed-OriginalFirmware.png
And even more weirdness ... IORegistry Explorer still shows ThunderboltLocalNode and ThunderboltPort@7:
IORegExpl-reflashed-OriginalFirmware.png

I can't make sense of it all ...
  • flashrom confirmed succesfull re-flash of the original firmware
  • after re-flashing I was able to get at least two backups with the exact same checksum as the original firmware, although requiring multiple read-attemps to get that (see spoiler with flashrom commandline output)
    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w tb-firmware-original.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading old flash chip contents... done.
    Erasing and writing flash chip... Erase/write done.
    Verifying flash... VERIFIED    .

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original1.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original1.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    flashrom is free software, get the source code at https://flashrom.org
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original2-vcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    flashrom is free software, get the source code at https://flashrom.org
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original2-hotplugvcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original3-vccstillconnected.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original4-vcchotplug.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin
    e105afc8a5cb82d025cbf1be0293676c81fd03d7 test-reflashed-original4-vcchotplug.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original5-vcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin
    e105afc8a5cb82d025cbf1be0293676c81fd03d7 test-reflashed-original4-vcchotplug.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 test-reflashed-original5-vcc.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original6-vcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin
    e105afc8a5cb82d025cbf1be0293676c81fd03d7 test-reflashed-original4-vcchotplug.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 test-reflashed-original5-vcc.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 test-reflashed-original6-vcc.bin
  • Yet macOS still sees a ThunderboltLocalNode and ThunderboltPort, even with only SSDT-Z390-DESIGNARE-TB3HP-V4 in CLOVER/ACPI/patched
The only thing I can think off is that CLOVER still sees the SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml that I have parked in CLOVER/ACPI/OFF. Will tests if System Information and IORegExplorer still report ThunderboltLocalNode after deleting CLOVER/ACPI/OFF/SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml and cold booting.

Edit: Just checked ... System Information and IORegExplorer still report ThunderboltLocalNode with ONLY the SDT-Z390-DESIGNARE-TB3HP-V4 on my EFI partition.
 
Last edited:
Speaking of RadeonBoost, just recomputed GeekBench 5 scores for both Metal and OpenCL. Wanted to see which specific tests produced the largest and smallest gains. Results:

Screen Shot 2020-04-28 at 1.57.26 PM_resize.png


Screen Shot 2020-04-28 at 2.09.14 PM_resize.png


This seems to suggest that Photo applications will experience the largest gains.
 
iRamon said:
I verified contents (just to make sure it wasn't filled with just garbage) and they seem identical.

Here is a screenshot of my System Information > Thunderbolt:
View attachment 465705
And even more weirdness ... IORegistry Explorer still shows ThunderboltLocalNode and ThunderboltPort@7:
View attachment 465706

I can't make sense of it all ...
  • flashrom confirmed succesfull re-flash of the original firmware
  • after re-flashing I was able to get at least two backups with the exact same checksum as the original firmware, although requiring multiple read-attemps to get that (see spoiler with flashrom commandline output)
    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w tb-firmware-original.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading old flash chip contents... done.
    Erasing and writing flash chip... Erase/write done.
    Verifying flash... VERIFIED    .

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original1.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original1.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    flashrom is free software, get the source code at https://flashrom.org
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original2-vcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    flashrom is free software, get the source code at https://flashrom.org
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original2-hotplugvcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original3-vccstillconnected.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original4-vcchotplug.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin
    e105afc8a5cb82d025cbf1be0293676c81fd03d7 test-reflashed-original4-vcchotplug.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original5-vcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin
    e105afc8a5cb82d025cbf1be0293676c81fd03d7 test-reflashed-original4-vcchotplug.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 test-reflashed-original5-vcc.bin

    pi@RBPi4B-RT:~/Desktop/20200427 $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-reflashed-original6-vcc.bin
    flashrom on Linux 4.19.97-v7l+ (armv7l)
    Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
    Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
    Reading flash... done.

    pi@RBPi4B-RT:~/Desktop/20200427 $ shasum *.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 tb-firmware-original.bin
    cceb66ecb01c7da3ff9e0de4031082d1af33f57c test-reflashed-original1.bin
    5ff1ac8ed10009cb876f5b21269492cba36005b7 test-reflashed-original2-hotplugvcc.bin
    e105afc8a5cb82d025cbf1be0293676c81fd03d7 test-reflashed-original4-vcchotplug.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 test-reflashed-original5-vcc.bin
    1809647344696d2bdc8a4982d1171bafb1dfd630 test-reflashed-original6-vcc.bin
  • Yet macOS still sees a ThunderboltLocalNode and ThunderboltPort, even with only SSDT-Z390-DESIGNARE-TB3HP-V4 in CLOVER/ACPI/patched
The only thing I can think off is that CLOVER still sees the SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml that I have parked in CLOVER/ACPI/OFF. Will tests if System Information and IORegExplorer still report ThunderboltLocalNode after deleting CLOVER/ACPI/OFF/SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml and cold booting.

Edit: Just checked ... System Information and IORegExplorer still report ThunderboltLocalNode with ONLY the SDT-Z390-DESIGNARE-TB3HP-V4 on my EFI partition.
Click to expand...
Sorry, I'm behind in the story.
Referring to the two screenshots in your post: did you have a Thunderbolt device connected at the time, and the problem is it's not showing up as connected in the system information--Thunderbolt devices screen, and not showing up in the IOReg?
 
iRamon said:
I verified contents (just to make sure it wasn't filled with just garbage) and they seem identical.

Here is a screenshot of my System Information > Thunderbolt:

And even more weirdness ... IORegistry Explorer still shows ThunderboltLocalNode and ThunderboltPort@7:
  • Yet macOS still sees a ThunderboltLocalNode and ThunderboltPort, even with only SSDT-Z390-DESIGNARE-TB3HP-V4 in CLOVER/ACPI/patched
The only thing I can think off is that CLOVER still sees the SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml that I have parked in CLOVER/ACPI/OFF. Will tests if System Information and IORegExplorer still report ThunderboltLocalNode after deleting CLOVER/ACPI/OFF/SSDT-TBOLT3-RP05-PORT7-DESIGNARE-Z390.aml and cold booting.
Click to expand...
Agreed -- this "memory" or ghost effect is very puzzling. Maybe I'll just go back to watching US Navy videos of UFOs. :)

Thunderbolt Bus won't appear with just that SSDT. Something else is at work...

Because the Titan Ridge JHL 7540 chip is separate from the Winbond W25Q80DV firmware chip, it's very likely that the Titan Ridge controller is in a zombie state because the firmware chip has not initialized it. Normally the firmware would initialize and interact with the controller, but if the Winbond chip is not working properly, then the controller stays in zombie land.

Because macOS queries the state of the Titan Ridge controller -- not the Winbond firmware -- the information we see in those screenshots may simply be coming from the Titan Ridge controller.
 
Last edited:
faithie999 said:
sorry I'm behind in the story.
referring to the two screenshots in your post: did you have a thunderbolt device connected at the time, and the problem is it's not showing up as connected in the system information--thunderbolt devices screen, and not showing up in the IOReg?
Click to expand...
Hi @faithie999,
No it's a little more complicated. Quick summary:
  • I tried flashing patched TB firmware to my Designare motherboard several days ago.
  • After flashing (flashrom said succesfully), ThunderboltLocalNode and ThunderboltPort appeared in my system, but Thunderbolt XHC/USB disappeared, and neither USB nor Thunderbolt would work on the two TB-ports.
  • Did all sorts of tests and troubleshooting, without succes.
  • Then re-flashed the original firmware back, hoping to get XHC back and default Thunderbolt support with original firmware.
  • However, with the original firmware flashed back (again, succesfully according to flashrom) I'm still missing my SSP1 and SSP2 USB ports, and I'm also still seeing a Thunderbolt Bus in System Information, and ThunderboltLocalNode in IOReg.
That's what the screenshots in my post are referring to.
 
CaseySJ said:
Agreed -- this "memory" or ghost effect is very puzzling. Maybe I'll just go back to watching US Navy videos of UFOs. :)
Click to expand...
Haha :lol: , yeah ... and when you watch that, you might just see how the US Navy captured footage of aliens messing with my motherboard while I was asleep :)

Thunderbolt Bus does not appear with just that SSDT.

Because the Titan Ridge JHL 7540 chip is separate from the Winbond W25Q80DV firmware chip, it's possible that the Titan Ridge controller has configured itself into a Default mode because of an inability to communicate with the firmware chip. Normally the firmware would initialize the Titan Ridge controller, thereby inducing non-default states.

Because macOS queries the state of the Titan Ridge controller -- not the Winbond firmware -- it's quite likely that the information we see in those screenshots is simply coming from the Titan Ridge controller.
Click to expand...
Your logic makes perfect sense.

Now the 290 euro question (and I think I know the answer) ... is there a way to fix it?

I'll leave you to watching the US Navy videos ... and before you do, please allow me to thank you so kindly for all your help and effort in my flashing adventures and recovery. Your knowledge and patience seem endless.
I will give the economy a 290 euro boost and order myself a new Designare.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top