Jump to content

ibanez_bass

Registered User
  • Posts

    11
  • Joined

  • Last visited

Everything posted by ibanez_bass

  1. Disable Test Signing will turn off the DSDT override. You can try this command in combination with disabling test signing: "bcdedit /set PCIEXPRESS forcedisable" Using that command resolved some boot issues I was having with my eGPU, but I have not tried it without the DSDT override.
  2. Yes. Easy Fix: Disable the audio device before shutdown. Plug in eGPU. Re-enable after boot. Here's how I fixed it. Download devcon.exe in the Windows Driver Kit. Create 2 scripts using the command below: @echo off "C:\Program Files (x86)\Windows Kits\10\Tools\x64\devcon.exe" (put enable or disable here) HDAUDIO\FUNC_01&VEN_1013&DEV_8409&SUBSYS_106B3600&REV_1001 (This part for Pro version of Windows only) Place these batch files in C:\Windows\System32\GroupPolicy\Machine\Scripts\Startup and C:\Windows\System32\GroupPolicy\Machine\Scripts\Shutdown. Run gpedit.msc and go to Computer Configuration->Windows Settings->Scripts and activate the corresponding startup and shutdown script. If you do not have Pro, you'll have to use task scheduler to coordinate an event on startup and shutdown. Enjoy!
  3. Use MaciASL in MacOS to extract, edit, and compile. Should work without issue. I was seeing the same syntax errors using iASL for Windows. On another note, has anyone with the 13" TB noticed massive FPS drops across all games when using an EGPU? Seems that it will randomly do it after I've been playing for a while. But only sometimes. I'm also having issues with automatic allocation to large memory space. Seems if I boot with ANY USB devices connected, the iGPU will fail to even load, which results in no functional internal screen. If you open device manager, the only GPU will be the external one, like the internal isn't even detected. I'm considering using the eGPU 1.31 tool to force allocation into large memory. Comparing to my mid-2014 MBP 15" w/ dGPU, the 2016 is superior in the fact that it never fails to POST. However, I didn't really have any resource allocation issues with the 2014, so it's a tie. The best part of the 2016 is being able to use Optimus without jacking with the EFI and NVRAM for 20 minutes to disable the dGPU and enable the iGPU on the 2014.
  4. Has anyone recompiled the DSDT for the 13" with touchbar? If so, how did you resolve the error with the unexpected if towards the end. Edit: Nevermind. Rebooted into macOS, used MacIASL without any issues.
  5. My chassis is only TB2. The values should be identical between the MBP and the XPS 15 unless something on the MBP is leaching PCIe throughput. I should be getting 16Gbps on both.
  6. Has anyone ran the CUDA Concurrent Bandwidth Test on their NVidia GPU (in Windows)? Strangest thing, my 2014 MBPr 15" w/ 750m gets around 850 MB/s throughput from Device to Host and vice versa with a combined of approximately 1300 MB/s. Not bad, that's around 10 Gbps combined, which is about 2/3 of what I would expect. So I ran it again, this time with the eGPU connected to my Dell XPS 13 9350 with a Thunderbolt 3 to Thunderbolt 2 adapter. This time, I got around 1300 MB/s DtoH and HtoD, and about 1800 MB/s combined, which brings it to around 14-15 Gbps combined. That's 50% more bandwidth in host to device and ~30% more bandwidth in combined. It makes a difference for sure. Can someone else run the Concurrent Bandwidth Test on their GPU and report back results? I'm wondering if my MBP is negotiating to 10 Gbps in Windows for some reason.
  7. I am closing in on finishing my first eGPU project, so I thought I would share it. I'm currently waiting on my super low profile PCIe adapter to come in so I can put the case on. I put a Zotac 1060 Mini in it and it fits perfectly. I've hooked this to my MBPr 15" w/ 750m and have not had too many issues getting it working. Basically just run the integrated graphics bat, disable 750m, reboot, hook up eGPU at bootloader, hibernate, boot again. Hibernation is to eliminate the 20% processor usage by the Intel Graphics driver. Comments are above images... It's also scratched up from where I had it while drilling through it, but all that will be hidden by the case and/or touched up. On the front, I drilled a 5/8" hole to put this latching button w/ LED through. The hole is through the front cover and the front case. This latching button is connected to the remote pin on the Dell DA-2 and ground. LED power is provided by the Thunder2 board. Here's my Zotac in use. The two female connectors you see are reserved for a case fan should I ever desire to use one. The 6 pins for PCIe power are soldered to the 6 +12v and Ground pins of the DA-2 and then wrapped in heat shrink tube. The black braided wire that is soldered in with these 6 is the power feed back to the Thunder2 barrel. The one piece of heat shrink tube that is sticking up is the single unused pin for the DA-2 PSU. It's listed as "sense", but I kept it incase I ever needed it for some reason. If you look closely, you can see where I trimmed out an L shape from the metal bracket of the GPU so the 10 cables could fit through the back of the chassis. Here you can see where I drilled a large hole in the bottom of the case to bring the 8 pin in and the barrel back out. The barrel is just looped around back into the Thunder2. And finally, here is the outside case that I drilled through with an 88mm hole saw. Now I just need to touch up those scratches.
  8. @jowos Just an FYI, I've managed to get my Thunder2 working on my XPS 9350 using the StarTech TB3TB adapter. I have had some issues here and there, mostly screen flickering issues and one BSOD, but Optimus seems to be working nicely. I played Crysis 3 on High settings at 1/2 native (3200x1800 = 1600x900) on the internal screen without issues. I have a 9550 that I can use for testing, so I'll see if it has to do with the 960M.
  9. It looks like you got it working, but I will go ahead and elaborate. I'm using Windows 10 EFI/GPT. I have the OS X Spoofing turned on in rEFInd (I still want to call it rEFIt from back in the day). As for knowing the first Thunder2 was bad... I took a chance and bought another. I was getting lockups at the boot loader just like you with the first one, now I can boot with it plugged in to my MBP. Oddly enough, my XPS 13 will still not let me boot with it plugged in... I have to wait for the screen to light up. As for the mirroring/optimus, Does the display setting show [1|2] in the Windows settings? Check the nVidia control panel as well. Today, I realized that my MBP would not display any output on DisplayPort but HDMI worked fine. On my iMac, DisplayPort worked fine. So, you might try different ports as well. Do note that I observed a significant performance decrease using optimus. With a +200/+250 overclock, non-optimus FireStrike was 11500 on the Graphics (not bad considering I saw a 980 non-egpu with a score just over 12K). With optimus, the score dropped down below 10000. That equated to non-optimus Heaven 4.0 ~53 fps and optimus ~42-45 fps (can't remember exactly off the top of my head) at Custom Extreme 1080p, 8x MSAA, Extreme Tesselation.
  10. I was having very similar issues to you. No boot when thunderbolt was connected, GPU wasn't detected most of the time, all kinds of issues. Sadly it turned out to be the Thunder2 itself, which I could not return because I had already modified the chassis. So I had to order another one, which I will be keeping the unmodified chassis in a closet just in case. But all is good now. I have the same 750m/Iris Pro 5200/GTX 1060 setup. Just make sure you run GPU switch integrated, disable the 750m, and reboot. Connect the thunderbolt cable at the boot loader.
  11. I bought that same card! Mine won't be in until Tuesday. In the meantime, I got my Akitio Thunder case in early, so I was testing out an old 740, but I haven't gotten it to work yet. Attempting to boot with it on results in no boot from all of my TB devices. I tried a 2014 15" MBP, 2015 iMac 27", XPS 13 9350, and a 13" 2011 MBP without any luck. Also tried to turn on after boot, but that just locks up the EFI. The card is acting weird as well. If the fans don't spin up to a medium speed, it won't get detected. Once it gets into the state where the fans only spin to low, I have to unplug it from the board and wait. The best I've gotten so far is the GPU to show up when hotplugged. No luck on boot. Hopefully my 1060 does better!
×
×
  • 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.