Black Screen on Mountain Lion with Nvidia GTX285 solved.

jhrfc · August 9, 2012

Ever since Mountain Lion DP2 my mac which has been working from lepoard through to lion using injection via graphics enabler, boots into a black screen under mountain lion.

i've spent a LOT of time but have now fixed it, so thought i'd share.

The black screen happened whether or not i set graphics enabler to yes (i have used various ML compatible boot loaders up to the latest r2030).

So i booted into single user mode, and enabled ssh login then rebooted. at least i could now login to see what was going on.

i dumped the currently injected properties both with and without graphicsenabler. As expected they where different.

I also dumped the currently injected properties from my working Lion drive.

I compared this with the injected propeties under ML with graphics enabler= yes.

There where some differences in the plists below, but the important thing is when i setgraphics enabler=no and injected the Lion properties into mountian lion using device-properties. bingo it worked, full graphics performance.

So i guess the newer bootloaders aren't injecting properly at least for my GTX285. who/where should i log this to help get it fixed?

Cheers

Jon

diff below :

TReport.html

verdant · August 10, 2012

@ jhrfc

I agree that being able to use GraphicsEnabler=Yes in org.chameleon.Boot.plist for the same graphics card in different OS X versions is not a given. For example, with my Inno3D GeForce 9800GT 512MB graphics card, to get full CI/QE and changeable resolutions, I can use GraphicsEnabler=Yes for Snow Leopard, but for Lion I used GraphicsEnabler=No and NVEnabler64, while in Mountain Lion, like you, I am having to use GraphicsEnabler=No and a <key>device-properties</key> custom hex entry in org.chameleon.Boot.plist, that I generated in Snow Leopard using OSX86 Tools.......

bigpoppa206 · August 10, 2012

Those of us still using the 8800GT 512mb have discovered this too. Having used injection, enablers and/or full blown DSDT editing tailored to our particular cards, I had to rip all of that out in order for my graphics to come back with Mountain Lion. Now it works with just GraphicsEnabler=Yes and the latest Chameleon.

TimeWalker75a · August 10, 2012

Just telling you a lil secret here .... if you had display_type set as NVDA,GeForche - therapy your problem. Has to be NVDA,Parent. I have no idea where the hell people got that wrong property ... I have been using Parent for my G92 based card since drivers appeared in 10.5.1 and never had problems ... people just use random ass {censored} found on the internet with no knowledge. Look at macpro device properties for a 8800gt ..

Peter_sm · August 10, 2012

Where do you set NVDA,Parent? DSDT ?

//Peter

verdant · August 10, 2012

@ Peter_sm

You can set it in your EFI graphics string; here is the .plist version of the hexadecimal version of an example EFI graphics string, showing the device_type entry location:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>

<dict>

<key>@0,compatible</key>

<string>NVDA,NVMac</string>

<key>@0,device_type</key>

<string>display</string>

<string>NVDA,Display-A</string>

<key>NVCAP</key>

<data>BAAAAAAADwAMAAAAAAAABwAAAAA=</data>

<key>VRAM,totalsize</key>

<data>AAAAOA==</data>

<key>device_type</key>

<string>NVDA,GeForce</string>

<key>model</key>

<string>GeForce</string>

<key>rom-revision</key>

</dict>

<dict>

<plist>

Changing NVDA,GeForce to NVDA,Parent may not work for all graphics cards in all situations, it can depend on the graphics card and number of connected displays too.......

For example, it has been posted that a GTX 295 single-PCB graphics card requires the device-type entry to be set to NVDA,GeForce for the first GPU (0x0,0x0) and NVDA,Parent for the 2nd GPU (0x2,0x0), whereas a GTX 295 dual-PCB graphics card may require the device_type entry for both GPUs to be set to NVDA,Parent....a GTX 295 dual-PCB graphics card user could confirm or otherwise......

Peter_sm · August 10, 2012

Hi , I have extracted my from Lizzard , perhaps that is wrong way, what is the best way to ge ta plist ? see my file below (chameleon-devprop.plist)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PciRoot(0x0)/Pci(0x1c,0x1)/Pci(0x0,0x0)</key>
<dict>
 <key>built-in</key>
 <string>0x01</string>
</dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
<dict>
 <key>@0,AAPL,boot-display</key>
 <string>0x00000001</string>
 <key>@0,built-in</key>
 <string>0x01</string>
 <key>@0,compatible</key>
 <data>
 TlZEQSxOVk1hYwA=
 </data>
 <key>@0,device_type</key>
 <data>
 ZGlzcGxheQA=
 </data>
 <key>@0,display-cfg</key>
 <string>0x00030103</string>
 <key>@0,name</key>
 <data>
 TlZEQSxEaXNwbGF5LUEA
 </data>
 <key>@1,compatible</key>
 <data>
 TlZEQSxOVk1hYwA=
 </data>
 <key>@1,connector-type</key>
 <string>0x00000800</string>
 <key>@1,device_type</key>
 <data>
 ZGlzcGxheQA=
 </data>
 <key>@1,display-cfg</key>
 <string>0x0100ffff</string>
 <key>@1,name</key>
 <data>
 TlZEQSxEaXNwbGF5LUIA
 </data>
 <key>AAPL,slot-name</key>
 <string>Slot-1</string>
 <key>NVCAP</key>
 <data>
 BAAAAAAAAQD+AAAAAAAACgAAAAA=
 </data>
 <key>NVPM</key>
 <data>
 AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
 </data>
 <key>VRAM,totalsize</key>
 <string>0x40000000</string>
 <key>device_type</key>
 <data>
 TlZEQSxQYXJlbnQA
 </data>
 <key>model</key>
 <data>
 SFAgR2VGb3JjZSBHVCAyMzAA
 </data>
 <key>rom-revision</key>
 <data>
 NzAuMTYuMjUuMDEuMDIA
 </data>
</dict>
</dict>
</plist>

verdant · August 10, 2012

@ Peter_Sm

I generally use the OSx86Tools Custom Graphics device option for convenience.......

But it can also be done via Terminal using gfxutil v0.71b......gfxutil.zip

EFIStudio has a wide range of graphics cards listed too (although not the latest)......EFIStudio_GTX.zip

BTW EFIStudio and OSx86Tools and Lizzard use gfxutil v0.71b.

A typical graphics .plist file should look like:

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”>
<plist version=”1.0″>
<dict>
<key>PciRoot(0×1)/Pci(0×1,0×0)/Pci(0×0,0×0)</key>
<dict>
<key>@[attachment=112406:OSX86Tools_1.0.150.zip]0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>
<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>NVCAP</key>
<data>BAAAAAAAAwAEAAAAAAAABwAAAAA=</data>
<key>NVPM</key>
<data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data>
<key>VRAM,totalsize</key>
<string>0×20000000</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>nVidia Geforce 8600GT</string>
<key>name</key>
<string>display</string>
<key>rom-revision</key>
<string>nVidia Geforce 8600GT OpenGL Engine</string>
</dict>
</dict>
</plist>

OSX86Tools_1.0.150.zip

TimeWalker75a · August 10, 2012

My post regarding NVDA, Parent was addressed to the person who had mentioned 8800gt. Afaik there were no dualgpu cards of this model.

verdant · August 10, 2012

My post regarding NVDA, Parent was addressed to the person who had mentioned 8800gt. Afaik there were no dualgpu cards of this model.

@ TimeWalker75

Apologies if you thought I was contradicting your post. I was not; I was replying to Peter_sm who has a GeForce GT230M and just wanted to ensure that he was aware that what works for the 8800GT may not necessarily work for all graphics cards, including his.......

Peter_sm · August 10, 2012

I have tried almost every solution , but no luck to get my 230M to work in ML, but using the NV* kext from DP it's works OK

ErOSx86 · September 10, 2012

I too am (un)fortunate to have the Dual PCB GTX 295. When Lion first came out I managed to get it working using nvenable.... once i updated 10.7.0 to 10.7.x it stopped working.

To get the ML installer to boot, i had to load the DP kexts and that works enough for the installer and can get me into the OS afterwards with no acceleration...

I am currently giving 10.8 a shot hoping that the new drivers etc might give me something. Unfortunately nothing. I am getting the infamous black screen on loading the Gui. Tried GE=yes, efi string, and an enabler but nothing appears to work thus far.

I am also on an nForce motherboard, though that shouldn't cause issues, it does make things a bit more complicated iv found.

Would love a solution to this or a way forward.

verdant · September 10, 2012

@ ErOSx86

Have you tried the nVidia GeForce driver for OS X 10.7.4 and CUDA 5.0 for OS X......?

Gringo Vermelho · September 10, 2012

10.7.4 nvidia drivers on 10.8 is probably not going to end well!

verdant · September 10, 2012

@ Gringo Vermelho

I understood ErOSx86's statements "When Lion first came out I managed to get it working using nvenable.... once i updated 10.7.0 to 10.7.x it stopped working." and "I am currently giving 10.8 a shot hoping that the new drivers etc might give me something." to be saying that he would initially be happy to get OS X Lion working......?

Gringo Vermelho · September 11, 2012

Can't argue with that..If he's happy with Lion he should definitely try the May nvidia drivers.

ErOSx86 · September 11, 2012

Thanks for the input guys, sorry that i missed this post while i updated others.

My issue was mainly that in 10.7.0 and 10.7.1 the only way I could get my GPU to work was with nvenable.kext. so far so good.

When updating to 10.7.2 my system got wiped out and due to my own ineptness i was unable to bring the system back even in safemode to re-organise the kexts and make changes... (single user mode was alien to me back then also)

However I have since managed to take my system from 10.7.0 with no graphics kexts working, up to 10.7.3.

Once I did this I installed the official nvidia drivers for 10.7.3 as downloadable on the nvidia website.

I then found much to my JOY that my GTX 295 works using the Graphics enable=yes option in chameleon... by works I mean that when the screen turns black, it is because the driver is switching to the HDMI output rather than either of the two DVI outputs... so my statement about the system not working is only partially true, as I was an idiot and didnt check the HDMI output *facepalm*

So pleased to inform that the GTX 295 (at least one of the two GPUs) works with little more than a combi update some nvidia drivers and Graphics Enable=yes, for more information mine is an XFX nVidia Geforce GTX296, dual pcb with 1.8-ish GB ram. For now this is good enough for me but will report back if i get them both working perfectly.

Many thanks once again guys, the forum is full of wonderful advice, but searching through the forest for that one tree you want is sometimes part of the challenge

Once i get this system running, 10.7.4 with sound etc and hopefully no finder glitches, i will be making a disk image and trying Mountain lion because very very interestingly, mountain lion suffers from the same blank screen of death after loading and registering the nVidia kexts, i am starting to suspect that it could be the same problem. (The HDMI output being used rather than the DVIs)

verdant · September 11, 2012

@ ErOSx86

Glad to help..........

If and when you get your dual PCB GTX 295 card fully working with both GPUs I will add a summary of what you did to get it working in my OS X 10.8 nForce install guide.

BTW thanks for your very useful post in my nForce OS X Lion guide........I have replied to it......

dellio · March 13, 2013

i'm currently running 10.7.2 on a dell 7500 gtx 285 2gb...

trying to install 10.8.2 on another hard drive but getting the black screen at install....

tried GraphicsEnabler=Yes and No

Trying to use GraphicsEnabler=No and a <key>device-properties</key> custom hex entry in org.chameleon.Boot.plist but i generated it in Lion... do i need to do this in snow leopard???

this is what the boot list file looks like:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>Boot Banner</key>

<key>GraphicsEnabler</key>

<key>Instant Menu</key>

<key>Legacy Logo</key>

<key>device-properties</key>

</dict>

</plist>

Do i need to also add the gtx285.plist to the extras folder?

I followed the guide and used the gtx285.plist from here. Also used this as a reference but his gtx285 2gb link is not working....

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>

<dict>

<key>@0,compatible</key>

<string>NVDA,NVMac</string>

<key>@0,device_type</key>

<string>display</string>

<string>NVDA,Display-A</string>

<key>@1,compatible</key>

<string>NVDA,NVMac</string>

<key>@1,device_type</key>

<string>display</string>

<string>NVDA,Display-B</string>

<key>@2,#adress-cells</key>

<key>@2,#size-cells</key>

<key>@2,compatible</key>

<string>NVDA,sensor-parent</string>

<key>@2,device_type</key>

<string>NVDA,gpu-diode</string>

<key>@2,hwctrl-params-version</key>

<key>@2,hwsensor-params-version</key>

<string>sensor-parent</string>

<key>NVCAP</key>

<data>

BAAAAAAAAwAMAAAAAAAACgAAAAA=

</data>

<data>

AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==

</data>

<key>VRAM,totalsize</key>

<data>

AAAAgA==

</data>

<key>device_type</key>

<string>NVDA,GeForce</string>

<key>model</key>

<string>GeForce GTX 285</string>

<string>NVDA,Parent</string>

<key>rom-revision</key>

<string>xx.xx.xx - internal</string>

</dict>

</plist>

Black Screen on Mountain Lion with Nvidia GTX285 solved.

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites