- Joined
- May 30, 2016
- Messages
- 980
- Motherboard
- Gigabyte Z490 Vision G
- CPU
- i9-10900K
- Graphics
- RX 5700 XT
- Mac
- Classic Mac
- Mobile Phone
not sure what you are talking about
hopefully @dgsga will check in and suggest troubleshooting steps.unfortunately I can't seem to get @dgsga 's method to work on Z170x-UD5 TH (Alpine Ridge NVM21)
View attachment 469102
No, I didn’t/don’t see DROM anywhere in the logs... I’m not sure it needs to be valid to appear in IOReg; maybe any property key/value can be added and it shows up?hopefully @dgsga will check in and suggest troubleshooting steps.
what my hangup is: his guide says to look in the system log after booting with the modded SSDT for a DROM error which will give the proper CRC32, since he changed one entry in my DROM to enable connection to port5. I don't find any reference to DROM in my system log. were you able to find that and correct your DROM crc32? it appears you did since your DROM appears in your IOReg screen shot.
thanks
When @dgsga looked at my IOReg and saw the absence of the DROM, he said to check again for a DROM error entry in my system log. None there.No, I didn’t/don’t see DROM anywhere in the logs... I’m not sure it needs to be valid to appear in IOReg; maybe any property key/value can be added and it shows up?
when @dgsga looked at my IOReg and saw the absence of the DROM, he said to check again for a DROM error entry in my system log. none there.
having said that, without the DROM loading, my apple TB monitor including camera and mic is working fine. that's the only TB device I have and no plans to add more.
in about this Mac--system report--Thunderbolt, does your Thunderbolt bus appear?
I've been doing lots of experimenting with flashing my AR AIC, and now with the non-flash approach, and I have found that often I have needed to reset CMOS (then reset BIOS and unlock MSR) for the thunderbolt bus to appear and to get the TB tree to populate properly in IOReg. other times when when TB is missing, I just need to shut power off to the PSU for a few seconds, then restart, then often followed by a "warm boot".
I have not yet figured out how to determine the codes for find and replace for ACPI patching via boot loader, so I always patch my DSDT and load it via acpi/patched. I know you said that the process for that in OC is much more involved, but you may want to give it a try. In Clover I don't need to drop the OEM DSDT, just specify the name of the DSDT to load. Only when Clover can't find a DSDT in ACPI/patched with the right name, does it load the OEM DSDT (as far as I understand, anyway!). I always confirm that the patched DSDT has loaded by using MaciASL--new from ACPI--DSDT and inspect the regions that I modded.Thunderbolt bus does not appear in the system report, but I'll try a CMOS reset and cold boot and see what happens too. I also think my RP05._INI rename might be wrong, the hex strings I've seen in guides are way longer than what I'm using....
Meaning it runs better on the FWs we have, no experimenting needed and no big issues so far. I think it's the main reason for most people to have gone with the Designare.