2017 MBP w/AMD 560, Mantiz Venus, MSI GTX1080Ti
 
Notifications
Clear all

2017 MBP w/AMD 560, Mantiz Venus, MSI GTX1080Ti  

 of  2
  RSS

hypernurd
(@hypernurd)
Trusted Member
Joined: 4 years ago
 

Hey Rastafabi,

Thanks for the response.

I ran the nvram -p command and got the following output;

SystemAudioVolume 7

boot-args nvda_drv=1

backlight-level %e4%00

HW_BOOT_DATA %01%00%00%00%05Z%00%00%004C"%06%00%00%00%00%00%00%00%00%00%00%00%00[%00%00%0068%06%07%00%00%00%00%00%00%00%00%00%00%00%00\%00%00%00FE%06%07%00%00%00%00%00%00%00%00%00%00%00%00]%00%00%00 R%17%08%00%00%00%00%00%00%00%00%00%00%00%00^%00%00%[email protected]%17%08%00%00%00%00%00%00%00%00%00%00%00%00_%00%00%00I%01%18%08%00%00%00%00%00%00%00%00%00%00%00%00V%00%00%00C%10!%06%00%00%00%00%00%00%00%00%00%00%00%00W%00%00%00E%11!%06%00%00%00%00%02%00%00%00%00%00%00%00X%00%00%00W)!%06%00%00%00%00%00%00%00%00%00%00%00%00Y%00%00%00%130!%06%00%00%00%00%00%00%00%00%00%00%00%00

gpu-policy %01

tbt-options <00>

InstallWindowsUEFI 1

bluetoothInternalControllerInfo %95%82%ac%05%00%00%00%00%8c%85%90%11%a3%8e

nvda_drv 1

prev-lang:kbd en:2

SystemAudioVolumeDB %f7

fmm-computer-name Aidan%e2%80%99s MacBook Pro

bluetoothActiveControllerInfo %95%82%ac%05%00%00%00%00%00%00%8c%85%90%11%a3%8e

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>114518CE-2466-4996-A27A-176185A38300</string></dict></dict><key>BLLastBSDName</key><string>disk2s1</string></dict></array>%00

efi-boot-device-data %03%0a,%00%1ba%99B%c9L%dfC%88+*%07%07%a4%a9_S%da%cds%f2%95%b4B%bc%87n_%0d,S[%00%f3X%b1%f8%dch%01%01%01%06%00%00%04%01%01%06%00%00%00%03%05%06%00%02%00%03%05%06%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%[email protected]%06%00%00%00%00%00%ce%18E%11f$%96I%a2z%17a%85%a3%83%00%02%02%7f%ff%04%00

csr-active-config w%00%00%00

 

LocationServicesEnabled %01

 

Seems the boot-args value is still set for the nvda_drv=1  - so this doesn't look like the issue.

I wondered about the TB3 port I was using (top left) and having rad several posts on other threads about this being quite sensitive thought I'd try another one (top right). Boom! Screens came back on a reboot. I'm back in business!

The system does appear sensitive to resolution though - no doubt due to the beta drivers. I get good performance on all HDMI (v1.4) and DisplayPort( v1.2) connected screens provided I don't go above 2560x1440. I'm running the internal retina at 2560x1600 and am not getting any strange artifacts on there either now. 

I'm going to write this up for other's benefit. 

Thanks again.

Hypernurd

 

2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

itsage liked
ReplyQuote
Rastafabi
(@rastafabi)
Trusted Member
Joined: 4 years ago
 
Posted by: hypernurd
[…]

I ran the nvram -p command and got the following output;

SystemAudioVolume 7

boot-args nvda_drv=1

[…]

Something went wrong, while you set this value (should not read the boot-args tag), though later it's included correctly. You also seem to have installed automated-eGPU-sh using the -a mode, which is redundant on newer TB2 and any TB3 Macs. Depending on the firmware it could theoretically have negative effects, so I recommend reinstalling it without the -a option. To exclude any hardware preferences to be causing your issues you might still want to reset SMC and PRAM. You would need to re-disable SIP afterward and might need to boot twice for the NVIDIA driver reenabling themselves (/manually in System Preferences).

Creator of the update-redundant macOS 10.12 eGPU enabler package for NVIDIA

AKiTiO Thunder 2 PCIe Expansion Box
NVIDIA GTX 750Ti
MacBook Pro 9.2 ••• until being stolen.
Thanks to the community for helping getting me going again.


ReplyQuote
hypernurd
(@hypernurd)
Trusted Member
Joined: 4 years ago
 

Hi Rastafabi,

Well spotted! I saw that too. OK. good idea. I'll attempt a 'clean' install. I'll remove all drivers and scripts, zap PRAM and reset SMC and then re-build.

It will be good to know what is needed and what is not as I've done a few things that by the sounds of it may have been unnecessary. To be honest, it was only when I thought about the HDMI version on my monitors that things improved and setting the displays to v1.4 (from 2.0) was what finally enabled display output. 

Hypernurd

2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
hypernurd
(@hypernurd)
Trusted Member
Joined: 4 years ago
 

Hi Rastafabi,

I did the clean install and you're 100% right

• -a argument is not needed

• two reboots and the Nvidia drivers were working perfectly

• No need to set the nvram boot-args either. See following output;

Aidans-MacBook-Pro:~ aidanbowen$ nvram -p

boot-args

HW_BOOT_DATA %01%00%00%00%05%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%01%00%00%00X%19"%08%00%00%00%00%00%00%00%00%00%00%00%00%02%00%00%00%05#"%08%00%00%00%00%00%00%00%00%00%00%00%00%03%00%00%00($"%08%00%00%00%00%00%00%00%00%00%00%00%00%04%00%00%001("%08%00%00%00%00%00%00%00%00%00%00%00%00%05%00%00%00E("%08%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00

gpu-policy %01

bluetoothInternalControllerInfo %95%82%ac%05%00%00%00%00%8c%85%90%11%a3%8e

nvda_drv 1

SystemAudioVolumeDB %00

fmm-computer-name Aidan%e2%80%99s MacBook Pro

bluetoothActiveControllerInfo %95%82%ac%05%00%00%00%00%00%00%8c%85%90%11%a3%8e

csr-active-config w%00%00%00

backlight-level %f2%00

SystemAudioVolume 7

 

LocationServicesEnabled %01

 

Top work fella!

Hypernurd

2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
Rastafabi
(@rastafabi)
Trusted Member
Joined: 4 years ago
 

Hi Hypernurd,

Let's see wether any improvements can be achieved. At least it's worth the try. What just came to my mind concerning the HDMI mode issue: Are the cables you use HDMI 2.0 approved? They could be the source of the issue, too. Well, as they work in bootcamp, they seem fine.

Rastafabi

Creator of the update-redundant macOS 10.12 eGPU enabler package for NVIDIA

AKiTiO Thunder 2 PCIe Expansion Box
NVIDIA GTX 750Ti
MacBook Pro 9.2 ••• until being stolen.
Thanks to the community for helping getting me going again.


ReplyQuote
hypernurd
(@hypernurd)
Trusted Member
Joined: 4 years ago
 

Hey Rastafabi.

I just edited my main Implementation post and removed the 'bum-steer' parts regards -a and boot-args. Have also uploaded some pics of the full physical setup and eGPU enclosure. 

Thanks for all your help!

Hypernurd

2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
Rastafabi
(@rastafabi)
Trusted Member
Joined: 4 years ago
 

I just came across a potential fix for your HDMI 2.0 issues on MacOS. While it only stats it should fix HDMI 2.0 compatibility with Maxwell cards, it does have a script for Pascal-based GPUs, too. You might want to try it out.

Creator of the update-redundant macOS 10.12 eGPU enabler package for NVIDIA

AKiTiO Thunder 2 PCIe Expansion Box
NVIDIA GTX 750Ti
MacBook Pro 9.2 ••• until being stolen.
Thanks to the community for helping getting me going again.


ReplyQuote
hypernurd
(@hypernurd)
Trusted Member
Joined: 4 years ago
 

Interesting. Thanks Rastafabi, I'll give this a go on my nMP. Seems a worthy candidate!

Hypernurd

2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
 of  2