2016 MacBook pro 15" Radeon Pro 455 - DEVILBOX
Hey everyone! I just received my DevilBox today! Here is the run down so far...
2016 MacBook pro 15" Radeon Pro 455, 512 GB SSD
Devil Box, GTX 780(for now)
I booted with it plugged in, it installed drivers for NVidia card, I downloaded the most up to date drivers and installed them. It uninstalled the older drivers. Done.
No error 12, nothing!
Works perfectly, was playing 4k 45ish FPS high in Arma 3. On my MacBook I could push internal screen, on low 20ishFPS. HUGE Difference. Now these numbers might not be exact, but I know it's working!
I booted up with it plugged and unplugged, tried to run automate eGPU
It said Thunderbolt device connected. No eGPU detected.
I am at a loss here on this one...
Are there any huge differences between the devil box and the akitio thunder 3 (as in ones ability to dodge the error 12). I've got a late 2016 mbp 15" with maxed out gpu and Radeon 460, and I've got the dreaded error 12 that I can't seem to fix.
Not sure what "causes" Device Manager's Code 12 error either.
I was getting Code 12 with my Devil Box on my 2016 MacBook Pro 13" (non-TouchBar), but that was before I updated to the new "unofficial" firmware circulating on Reddit.
After updating, I no longer see Code 12 without DSDT override, but as detailed in my thread, it's giving me quirky behavior now. If someone could enlighten us on the origins of Code 12, that'd be pretty sweet.
Hey mike, if you remember we had a nice discussion on Reddit earlier! Now if I could only figure out why macOS is wont detect the GPU, even though it sees the devil box...
That's why I'm here 😋 I was told in my thread by a few others familiar with automate-eGPU.sh that the Devil Box firmware needs to be updated before the GPU is detected in macOS. I cannot confirm this though, since my only GPU is the EVGA GTX 1080 Hybrid I'm using.
I was looking earlier, and under About This Mac > System Report... > Thunderbolt > DEVIL BOX, it displays "23.1", which is very odd because it said 23.1 before I applied the update in BootCamp.
I'm thinking that maybe the macOS System Report doesn't reflect what the update changed inBootCamp?
Another user in my thread reported that the firmware update did not change the reported firmware version under macOS System Report. See here.
Well shoot. I applied the firmware patch and now windows won't boot. It hangs with the little loading thing. Any idea how to get past it?
Edit: Got to to post by inserting thunderbolt 3 in right after windows logo shows... any ideas how to turn this back to the original firmware?