- Joined
- Aug 22, 2018
- Messages
- 453
- Motherboard
- Gigabyte Z690 Aorus Master
- CPU
- i9-12900K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
Maybe it helps: https://github.com/5T33Z0/OC-Little-Translated Thanx 5T33Z0!
z170-Deluxe.ioreg is after HackinDROM and DTGP SSDTs were booted with. z170-Deluxe_Thunderboltz.ioreg is with the SSDT that I use which works.Are both IOReg files based on HackinDROM SSDT?
There are notable differences between the two:
- z170-Deluxe.ioreg --> booted with HackinDROM SSDT?
- z170-Deluxe_Thunderbolt.ioreg --> also booted with HackinDROM SSDT?
z170-Deluxe.ioreg:
View attachment 514018
z170-Deluxe_Thunderbolt.ioreg:
View attachment 514017View attachment 514016
This means SSDT-HackinDROM.aml was either (a) not processed or (b) rejected by macOS. We can find out what happened by booting with that SSDT and then grabbing the first few lines of the boot log as follows:z170-Deluxe.ioreg is after HackinDROM and DTGP SSDTs were booted with. z170-Deluxe_Thunderboltz.ioreg is with the SSDT that I use which works.
log show --last boot | tail -1000 > ~/Documents/bootlog.txt
Hello @Elias64Fr,Hello, Bonjour @CaseySJ,
if someone is interested on a modified BIOS firmware based on F9i version by including new F9j CPU microcodes (05/2020 and 06/2020 instead of 04/2020) [cut]
I just try it by flashing with Q-Flash BIOS feature without issue.
Yes please!If you want more details on what I have done, I can explain .
Sounds interesting. What are some of the changes/benefits?Otherwise, I have including on another customised BIOS firmware (not on previous one), some DSDT and SSDT modifications previously done on Opencore patching. Result is really nice !
I attached two versions.This means SSDT-HackinDROM.aml was either (a) not processed or (b) rejected by macOS. We can find out what happened by booting with that SSDT and then grabbing the first few lines of the boot log as follows:
This will create a file in Documents folder called bootlog.txt. I can then take a closer look.Bash:log show --last boot | tail -1000 > ~/Documents/bootlog.txt
So as I understand it, firmware flash does not lead to link speed improvements.Hello @LeleTuratti,
Thanks for pointing out the corrections. Changes made.
We spent months trying to activate Thunderbolt Bus on Titan Ridge with SSDT, but the effort failed. The Titan Ridge controller resets to Internal Connection Manager (ICM) mode after 20-30 seconds. Flashing the controller is the solution we're aware of.
Daisy chaining already work on my system.But you can make daisy chaining if you flash it
Arg, I made a careless mistake. The boot log should be generated like this (head, not tail):I attached two versions.
log show --last boot | head -1000 > ~/Documents/bootlog.txt
You can find attached ZIP file with this firmware.Hello @Elias64Fr,
Bonjour! I would be glad to test the modded F9i firmware if you can post it here publicly.
Yes please!
Sounds interesting. What are some of the changes/benefits?
Either "One" or "Zero" is okay because macOS checks for the existence of the property "PCIHotplugCapable" instead of any particular value of that property....
In fact in the part of the XHC1 controller (which I have renamed XHC3 to avoid conflicts) some parts were missing.
The "PCIHotplugCapable" methods are also set to "One", from what I know they should be "Zero", right?
...
Here you go.Arg, I made a careless mistake. The boot log should be generated like this (head, not tail):
Bash:log show --last boot | head -1000 > ~/Documents/bootlog.txt