DIY eGPU Macbook experiences

jt_dylan · January 21, 2015

Thanks, that showed good info:

$grep IOPCITunnelCompatible /var/log/system.log

Jan 21 0037 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 00:11:58 memreas-mac-mini kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 00:13:02 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 00:20:22 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 01:15:38 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 09:22:52 memreas-mac-mini kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

I had it set in the middle but not the bottom of the file. ... testing...

euqlaog · January 21, 2015

Thanks, that showed good info:
$grep IOPCITunnelCompatible /var/log/system.log
Jan 21 0037 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 0037 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 00:11:58 memreas-mac-mini kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 00:13:02 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 00:13:02 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 00:20:22 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 00:20:22 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 01:15:38 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
Jan 21 09:22:52 memreas-mac-mini kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist
I had it set in the middle but not the bottom of the file. ... testing...

Ok, along with the missing IOPCITunnelCompatible true value, check also that you correctly typed "nvda_drv=1".

jt_dylan · January 21, 2015

Thanks, that showed good info:

$grep IOPCITunnelCompatible /var/log/system.log

Jan 21 0037 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 00:11:58 memreas-mac-mini kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 00:13:02 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 00:20:22 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 01:15:38 localhost kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

Jan 21 09:22:52 memreas-mac-mini kernel[0]: Driver "NVDAStartup" needs "IOPCITunnelCompatible" key in plist

I had it set in the middle but not the bottom of the file. ... testing...

- - - Updated - - -

Looks like it's loading. This is NVDAStartup from system.log:

Jan 21 14:44:57 memreas-mac-mini.local com.apple.kextcache[788]: kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext NVDAStartup.kext

Jan 21 1405 memreas-mac-mini.local com.apple.kextcache[788]: Invalid signature -67030 for kext <oskext 0x7f81bb449200="" [0x7fff73cc0cf0]=""> { URL = "NVDAStartup.kext/ -- file:///System/Library/Extensions/", ID = "com.nvidia.NVDAStartup" }

Jan 21 1441 localhost kernel[0]: NVDAStartup: Web</oskext>

euqlaog · January 21, 2015

Looks like it's loading. This is NVDAStartup from system.log:
Jan 21 14:44:57 memreas-mac-mini.local com.apple.kextcache[788]: kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext NVDAStartup.kext
Jan 21 1405 memreas-mac-mini.local com.apple.kextcache[788]: Invalid signature -67030 for kext <oskext 0x7f81bb449200="" [0x7fff73cc0cf0]=""> { URL = "NVDAStartup.kext/ -- file:///System/Library/Extensions/", ID = "com.nvidia.NVDAStartup" }
Jan 21 1441 localhost kernel[0]: NVDAStartup: Web</oskext>

Great if you got it working and let's hope you also get screen output with the DVI-HDMI or DP-HDMI adapter! The loaded/not loaded extensions are listed in System Report -> Software -> Extensions.

jt_dylan · January 21, 2015

still no luck. here's the latest from my syslog (NVDA search):

1/21/15 420.286 PM com.apple.kextd[22]: kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/System/Library/Extensions/NVDAStartup.kext"

1/21/15 420.000 PM kernel[0]: NVDAStartup: Web

1/21/15 420.801 PM com.apple.kextd[22]: kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/System/Library/Extensions/NVDAGM100HalWeb.kext"

1/21/15 421.000 PM kernel[0]: NVDAGM100HAL loaded and registered

1/21/15 424.000 PM kernel[0]: NVDA::rmStart failed

1/21/15 424.000 PM kernel[0]: NVDA,Display-B: Not usable

1/21/15 424.000 PM kernel[0]: NVDA,Display-C: Not usable

1/21/15 424.000 PM kernel[0]: NVDA,Display-D: Not usable

1/21/15 424.000 PM kernel[0]: NVDA,Display-E: Not usable

1/21/15 424.000 PM kernel[0]: NVDA,Display-F: Not usable

Any way to test the card from command line?

-J

euqlaog · January 21, 2015

still no luck. here's the latest from my syslog (NVDA search):
1/21/15 420.286 PM com.apple.kextd[22]: kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/System/Library/Extensions/NVDAStartup.kext"
1/21/15 420.000 PM kernel[0]: NVDAStartup: Web
1/21/15 420.801 PM com.apple.kextd[22]: kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/System/Library/Extensions/NVDAGM100HalWeb.kext"
1/21/15 421.000 PM kernel[0]: NVDAGM100HAL loaded and registered
1/21/15 424.000 PM kernel[0]: NVDA::rmStart failed
1/21/15 424.000 PM kernel[0]: NVDA,Display-B: Not usable
1/21/15 424.000 PM kernel[0]: NVDA,Display-C: Not usable
1/21/15 424.000 PM kernel[0]: NVDA,Display-D: Not usable
1/21/15 424.000 PM kernel[0]: NVDA,Display-E: Not usable
1/21/15 424.000 PM kernel[0]: NVDA,Display-F: Not usable
Any way to test the card from command line?
-J

Yes, there are some command line tools, for instance "ioreg", but it's difficult to read the results. If there are no more "needs IOPCITunnelCompatible key" rows in system log (check after the line of latest boot) and as it now says "loaded and registered", this is a very good sign. The screen output problem can be probably solved by the display adapter. Trying only HDMI most likely does not work with your GPU. Is the card name correct under System Report -> Hardware -> Graphics/Displays?

These instructions are very clearly done:

http://forum.techinferno.com/implementation-guides/6088-%5Bguide%5D-2011-13-macbook-pro-gtx660%4010gbps-tb1-sonnet-ee-pro-win8-1-osx10-9-1-a-2.html#post87145

Check also that "NVIDIA Web driver" is selected at the top bar menu. If under Graphics/Displays it still says something like "NVDA Chip Model (PCIe)", check again the kexts that you have modified.

jt_dylan · January 22, 2015

I checked the kexts. Here are the modified files but I still get "NVDA Chip Model (PCIe)" in System Info.

$cat NVDAStartup.kext/Contents/Info.plist

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>BuildMachineOSBuild</key>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>NVDAStartup</string>

<key>CFBundleGetInfoString</key>

<string>NVDAStartup 10.1.43 (343.02.01f01)</string>

<key>CFBundleIdentifier</key>

<string>com.nvidia.NVDAStartup</string>

<key>CFBundleInfoDictionaryVersion</key>

<key>CFBundleName</key>

<string>NVDAStartup</string>

<key>CFBundlePackageType</key>

<key>CFBundleShortVersionString</key>

<key>CFBundleSignature</key>

<key>CFBundleVersion</key>

<key>IOKitPersonalities</key>

<dict>

<key>NVDAStartup</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.nvidia.NVDAStartup</string>

<key>IOClass</key>

<string>NVDAStartup</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IOPCIClassMatch</key>

<key>IOPCIMatch</key>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>NVDARequiredOS</key>

<key>NVDAType</key>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOPCIFamily</key>

<key>com.apple.kpi.iokit</key>

<key>com.apple.kpi.libkern</key>

</dict>

<key>OSBundleRequired</key>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

</plist>

$cat IONDRVSupport.kext/Info.plist

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>BuildMachineOSBuild</key>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>IONDRVSupport</string>

<key>CFBundleGetInfoString</key>

<string>2.4.1, Copyright Apple Computer, Inc. 2000-2012</string>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>CFBundleInfoDictionaryVersion</key>

<key>CFBundleName</key>

<string>I/O Kit NDRV Support</string>

<key>CFBundlePackageType</key>

<key>CFBundleShortVersionString</key>

<key>CFBundleSignature</key>

<key>CFBundleVersion</key>

<key>DTCompiler</key>

<string>com.apple.compilers.llvm.clang.1_0</string>

<key>DTPlatformBuild</key>

<key>DTPlatformVersion</key>

<key>DTSDKBuild</key>

<key>DTSDKName</key>

<string>macosx10.10internal</string>

<key>DTXcode</key>

<key>DTXcodeBuild</key>

<key>IOKitPersonalities</key>

<dict>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>IOClass</key>

<string>IONDRVFramebuffer</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IONameMatch</key>

<string>display</string>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>IOClass</key>

<string>IONDRVFramebuffer</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IONameMatch</key>

<string>display</string>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPlatformDevice</string>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>IOClass</key>

<string>IONDRVFramebuffer</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IOPCIClassMatch</key>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

<key>OSBundleCompatibleVersion</key>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOGraphicsFamily</key>

<key>com.apple.iokit.IOPCIFamily</key>

<key>com.apple.kpi.iokit</key>

<key>com.apple.kpi.libkern</key>

<key>com.apple.kpi.mach</key>

<key>com.apple.kpi.unsupported</key>

</dict>

<key>OSBundleRequired</key>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

</plist>

$cat /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAController.kext/Contents/Info.plist

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>BuildMachineOSBuild</key>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>AppleHDAController</string>

<key>CFBundleGetInfoString</key>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AppleHDAController</string>

<key>CFBundleInfoDictionaryVersion</key>

<key>CFBundleName</key>

<string>HDA Controller Driver</string>

<key>CFBundlePackageType</key>

<key>CFBundleShortVersionString</key>

<key>CFBundleSignature</key>

<key>CFBundleVersion</key>

<key>DTCompiler</key>

<string>com.apple.compilers.llvm.clang.1_0</string>

<key>DTPlatformBuild</key>

<key>DTPlatformVersion</key>

<key>DTSDKBuild</key>

<key>DTSDKName</key>

<string>macosx10.10internal</string>

<key>DTXcode</key>

<key>DTXcodeBuild</key>

<key>IOKitPersonalities</key>

<dict>

<key>BuiltInHDA</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AppleHDAController</string>

<key>CodecAddressFilterArray</key>

<array>

<dict>

<key>CodecAddressMask</key>

<data>

AQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

<dict>

<key>CodecAddressMask</key>

<data>

AQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

<dict>

<key>CodecAddressMask</key>

<data>

CQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

<dict>

<key>CodecAddressMask</key>

<data>

AQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

</array>

<key>DPAlwaysDisplayRouting</key>

<array>

</array>

<key>DPAudioDeviceExclusion</key>

<array>

<dict>

<key>ManufacturerID</key>

<key>ProductID</key>

</dict>

</array>

<key>HighFIFOLimitSupport</key>

<key>HwFactoryPrefixTranslation</key>

<array>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

</array>

<key>IOClass</key>

<string>AppleHDAController</string>

<key>IOPCIClassMatch</key>

<string>0x04020000&0xFFFE0000</string>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>RequireMaxBusStall</key>

<array>

<dict>

<key>Layouts</key>

<key>MaxBusStall</key>

</dict>

</array>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

<key>NSHumanReadableCopyright</key>

<key>OSBundleCompatibleVersion</key>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOGraphicsFamily</key>

<key>com.apple.iokit.IOHDAFamily</key>

<key>com.apple.iokit.IOPCIFamily</key>

<key>com.apple.kpi.bsd</key>

<key>com.apple.kpi.iokit</key>

<key>com.apple.kpi.libkern</key>

<key>com.apple.kpi.mach</key>

<key>com.apple.kpi.private</key>

<key>com.apple.kpi.unsupported</key>

</dict>

<key>IOPCITunnelCompatible</key>

<true/>

</dict>

</plist>

Here are the nvram args:

$sudo nvram boot-args

Password:

boot-args -v -f kext-dev-mode=1 GraphicsEnabler=Yes nvda_drv=1

If anyone sees something off please let me know.

Thanks!!

-J

- - - Updated - - -

I checked the kexts. Here are the modified files but I still get "NVDA Chip Model (PCIe)" in System Info.

$cat NVDAStartup.kext/Contents/Info.plist

<dict>

<key>BuildMachineOSBuild</key>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>NVDAStartup</string>

<key>CFBundleGetInfoString</key>

<string>NVDAStartup 10.1.43 (343.02.01f01)</string>

<key>CFBundleIdentifier</key>

<string>com.nvidia.NVDAStartup</string>

<key>CFBundleInfoDictionaryVersion</key>

<key>CFBundleName</key>

<string>NVDAStartup</string>

<key>CFBundlePackageType</key>

<key>CFBundleShortVersionString</key>

<key>CFBundleSignature</key>

<key>CFBundleVersion</key>

<key>IOKitPersonalities</key>

<dict>

<key>NVDAStartup</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.nvidia.NVDAStartup</string>

<key>IOClass</key>

<string>NVDAStartup</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IOPCIClassMatch</key>

<key>IOPCIMatch</key>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>NVDARequiredOS</key>

<key>NVDAType</key>

<key>IOPCITunnelCompatible</key>

<true>

</true></dict>

</dict>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOPCIFamily</key>

<key>com.apple.kpi.iokit</key>

<key>com.apple.kpi.libkern</key>

</dict>

<key>OSBundleRequired</key>

<key>IOPCITunnelCompatible</key>

<true>

</true></dict>

</plist>

$cat IONDRVSupport.kext/Info.plist

<dict>

<key>BuildMachineOSBuild</key>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>IONDRVSupport</string>

<key>CFBundleGetInfoString</key>

<string>2.4.1, Copyright Apple Computer, Inc. 2000-2012</string>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>CFBundleInfoDictionaryVersion</key>

<key>CFBundleName</key>

<string>I/O Kit NDRV Support</string>

<key>CFBundlePackageType</key>

<key>CFBundleShortVersionString</key>

<key>CFBundleSignature</key>

<key>CFBundleVersion</key>

<key>DTCompiler</key>

<string>com.apple.compilers.llvm.clang.1_0</string>

<key>DTPlatformBuild</key>

<key>DTPlatformVersion</key>

<key>DTSDKBuild</key>

<key>DTSDKName</key>

<string>macosx10.10internal</string>

<key>DTXcode</key>

<key>DTXcodeBuild</key>

<key>IOKitPersonalities</key>

<dict>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>IOClass</key>

<string>IONDRVFramebuffer</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IONameMatch</key>

<string>display</string>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOPCITunnelCompatible</key>

<true>

</true></dict>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>IOClass</key>

<string>IONDRVFramebuffer</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IONameMatch</key>

<string>display</string>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPlatformDevice</string>

<key>IOPCITunnelCompatible</key>

<true>

</true></dict>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.iokit.IONDRVSupport</string>

<key>IOClass</key>

<string>IONDRVFramebuffer</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IOPCIClassMatch</key>

<key>IOProbeScore</key>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOPCITunnelCompatible</key>

<true>

</true></dict>

</dict>

<key>OSBundleCompatibleVersion</key>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOGraphicsFamily</key>

<key>com.apple.iokit.IOPCIFamily</key>

<key>com.apple.kpi.iokit</key>

<key>com.apple.kpi.libkern</key>

<key>com.apple.kpi.mach</key>

<key>com.apple.kpi.unsupported</key>

</dict>

<key>OSBundleRequired</key>

<key>IOPCITunnelCompatible</key>

<true>

</true></dict>

</plist>

$cat /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAController.kext/Contents/Info.plist

<dict>

<key>BuildMachineOSBuild</key>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>AppleHDAController</string>

<key>CFBundleGetInfoString</key>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AppleHDAController</string>

<key>CFBundleInfoDictionaryVersion</key>

<key>CFBundleName</key>

<string>HDA Controller Driver</string>

<key>CFBundlePackageType</key>

<key>CFBundleShortVersionString</key>

<key>CFBundleSignature</key>

<key>CFBundleVersion</key>

<key>DTCompiler</key>

<string>com.apple.compilers.llvm.clang.1_0</string>

<key>DTPlatformBuild</key>

<key>DTPlatformVersion</key>

<key>DTSDKBuild</key>

<key>DTSDKName</key>

<string>macosx10.10internal</string>

<key>DTXcode</key>

<key>DTXcodeBuild</key>

<key>IOKitPersonalities</key>

<dict>

<key>BuiltInHDA</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AppleHDAController</string>

<key>CodecAddressFilterArray</key>

<array>

<dict>

<key>CodecAddressMask</key>

<data>

AQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

<dict>

<key>CodecAddressMask</key>

<data>

AQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

<dict>

<key>CodecAddressMask</key>

<data>

CQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

<dict>

<key>CodecAddressMask</key>

<data>

AQAAAA==

</data>

<key>LayoutID</key>

<key>PCIVendorDeviceID</key>

</dict>

</array>

<key>DPAlwaysDisplayRouting</key>

<array>

</array>

<key>DPAudioDeviceExclusion</key>

<array>

<dict>

<key>ManufacturerID</key>

<key>ProductID</key>

</dict>

</array>

<key>HighFIFOLimitSupport</key>

<array>

<key>HwFactoryPrefixTranslation</key>

<array>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

<dict>

<key>LayoutID</key>

<key>SourceDID</key>

<key>StandInDID</key>

</dict>

</array>

<key>IOClass</key>

<string>AppleHDAController</string>

<key>IOPCIClassMatch</key>

<string>0x04020000&0xFFFE0000</string>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>RequireMaxBusStall</key>

<array>

<dict>

<key>Layouts</key>

<array>

<key>MaxBusStall</key>

</array></dict>

</array>

<key>IOPCITunnelCompatible</key>

<true>

</true></array></dict>

</dict>

<key>NSHumanReadableCopyright</key>

<key>OSBundleCompatibleVersion</key>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOGraphicsFamily</key>

<key>com.apple.iokit.IOHDAFamily</key>

<key>com.apple.iokit.IOPCIFamily</key>

<key>com.apple.kpi.bsd</key>

<key>com.apple.kpi.iokit</key>

<key>com.apple.kpi.libkern</key>

<key>com.apple.kpi.mach</key>

<key>com.apple.kpi.private</key>

<key>com.apple.kpi.unsupported</key>

</dict>

<key>IOPCITunnelCompatible</key>

<true>

</true></dict>

</plist>

Here are the nvram args:

$sudo nvram boot-args

Password:

boot-args -v -f kext-dev-mode=1 GraphicsEnabler=Yes nvda_drv=1

If anyone sees something off please let me know.

Thanks!!

-J

MVC · January 22, 2015

What is "Graphics enabler" doing in there?

That is hackintosh tech and isn't going to help you.

You can't shotgun this, it just has to be done right once.

And what is this about:

": kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/System/Library/Extensions/NVDAGM100HalWeb.kext"

Did you modify the drivers more than the guide?

No reason for that kext to have a bad signature.

w4vz · January 22, 2015

Ok so this time I did not take any chances and bought an EVGA 970 to replace my 770 sc after suspecting that its power draw would be somehow better handled.

Crossing fingers but not a problem since. Everything smooth as my girlfriend's legs even the safari bug disappeared. I only had time to test league of legend with Netflix for about an hour and still need more extensive testing but it has never been that far so definitely an improvement. I managed to use hdmi and dvi d for now in a 3 monitors setup.

Away for the next four days so wait until Monday/Tuesday for more infos..

gianni · January 22, 2015

RE: http://forum.techinferno.com/diy-e-gpu-projects/8691-2013-15-macbook-pro-gt750m-gtx980%4016gbps-tb2-akitio-thunder2-osx10-10-a.html#post118614

Hi @rossfrederick,

I'm trying to install a Gigabyte GTX 970 and I've a Mac like your.

On this forum I've posted a tread:

http://forum.techinferno.com/diy-e-gpu-projects/8735-%5Bwip%5D-2013-15-macbook-pro-gtx970%4016gpbs-tb2-sonnet-ee-se-ii-osx10-10-a.html

If you have some solution to my problems/mistakes, please try to help me!! Thanks!!

These are the drivers and the softwares I've used:

WebDriver-343.02.01f01

cudadriver-6.5.37-macos

TextWrangler_4.5.12

xcode44auxtools6938114a

Kext Wizard

Yosemite 10.10.1

HARDWARE

PSU Corsair RM 550W

Gigabyte GTX 970

MacBook Pro late 2013

Sonnet echo express se II

MVC · January 23, 2015

Got this pm:

Hi MVC,

I know I've made a lot of mess. Sorry...but I just want to fix my eGPU. I'll try to be methodical as you suggest.

1. Is it possible to install a GIGABYTE GTX 970 on a MacBook Pro late 2013?

2. This graphic card is supported by Sonnet Echo Express SE II?

3. If yes, can you kindly describe the correct way to install my GPU?

I hope you would help me. Thank you.

Gianni"

Please try reading forum posts.

Everything you need is here.

w4vz · January 23, 2015

Anyone tried their egpu with filevault? Tried to search the forum with no result. Anyone can share some experience?

jt_dylan · January 24, 2015

What is "Graphics enabler" doing in there?
That is hackintosh tech and isn't going to help you.
You can't shotgun this, it just has to be done right once.
And what is this about:
": kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext "/System/Library/Extensions/NVDAGM100HalWeb.kext"
Did you modify the drivers more than the guide?
No reason for that kext to have a bad signature.

Ok, I cleaned up the kexts or at least I think so. See the output below:

[j@memreas-mac-mini:AWS]$grep IOPCITunnelCompatible /var/log/system.log

[j@memreas-mac-mini:AWS]$

next I tried these statements:

[j@memreas-mbp:AWS]$grep IOPCITunnelCompatible /var/log/system.log

[j@memreas-mbp:AWS]$

[j@memreas-mbp:AWS]$sudo kextcache -system-prelinked-kernel

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext NVDAStartup.kext

kext file:///System/Library/Extensions/MotMobileUSB.kext/Contents/PlugIns/MotMobileUSBSwch.kext/ is in hash exception list, allowing to load

kext file:///System/Library/Extensions/MotMobileUSB.kext/Contents/PlugIns/MotMobileUSBLANMerge.kext/ is in hash exception list, allowing to load

kext file:///System/Library/Extensions/MotMobileUSB.kext/Contents/PlugIns/MotMobileMTP.kext/ is in hash exception list, allowing to load

kext file:///System/Library/Extensions/MotMobileUSB.kext/Contents/PlugIns/MotMobileMS.kext/ is in hash exception list, allowing to load

kext file:///System/Library/Extensions/JMicronATA.kext/ is in hash exception list, allowing to load

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOPCIFamily.kext

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IONDRVSupport.kext

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAController.kext

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDA.kext

Invalid signature -67030 for kext <OSKext 0x7fb48b409480 [0x7fff7957dcf0]> { URL = "NVDAStartup.kext/ -- file:///System/Library/Extensions/", ID = "com.nvidia.NVDAStartup" }

Note the invalid signature at the bottom but valid at the top for the NVDAStartup??

Here is the PCI data:

$grep PCI /var/log/system.log

Jan 23 20:13:20 memreas-mbp com.apple.kextcache[741]: kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOPCIFamily.kext

Jan 23 20:14:11 localhost kernel[0]: PMAP: PCID enabled

Jan 23 20:14:11 localhost kernel[0]: [ PCI configuration begin ]

Jan 23 20:14:11 localhost kernel[0]: [ PCI configuration end, bridges 16, devices 18 ]

Jan 23 20:14:11 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/M4-CT512M4SSD2 Media/IOGUIDPartitionScheme/Macintosh HD@2/CoreStoragePhysical/Macintosh HD/Macintosh HD

Still same issue. Any help is much appreciated.

Regards,

J

w4vz · January 26, 2015

So far so good for me. Actually became a video editor too over the weekend lol and currently using cuda to render with premiere 2014. 6 hours video rendering in 3 hours instead of 5 hours with the internal 650 GPU. No crash so far.

One thing is that I had to downgrade my cuda drivers in order to get it recognised by Premiere. Currently using 6.5.25 with latest web drivers.

Will continue testing until tomorrow and if everything goes well will publish a guide.

Thanks to everyone who helped me out, especially @Tech Inferno Fan this forum has been an eye opener so far.

edit: also after downgrading the cuda drivers, my computer stopped booting but reseting the Pram solved the problem

MVC · January 27, 2015

w4vz, the CUDA drivers that load automatically are no good for Maxwell (6.5.36)

But if you go right to CUDA archives, you can get 6.5.37 that DO work with 970.

w4vz · January 27, 2015

w4vz, the CUDA drivers that load automatically are no good for Maxwell (6.5.36)
But if you go right to CUDA archives, you can get 6.5.37 that DO work with 970.

Ok thanks for that. I will try them next time.

Do you know why 6.5.36 does not work but 6.5.37 does ? Seems bizarre because I had 6.5.33 that did NOT work and installed 6.5.25 and it worked. seems very confusing lol

Oscar J · January 27, 2015

Any news on AMD external GPU's on MacBooks in OS X?

Morv · January 27, 2015

News what for? They already work after modifying the responsible Kext including external screens. See http://forum.techinferno.com/implementation-guides/8585-%5Bguide%5D-2014-15-macbook-pro-2x-r9_280x%4016gbps-tb2-netstor-na211tb-win8-1-osx.html

Had a R9 280 running OS X on external screen after following his guide with a Akitio Thunder2.

Oscar J · January 27, 2015

My bad, should have mentioned that I meant a budget solution (like the Akitio Thunder2). From what I've seen there has been problems with stability with AMD cards on the Akitio? Good to see that you managed to get it working though! Did you use a powered riser?

Morv · January 27, 2015

Yes, powered riser. The card was crashing in Windows though and OS X didn't run long enough to see if it would have been stable there.

I've opened a thread regarding the instability here -> http://forum.techinferno.com/diy-e-gpu-projects/8844-targeting-akitio-thunder2-pcie-boxs-stability-issues.html

It seems like there's something happening at boot time which causes the instability later on. It doesn't seem to be caused by powered risers or power related stuff at all. Maybe it's not even the Akitio.

Oscar J · January 28, 2015

Interesting. I'll probably wait until the AMD 200 series has been tried in OS X for a longer while to ensure the Akitio + AMD combo is stable. When I'm rendering, I'll have scenes standing overnight to clear up - so 100 % load for 10+ hours.

Sgt. Pepper · January 28, 2015

Hi everybody!

First and foremost I want to thank everybody here on Techinferno, you guys made this possible to happen!

I currently am using an eGPU Setup consisting of the Akitio Thunder2Pcie Box and the OcUK(Caseking) GTX970 „reference“.

It was really painless to get this up and running, based on the things Tech Inferno Fan and goalque found out here.

I really tried to read everything which has been discussed here in the "akitio thunder2pcie thread" but i couldn't find any information on my problem.

But lets start with good things first:

I'm running this on a late 2013 13"rMBP, OSx 10.10.2 with latest nvidia web driver 343.02.02f1 driving a Dell up2414q (4k MST) Monitor.

everything works flawless so far.

But no it comes to a point where i couldn't find a solution over the last week:

1. When the egpu is connected, i have all the beautiful pixels and even all the scaled HiDPI resolutions up to 3200x1800 HiDPI, so no problem.

BUT I did not manage to get this display working at 60HZ.

2. I then found MVC's post here:

http://forums.macrumors.com/showthread.php?t=1760435

I did it just as he described and now my MacBook can drive the up2414q at native resolution 4k@60hz.

BUT my GTX 970 is no longer putting out video at all, although it is correctly recognized by OSX and performs well in e.g. OpenCL benchmarks.

And as the Intel iris is not as powerful, i can no longer use HiDPI resolutions other than 1920*1080.

The strange thing is, i was able to test this setup today with a 2011 MacbookAir and it worked exactly as it should, eGPU is detected, and works properly, giving me 4k@60hz AND resolutions up to 3200x1800 HiDPI.

Maybe someone has a good idea or already got this combination working?

Thanks a lot!

If i get this working, i’ll make an implementation guide with pictures etc.

- - - Updated - - -

Anyone tried their egpu with filevault? Tried to search the forum with no result. Anyone can share some experience?

I can confirm this works without any problems

euqlaog · January 28, 2015

Have you tried SwitchResX? It shows all the available resolutions, including HiDPI

SwitchResX - Download

Sgt. Pepper · January 28, 2015

Yes, i have, it doesn't change anything to it

i think it is not as simple as MVC described it in his tutorial when using an eGPU

what i found out using the Macbook air is that its board id is not on this "blacklist" in AppleGraphicsControl.kext.

maybe there is another location where i must add or remove the board id?

- - - Updated - - -

To be more clear:

My problem is not that intel iris doesn't support more than 1920x1080HiDPI.

I just do not understand why a intel HD4000 Macbook air with eGPU which is not certified at all by apple to drive something at 4k works so flawless but my rMBP is limited to 30 hz

I read in some forums for mackintosh, for them MVCs tutorial worked just fine with a GTX 970, but this were all internal

Do you know anything about why some cards work for accelerated graphics and some do not, i guess there has to be some kind of driver controlling the display output?

euqlaog · January 28, 2015

Haven’t look closer at MVC’s post, but my Samsung 28” UHD LED Monitor (U28D590D) enables 3840x2160@60Hz via DP. And I didn’t do any other mod than what was necessary for a Maxwell architecture GPU:

http://forum.techinferno.com/implementation-guides/8199-%5Bguide%5D-2013-13-macbook-pro-gtx980%4016gbps-tb2-netstor-na211tb-win8-1-osx10-10-a.html#post111834

You said 3200x1800 HiDPI which is not the native resolution of your monitor:

“3840 x 2160 at 60 Hz (DP1.2)

3840 x 2160 at 30 Hz HDMI”

The last option is to completely reinstall OS X. Hopefully this information helps.

Sign In

DIY eGPU Macbook experiences

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Morv

Phtoon

svl7

Posted Images

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Important Information