Contribute
Register

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

NorthAmTransAm said:
I went to Hackintool>Logs>System and hit refresh then searched "DROM"

I have zero boot args at the moment!

I'm guessing if you're not seeing anything then yours is correct?
Click to expand...
I specifically entered a fake CRC32!
 
CaseySJ said:
  • I assume you're seeing the Thunderbolt Bus and are injecting a particular Thunderbolt DROM?
  • Does the same DROM appear in NHI0?
  • What are your Boot Arguments?
    • I've tried with and without debug=0x100, but no luck.
  • I wonder if something in the Thunderbolt SSDT might affect this?
Click to expand...

Yes to both. TB3 appears to be fully (well 99%) working. Thunderbolt networking works with an invalid CRC32, despite what has been said in this thread.
Yes, the same DROM appears in NHI0.
I tried debug=0x100 as well with no change. Initial boot-args: agdpmod=pikera slide=0 dart=0 darkwake=0 -v

Maybe, but you all are using the old style TB3-SSDT, right? (I can't call it KGP, sorry, I posted it first on InsanelyMac ;p). I am using Osy's style of SSDT with true hotplug instead of PciHotplug which is pretty different.

I guess I'll try altering my FW DROM to see if that has any effect.
 
maleorderbride said:
Yes to both. TB3 appears to be fully (well 99%) working. Thunderbolt networking works with an invalid CRC32, despite what has been said in this thread.
Yes, the same DROM appears in NHI0.
I tried debug=0x100 as well with no change. Initial boot-args: agdpmod=pikera slide=0 dart=0 darkwake=0 -v

Maybe, but you all are using the old style TB3-SSDT, right? (I can't call it KGP, sorry, I posted it first on InsanelyMac ;p). I am using Osy's style of SSDT with true hotplug instead of PciHotplug which is pretty different.

I guess I'll try altering my FW DROM to see if that has any effect.
Click to expand...
It's still a puzzle why some folks see detailed Thunderbolt logs and others like us do not...

We've been experimenting with several SSDTs including skeleton ones that do the bare minimum. We've also developed an extensive SSDT based on Osy86's work that activates Thunderbolt Bus without a firmware modification, but the link drops after about 20 seconds, after which Thunderbolt devices do not connect.

I'm trying several variations of the SSDT now to see if that makes any difference in the logs.
 
@CaseySJ
Not sure if it's pertinent but I was using the attached SSDT. I changed:

71 -- CRC-8 to 11
02 C7 -- TBSwitch7 to 02 87
And used 01 58 00 01 00 0d 00 01 00 (iMac 19,1) for the fixed 9 bytes

When I fixed the first error, I restarted and the second error appeared. Fixed and now there's no mention of DROM in the log.

Infamously on the EX3.

I was experimenting with different things so I might have been a little aimless. I believe I changed 71 to 11 because that was what was in my DROM section. I hope this helps more than it muddies things up.
 

Attachments

  • SSDT-TBOLT3-RP21-GC-TITAN-RIDGE-Custom ***Edited***.aml
    2.1 KB · Views: 94
  • SSDT-TBOLT3-RP21-GC-TITAN-RIDGE-APPLE-DROM ***CLEAN***.aml
    2.1 KB · Views: 99
NorthAmTransAm said:
@CaseySJ
Not sure if it's pertinent but I was using the attached SSDT. I changed:

71 -- CRC-8 to 11
02 C7 -- TBSwitch7 to 02 87
And used 01 58 00 01 00 0d 00 01 00 iMac 19,1 for the fixed 9 bytes

When I fixed the first error, I restarted and the second error appeared. Fixed and now there's no mention of DROM in the log.

Infamously on the EX3.

I was experimenting with different things so I might have been a little aimless. I believe I changed 71 to 11 because that was what was in my DROM section. I hope this helps more than it muddies things up.
Click to expand...
Thanks! That is the same NICO version that I've been using. Out of the two SSDTs, which one caused the error to show up in the logs?
 
@CaseySJ

Just popped open hackintool on my 2 systems that are booted right now, Builds 1 and 3 in my sig.

Build 1:
GC-Titan Ridge Firmware: DSM2
SSDT: NO DROM INJECTED - Original DSM2 SSDT
IOreg: Fully Populated but TB7 has nothing in reg
Hackintool DROM Search Result:
Code: 
2020-03-16 15:32:25.320972-0700  localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::getDROM()> IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe00002be)

Build 3:
GC-Titan Ridge Firmware: E64FR+CSJ NVM23
SSDT: APPLE DROM from early SSDT Posted along with NVM23 originally (attached)
IOreg: Fully Populated but TB7 is populated but not like @Elias64Fr
Hackintool DROM Search Result:
No Results in the System Log File for DROM
 

Attachments

  • SSDT-TBOLT3-RP21-GC-TITAN-RIDGE-APPLE-DROM.aml
    2.1 KB · Views: 85
qthegaijin said:
@CaseySJ

Just popped open hackintool on my 2 systems that are booted right now, Builds 1 and 3 in my sig.

Build 1:
GC-Titan Ridge Firmware: DSM2
SSDT: NO DROM INJECTED - Original DSM2 SSDT
IOreg: Fully Populated but TB7 has nothing in reg
Hackintool DROM Search Result:
Code: 
2020-03-16 15:32:25.320972-0700  localhost kernel[0]: (IOThunderboltFamily) <IOThunderboltFamily`IOThunderboltEEPROM::getDROM()> IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Registry (0xe00002be)

Build 3:
GC-Titan Ridge Firmware: E64FR+CSJ NVM23
SSDT: APPLE DROM from early SSDT Posted along with NVM23 originally (attached)
IOreg: Fully Populated but TB7 is populated but not like @Elias64Fr
Hackintool DROM Search Result:
No Results in the System Log File for DROM
Click to expand...
Build 1:
I believe the original DSM2 SSDT injects ThunderboltDROM, right?

Build 3:
No error here because the ThunderboltDROM used inside the SSDT is fully valid.
 
I tried without any SSDT just now and I still have no errors. DROM injected via Clover with a patched card.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top