Contribute
Register
I am happy with your sleep/wake working now. Is your OS is Catalina? or Mojave? And my USB map is fine patched from Mojave. nothing changed cuz I installed Catalina from Mojave using AppStore.
Anyway, can you share your x299 EFI to compare to mine. I am using Z390's TB3 SSDT not working HP. I have another TB3-SSDT which works HP first time but not second time anymore.
I'm with Mojave, and this is my Clover configured for a 12 core CPU.
I have some Kext in L/E so Inject Kexts is set on Detect, on Catalina instead, it must be set on Yes.
 

Attachments

  • CLOVER.zip
    5.3 MB · Views: 114
Do not connect the cable and then put a jumper on Pin 3 to Pin 5 this will force power. If you got a GC - Alpine or Titan Ridge the 5 pin is the one furthest from the PCI blade.
This is sufficient if the hotplug works partially?

Also I still highly suggest Using Casey Mini Guide to flashing modified firmware to your card with raspberry pi & SOC8 clip(around $70) there are other cheaper options that come in around ($15) but need some modification and be handy with a soldering iron. After flashing the firmware use Casey mini guide for adding proper DROM to your SSDT.
I consider it a risky procedure, but I'm curious about it, where can I find the guide?
 
LeleTuratti Thanks for that. I did just adjusted accordingly to E.7 section and nothing changed. The devices plugged are still powered off when the machine starts :(
Does the Dock turn on or stay off at boot? Can you test it on a Macbook to see if it turns on automatically at boot?
Also try to connect the OWC 5bay directly without linking it to the Dock and see if it turns on at boot.
I would make sure that the problem is not related to the devices before intervening on the computer...
 
Does the Dock turn on or stay off at boot? Can you test it on a Macbook to see if it turns on automatically at boot?
Also try to connect the OWC 5bay directly without linking it to the Dock and see if it turns on at boot.
I would make sure that the problem is not related to the devices before intervening on the computer...

Good shout! MBP does power the dock with the drive together upon boot.
Video attached: https://mab.to/tJpazLIlZNSu7

It doesn't automatically boot with the drive directly plugged.

I'm wondering if the USB 2.0 not being connected might be the problem. My motherboard doesn't have a USB 2 port but I could order an adapter:tiny.cc/gvapnz

Do your machine boot up with the TB device? Also, does it have the USB2 port connected?
 
Last edited:
This is sufficient if the hotplug works partially?

I can not say as I never tried it with an unmodified firmware but I do not see how it would not work since we are just forcing power to the card.

I consider it a risky procedure, but I'm curious about it, where can I find the guide?

It sounds much more scary and risky than it is! However, the risk is more inline with writing to a floppy disk. I have put an Titan ridge firmware on an Alpine ridge just to see if it would break it. The card did not work but when I hooked it up to the programer and put an Alpine ridge firmware back onto the card it was working again. I also had a time where the SOC clip got bumped by my tornado child and I had the write fail tested the card and did not work so I ran the programer again write completed and the card worked fine. I use the NVM 33 firmware as it gives the most functionality.

I think there is one person that has messed up the chip but I am pretty sure they removed/desoddered it from the motherboard since they could not get the SOC clip to attach.

Modified firmware downloads:

Flashing processes:

Modified DROM:
 
Last edited:
I can not say as I never tried it with an unmodified firmware but I do not see how it would not work since we are just forcing power to the card.



It sounds much more scary and risky than it is! However, the risk is more inline with writing to a floppy disk. I have put an Titan ridge firmware on an Alpine ridge just to see if it would break it. The card did not work but when I hooked it up to the programer and put an Alpine ridge firmware back onto the card it was working again. I also had a time where the SOC clip got bumped by my tornado child and I had the write fail tested the card and did not work so I ran the programer again write completed and the card worked fine.

I think there is one person that has messed up the chip but I am pretty sure they removed/desoddered it from the motherboard since they could not get the SOC clip to attach.

Modified firmware downloads:

Flashing processes:

Modified DROM:
Hi there,
Just to be sure, could you please confirm that modifying the firmware/Eprom of a TB3 Alpine Ridge V2 AIC will give you all of the following:
- Cold plug/Hot Plug ( before & after sleep/wake )
- Video Pass through
- TB Networking
- Both USB-C ports working.

I know it's working via Titan Ridge, but unsure @ Alpine Ridge.

As of now the only thing missing on my system is TB networking.
Thanks for your amazing work and sharing your experience with the hack community.
 
Last edited:
Hi there,
Just to be sure, could you please confirm that modifying the firmware/Eprom of a TB3 Alpine Ridge V2 AIC will give you all of the following:
- Cold plug/Hot Plug ( before & after sleep/wake )
- Video Pass through
- TB Networking
- Both USB-C ports working.

I know it's working via Titan Ridge, but unsure @ Alpine Ridge.

As of now the only thing missing on my system is TB networking.
Thanks for your amazing work and sharing your experience with the hack community.

Since I only messed with the alpine ridge for a short min I took some time and I flashed every Alpine ridge firmware onto the card that is in the repository linked above including the ones other brands such as the Asus EX alpine ridge. I even tested a few files that I had that were beta so to speak. I received the same result when the video pass threw works the TB3 does not and when TB3 works video pass threw does not. No one is really giving the Alpine Ridge Firmware the love that NVM 33 "Designare" firmware received. I have a Titan Ridge add-in card but I use the modified firmware for the Designare onboard "NVM33". Since I had nothing to do with the creation "that is beyond my tech ability" I can only test files.

The file I recommend for alpine ridge is V3 from the repository it provided everything on your list without video pass threw. But if video pass threw is important the I would stick with your current implementation. You could also scrap the alpine and get a Titan if you can find one.
 
Thank you so much for your detailed response. Very helpful. Video pass threw is important for me, so I guess I'll wait & maybe get a Titan Ridge later on.
 
I can not say as I never tried it with an unmodified firmware but I do not see how it would not work since we are just forcing power to the card.



It sounds much more scary and risky than it is! However, the risk is more inline with writing to a floppy disk. I have put an Titan ridge firmware on an Alpine ridge just to see if it would break it. The card did not work but when I hooked it up to the programer and put an Alpine ridge firmware back onto the card it was working again. I also had a time where the SOC clip got bumped by my tornado child and I had the write fail tested the card and did not work so I ran the programer again write completed and the card worked fine. I use the NVM 33 firmware as it gives the most functionality.

I think there is one person that has messed up the chip but I am pretty sure they removed/desoddered it from the motherboard since they could not get the SOC clip to attach.

Modified firmware downloads:

Flashing processes:

Modified DROM:
Thanks for the links, I read in depth, it is not for everyone, but being careful you can succeed.
In my case I already have the hotplug working, even if not completely, so I don't run the risk of making these changes, also I would have to spend more money to buy accessories that I would only use once.

I would like to try to bridge the pins 3 and 5 of the THB_C cable, but I'm not sure which pins are right and I have too little information about it.
 
I wanted to report that in my X299 configuration, the hotplug only works from the second bridge-connected device onwards.

In my case I have a Thunderbolt Dock connected to the Alpine Ridge, the devices connected to the Dock are Hotpluggable, but if I disconnect the Dock and reconnect it, it is no longer reconnected to the computer.
The only way to have the Dock connected again is: reboot my computer and in some cases I have to disconnect it and reconnect it after a few seconds from boot (just before the Bios screen).
It's a situation I've seen in the past with my previous Z370 configuration, and the solution came from Gigabyte with the F10 Bios and subsequently F15 and F16a, which enabled the hotplug on MacOS.
 
Back
Top