Jump to content

MacPro6,1 + Dual Display (NVIDIA) connected = Reboot loop


gxsolace
 Share

5 posts in this topic

Recommended Posts

Specs:

Clover.
Yosemite 10.10.2 with latest NVIDIA drivers.

GTX 980.

MacPro6,1 system definition:

One display connected = OK
- After booted, connect 2nd display = OK
Two displays connected at boot = reboots instantly at UI load

MacPro5,1 system definition:
All OK

Anyone have any ideas?

Thanks / gx

Link to comment
Share on other sites

  • 8 months later...

Hi there

 

Try this,in Clover Bootloader/DSDT select or untick those FixDisplay,FixLAN,FixUSB and try again to boot,have same issue with running two different GPU(TitanX and GTX780) and after that I untick those DSDT fixes I can boot and I can use both monitors,although I'm running my displays from TitanX

 

Hope this helps

 

Thanks,Jura

Link to comment
Share on other sites

Thanks jura_11 for the information. Will try this although I suspect the only fix needed is FixDisplay.

I also confirm that changing SMBIOS to iMac 14.2 fixes reboot loop with two displays connected.

 

Hi there

 

I've used above DSDT fixes,you can try to use only one and you will see how it goes,in my case I'm using SMBIOS MacPr6,1 

 

And please check this too

 

 

 

Fix: modify the AppleGraphicsDevicePolicy.kext 

 

 

  1. Open Terminal
  2. Enter this command (it is one line)

    sudo nano /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/Info.plist

     

  3. Arrow down to where you see <key>ConfigMap</key>
  4. For the iMac15,1 locate the board-id "Mac-42FD25EABCABB274" and change string below it from "Config2" to "none". For the MacPro6,1 you will do the same thing but for the board-id "Mac-F60DEB81FF30ACF6". For the iMac17,1 you'll have to see which board-id is declared in your config.plist SMBIOS: "Mac-B809C3757DA9BB8D" or "Mac-65CE76090165799A" or "Mac-DB15BD556843C820" and change the appropriate entry to "none".
  5. Save the file by pressing Ctrl+O, then enter.
  6. Exit by pressing Ctrl+X
  7. Rebuild the kernel cache using the following two commands in terminal:

    sudo kextcache -system-prelinked-kernel

    sudo kextcache -system-caches

     

     

  8. Reboot

Hope this helps there

 

Thanks,Jura

Link to comment
Share on other sites

 Share

×
×
  • Create New...