justroach Posted August 27, 2012 Share Posted August 27, 2012 I just upgraded my S5520SC-based system with a 285 GTX to Mountain Lion. The installer worked fine, but when I reboot, no matter what I try I cannot get the video to work. GraphicsEnabler=Yes, PCIRootUID=0, EFI strings, nothing. Any tips or ideas out there? I looked at a bunch of threads, but nothing that helped. Link to comment Share on other sites More sharing options...
VirtualGuitarist Posted August 27, 2012 Share Posted August 27, 2012 Just a noob suggestion: have you tried PCIRootUID=1? You could also try npci=0x3000 (with or without PCIRootUID=1), this is directly related to graphics and can help in certain cases. Because this is the only way to boot ML on my config... Link to comment Share on other sites More sharing options...
justroach Posted August 27, 2012 Author Share Posted August 27, 2012 Yes and yes. . Thanks for the tip though. Link to comment Share on other sites More sharing options...
VirtualGuitarist Posted August 27, 2012 Share Posted August 27, 2012 Have you tried older versions of nvidia kexts? Or those directly from nvidia? Link to comment Share on other sites More sharing options...
justroach Posted August 27, 2012 Author Share Posted August 27, 2012 Yes, I installed the Cuda drivers that you linked to there. I tried installing the "Retail" driver as well, but that through an error saying that a driver was already installed. The card shows up in the System Profiler, but doesn't show any ports or displays... Link to comment Share on other sites More sharing options...
justroach Posted August 27, 2012 Author Share Posted August 27, 2012 I just tried a clean install instead of upgrading and ended up with the same result. If I boot from the USB drive and then select the drive I installed on graphics work fine, but if I boot directly to the drive that I just installed on I get nothing but a black screen. Link to comment Share on other sites More sharing options...
VirtualGuitarist Posted August 27, 2012 Share Posted August 27, 2012 So it's perhaps related to your version of Chameleon: the version installed to your USB drive is the version that works for you, so perhaps you should try to install different versions, just to see if one of them works better for you. You could also try to see if there isn't in the /Extra folder of your USB drive a kext that's particularly useful for your mobo, and not present in the /Extra folder of your ML partition? By comparison you could know where the problem is...? You could also try the app "MyHack", it's not magic but it can solves some problems... Link to comment Share on other sites More sharing options...
jhrfc Posted August 28, 2012 Share Posted August 28, 2012 I had exactly the same problem. The newer boot loaders are not injecting the properties of the GTX 285 correctly anymore. you need to inject via device-properties. see http://www.insanelymac.com/forum/index.php?showtopic=281663&hl=&fromsearch=1 Link to comment Share on other sites More sharing options...
justroach Posted August 28, 2012 Author Share Posted August 28, 2012 Thanks for the reply jhrfc. I actually saw your post and tried that as well. The plist file I used is this: <?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(0x3,0x0)/Pci(0x0,0x0)</key> <dict> <key>@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>@2,#adress-cells</key> <string>0x01000000</string> <key>@2,#size-cells</key> <string>0x00000000</string> <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> <string>0x02000000</string> <key>@2,hwsensor-params-version</key> <string>0x02000000</string> <key>@2,name</key> <string>sensor-parent</string> <key>@2,reg</key> <string>0x02000000</string> <key>NVCAP</key> <data>BAAAAAAAAwAMAAAAAAAABwAAAAA=</data> <key>NVPM</key> <data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data> <key>VRAM,totalsize</key> <data>AAAAQA==</data> <key>device_type</key> <string>NVDA,GeForce</string> <key>model</key> <string>NVIDIA GeForce GTX 285 DDL</string> <key>name</key> <string>NVDA,Parent</string> <key>rom-revision</key> <string>3172a</string> </dict> </dict> </plist> I dumped that into my org.chameleon.Boot.plist file: <?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>EthernetBuiltIn</key> <string>Yes</string> <key>GenerateCStates</key> <string>Yes</string> <key>GeneratePStates</key> <string>Yes</string> <key>GraphicsEnabler</key> <string>No</string> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string>darkwake=0 npci=0x3000 -v</string> <key>Legacy Logo</key> <string>Yes</string> <key>device-properties</key> <string>d10300000100000001000000c50300001500000002010c00d041030a000000000101060000030101060000007fff04003a000000400032002c0068007700730065006e0073006f0072002d0070006100720061006d0073002d00760065007200730069006f006e000000080000000000000222000000400032002c006400650076006900630065005f0074007900700065000000120000004e5644412c6770752d64696f64650e0000004e00560050004d00000020000000010000000000000000000000000000000000000000000000000000001e00000072006f006d002d007200650076006900730069006f006e000000090000003331373261100000004e00560043004100500000001800000004000000000003000c000000000000070000000022000000400032002c002300730069007a0065002d00630065006c006c0073000000080000000000000022000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001e0000004e5649444941204765466f72636520475458203238352044444c14000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d4120000000400032002c0063006f006d00700061007400690062006c0065000000160000004e5644412c73656e736f722d706172656e7414000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4212000000400032002c00720065006700000008000000000000021c0000006400650076006900630065005f0074007900700065000000100000004e5644412c4765466f72636520000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616326000000400032002c0023006100640072006500730073002d00630065006c006c007300000008000000000000010e0000006e0061006d00650000000f0000004e5644412c506172656e7422000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c617920000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163220000005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000004036000000400032002c00680077006300740072006c002d0070006100720061006d0073002d00760065007200730069006f006e000000080000000000000214000000400032002c006e0061006d00650000001100000073656e736f722d706172656e74</string> <key>Timeout</key> <string>2</string> <key>UseKernelCache</key> <string>Yes</string> </dict> </plist> Anything that you can see I am missing as it still does not work? Link to comment Share on other sites More sharing options...
The-One***** Posted August 28, 2012 Share Posted August 28, 2012 Hi, I had the same problem, and I eventually tried using 'NVEnabler.kext' and it seemed to fix the problem. Hope this helps. Link to comment Share on other sites More sharing options...
justroach Posted August 28, 2012 Author Share Posted August 28, 2012 Can you point me to the version you used The-One*****? I tried that too, but all I got was a screen with distorted lines filling it. For the heck of it I tried pulling out NVDANV50Hal.kext from /S/L/E/ and got video, but in a terrible resolution. My understanding is that the injection tools (device-properties, GraphicsEnabler, NVEnabler, etc.) all use the the driver from that kext and just allow the driver to see the PC versions of the cards. Is that correct? I'm going to try poking at the driver it looks like. Link to comment Share on other sites More sharing options...
justroach Posted August 28, 2012 Author Share Posted August 28, 2012 I tried swapping out NVDANV50Hal.kext with the version from NVIDIA's driver .pkg as well as from the installer USB thumb drive that the driver works perfectly on. Still no go. I can't see how the USB drive with the installer would work with the graphics card perfectly, but not the installed version. Any ideas as to what to look for for differences? Link to comment Share on other sites More sharing options...
TimeWalker75a Posted August 28, 2012 Share Posted August 28, 2012 You are missimg one importamt thing for this gen of cards .. Change NVDA,GeForce to NVDA,Parent and it will boot with full acceleration etc.. Link to comment Share on other sites More sharing options...
justroach Posted August 28, 2012 Author Share Posted August 28, 2012 Oh TimeWalker75a!!! So close! I have video now, but no QE/CI. Any ideas what I am missing? Link to comment Share on other sites More sharing options...
SiliconVoid Posted August 29, 2012 Share Posted August 29, 2012 Have you tried a clean install with just the last mod you did (via TimeWalker75a)? The GTX285 was a gpu option in 2009/2010 Mac Pro (custom build) - it was supported by Mac OS (same as 8800GT). I have used the same card in numerous test builds - never needed anything but PCIRootUID=0 to get to install screen, and GraphicsEnabler=Yes on a few occasions. Link to comment Share on other sites More sharing options...
justroach Posted August 29, 2012 Author Share Posted August 29, 2012 After some more digging it looks like EthernetBuiltIn and GraphicsEnabler are mutually exclusive. If I have EthernetBuiltIn set to yes GraphicsEnabler doesn't work. Anyone ideas what might be doing that? Link to comment Share on other sites More sharing options...
TimeWalker75a Posted August 29, 2012 Share Posted August 29, 2012 Bootloader probably has a hard time combining efi strings together. Link to comment Share on other sites More sharing options...
justroach Posted August 30, 2012 Author Share Posted August 30, 2012 Unacceptable!! I want a refund! Looks like the best thing was to stick the Ethernet injection into DSDT. I tried to get my graphics card in there, but the best I could do was a resolution stuck at 2880x1800. GraphicsEnabler and the DSDT file looks to be my solution for now. THanks all for the help! Link to comment Share on other sites More sharing options...
Recommended Posts