Search results

I found some useful info here, i might try the suggestion of booting windows (i'll need to restore my windows partition) to install updated drivers/firmware. http://www.tonymacx86.com/general-hardware-discussion/120690-gigabyte-ga-z87x-ud7-th-thunderbolt-2-0-testing.html I'll update with any...

Aright, I'm back up. I have some sucess to report, using those latest kexts the device ID of this TB device is reflected as 156c (Vs. 1566) under Hardware -> PCI -> Expresscard (System Information). The Apple Thunderbolt->FW800 adapter is still unrecognized (and thus any attached peripherals)...

Thanks! I'll give it a shot tonite. I changed something on in my bios that corrupted my osx installation, so i'm working now to get yosemite back.

No unfortunatley, I only know a smattering of c++. Initially i had looked inside all the TB kexts to see if one contained a .plist with the device id's, but i didn't see any. I don't suppose a hexedit is possible? Thats about the limits to my hack skillz. thanks

It seems like he Gigabyte boards use the same 156c TB as the Macbook Pro 11,2. Is it possible that a ID change at the DSDT or Clover level would be applied earlier in the boot process than fakepciid?

Probably not the ioreg, was thinking maybe the system log revealed some process that was happening in a real thunderbolt equipped mac that didn't with this system. Thanks again for your patience and time trying to solve this.

Gottcha. Would it be of any use to provide the system.log & ioreg of a thunderbolt equipped mac-mini booting with the thunderbolt-firewire dongle attached?

Wouldn't the device show up as 8086:156c in DPCIManager though? The PCI id still is showing 8086:1566. My HD4600, which uses your fakepciid, shows in DPCIManager as 8086:0412 (originally 0416). Maybe I'm misunderstanding. thanks again

K, does that mean changing the chipset devID from 1566 to 156c in this system isn't possible through fakepciid or dsdt? i know some bluetooth devices beed a kext to correctly load firmware on every boot, wonder if thunderbolt behaves in the same way...

Hi. Yes it definitely doesn't work when hotplugged, but I've had the Apple Thunderbolt -> Firewire 800 dongle installed/inserted throughout the whole testing process. One thing that is slightly glaring is under IOThunderboltController in ioreg for the MacbookPro 11,2, there is a node called...

Hey, I appreciate you taking the time to look into this. I think the Lenovo W540 & Dell M3800 workstations are the only two PC laptops atm equipped with Thunderbolt 2, they may use the same chipset. Anyways, I see more action when booting up with FakePCIID but it looks like the Kext is...

I can see FakePCIID attaching to the graphics card on boot, but not the thunderbolt device. Attaching the system.log & ioreg. This reflects booting without dropping the OEM SSDT tables & with the update kext darkvoid provided. Thanks@!

Thanks for your help in looking into this. I was pretty sure FakePCIID was installed correctly cause i was using it to get hardware acceleration in my HD4600 working. Clover is set up to drop the ssdt as I used maciASL to create a speedstep profile. Should i undo this and use the native SSDT...

Thanks for your help. Installed using kextwiazrd and fixed permissions + rebuilt cache, but nothing seems to have changed PCI device is still showing up as 8086:1566 (see *attachment). Don't suppose anyone would be willing to give a DSDT re-injection patch a shot? My ACPI tables were attached...

I've actually got that kext installed, i think i had followed a guide of yours involving using it to enable the hd4600 under yosemite. I re-read the description for FakePCIID but it's a little over my head. If it can change the device 8086:1566 to appear as 8086:156c (MBP 11,2), then hopefully...

I was hoping the thunderbolt 2 port on this Lenovo W540 would work out of the box, but that doesn't seem to be the case. I bought an Apple Thunderbolt to Firewire 800 adapter, when this is inserted two of the Apple Thunderbolt kext's load (see attachment) & "ExpressCard" appears under PCI in...