- #GEFORCE 210 FOR MAC HIGH SIERRA DRIVERS#
- #GEFORCE 210 FOR MAC HIGH SIERRA DRIVER#
- #GEFORCE 210 FOR MAC HIGH SIERRA WINDOWS#
#GEFORCE 210 FOR MAC HIGH SIERRA DRIVERS#
In my case, it usually panic'd and you wouldn't even get that far unless you booted in safe mode or disabled the NVidia drivers.Īnd post what drivers are loading related to the card. It looks like your injection isn't working right, or your NVDAStartup is causing the drivers not to load. With HS in general I've had the best luck with iMac13,1 and iMac14,2. YMMV, but I'd try to get it working with the built-in OSX ones.Ħ) Try some different system definitions.
#GEFORCE 210 FOR MAC HIGH SIERRA WINDOWS#
I'd actually recommend against that as it's easy to brick the card - I've had to do some EEPROM programmer & test clip recoveries screwing around w/the 550 and if you can't do that (the equipment is all of $15 if you have access to a windows box and some electronics knowledge though) it's easy to end up with a paper weight.ĥ) Forget the Web drivers for Tesla - I've had nothing but trouble with em, never made an improvement when they did work, and shouldn't be needed. 4279 and above is the lowest version I'm positive will work - there is a version break somewhere a little earlier and anything before that is not compatible w/High Sierra.Ĥ) You could try flashing different BIOS's to the card but I haven't had much luck with it making any difference - the Mac drivers pretty much ignore the BIOS from what I can tell except for the device/ID. They've pretty much worked OOTB w/injection.ģ) Speaking of Clover, make sure you're running a later version.
#GEFORCE 210 FOR MAC HIGH SIERRA DRIVER#
but, see below - I think they're just adding unnecessary complications to be honest.Ģ) I've never got one to work withour Clover Nvidia injection, but not much of anything else screwed with - I've never needed to load bios's in Clover, flash different BIOS versions to the card, do one off DSDT or driver editing, etc. I don't know about the Web drivers, you could try a NVDAWebstartup from an older build and see if it helps. I've had this problem & mostly was the only resolution needed on tens of builds/rebuilds with older Nvidia cards. The rest of the kexts work just fine w/the older NVDAStartup.kext, and this behavior continues through the latest HS update. Oh yeah and a HP laptop I have w/GeForce 9200 is a Tesla arch too IIRC.ġ) You're almost certainly going to need to replace NVDAStartup.kext with a version from El Capitan or an early Sierra - I can't remember if I had already replaced the original Sierra kext with the one from El Cap or not, but one of the Sierra updates broke things until I rolled that kext back to the El Capitan version from another box.
I have had HS running fine w/a XFX 280 (the card I'm trying to replace w/the GTX 550 ti for the HDMI outout w/audio), an EVGA GTX 275 & the Pegatron 310, along with some others I don't have anymore. I have had very good luck with Tesla architecture cards in everything from Yosemite to High Sierra. That's actually the fallback card I'm using to troubleshoot a GTX 550 ti in one box right now as a spare time project.
Any DSDT edits or anything that could be screwing with the card identification? What system definition?īut what I can tell you is that you should be able to make it work - it's a Tesla card and I don't believe it's very different from a Pegatron card I have running just fine w/a GT218 GPU. such as Clover build, options you're booting with, etc. I'd need a few more details to try and help. Building a CustoMac Hackintosh: Buyer's Guide