I know you didn't ask me, but the Gigabyte support page states the Z370 Gaming 5 has official support for the i9-9900K since BIOS F12. So you should be fine. You can find the list here - https://www.gigabyte.com/Motherboard/Z370-AORUS-Gaming-5-rev-10/support#support-cpu
With latest WEG/Lilu and a RX580 it seemed to upgrade fine, but I actually lost HEVC/h265 acceleration (h264 still works fine). Can people who run an RX570 or RX580 who presume things went fine with their 10.15.2 upgrade please check if h265 acceleration is still working for them?
Well I cant explain it, but it seems to work here. I got a Caldigit TS3 dock today, can power it off and on, and it hot swaps. If there is a UAD Arrow in the chain after it, it also gets reconnected. I can change the order of devices, and change ports, and everything appears every time...
Thats true. The Arrow also has no power connector also, so its powered off between hotplugs, I must be missing something cause I'm not sure how its different? I'm getting a caldigit thunderbolt 3 dock later this week, I can try powering that on and off and see if hotplug works in that...
No I meant NVM, as in the Thunderbolt NVM, because mine was on 35 (0x23), while yours was on 32 (0x20). But I didnt realise you had Alpine Ridge so my mistake. I've only used the GC-TitanRidge (and briefly at that, just lucky it worked first go), no experience with Alpine Ridge. Hopefully...
In IOReg our thunderbolt's look pretty similar, except I notice you have an older NVM. Have you installed the latest Titan Ridge driver (220.127.116.110 from gigabytes website) in windows in order to update the firmware?
Here is my IOreg during an unplug and replug. The unplug looks similar...
I just got a GC-Titan ridge and installed it on a Z370 Aorus Gaming 3 (v1.0) board using F13 bios. Unexpectedly TB3 works perfectly fine in macOS (High Sierra - 10.13.6), including hotswapping. The only thunderbolt device I have is a UAD Arrow, but I can unplug it and plug it back in (even...
I was experimenting more with mine, and despite iMac13,x and iMac14,x definitions not booting, Macmini6,2 booted fine. Much easier than mucking around editing the installer, but the steps are there in case anyone needs it.
If you can use a more modern system definition like karlson12 says, thats the easiest way. Something like iMac14,2 or iMac13,2 work fine, unfortunately on one of my Sandy Bridge systems, those definitions froze on boot.
If you are stuck on something earlier like iMac12,2 - try the following -...
Thanks heaps for your help, I got it all working, ended up being HS10 -> SSP6. I do have one question, not to fix anything, just for my own understanding.
When I made the SSDT with -:
SSP4 (not used but included anyway to...
I already use -no_compat_check to boot with my chosen system_id. This was more just to *start* the 10.14.1 delta update, as it would spit up a window stating it cant install on this system (which is already running 10.14.0). I'm guessing its the same thing the original poster is referring to.
I have a question regarding something I'm seeing on a Haswell based system (Z97x-UD5-BK mobo), during the port discovery process (with port limit patch successfully applied on high sierra, I can see HS01 through HS15, and SSP1 through SSP6). Everything seems fine, apart from a single USB3...
I've updated my sandy bridge system just fine, but I had to unpackage the 10.14.1 updater, modify the distribution file, and repackage it. Basically removed the system and board checks. 10.14.1 seems to be working okay.