Jump to content

Shez

Registered User
  • Posts

    23
  • Joined

  • Last visited

Posts posted by Shez

  1. No issue up to now, everything is stable, easy and cheap setup. However, Nvidia Optimus isn't working with latest Nvidia drivers.

     

    Hardware:

     - Mac mini Late 2012 (MD387LL/A) / Macbook Pro Retina Late 2013 (ME293LL/A)

     - Akitio Thunder2

     - Zotac GTX1050Ti

     - Samsung T3 Portable SSD - 250GB (for Windows To Go)

     - DC 12V/12.5A from Aliexpress

     

    Setup:

     - Install Windows 10 as Windows To Go with Rufus;

     - Install Bootcamp;

     - Reboot to Windows with Akitio connected and install latest Nvidia Driver;

     

    System Start:

     - Connect External SSD with Windows To Go to your Mac;

     - Power up and hold down ALT keyboard;

     - Connect Akitio and wait 2-4 minutes;

     - Choose Windows from boot menu;

     

    sorry guys, I can't attach files here, every times it gives me an error. I uploaded images and benchmarks to my google drive here

  2. On 12/28/2016 at 10:16 AM, Gaximus said:

    I'm trying to do the same set up. Are you able to use it in macOS? 

    Also did you mean >100W?

     

    I will try it with macOS tomorrow. I'm using this DC from aliexpress, working stable for hours at max load. 

    There is only one problem, optimus is not working (on Windows), since gtx1050 not yet supported to be used as eGPU officially by nvidia drivers.

  3. Yep, my system is currently very bugy. Loot of issue is going on and at least 1 or 2 dead screen message appear during 1-3 days usage. Unfortunately, I don't have much time to reinstall it :0

    It was the same issue after manually eGPU software setup, when I checked system_profiler SPDisplaysDataType, but currently, everything is fine :)

  4. I uninstalled your script and installed manually. Same result, looks like it some kind of system security (or maybe limitation)? I need test it on Macbook Pro. Point is that, on HD5000 and higher you don't notice any lag like on HD3000-4000 with 1440p resolution)

    I also noticed that most games (especially that ported with Feral Interactive) on OS X use only iGPU, even if monitor connected to eGPU.

    Upd. Looks like you are right. System use both gpu when it need it. But it start using the second one (eGPU) not right away, that's why it lags a little at the beginning on the Mission Control start. But works then very smooth, when without eGPU, Mission Control always lags.

    Thanks for the help :)

  5. Graphic processing from eGPU switch back to HD4000. It's not going to sleep, just switching in background gpu to default as processing unit, even if the monitors connected to eGPU.

    OS X is not switching to eGPU when it's offline, because I feel when the Mission Control works with 120 fps and 15-25 fps.

    Just starting my mac mini and it's showing that:

    post-32580-14495000733746_thumb.png

    after 5 minutes without running any apps:

    post-32580-14495000734019_thumb.png

    Mission Control:

    post-32580-14495000734293_thumb.png

    system_profiler SPDisplaysDataType:

    post-32580-1449500073462_thumb.png

    ---

    OS X 10.10.5

  6. Hi, I have a problem with Mission Control performance on my mac mini 2012 with Intel HD 4000, when I connecting two or more 1440p monitor. Even if I connect all of them to eGPU (GTX 960), after system start +10 minutes, system anyway switch all of them to Intel HD 4000, it shows below the About This Mac -> Displays. The graphic processing work thru HD4000. Is it possible to make that system use force eGPU on OS X? Anyone have same problem?

  7. @Shez: Was the eGPU switched on during the installation? Or was it turned off, installed everything and rebooted with eGPU?

    Fully off and not connected, rebooted with eGPU after installation.

    - Are you sure that you didn’t have your own “expanded.pkg” on your desktop before running the script? I should add check or force delete if there exists such a file.

    Yes I'm sure.

    - Did you run the script with sudo?

    Without sudo, looks like I missed sudo word being so exciting from this script

    I think you should add force permission check before start the script, if possible. And if someone is already installed Web driver but want only activate eGPU screen output, your script doesn't allow that at that state of version of course ;)

    • Thumbs Up 1
  8. Which is the best in term of quality? When I plugged my Apple Thunderbolt cable to Mac mini 2012 (Thunderbolt 1), after a minutes it heated up to 50-60 Celsius degree. Doesn't matter which side I connect, only the mac mini side got to hot. Original AKiTiO thunderbolt cable always stay cold, even under GPU stress test.

    I can buy it from US then send it to Uzbekistan. Thanks for the recommendation, maybe someone tested OWC cable? Is it going to hot?

  9. Hi, everyone, just want to say thanks for every forum member.

    Finally, I made it! Mac Mini 2012 + Evga GTX 960 on OS X 10.10.2 and Windows 8.1 EFI working flawless smooth, except GPU's coil whine noise on max load..

    From my experience here some advices:

    1. Advice for OS X, do not download latest Nvidia Web Driver. Download only the driver that specific for your OS X BUILT. Different mac can have a different OS X built version even if the OS X version number is the same. Do not download already patched web drivers for Hackintosh, it won't work. Links for web drivers for a specific built can be found here: Nvidia Web Driver updates for Yosemite - New Releases and Updates - InsanelyMac Forum

    2. Windows advice for mac mini users. If you have a force loop reboot problem, try this:

    1) Boot your Windows normally with monitor attached, make sure that Windows selected as default boot drive on Bootcamp config. Shut Down. Remove monitor from your mac.

    2) Connect your eGPU, turn on eGPU, turn on mac. After how Windows fully load, attach your monitor to your eGPU.

    +) Make sure that your Windows is installed on EFI mode, best way to do that described here: Gadget Unit | [Tutorial] Install Windows 8 on a Mac via native EFI

    3. Try to avoid powered risers. They could not properly power your AKiTiO. To make sure that your AKiTiO is properly powered, go to Apple logo -> About This Mac -> System Report -> Thunderbolt, if you don't see here AKiTiO then your power riser isn't powered your AKiTiO as it should.

    Some power risers could be defected from the box. And they could burn your GPU if your PSU don't have Circuit protection. For example, my Sintech Riser was defected. Use Barrel to Molex instead riser power.

    post-32580-1449499981757_thumb.jpg

    My eGPU built photos with the Silverstone SG05 case:

    post-32580-1449499981866_thumb.jpg

    OS X Screenshots:

    post-32580-14494999820264_thumb.jpg

    3dmark results screencaps in spoiler

    3dmark13-FS.gpu=7144

     

     

    post-32580-14494999821069_thumb.jpg

     

    post-32580-14494999816831_thumb.jpg

    post-32580-14494999817197_thumb.jpg

    post-32580-14494999817917_thumb.jpg

    post-32580-14494999818276_thumb.jpg

    post-32580-14494999819021_thumb.jpg

    post-32580-1449499981937_thumb.jpg

    post-32580-14494999819718_thumb.jpg

    post-32580-14494999820009_thumb.jpg

    post-32580-14494999820434_thumb.jpg

    post-32580-14494999820694_thumb.jpg

     

     

    more photos available on my Google Drive 

    • Thumbs Up 4
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.