Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I'm thinking something is wrong, or perhaps I'm doing things wrong.

I've used Terminal to set my boot-arg to nv_disable=1 (overwriting nvda_drv=1).
I then reboot and never again reach the desktop (which makes screen sharing impossible).

I don't know how to recover from a boot loop, so I just restore OS X from an external backup. Since I revert to a backup, I don't have access to the panic logs that would have been generated.
 
I'm thinking something is wrong, or perhaps I'm doing things wrong.

I've used Terminal to set my boot-arg to nv_disable=1 (overwriting nvda_drv=1).
I then reboot and never again reach the desktop (which makes screen sharing impossible).

I don't know how to recover from a boot loop, so I just restore OS X from an external backup. Since I revert to a backup, I don't have access to the panic logs that would have been generated.

What GPU(s) do you have in the system when you attempt to boot with nv_disable=1?
 
I'm thinking something is wrong, or perhaps I'm doing things wrong.

I've used Terminal to set my boot-arg to nv_disable=1 (overwriting nvda_drv=1).
I then reboot and never again reach the desktop (which makes screen sharing impossible).

There are some misconceptions going on here.

To actually see something on the screen or have a desktop, SOMETHING needs to create that screen. The 2 choices are EFI driver, or Nvidia driver. If you have a non-EFI card and you turn off the Nvidia driver, then obviously there is nothing to create an image. So nothing will ever show up on a display connected to an Nvidia card with no EFI.

You would be better off removing the card and trying screen sharing with no card, I seem to recall that it creates a small, default desktop, but am not sure.

The cards that require Web Driver are basically all Maxwell, and the last Kepler cards that Apple has decided to ignore. Titan Black and GTX780 Ti.

As to why a 650 needs Web Drivers I do not know. It shouldn't require them but I believe that the real issue likely lies with monitor definitions. You might be able to flash with another 650 rom and find card works but that would be a lot of trial and error. We used to do an EFI 650 but went with 640 instead as it doesn't need power cable and thus more desirable for many, we no longer play with 650s much. I won't go in to much detail, but the thing that crippled Nvidia flashing for so long was Monitor Definitions. Nvidia driver does some clever footwork to hide this fundamental difference in these. It works hard to keep you from knowing that it is working hard. Some lazy coder at Asus drops a byte in Monitor Defs that Windows can gloss over, it sometimes results in bad OS X behavior.

It is likely that adding EFI to that 650 would solve most problems, though I understand that the cost may exceed the benefit.

I have spent last several days trying to fix a 3yr old LG Plasma that crapped out. Testing voltages, reflowing inductor coils, replacing MOSFETS, etc. At this point I would have been MILES ahead if I had just called Earl's TV Repair to fix the thing. But I didn't know that when I pulled the back off, was hoping it was just a fuse. Hours I won't get back.

To the OP, I would suggest treating this thread as a practical thing instead of theoretical. Create a disc image of a basic 10.10.3 install. Before recording this disc image, download the 10.10.4 update and the needed Web Driver to the desktop. Use Disc Utility to make a restore image. Use a Non-EFI card from Maxwell. Document the exact steps and how they work to get install to working 10.10.4 with Web Driver. Get out a piece of paper and a pen and write things down as you do it, what you did and what the result it. When they don't work, restore the disc image and start over. Treating this as theoretical is causing a lot of guesswork to come in. Once you find a method that works, do it again.
 
What GPU(s) do you have in the system when you attempt to boot with nv_disable=1?

Only the GTX 650 card is in the system when booting with nv_disable=1. I've got it in Slot #2 if that makes any difference. Slot 1 is empty.
My Apple card is the Radeon 4870 which requires both power cables, so I don't keep it installed.
 
As to why a 650 needs Web Drivers I do not know. It shouldn't require them but I believe that the real issue likely lies with monitor definitions..

My 650 is a Zotac. I wonder if I'd had better luck with a EVGA.
It's Yosemite that hates my card. Mavericks likes it just fine.

Might be worth flashing since it's the one I want to use. I'll think about it.
 
I should mention that installing a beta driver did work when updating from 10.10.2 to 10.10.3. It successfully installed in 10.10.2, and I was able to update through the App store, then install the proper web driver once I landed in 10.10.3. All of this without swapping in the Apple card.

Installing the 10.10.3 beta driver posted on MVC's site puts me in the restart loop. The 10.10.4 beta won't install because my OS build number is incompatible.

Should I hack something to get the 10.10.4 beta installer to work in 10.10.3?
 
I don't think anything is fail proof to everyone, but Screen Sharing so far has been 100% reliable for me. Well, on a LAN anyway. Some times I have problems accessing over the Internet.

While screen sharing you can use the Nvidia Control Panel (Driver Manager?) to switch between the default drivers and the web drivers. You can also use the terminal command line to disable or re-enable the Nvidia drivers.

I'm not aware of a step-by-step guide. I suppose it depends on what you are trying to do. I also don't have any non-EFI cards, so someone else would have to help you with that.



I can't confirm that as I do not a GT120 nor do I have a non-EFI card. But why would an Apple GT 120 EFI card crash the built-in drivers? That doesn't make sense. Mac Pros used to come with those...everyone still using them would be crashing.

I know this thread has been quiet for a while, but I am thinking whether we could create a practical step-by-step process for updating webdrivers without a efi-card?

For example a Lan-solution like ActionableMango suggested.

I have some ideas, which I would like to test asa I will be back to my office in a few days, but I would like to hear if there is anyone who has more experience, different solutions, exc who could chime in :)

All help appreciated!
 
Strange. I have a Geforce 980 in slot 1 connected to an Apple display and a GT120 in slot 2 just in case something goes wrong. I have never used the terminal commands. Every system update, I disable the web driver in the nVidia control panel and upon reboot, I use screen sharing on my MacBook to install and enable the new web driver on my Mac Pro. It works great.
 
  • Like
Reactions: bsbeamer
I also use screensharing via MacBookPro to install graphics driver updates to MacPro. Generally will download the .pkg to the desktop, then just have to execute the file and upon reboot monitors are back. Years ago was using Chicken of the VNC (now just "Chicken") for screensharing into non-monitor systems/servers, but haven't needed to go through that recently. The built-in screensharing works fine for this usage.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.