SURPRISE! Nvidia 970 trouble with Yosemite (10.10.2) and Clover....

I've read a bunch of posts about this already, and everyone seems to have similar issues, but after deleting/reinstalling nvidia's web drivers (using nv_disable=1 to boot) I'm still unable to get into a working nvidia environment...

Had this running smoothly in Multibeast with 10.10.2 / nvidia web drivers. Multiple (3) displays using DVI and HDMI. When I started experimenting with a Clover USB to get my config.plst tight before installing to the SSD, I screwed something up (I'm guessing by "injecting nvidia"?) and now the only way I'm able to get into OSX at all is by disabling nvidia. So obviously you get the choppy screen/graphics. However, once I d/l and reinstall web drivers, I go back in to boot with nvda_drv=1 I make it to login, and barely get signed in before I get the dreaded "no signal" on my screen / crash / reboot. And now to top it off, it happens on my SSD install of Chimera/Chameleon whatever as well. Can only get in with nv_disable=1, and the reinstallation of web drivers seems to matter not.

Thoughts? Seems like this is a fairly common problem, but I'd love to get Clover working with all displays functional from my 970. Seen a lot of guides, but not really a definitive "YES! This fixes it!"...

Have tried multiple SMBIOS, currently on Mac 3,1 but same results with 5,1.
Thanks for any help in advance.

The only people experiencing issues are usually those running 4K monitors. My GTX 970 has been perfect since I built the rig in November on a 1080P monitor and now a 1920x1200.

There are 4 things needed to run a Maxwell GPU:

1. Must be running Yosemite
2. Have the web drivers installed
3. Have the boot flag nvda_drv=1
4. Inject/Nvidia - False or GraphicsEnabler=NO (depending on boot loader)

On my card I have used DVI-HDMI, HDMI-HDMI and DP-DP all with out issue and working audio.

My guess is you either are using a 4K monitor or you still have Inject/Nvidia - True.

Interesting. I think you're correct on the inject nvidia... I think that's what caused this issue in the first place... I'm figuring out how to switch that out now.. Thanks a bunch Slim Jim- will update with result.

*UPDATE*

Adding NVidia=False boot flag and making sure the graphics / inject / nvidia portion of config.plst was set to False DID get me to the login screen, and for the first time, my 1080 display (no 4k's sadly) on the 970's HDMI port popped up with a screen... However, it immediately crashed afterwards. This is also after reinstalling the web drivers again... Is there anything else I need to do to un-inject the nvidia drivers? If I did it once already is it saved somewhere, screwing stuff up?

Really not sure what the hell, but seems clear to be an issue with the GPU. I feel like I remember when I very first installed OSX on this SSD drive with Unibeast/Multibeast, I had to run the Intel GPU, install the nvidia web drivers, THEN go in and disable Intel in BIOS and add the nvda_drv=1 flag to get the 970 working. Is there a reason that going in and unplugging the gpu until re-installation of the drivers should matter / would be necessary?

You can usually boot with the GPU installed using the flag nv_disable=1. The only boot flags you should need are: kext-dev-mode=1 nvda_drv=1.

Are you sure you have the correct Nvidia Web Drivers installed?

I'm on 10.10.2 and I'm running the only web drivers available for that release. I tried upgrading to 10.10.3 and trying those web drivers (that UPDATE of OSX has been UPDATED past nvidia's drivers btw.... didn't realize there were updates to the updates until today), but I've found that with this motherboard / gpu combo the marriage has always been a little ****y. When I first installed everything I had plenty of un-sensible things keep the nvidia stuff from working, and had that random "it just worked, don't touch anything" moment. So of course, now that I'm messing around with Clover that's all been negated. I'm in the middle of a complete re-install with Clover... We'll see how it goes...

And yes, your previous post of the "only four things you should need" made perfect sense to me... Bizarrely this has proven to not be the case in my... case. (pun intended). I have no trouble boting with nv_disable=1... But once the web drivers are installed (without fanfare) it's still disable or crash. No smooth sailing. Very strange.

ForteeToo said:

I'm on 10.10.2 and I'm running the only web drivers available for that release. I tried upgrading to 10.10.3 and trying those web drivers (that UPDATE of OSX has been UPDATED past nvidia's drivers btw.... didn't realize there were updates to the updates until today), but I've found that with this motherboard / gpu combo the marriage has always been a little ****y. When I first installed everything I had plenty of un-sensible things keep the nvidia stuff from working, and had that random "it just worked, don't touch anything" moment. So of course, now that I'm messing around with Clover that's all been negated. I'm in the middle of a complete re-install with Clover... We'll see how it goes...

Click to expand...

For 10.10.2 there was actually a total of 5 driver releases because of the security updates before 10.10.3 was released.

What I would do is start with a cmos reset and then make sure all of the bios settings are correct and work my way back through to see if I could find any errors.

If you would like to, post your config file for Clover I can take a look at it.

Here's the config file. It has the nvda_drv=1 boot flag, which I delete and substitute with the nv_disble=1 until after I install the web drivers...

You can completely remove these two flags: dart=0 Nvidia=False

Nothing else really jumps out at me.

One thing that seems strange, when I check the system profiler both the built in video card and the 970 seems to not be recognized correctly...



I'm betting this may be related to the web drivers not taking...