Recent Posts

Just have to say, nvidia's drivers on multiple displays are absolute crap. I'm one of those users who had a single display until this week and I must say, the code is spagetti and a disaster on macOS

1. Toggling 2nd display on or off has a chance to make both displays perma black/standby and be unusuable until hard reboot
2. Any of displays going into standby mode have a chance to get perma stuck that way until hard reboot.

As long as 2nd display remains off no issues.

Display one is hooked up to 1080ti Display Port. Display 2 is hooked up to 1080ti DVI (yes same card, single card configuration).

I don't know if driver just sucks balls at managing a DP and DVI at same time instead of dual DP, or what the problem is. All I know is when I google the problem it seems universal to windows and mac and ONLY on nvidia drivers.

It's a real shame nvidia makes best hardware but their drivers have been such a buggy disgrace for years now. Meanwhile AMD drivers probably more reliable but their cards are crap (their radeon 7 is an utter disgrace. A grossly overclocked vega that's STILL 8% slower than a STOCK 1080ti. an overclocked one? or a 2080ti, forget it, all while needing 50 more watts of power and able to heat a small village)

I want to find a working 2 display configuration but I don't want to do it with an inferior GPU that's going to turn my room into a loud sauna.

Thanks!

I’ll order it ASAP

Recently installed Mojave in my Mac pro 5.1 tower GPU is a GTX 460. I have several drives with earlier versions of OSX El Cap, Mavericks etc. According the many different things I have read you cannot have two video cards installed while running Mojave. Along with the GTX 640 I also have a GT120 in the tower which is not tethered to any monitor. When I boot into EL Capitan and later on boot to Mojave the dock vanishes along with all the icons for the internal drives. Selected View options does nothing as the drive options are checked off. The entire desk top appears darker and more pixelated. I found that rebooting and zapping the PRAM fixes theses issues until a boot into an earlier OS. Is this a viable work around zapping the PRAM every time I boot into Mojave or could this create more problems down the road. Needless to say I would like to keep the GT120 in the tower in case I need recover a drive etc. Any insights here

Admittedly I am a relative newbie when it comes to flashing, that being said I am finding it rather difficult finding a GTX 680 for a decent price. I did find a GTX 670 and was wondering how different the board design is. Can the 670 be flashed with a GTX 680 rom???

Yes, it's the best option.

Drivers are inside macOS Mojave so it will be always supported.

PSU will handle this GPU without any problems.

Hi,

I am about to buy a GTX 780 Ti from macvidcards-europe and I am wondering if that's the best choice for performance/compatibility ratio?!
As I do understand, the GTX 7XX family is natively supported in Mojave because of the drivers being present.
Having a macvidcards will allow me to have the boot screen which is pretty important to me.

The last bit that I am unsure is: are the drivers integrated in Mojave ensuring that this card will be used as its full potential or not?!
Also I've read of potential issues with the PSU not being able to supply enough wattage at some point?!

I am using Premiere Pro with After effects and a powerful but compatible GPU is necessary for real time rendering.

I was thinking of the RX 580 at first, but the lack of boot screen made me look elsewhere.

What do you guys think?

I guess it is now "abandon all hope"...

Web driver for 17G6030 is:

https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.40.124.pkg

Lou

Hi guys, I was able to successfully flash an MSI R9 270x Gaming 2GB with the instructions in this topic, combined with a different patched efi.
Before flashing, the card was working fine in a 2009 Mac Pro (4,1 flashed to 5,1), with MacOS 10.14.4 and Mac firmware 141.0.0.0.0. As I understood, this firmware als enables 5.0 GT/s mode, so no R17 hack needed.
Card was detected as AMD Radeon HD 7xxx. Both DVI outputs working, unable to test HDMI and Displayport because I don’t have matching monitors or adapters.
I needed boot screens because I want to enable Filevault on my boot drive.

Started with the instructions and files from the first post in this topic. I flashed one of the roms (this card has dual roms, one legacy and one hybrid (legacy+UEFI)).
Boot the system, and yes! Boot screen on the bottom DVI. Was a happy puppy for about 15 seconds, because when the system (10.14.4) loaded the driver at login screen, all went black. Tried both DVI outputs, both black. Reverted the rom, and patched&flashed the other rom on the card. No difference.
I could access the system through screen sharing though, system profiler showed the card correctly as a 7950, so why was it not working?
Read some more, and I understood that this could be a framebuffer/port layout issue (maybe in combination with Metal/Mojave?)
So..I got either a card with boot screen but not working in the OS, or one without boot screen but working in the OS with the default RadeonFramebuffer.

Then I found this post in the Radeon Port mapping topic.
Here Fl0r!an posted an efi file with a purposely broken framebuffer. Theoretically, if I understand well, this causes the OS to not recognize the framebuffer set by the efi, and instead use the default RadeonFramebuffer.
I used the commands from the first post to patch my rom, but using Florian's RFB.efi instead of 7950mac.efi.
Flashed the rom, and it’s working! Boot screen on the bottom DVI (not on the top DVI, and HDMI and DisplayPort untested). When booted into the OS, both DVI ports are working. Again, HDMI and DisplayPort untested.

So I’m very happy, but still a question:
- The card now shows up as AMD Radeon HD 7xxx (Type DisplayController, with driver loaded) and AMD Radeon 7970 (Type ATY,HamachoParent, with no driver loaded). Where I think 'Hamacho' is where Florian changed 'Hamachi' to ‘disable’ the framebuffer.
Is there any disadvantage of it showing up also as a 7970? Probably because the RFB.efi was based an a 7970, but since (I think) it’s not used when the system is booted, it’s no problem? Everything seems to be working ok. Or could there be an advantage by patching 7950mac.efi the same way Florian did, and using that?

Rom and screenshots attached.

^^^^The pulled 108 driver is NOT patched.  It has worked, as downloaded, on all iterations of HS 10.13.6.  And if I recall correctly it worked fine on 10.13.5.

Lou