Contribute
Register

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

losinka said:
If I connect devices before computer start, then I see all of devices: OWC14Ports & eGPU (see screenshot). But this is same works with the original firmware (and without ssdt) too.
View attachment 456337


OK, I'll try...
Are you still gonna watch my original firmware that I posted here?
Click to expand...
So the modified firmware did not brick the Thunderbolt controller, but it did not enable Thunderbolt Bus either. It's best to flash the original one back for now.
 
@losinka
As you don't have same motherboard, could you send me your original dump of thunderbolt flashROM ?
 
CaseySJ said:
So the modified firmware did not brick the Thunderbolt controller, but it did not enable Thunderbolt Bus either. It's best to flash the original one back for now.
Click to expand...

I don't understand this topic about Thunderbolt.

How can Thunderbolt be bricked?
 

Attachments

  • TB_Z170x-UD5_TH_AlpineRidge_on_board_Dump_patched_TEST_ONLY.zip
    820.1 KB · Views: 64
Last edited:
cylsfar said:
I don't understand this topic about Thunderbolt.

How can Thunderbolt be bricked?
Click to expand...
  • Thunderbolt is controlled by special firmware located in a dedicated flash ROM chip on the motherboard.
  • The motherboard itself is also controlled by firmware located in a dedicated flash ROM chip. This firmware is often (mistakenly) called BIOS.
  • If we damage the BIOS, then the entire computer will not boot, because the motherboard firmware has overall control of the motherboard. In this case we say the motherboard is "bricked".
  • Likewise, if we damage the firmware that controls the Thunderbolt chip, we "brick" the Thunderbolt system. We can still boot the motherboard and run everything else because the motherboard firmware is separate from the Thunderbolt firmware.
  • But if we "fix" the Thunderbolt firmware with an external flasher, we can "un-brick" the Thunderbolt controller as well.
 
CaseySJ said:
  • Thunderbolt is controlled by special firmware located in a dedicated flash ROM chip on the motherboard.
  • The motherboard itself is also controlled by firmware located in a dedicated flash ROM chip. This firmware is often (mistakenly) called BIOS.
  • If we damage the BIOS, then the entire computer will not boot, because the motherboard firmware has overall control of the motherboard. In this case we say the motherboard is "bricked".
  • Likewise, if we damage the firmware that controls the Thunderbolt chip, we "brick" the Thunderbolt system. We can still boot the motherboard and run everything else because the motherboard firmware is separate from the Thunderbolt firmware.
  • But if we "fix" the Thunderbolt firmware with an external flasher, we can "un-brick" the Thunderbolt controller as well.
Click to expand...


OK, thank you. I think it is same problem of my missing Thunderbolt in BIOS?
 
@losinka I have changed Zipped files after an inverted Motherboard, Could you try new files on my previous updated post :)
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top