- Joined
- Feb 9, 2013
- Messages
- 18
- Motherboard
- I didn't read
- CPU
- the RULES
- Graphics
- so ignore me
Hey friend
hey there, BoomR
i got myself a dual port card
the general info from the TBEX thread doesn't make it clear the way the controller functions on a hack
it'd be nice to make it clear that:
any driver version prior to v3 on windows configures the device in a way that will make OSX see the device upon RESTARTING from windows and will keep it configured between RESTARTS
shutdown makes it necessary to boot into windows again
but that's not the reason I'm writing
my tech-guru friend with a reputation in all parts of the world is currently hardware modding my dual port controller to make it work natively in macos, he has done so with a single port controller of his while modding it to work WITHOUT the header for people with a mac pro and such
but it suddenly occurred to me, that i haven't tried the simple path of forcing the TB kext to load via
<key>ForceKextsToLoad</key>
<array>
<string>\System\Library\Extensions\AppleThunderboltNHI.kext</string>
</array>
since i don't have the controller as it is being surged - can you please try that config.plist string and see if it is recognized as a native controller and if the firmware modding is an overkill on my part since my mobo has the GPIO header?
my interest is not the cosmetic nativeness, but dropping the windows requirement and enabling hot-plug
thank you
offtopic P.S.
i've also seen your last post in another thread that you are servicing your X99 system. could you please tell me why? for i suspect the hack is unstable under heavy GPU+CPU load in these systems, I'm doing my last test before sending my cpu for warranty (everything else has been swapped)