panini Posted January 31, 2016 Share Posted January 31, 2016 Hi, First off all a big thank you for all the information on this forum but most of all for this script! I've been balancing between a hackintosh, a core i7 macbook pro and a core i7 mac mini to get my multi monitor setup going. I ultimately chose the Thunderbolt way, and invested in some TB toys. I've tested 2 setups: Mac mini (late 2012; Macmini6,2 ; Core i7 2,3 Ghz ; Yosemite 10.10.5) 15” MacBookPro9,1; (mid 2012 ; Core i7 2,3 Ghz ; Yosemite 10.10.5) Sonnet Technologies ECHO-EXP3FD Echo, containing EVGA GTX 650Ti Gigabyte G1 GeForce GTX 960 4GB Quadro NVS 450 I cannot seem to get the GTX 960 to work. After running the script, I can see 4 slots (if I'm correct) in the ECC tab of Nvidia settings. The EVGA GTX 650 Ti works a treat on both setups. I also have an elderly Quadro NVS 450, this one has 4 DisplayPort connections, and used to work fine in the hackintosh, however it's too slow and short on memory for CAD and Sketchup etc. So my question is: - What would be the way to debug the GTX 960? - I've read: Any recent nVidia card should work fine, both with an external monitor and the internal laptop screen through Optimus. [Optimus nVidia] EVGA branded nVidia cards are powered differently internally and work better for eGPU setups. Maybe coincidence, but the only card working is an EVGA card... - Ultimately: What card would you recommend buying with the highest degree of probability that it'll work? I'm considering EVGA 4GB D5 X GTX960 FTW ACX 2.0+ but worry that it is just a shot in the dark whether it will work... Thanks for your input!! Erwin Quote Link to comment Share on other sites More sharing options...
euqlaog Posted January 31, 2016 Author Share Posted January 31, 2016 36 minutes ago, panini said: So my question is: - What would be the way to debug the GTX 960? https://www.techinferno.com/index.php?/forums/topic/7989-script-automating-the-installation-of-egpu-on-os-x-inc-display-output/&page=12#comment-130567 First of all, please provide the build version of Yosemite: sw_vers -buildVersion Some of the Yosemite security updates disabled eGPU use completely on a 2014 Mac mini. Not sure about the Late 2012 Mac mini. I’ve not had any issues with Gigabyte, should work as well as EVGA. III-D is a multi-slot enclosure, please turn on -a mode and report if that helps: sudo ./automate-eGPU.sh -a and restart the Mac. Quote Link to comment Share on other sites More sharing options...
panini Posted February 2, 2016 Share Posted February 2, 2016 Hi and thanks for replying! Here are my build versions: 01-02-2016 23:10 10.10.5 (14F27) MacBook Pro 10.10.5 (14F1605) Mac mini I will test and try -a mode and report back in the next couple of days. Thx, Erwin Quote Link to comment Share on other sites More sharing options...
kblack21 Posted February 2, 2016 Share Posted February 2, 2016 Setup: Late 2013 27" iMac w/TB1 OS X Yosemite 10.10.5 (14F1605) 1000 Corsair PSU Modified AKiTiO Box powered by PSU with Barrel Plug mod Titan Z (Plugged directly into PSU) Secondary Monitor running at 2K Hey guys hate to come on like a noob (though i'll admit i'm pretty green at this), but i've had my setup for about 3 days and i've noticed a weird random Kernel Panic that doesn't happen too often (twice so far). The setup works great most of the time and doesn't seem linked to any extended time of use, so i'm not sure what causes it. If it helps right now I do have an external monitor plugged into the display port of the Titan. I don't use the egpu for gaming, it's solely for CUDA acceleration when I edit videos and animate. Will try an save the error report next time, but I think it made mention of "drv = 1" in both cases of the kernel panic. Apologize if its too vague of a description at the moment. Quote Link to comment Share on other sites More sharing options...
Dschijn Posted February 3, 2016 Share Posted February 3, 2016 Maybe an unstable cable? Thunderbolt cable or the barrel plug? Quote Link to comment Share on other sites More sharing options...
kblack21 Posted February 3, 2016 Share Posted February 3, 2016 Hmm the thunderbolt cable is a 6ft, think maybe that's causing issues? Quote Link to comment Share on other sites More sharing options...
Dschijn Posted February 3, 2016 Share Posted February 3, 2016 I am using a 2m Apple TB cable myself. Maybe your barrel plug doesn't "sit" right? Quote Link to comment Share on other sites More sharing options...
kblack21 Posted February 3, 2016 Share Posted February 3, 2016 I still think it might be the cable, I have an off brand TB cable too. Before I had the barrel plug I was using a riser and would on occasion get a similar occurrence. I'll try a switch out both though. Could you recommend a good barrel plug option, or did you create it yourself? Quote Link to comment Share on other sites More sharing options...
Dschijn Posted February 3, 2016 Share Posted February 3, 2016 36 minutes ago, kblack21 said: I still think it might be the cable, I have an off brand TB cable too. Before I had the barrel plug I was using a riser and would on occasion get a similar occurrence. I'll try a switch out both though. Could you recommend a good barrel plug option, or did you create it yourself? Let's continue here: https://www.techinferno.com/index.php?/forums/topic/6543-guide-making-a-molex-to-barrel-adapter/&page=3#comment-137372 Quote Link to comment Share on other sites More sharing options...
euqlaog Posted February 3, 2016 Author Share Posted February 3, 2016 (edited) A few days ago, when I was researching in greater depth the EFI, I found out something amazing. I had an Asus R9 270X plugged, reporting a valid GOP (AMD GOP X64 Release Rev.1.54) by the “drivers” EFI Shell command and by the “dh” command, which displays all the protocols that are associated with that device handle. So, I unplugged the TB cable, swapped for an Asus HD 7870 (non-UEFI card) which doesn’t report about the GOP by itself, replugged the TB cable, typed “dh -p graphicsoutput” and the shell printed TxtOut, GraphicsOutput, EdidDiscovered and EdidActive protocols for the HD 7870. All the display interfaces worked (HDMI, DP, DVI). They can be seen under the device tree as “DFP2_HDMI” for example. The same trick worked for my another non-UEFI AMD card as well. Intel’s UEFI Specification 2.0 says “A PCI Device Driver should not be designed to care where it is stored. It can reside in a PCI Option ROM, the system's motherboard ROM, a hard drive, a CD-ROM drive, etc. All PCI Device Drivers are compiled and linked to generate a PE/COFF image.” Sounds logical. When the driver image is loaded, it stays permanent in the memory, even if the eGPU is swapped. I also looked at a couple of Nvidia’s UEFI images. Nvidia’s UEFI section in the ROM file complies with the Intel’s recommended PCI device driver layout (has 0x0EF1 value at offset 0x04). Took out the PE/COFF part from the correct offset, decompressed it with efidecompress command successfully, and then tried load command, but the EFI Shell said “incompatible version”. I said earlier that my Nvidia cards didn’t seem to support GOP. I meant that my test app didn’t find any frame buffer. I was thinking that if I could load the Nvidia GOP driver as well, but for some reason it wasn’t compatible. No new Nvidia drivers appeared in the list of loaded EFI drivers and that explains why my EFI test app didn’t find the GOP for my Nvidia card. AMD UEFI worked out of the box. I didn’t give up. Thought maybe a Kepler card UEFI GOP would work, so did the same extract procedure for the GTX 780 ROM. Plugged in my USB stick, typed “load GTX780_dec.efi” and… Success. These tests confirm what Intel says - the UEFI driver doesn’t have to be in the GPU ROM. As we know, the eGPU boot screen is not important with TB Macs since it’s always visible through the iGPU/dGPU. However, I’m rethinking about EFI version of the automate-eGPU.sh since I found a way to bypass SIP via dmpstore in EFI environment. That would be a huge amount of work. At least, my EFI test app written in C will be available on GitHub. Edited February 3, 2016 by goalque 3 Quote Link to comment Share on other sites More sharing options...
fredelf Posted February 3, 2016 Share Posted February 3, 2016 Hi there! While I am currently having issues with desktop stuttering, the script seems to be working brilliantly and I am very grateful for it! While I did disable FileVault, I was wondering, if it is an absolute necessity to do so, or if it is simply part of the 'standard' troubleshooting procedure? Also, I will try the Disable Internal Screen script soon to see if that works. Thanks again! Quote Link to comment Share on other sites More sharing options...
nickatitfactor Posted February 4, 2016 Share Posted February 4, 2016 Has anyone had successful luck with doing 2 980 ti via thunderbolt? I have 1 980 ti hooked up via thunderbolt with Akitia thunderbolt bridge. It works pretty well. It isn't as fast as if you have it direct connect with PCI to motherboard. I am using a Mac Pro 2013. However many many thanks to Goalque and the team. had to reinstall the OS, but then the script worked like a charm. Quote Link to comment Share on other sites More sharing options...
Dschijn Posted February 4, 2016 Share Posted February 4, 2016 @nickatitfactor I had a GTX970 and a GTX980Ti daisychained in OSX and was able to use both in rendering apps. Quote Link to comment Share on other sites More sharing options...
panini Posted February 6, 2016 Share Posted February 6, 2016 (edited) On 2/2/2016 at 5:22 AM, panini said: Here are my build versions: 01-02-2016 23:10 10.10.5 (14F27) MacBook Pro 10.10.5 (14F1605) Mac mini I will test and try -a mode and report back in the next couple of days. Hi, Thanks for sticking with me. 1. Tested on 10.10.5 build 14F1605 mac mini - I took out the GTX 650 Ti - boot and run sudo ./automate-eGPU.sh -a (system reports background services enabled) - halt machine - added GTX 960 & reboot => machine boots and runs without problem <=> eGPU does not work Also NVIDIA driver manager shows 4 empty slots?? 2. Another test: - added a MSI GeForce 9400 GT card - it just works - But why does it keep reporting 4 empty slots in nvidia driver manager? - and adding a slot without a number?? What can I do to debug this situation? Thx, Erwin Edited February 6, 2016 by panini additional info Quote Link to comment Share on other sites More sharing options...
euqlaog Posted February 6, 2016 Author Share Posted February 6, 2016 1 hour ago, panini said: Hi, Thanks for sticking with me. 1. Tested on 10.10.5 build 14F1605 mac mini - I took out the GTX 650 Ti - boot and run sudo ./automate-eGPU.sh -a (system reports background services enabled) - halt machine Did you also type "sudo ./automate-eGPU.sh" before executing "sudo ./automate-eGPU.sh -a" ? Quote Link to comment Share on other sites More sharing options...
panini Posted February 6, 2016 Share Posted February 6, 2016 (edited) 44 minutes ago, goalque said: Did you also type "sudo ./automate-eGPU.sh" before executing "sudo ./automate-eGPU.sh -a" ? No I did not. That is, It has been run before on the system, but not during this uptime. So I need to run the 2 commands consecutively? Also: 1. Does the 6 pin connector of the III-D supply enough power for the 960? 2. Any other terminal commands to interrogate thunderbolt egpu? Edited February 6, 2016 by panini Quote Link to comment Share on other sites More sharing options...
euqlaog Posted February 6, 2016 Author Share Posted February 6, 2016 29 minutes ago, panini said: No I did not. That is, It has been run before on the system, but not during this uptime. So I need to run the 2 commands consecutively? Also: 1. Does the 6 pin connector of the III-D supply enough power for the 960? 2. Any other terminal commands to interrogate thunderbolt egpu? If you have executed the command without -a once, it’s enough. I’ll check how my Mac mini behaves in Yosemite. There were a lot of security updates from Apple. 1. Yes, I think so. 2. sudo ./automate-eGPU.sh -clpeak confirms that eGPU can run OpenCL. But I guess you can't do that due to the kernel panic during reboot. Quote Link to comment Share on other sites More sharing options...
panini Posted February 6, 2016 Share Posted February 6, 2016 Hi, 1. sudo ./automate-eGPU.sh -clpeak sudo ./automate-eGPU.sh -clpeak Quote Downloading clpeak % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 124 0 124 0 0 130 0 --:--:-- --:--:-- --:--:-- 204 100 137k 0 137k 0 0 72525 0 --:--:-- 0:00:01 --:--:-- 265k /Users/erwin/Desktop Downloading cl.hpp % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 292k 100 292k 0 0 227k 0 0:00:01 0:00:01 --:--:-- 227k Downloading cmake-3.3.0 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 21.3M 100 21.3M 0 0 581k 0 0:00:37 0:00:37 --:--:-- 633k /Users/erwin/Desktop -- The C compiler identification is AppleClang 7.0.2.7000181 -- The CXX compiler identification is AppleClang 7.0.2.7000181 -- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc -- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/clang++ -- Check for working CXX compiler: /usr/bin/clang++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Setting build type to Release -- Selected OpenCL includes from /System/Library/Frameworks/OpenCL.framework -- Selected OpenCL lib /System/Library/Frameworks/OpenCL.framework -- Configuring done -- Generating done -- Build files have been written to: /Library/Application Support/Automate-eGPU/clpeak Scanning dependencies of target clpeak [ 8%] Building CXX object CMakeFiles/clpeak.dir/src/common.cpp.o [ 16%] Building CXX object CMakeFiles/clpeak.dir/src/clpeak.cpp.o [ 25%] Building CXX object CMakeFiles/clpeak.dir/src/options.cpp.o [ 33%] Building CXX object CMakeFiles/clpeak.dir/src/logger.cpp.o [ 41%] Building CXX object CMakeFiles/clpeak.dir/src/global_bandwidth.cpp.o [ 50%] Building CXX object CMakeFiles/clpeak.dir/src/compute_sp.cpp.o [ 58%] Building CXX object CMakeFiles/clpeak.dir/src/compute_dp.cpp.o [ 66%] Building CXX object CMakeFiles/clpeak.dir/src/compute_integer.cpp.o [ 75%] Building CXX object CMakeFiles/clpeak.dir/src/transfer_bandwidth.cpp.o [ 83%] Building CXX object CMakeFiles/clpeak.dir/src/kernel_latency.cpp.o [ 91%] Building CXX object CMakeFiles/clpeak.dir/src/entry.cpp.o [100%] Linking CXX executable clpeak [100%] Built target clpeak Platform: Apple Device: HD Graphics 4000 Driver version : 1.2(Nov 12 2015 16:12:01) (Macintosh) Compute units : 16 Clock frequency : 1200 MHz Global memory bandwidth (GBPS) float : 15.62 float2 : 17.77 float4 : 17.07 float8 : 13.59 float16 : 7.95 Single-precision compute (GFLOPS) float : 234.60 float2 : 229.88 float4 : 209.64 float8 : 237.08 float16 : 201.60 No double precision support! Skipped Transfer bandwidth (GBPS) enqueueWriteBuffer : 4.85 enqueueReadBuffer : 5.08 enqueueMapBuffer(for read) : 482.80 memcpy from mapped ptr : 5.53 enqueueUnmap(after write) : 3334.60 memcpy to mapped ptr : 6.34 Kernel launch latency : 51.16 us Device: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz Driver version : 1.1 (Macintosh) Compute units : 8 Clock frequency : 2300 MHz Global memory bandwidth (GBPS) float : clEnqueueNDRangeKernel (-54) Tests skipped Single-precision compute (GFLOPS) float : clEnqueueNDRangeKernel (-54) Tests skipped Double-precision compute (GFLOPS) clCreateKernel (-46) Tests skipped Transfer bandwidth (GBPS) enqueueWriteBuffer : 5.91 enqueueReadBuffer : 6.03 enqueueMapBuffer(for read) : 48366.75 memcpy from mapped ptr : 7.28 enqueueUnmap(after write) : 9084.11 memcpy to mapped ptr : 7.20 Kernel launch latency : clEnqueueNDRangeKernel (-54) Tests skipped macmini2:Desktop erwin$ I notice 3 or 4 tests are skipped... What does this tell us? No kernel panic on the mini.. Thx, Erwin Quote Link to comment Share on other sites More sharing options...
panini Posted February 6, 2016 Share Posted February 6, 2016 1. sudo ./automate-eGPU.sh -clpeak And here for the 10.10.5 (14F27) MacBook Pro MBPI7-2:Desktop erwin$ sudo ./automate-eGPU.sh -clpeak Installing command line tools xcode-select: note: install requested for command line developer tools Please wait until Command Line Tools installation is complete and then press "Enter"...^[[A^[[A^[[B^[[B^[[A^[[A^[[A^[[A Downloading clpeak % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 124 0 124 0 0 148 0 --:--:-- --:--:-- --:--:-- 1087 100 137k 0 137k 0 0 64300 0 --:--:-- 0:00:02 --:--:-- 249k /Users/erwin/Desktop Downloading cl.hpp % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 292k 100 292k 0 0 205k 0 0:00:01 0:00:01 --:--:-- 205k Downloading cmake-3.3.0 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 21.3M 100 21.3M 0 0 536k 0 0:00:40 0:00:40 --:--:-- 506k /Users/erwin/Desktop -- The C compiler identification is AppleClang 7.0.2.7000181 -- The CXX compiler identification is AppleClang 7.0.2.7000181 -- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc -- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/clang++ -- Check for working CXX compiler: /usr/bin/clang++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Setting build type to Release -- Selected OpenCL includes from /System/Library/Frameworks/OpenCL.framework -- Selected OpenCL lib /System/Library/Frameworks/OpenCL.framework -- Configuring done -- Generating done -- Build files have been written to: /Library/Application Support/Automate-eGPU/clpeak Scanning dependencies of target clpeak [ 8%] Building CXX object CMakeFiles/clpeak.dir/src/common.cpp.o [ 16%] Building CXX object CMakeFiles/clpeak.dir/src/clpeak.cpp.o [ 25%] Building CXX object CMakeFiles/clpeak.dir/src/options.cpp.o [ 33%] Building CXX object CMakeFiles/clpeak.dir/src/logger.cpp.o [ 41%] Building CXX object CMakeFiles/clpeak.dir/src/global_bandwidth.cpp.o [ 50%] Building CXX object CMakeFiles/clpeak.dir/src/compute_sp.cpp.o [ 58%] Building CXX object CMakeFiles/clpeak.dir/src/compute_dp.cpp.o [ 66%] Building CXX object CMakeFiles/clpeak.dir/src/compute_integer.cpp.o [ 75%] Building CXX object CMakeFiles/clpeak.dir/src/transfer_bandwidth.cpp.o [ 83%] Building CXX object CMakeFiles/clpeak.dir/src/kernel_latency.cpp.o [ 91%] Building CXX object CMakeFiles/clpeak.dir/src/entry.cpp.o [100%] Linking CXX executable clpeak [100%] Built target clpeak Platform: Apple Device: HD Graphics 4000 Driver version : 1.2(Jul 29 2015 02:40:37) (Macintosh) Compute units : 16 Clock frequency : 1200 MHz Global memory bandwidth (GBPS) float : 16.24 float2 : 19.11 float4 : 18.26 float8 : 14.61 float16 : 8.15 Single-precision compute (GFLOPS) float : 234.75 float2 : 230.19 float4 : 210.07 float8 : 237.22 float16 : 201.75 No double precision support! Skipped Transfer bandwidth (GBPS) enqueueWriteBuffer : 6.69 enqueueReadBuffer : 6.75 enqueueMapBuffer(for read) : 906.88 memcpy from mapped ptr : 6.48 enqueueUnmap(after write) : 4407.81 memcpy to mapped ptr : 7.38 Kernel launch latency : 39.42 us Device: GeForce GT 650M Driver version : 10.5.2 346.02.03f01 (Macintosh) Compute units : 2 Clock frequency : 774 MHz Global memory bandwidth (GBPS) float : 19.52 float2 : 20.33 float4 : 42.34 float8 : 23.73 float16 : 19.32 Single-precision compute (GFLOPS) float : 386.89 float2 : 511.23 float4 : 514.50 float8 : 497.45 float16 : 465.10 Double-precision compute (GFLOPS) clCreateKernel (-46) Tests skipped Transfer bandwidth (GBPS) enqueueWriteBuffer : 8.63 enqueueReadBuffer : 8.55 enqueueMapBuffer(for read) : 8134.41 memcpy from mapped ptr : 8.25 enqueueUnmap(after write) : 1997.29 memcpy to mapped ptr : 8.45 Kernel launch latency : 44.16 us Device: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz Driver version : 1.1 (Macintosh) Compute units : 8 Clock frequency : 2300 MHz Global memory bandwidth (GBPS) float : clEnqueueNDRangeKernel (-63) Tests skipped Single-precision compute (GFLOPS) clCreateBuffer (-61) Tests skipped Double-precision compute (GFLOPS) clCreateBuffer (-61) Tests skipped Transfer bandwidth (GBPS) enqueueWriteBuffer : 0.00 enqueueReadBuffer : 0.00 enqueueMapBuffer(for read) : 0.00 memcpy from mapped ptr : inf enqueueUnmap(after write) : 0.00 memcpy to mapped ptr : inf Kernel launch latency : clEnqueueNDRangeKernel (-54) Tests skipped MBPI7-2:Desktop erwin$ Results: - no kernel panic - Why are tests skipped?? Quote Link to comment Share on other sites More sharing options...
euqlaog Posted February 6, 2016 Author Share Posted February 6, 2016 @panini You have to ask the creator of the clpeak why some tests are skipped. The eGPU should be there and it is not. Something is wrong. I’m writing this from my 2014 Mac mini. I reinstalled OS X Yosemite, ran the script, turned on automatic mode, restarted and no issues with detecting a Maxwell eGPU. The script prompted about OS X update (14F1605), clicked OK and enter on terminal, restarted the Mac and everything was ok. You should have the following structure under /Library/Application Support/Automate-eGPU/ - Do you have FileVault turned off? - Can you try another Maxwell architecture GPU? Please try these commands: https://www.techinferno.com/index.php?/forums/topic/7989-script-automating-the-installation-of-egpu-on-os-x-inc-display-output/&page=12#comment-130567 Quote Link to comment Share on other sites More sharing options...
fredelf Posted February 6, 2016 Share Posted February 6, 2016 6 minutes ago, goalque said: - Do you have FileVault turned off? Is this for debugging only, or will I never be able to have FileVault enabled while using an eGPU @goalque? Quote Link to comment Share on other sites More sharing options...
euqlaog Posted February 6, 2016 Author Share Posted February 6, 2016 36 minutes ago, fredelf said: Is this for debugging only, or will I never be able to have FileVault enabled while using an eGPU @goalque? I've never tested when it's turned on so cannot say about it. Quote Link to comment Share on other sites More sharing options...
panini Posted February 6, 2016 Share Posted February 6, 2016 (edited) 3 hours ago, goalque said: You should have the following structure under /Library/Application Support/Automate-eGPU/ - Do you have FileVault turned off? - Can you try another Maxwell architecture GPU? Thank you for going through all this trouble to help me! Much appreciated!! - file structure resembles yours, but I don't have 346.02.03f05 (I checked both MBP and Mini) - FileVault: I have never used it, it is off - Try another Maxwell architecture GPU - unfortunately the GTX 960 is the only one I have right now, that was why I was looking at the EVGA.. => I was also checking this thread and compared with my systems and it struck me that NVDAStartup is not loaded... see screenshot below. Also the last modified date seems odd? - For the commands you asked: Quote MBPI7-2:Extensions erwin$ syslog -B -F '$Time $(Sender): $Message' | grep NVDA Feb 6 19:45:58 kernel: NVDAStartup: Web Feb 6 19:45:58 kernel: NVDAGK100HAL loaded and registered Quote MBPI7-2:Extensions erwin$ kextstat -l |grep NVDA 118 2 0xffffff7f81006000 0x2d8000 0x2d8000 com.nvidia.web.NVDAResmanWeb (10.0.5) <94 88 85 12 7 5 4 3 1> 132 0 0xffffff7f814ff000 0x1af000 0x1af000 com.nvidia.web.NVDAGK100HalWeb (10.0.5) <118 12 4 3> MBPI7-2:Extensions erwin$ Edited February 6, 2016 by panini Quote Link to comment Share on other sites More sharing options...
euqlaog Posted February 7, 2016 Author Share Posted February 7, 2016 @panini You have messed up your system if you are running build 14F1605 on Mac mini and there is no driver 346.02.03f05 for NVDAStartup. Reinstall OS X. Never install/update Nvidia web drivers manually. Let the script download the correct driver. On OS X Yosemite, the NVDAStartup stays loaded just a moment after restart so run kextstat command immediately. It’s normal that it vanishes away from the kextstat list and shows Loaded: No. Quote Link to comment Share on other sites More sharing options...
panini Posted February 7, 2016 Share Posted February 7, 2016 (edited) @goalque Thanks for helping and pointing out. I have a kept copy of OS X Yosemite Installer on my synology nas, but when I try to put it back to /Applications and try to create a new usb Yosemite installer I get following error: sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install OS X Yosemite.app --nointeraction Password: /Applications/Install does not appear to be a valid OS installer application. When I just click on the app, the familiar install window appears. I seem to remember one day I had the same trouble due to some changes in rights to the installer file. Unfortunately it is not available for download anymore in the App store. Do you know of a way to get a clean copy of the yosemite installer? Or check / correct the access rigths? Answer: Look in the purchased tab in App Store. Thx ;-) Edited February 7, 2016 by panini Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.