Contribute
Register

OS X 10.11.4 Update

Status
Not open for further replies.
Hello,
I'm part of the lucky ones (for once)
It's the first time since the I built this computer (Maverick) that I do a seamless update like that, I just feel like I'm on an actual mac, so cool :)
trim, audio, etc.. all still working without anything to do.
 
Updated both of my Laptops (Lenovo ThinkPad L440 & Lenovo B570e)

Everything did go well without a problem,smooth!!
All i had to do after update is replace AppleHDA kext for each laptop since i use a patched AppleHDA kext instead of an Injector.
 
Pre Update Notes:
- This update may break some of your El Capitan functions, like audio and the nVidia Web drivers. So, being an Early Adopter maybe fraught with problems. Make sure you backup first.:thumbup:

- If you're using nVidia drivers for your GeForce GTX 750, 750Ti, 960, 970, 980, 980 Ti and the Titans 'Maxwell' graphics cards, you'll need to install the nVidia 10.11.4 Web driver(s) after the 10.11.4 update. You are advised to wait for nVidia's update or use the nVidia Yosemite Beta Web drivers. tonymacx86 will publish the link to the nVidia Web Driver as soon as it's announced, usually within 2-3 days. See threads in the Graphics forum section if you have one of these Maxwell graphics cards.

Here's the step by step way to update for those who aren't using the nVidia Maxwell graphics cards :
:ch: Backup your current installation using Carbon Copy Cloner or SuperDuper;
:ch: Download the Software Update or Combo Update and run it to update to 10.11.4 - the updater will reboot upon completion;
:ch: Upon rebooting into El Capitan, you can:
:ch: Check to see if your audio is working (If you enabled Realtek onboard audio using MultiBeast v8 or toleda's CloverALC110 script, your audio should be OK),
:ch: (Optional) Update to the latest version of Clover,
:ch: (Optional) Check to see if your TRIM setting has survived through the update - if not, use the "trimforce" Terminal command[SUP]1[/SUP]; if you've used the "trimforce" command in 10.11.0, then it should "survive" the update, but check to make sure; and
:ch:Re-boot​

Please post help requests in the El Capitan Desktop Support Forum section (not in this thread).

Tip: Don't use the iMac15,1 and Mac Pro 4,1/5.1/6.1 System Definitions. These SysDefs have been found to cause problems. For Haswell builds, toleda recommends iMac 14,1 for HD4600 and iMac14,2 for graphics cards; MacPro6,1 is only appropriate for X99 systems. Additionally, Clover is pretty "smart" about choosing a default System Definition for your system.

[SUP]1[/SUP] Use the new Terminal trimforce command in the following manner:
Code:
sudo trimforce enable


Enabling trimforce is far from "new". Thanks for reminding us, though :)
 
Updated from App Store with one minor issue and no major issues. Installed update then rebooted and installed graphics drivers from Nvidia Preference Pane. Had to modify a kext as described here in order to get my display back since I'm using a MacPro6,1 definition. It would boot to a black screen unless I used "nv_disable=1". Everything else works including audio.
 
FYI OsxAptioFix2Drv is used by default in MultiBeast and UniBeast.
So maybe it's only effect those of whom Originally install Yosemite use Clover then upgrade to El Capitan and the OsxAptioFixDrv is still there along with OsxAptioFix2Drv. For instant in my case. Anyway Thanks for the Info.
 
Installed successfully the update on HP Probook 6560b with Intel HD Graphics 3000 512MB but i have a lot of artifacts in my screen. How this can be fixed? Thank you.
 
Hello
Have kernel panic after update 10.11.4 from app store. on :
MSI Gaming 3
i7 - 4790k
nvidia 970 MSI
Chameleon Enoch 2795
had to replace kernel whit one from 10.11.3 and it work "kind off"
 
My system is using the Z97X-UD7 TH motherboard. The last two updates worked flawlessly, this one (as reported by others) gave me problems. I had to restore from a cloned drive. Going to try again soon with OsxAptioFix2Drv installed as recommended by others. Although, I used the OsxAptioFix2Drv driver in the past and (again as mentioned by some previous commenters) it boots sometimes, and not others. We'll see what happens.
 
Status
Not open for further replies.
Back
Top