Contribute
Register

macOS 10.12.6 Security Update (2018-002)

Status
Not open for further replies.
Benjah said:
Previous security update left me in horror because of Lilu.kext breaking and causing a kernel. (fixed after a few hours of cursing and sweating)
Any issue reports on a similar problem with this update?
Click to expand...

I'm a non-AMD, non-Nvidia person who got burned by outdated kexts last time. This time it all went smoothly using the appstore update. I also have been installing all Clover updates, FWIW.

I need to remember to dig through the forums here and figure out how to best keep all the third-party kexts updated (and try to figure out why some go in the EFI partition and some don't).
 
trevorkw said:
Not super related but for those of you looking to get nvidia on the hackintosh side you might want to consider an RX series AMD card. If you can get your hands on them they work OOB and are native past 10.12.6. No dependence and display glitches on the web drivers needed.
Click to expand...

I thought there was a reason that AMD cards aren't recommended. Does sleep work?
It's a bit confusing, the buyers guide only mentions a few AMD cards, and say's they are only supported in macOS High Sierra 10.13.4 and later.
 
cardcomm said:
I thought there was a reason that AMD cards aren't recommended. Does sleep work?
It's a bit confusing, the buyers guide only mentions a few AMD cards, and say's they are only supported in macOS High Sierra 10.13.4 and later.
Click to expand...

The recommendation is because non-native AMD GPUs use a hard switching driver, for which setting up is a matter of trial and error and often non trivial (AMD Framebuffers use internal reference GPU names so theres a few per GPU design for mfr to pick from. The only way to know which your Brand of card is based on for sure is trial and error), and performance is inconsistent as some drivers simply get pulled out in an update or need fakeIDs, esp at the low end. Think of it as having 50 kexts and a set of switches and having to pick a few for your card yourself.

Nvidia has two soft switch drivers, NVHal or Hardware abstracrion layer, that will read the card and load the appropriate drivers. Web drivers literally just add more drivers to that list and keep em in a seperate box controlled by the -nvda drv switch. This is why nv_disable can set your GPU to VESA (picks Vesa driver) and why you'll always see Hal tell you 'Web' on startup.

Not perfect, but much less hassle. Funnily enough though Nvidia desktop performance fell off a cliff recently. I suspect it's got a lot to do with the lack of Nv Macs that are actually being made by Apple, and the widespread recommendation here for nearing a decade.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top