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

[Inqnuam]

Please try the script I just updated

yes sir, bad manipulation with codes...

5AM: Updated!

Please check again when you have a time

EDIT: I think I missed the part of fields length for Vendor and Device name.





6AM:

I think, now I can die in peace.
Thank you Sir @CaseySJ and Sir @joevt. Sorry for my awful questions!

HackinDROM for GIGABYTE Z390 is fully working now!

The other Motherboards and PCIe devices will be available in the week. My brain needs some rest.

 

[jleahy2]

no USB freezes all day.

@mobi , @ziggenpuss , @jleahy2 how are you fairing?
are we over this hump?!?

Woohoo! Awesome!

I've got to say, so far... I haven't had any issues on my end either. I haven't rebooted the computer yet in probably at least a good 3-5 days at least. I'm going to try to keep it up and going for another week or two to make sure.

I'm still not sure I've seen a USB dropout at all since switching to the card. I've still got my bluetooth pad hooked up, and periodically move the mouse with it just to make sure it's still working, and...sure enough it still is.

So, that means, for me, one of two things is happening:
1- It's a coincidence I haven't had the on-board USB drop out yet, and it still may
2- Either my Mouse, Keyboard, or Ableton Push 2 device were the cause of the dropouts.


I still feel it's too early for me to say for certain, as I've been able to go a good week or so without seeing the issue before. I also haven't had time to work in Ableton here for over a week, which... that's when I got the drop outs, so.. until I can really sit down in that software, use the crap out of the keyboard, mouse, and Push2 controller, for maybe a good week or two, I probably won't be satisfied it's fixed/gone. But, so far, it's looking promising!

 

[joevt]

# example: If there's a space anywhere in the path name, use "\" before the space:
% loadfwfile ~/Downloads/Vision\ D/Vision-D-FW-1.bin

Quotes might be easier to do and read (but ~ must be outside the quotes)
loadfwfile ~"/Downloads/Vision D/Vision-D-FW-1.bin"

Method 1: From a newly extracted Thunderbolt Firmware file

sources:
/Users/casey/Downloads/Vision D/Vision-D-1.bin:active:v50:nvm_v50.0:0x4200

• The command listdroms shows the DROM itself and the source information, which in this example is the file Vision-D-1.bin. We also see that its firmware version (NVM) is v50.0 and the DROM is located at file offset 0x4200.

The "source" info also shows if the DROM came from the active or inactive part of the firmware (if you have a 1MB firmware which has been updated once before then it will have two DROMs). Firmware extracted from Linux
/sys/bus/nvmem/devices/nvm_active*/active
or
/sys/bus/thunderbolt/devices/*/nvm_active*/nvmem
are missing the 16K header and the source will indicate "linux". Linux can only extract the active part of the firmware. The inactive part is for updating the firmware (DROM should be at 0x200 and length should be <= 516096 bytes).

Method 2: From IORegistry

• If we already have a Thunderbolt DROM in use, it will appear in IOReg. We can load it into ThunderboltUtil with the command loadioreg
• The source information for DROM 2 shows that it's from ioreg at RP05.

Many Macs have two Thunderbolt controllers. loadioreg will load all the DROMs it finds.

Method 3: As a string of bytes

Spoiler

% listdroms
1)
thedrom=71000000000000ed009a1ec570016800ed000dc0010208818002800000000882900180000000088380048001000008849003800100000585500000058650000002c70b88200100640000000000038980058a504000058b5040000b0147494741425954450010025a34393020564953494f4e2044000000000000000000000000000000000000000000000000000000000000000000
sources:
/Users/casey/Downloads/Vision D/Vision-D-1.bin:active:v50:nvm_v50.0:0x4200
string:1

2)
thedrom=14004fc2e997aa0000432b79fc016800ed000dc0010208818002800000000882900180000000088380048001000008849003800100000585500000058650000002870b88200100640000000000038980058a504000058b5040000b0147494741425954450010025a34393020564953494f4e204400
sources:
ioreg:/Root/iMac19,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0/ThunderboltDROM

3)
thedrom=71000000000000ed009a1ec570016800ed000dc0010208818002800000000882900180000000088380048001000008849003800100000585500000058650000002c70b88200100640000000000038980058a504000058b5040000b0147494741425954450010025a34393020564953494f4e204400
sources:
test-DROM
string:2

• Notice that three DROMs are now in memory. The source information for item 3 is test-DROM because that was specified as the 2nd parameter to loadstring.

DROMs with multiple sources are duplicates. DROM #1 was loaded from a firmware and an unnamed string (string:1). DROM #3 was loaded from a named string (test-DROM) and an unnamed string (string:2)

At this point a "Method 4: from .aml file" might be useful since your DROM guides provide a compiled aml file. The source includes the aml file name, and the ACPI path (as best as the script can interpret it from parsing the dsl output). This method requires MaciASL.app to disassemble the aml to dsl so it can be parsed). The location is stored in the script (update the location if the app is not in /Applications).

Task 2: Specify a new unique UID
UID consists of 8 hex bytes in the form 8877665544332211. These bytes will be reversed when the ACPI output is generated. The last byte (11 in this example) is also the Thunderbolt Bus ID.

UID is a 64 bit number stored in little endian format (least significant byte first - which is the Bus ID in macOS). The UID is entered and displayed as it appears in macOS System Information.app (with or without the 0x hex prefix).

We use the command dumpdrom to show the modified DROM. Recall that listdroms displays the original unmodified DROMs.

You could add your changes to the DROM list using the following command:
loadstring $thedrom "my changes so far"

% dumpdrom
14004fc2e997aa0000432b79fc016800ed000dc0010208818002800000000882900180000000088380048001000008849003800100000585500000058650000002870b88200100640000000000038980058a504000058b5040000b0147494741425954450010025a34393020564953494f4e204400

That looks like the output of echo $thedrom instead of dumpdrom

 

[dehjomz]

** Mini-Guide for Viewing, Editing and Verifying Thunderbolt DROM
with ThunderboltUtil **
Please do not quote this guide in its entirely. Post a link instead.
Credit: @joevt
​

Trying to test this, extracted it and renamed the folder as specified. but upon running the script, it says permission denied. So I did a chmod +x to make it executable, but nothing happens upon execution... even changed terminal from bash to zsh, but nothing happens upon execution. Not sure what to do next.

 

[zkejonathan]

@CaseySJ Hey mate! Finally, I have found out the answer to why Bluetooth keeps dropping connecting and I cannot vanilla install 10.15.5, because of the Corsair Commander Pro, I attached its USB connector on HS11 and the Bluetooth USB connected to Commander.

It worked very well under Mojave, do I have any solution to resolve this issue other than removing the light switcher from the case? Thx in advance!

 

[boob]

Thought I should post that some of the Macbook users who are experiencing the same USB problems are claiming that simple OTG adaptors are fixing it. Hesitant to believe there's such a cheap solution but thought I should add it here. The only difference with OTG adaptors is the ground is bridged, which apparently is stopping the devices being seen as USB 2, so they're not causing the problem.

They're also confirming that the problem doesn't exist under Windows in Bootcamp, so thankfully it seems as though it is software based.

 

[Bobby22]

Hello @Bobby22,

This may be a hardware problem. If you have already updated to latest BIOS (which has the effect of clearing CMOS and starting from a clean state) then the problem you describe is most likely hardware-related. Please describe the problem to Gigabyte. One of the components or one of the connections in the system may be flawed. Gigabyte will probably ask you to replace or disconnect/reconnect various components in order to localize the problem.

@CaseySJ ,
Hi again,
I finally removed every part of the Computer one by one.
It appeared the Fenvi-T919 was causing the PC to BootLoop. When removed it will do its post test then Boot normally and even shutdown normally.
However it is strange, that with the Fenvi Plugged,
once you wait 4-6 hours of shutdown, the computer will work, at the first boot (not the second one).
It will run the POST and run, the Fenvi working perfectly (WiFi and Bluetooth).
If you shut it down, it will boot loop forever (until you wait 4-6h).
This problem can be solved by removing instantly the Fenvi, which will allow the computer to Boot.

Is there anyone which had the same problem here ?
I’m hesitating buying a new brand one Fenvi-T919. Could it be a support/conflict hardware problem ?
I can’t remember but you where talking about allowing the Intel WiFi/BT card to be displayed on Mac.
Is that a good solution or do you advise me to buy a new one ?
Should I buy a new one or just maybe change the brand.
What is the best WiFi/BT card supporting MacOS available nowadays ?

thank you

 

[zipb]

As usual, every couple of weeks or so, I lost USB connections, after rebooting gets fixed, fortunately my main audio interface it's FW and solid as a rock in Mojave , it's good to know that the inatek card works, sooner or later probably I'll take it away from the vintage MacPro where it lives to give it a spin

Every couple of weeks a hiccup? That's actual normal behaviour... I even have this on my official MacBook Pro.

 

[CaseySJ]

Trying to test this, extracted it and renamed the folder as specified. but upon running the script, it says permission denied. So I did a chmod +x to make it executable, but nothing happens upon execution... even changed terminal from bash to zsh, but nothing happens upon execution. Not sure what to do next.

Please look at the Downloading and Installing new "Activating ThunderboltUtil" section. This is why the mini-guide exists!

 

[CaseySJ]

...
At this point a "Method 4: from .aml file" might be useful since your DROM guides provide a compiled aml file. The source includes the aml file name, and the ACPI path (as best as the script can interpret it from parsing the dsl output). This method requires MaciASL.app to disassemble the aml to dsl so it can be parsed). The location is stored in the script (update the location if the app is not in /Applications).
...

Thank you for proof-reading the Mini-Guide. Changes have been made except for Method 4. Please see if you get the same errors on the attached dsl and aml files. MaciASL is in /Applications folder.

casey@iMac ~ % loadamlfile ~/Downloads/SSDT-Z390-DESIGNARE-TB3HP-V4.aml

loadonedslfile:7: command not found: #
loadonedslfile:8: no matches found: [A-Za-z_]
loadonedslfile:9: no matches found: [0-9]
loadonedslfile:10: no matches found: [A-Za-z_0-9]
loadonedslfile:11: command not found: #
loadonedslfile:13: command not found: #
loadonedslfile:14: command not found: #
loadonedslfile:15: command not found: #
loadonedslfile:16: command not found: #
loadonedslfile:17: no matches found: [A-Za-z_][A-Za-z_0-9]0
loadonedslfile:18: command not found: #
loadonedslfile:19: no matches found: ^*
loadonedslfile:20: command not found: #
loadonedslfile:21: no matches found: ([.][A-Za-z_][A-Za-z_0-9]0)*
loadonedslfile:22: command not found: #
loadonedslfile:23: no matches found: (([A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*)|)
loadonedslfile:24: command not found: #
loadonedslfile:25: no matches found: [A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*
loadonedslfile:26: command not found: #
loadonedslfile:27: no matches found: ([\]|^+|)(([A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*)|)
loadonedslfile:28: no matches found: [A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*

casey@iMac ~ % loaddslfile ~/Downloads/SSDT-Z390-DESIGNARE-TB3HP-V4.dsl

loadonedslfile:7: command not found: #
loadonedslfile:8: no matches found: [A-Za-z_]
loadonedslfile:9: no matches found: [0-9]
loadonedslfile:10: no matches found: [A-Za-z_0-9]
loadonedslfile:11: command not found: #
loadonedslfile:13: command not found: #
loadonedslfile:14: command not found: #
loadonedslfile:15: command not found: #
loadonedslfile:16: command not found: #
loadonedslfile:17: no matches found: [A-Za-z_][A-Za-z_0-9]0
loadonedslfile:18: command not found: #
loadonedslfile:19: no matches found: ^*
loadonedslfile:20: command not found: #
loadonedslfile:21: no matches found: ([.][A-Za-z_][A-Za-z_0-9]0)*
loadonedslfile:22: command not found: #
loadonedslfile:23: no matches found: (([A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*)|)
loadonedslfile:24: command not found: #
loadonedslfile:25: no matches found: [A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*
loadonedslfile:26: command not found: #
loadonedslfile:27: no matches found: ([\]|^+|)(([A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*)|)
loadonedslfile:28: no matches found: [A-Za-z_][A-Za-z_0-9]0([.][A-Za-z_][A-Za-z_0-9]0)*