- Joined
- Jun 15, 2019
- Messages
- 62
- Motherboard
- ASRock Z390 Phantom Gaming-ITX/ac
- CPU
- i9-9900K
- Graphics
- RX 6950 XT
- Mac
- Mobile Phone
Yep, saw it 
Appreciate the quick reply, of course. Unfortunately, I cannot get back to my i9 during the day to upload my config.plist (for a prior poster) or write up a more thorough response to your post until I'm back at my i9 and have spent more time testing/reading!
I'll also be working on fixes I might come up with / find—ultimately I think the best bet overall for the most Apple-like TB3 functionality will be an SSDT fix similar to the NUC link I provided a few pages back. He specifically accounts for the interrupts that the Alpine Ridge controller sends the system on different events, which he specifically wrote was for the purpose of enabling hot-plugging. If that type of fix works, I suspect it'll take care of 3.0 (and 3.1 gen 2?) speeds by virtue of it hooking into Apple's TB XHC configs. (While I'm not ruling out modifications to the XHC-5 section of the codeless kext, and we may be able to get USB working manually that way.) I didn't have time to test the SSDT thing over the weekend, though, but I will post when I get to it. Also I of course don't expect you to do to it for me (I'm working on this also), but I thought it was better sharing promising notes before I totally checked it out in case you were interested.
One thing to note: I highlighted the electrical current control parameters in the plist only in connection with the HighCurrent USB setting you have set for Clover—I thought you may have enabled it to overcome an "insufficient power" warning, and I wanted to point out that Hackintool provides these values and that with them, I've not seen such issues. I doubt USB 3.0/3.1 speeds are related just to power settings, but I may be wrong. I'm also slightly wary about manipulating power values for a TB3 controller, since it's pretty different than a standard USB bus.
Also I agree: your settings seem right for the Z bluetooth card, I just shared mine for others who have the CS2 card like I do. I also tried some modifications for my NVMe controllers (I have Samsung 970s, and they're in different PCI port IDs.), but my fix didn't work—I'll upload that when I have it working.
Also- what corruption issues did you observe? I haven't noticed anything myself but I might have missed something.
Appreciate the quick reply, of course. Unfortunately, I cannot get back to my i9 during the day to upload my config.plist (for a prior poster) or write up a more thorough response to your post until I'm back at my i9 and have spent more time testing/reading!
I'll also be working on fixes I might come up with / find—ultimately I think the best bet overall for the most Apple-like TB3 functionality will be an SSDT fix similar to the NUC link I provided a few pages back. He specifically accounts for the interrupts that the Alpine Ridge controller sends the system on different events, which he specifically wrote was for the purpose of enabling hot-plugging. If that type of fix works, I suspect it'll take care of 3.0 (and 3.1 gen 2?) speeds by virtue of it hooking into Apple's TB XHC configs. (While I'm not ruling out modifications to the XHC-5 section of the codeless kext, and we may be able to get USB working manually that way.) I didn't have time to test the SSDT thing over the weekend, though, but I will post when I get to it. Also I of course don't expect you to do to it for me (I'm working on this also), but I thought it was better sharing promising notes before I totally checked it out in case you were interested.
One thing to note: I highlighted the electrical current control parameters in the plist only in connection with the HighCurrent USB setting you have set for Clover—I thought you may have enabled it to overcome an "insufficient power" warning, and I wanted to point out that Hackintool provides these values and that with them, I've not seen such issues. I doubt USB 3.0/3.1 speeds are related just to power settings, but I may be wrong. I'm also slightly wary about manipulating power values for a TB3 controller, since it's pretty different than a standard USB bus.
Also I agree: your settings seem right for the Z bluetooth card, I just shared mine for others who have the CS2 card like I do. I also tried some modifications for my NVMe controllers (I have Samsung 970s, and they're in different PCI port IDs.), but my fix didn't work—I'll upload that when I have it working.
Also- what corruption issues did you observe? I haven't noticed anything myself but I might have missed something.
