OS X 10.11.4 is out!

Flawless update on clover. There isn't a web driver yet, so those with gpus without original drivers support should wait...

Good music helps update's paranoia.

Updated even on AMD   Only issue was AppleHDA. Patched 10.11.4 version didn't work so reverted to the 10.11.3 kext.

I was hoping I'd be able to boot with SIP fully enabled now that I'm using AppleALC, but I still needed to set unrestricted nvram (CsrActiveConfig=0x40) otherwise AptioFixDrv gets stuck at boot.

Maybe AptioFixDrv needs an update for 10.11.4?

Updated from App Store, all went fast and smooth.

For now I used WebDriver-346.03.06b01

Working good for me 

Edit*** Updated NV Drivers 346.03.06f01 

I spent the last 2 hours trying to boot again in my desktop. After update I got the ALT circle. Tried to boot in safe mode and update finished, at reboot I couldn't boot, osxaptio problems. I moved it out of clover drivers directory and nothing worked again until I managed some how to enter recvoery and disable SIP completely, not even setting 0x67 in clover and restoring the aptiofixdriver was enough to boot.

I had to plug my HD in another machine and install the latest clover, after that I could boot from an USB pen into recovery to disable SIP and I was able to boot again. The question is: what is the level of SIP we can use in 10.11.4 ?

+ CSR_ALLOW_UNRESTRICTED_NVRAM / replace with OsxAptioFix2Drv

I was thinking about trying AptioFix2 again. I used it in the past but something made me drop it for AptioFix. Can't remember what the problem was now.

Update 1: Switched to AptioFix2 on the laptop and it's working ok with SIP fully enabled.

Update 2: Switched back to AptioFix and CsrActiveConfig=0x40. Boot would occasionally fail with AptioFix2. This is probably why I dropped it last time.

Hello
eager to return to France to test on my X99

I am sending you some sunshine Portugal

P8P67 Deluxe Rev3 on 3203 BIOS (using USB sound)

- updated, restarted, AptioFix error.

- used DOS on windows install to mount EFI partition

- removed OsxAptioFix, installed OsxAptioFix2

- still finnicky. 1/3 times it will get passed OsxAptioFix error (clearing nvram issue?)

- booted verbose- error with Heirarchy B-tree on Macintosh HD drive. PC shut down.

- booted single user, repaired catalog file using terminal. 

- now back into OSX, repaired permissions and partitions fix using Disk Utility.

Tried restarting again to see if OsxAptioFix2Drv-64.efi is still random. Sometimes it wants to work, sometimes it doesn't. I think that may have been why I used OsxAptioFixDrv instead. Though it's been so long that I can't recall.

Still, glad to be able to access my installation again.

a clean install of 10.11.4
cant login imessage and facetime
spam Certificate not yet generated in console

edit:

seems there's bug in 10.11.4

https://discussions.apple.com/message/29956490#29956490

P8P67 Deluxe Rev3 on 3203 BIOS (using USB sound)

 

- updated, restarted, AptioFix error.

- used DOS on windows install to mount EFI partition

- removed OsxAptioFix, installed OsxAptioFix2

- still finnicky. 1/3 times it will get passed OsxAptioFix error (clearing nvram issue?)

- booted verbose- error with Heirarchy B-tree on Macintosh HD drive. PC shut down.

- booted single user, repaired catalog file using terminal. 

- now back into OSX, repaired permissions and partitions fix using Disk Utility.

 

Tried restarting again to see if OsxAptioFix2Drv-64.efi is still random. Sometimes it wants to work, sometimes it doesn't. I think that may have been why I used OsxAptioFixDrv instead. Though it's been so long that I can't recall.

 

Still, glad to be able to access my installation again.

All good here with just a few steps required for the EVGA GTX 670 on Asus X79 Deluxe (hint new UEFI March 2016 update 4805 enables NVMe support) to work using smbios Mac Pro 6,1.  

First Install update:

At Clover go to options change to smbios 5,1 remove nvda_drv=1 ( the screen will be black if you don't)

1. AGDPfix

2. Install new Nvidia 10.11.4 drivers http://www.insanelymac.com/forum/topic/306535-nvidia-web-driver-updates-for-el-capitan-update-03222016/page-1

3. update CUDA 

Thats really all that was wrong using the components in signature. 

All good here with just a few steps required for the EVGA GTX 670 on Asus X79 Deluxe (hint new UEFI March 2016 update 4805 enables NVME) to work using smbios Mac Pro 6,1.  

 

First Install update:

At Clover go to options change to smbios 5,1 remove nvda_drv=1 ( the screen will be black if you don't)

1. AGDPfix

2. Install new Nvidia 10.11.4 drivers http://www.insanelymac.com/forum/topic/306535-nvidia-web-driver-updates-for-el-capitan-update-03222016/page-1

3. update CUDA 

 

Thats really all that was wrong using the components in signature. 

You do not need to change your SMBIOS for an update, you can use nv_disable=1, or set GFX1 in your SSDT/DSDT and you can avoid AGPM problems entirely and then just remove the nvda_drv=1 flag while starting up on outdated Nvidia drivers.

The latter option also allows you to boot the Recovery HD without any graphics flags and a MP6,1 SMBIOS.

@maleorderbride

Its not changed its simply an edit in clover under options for when you reboot. 

My SMBIOS is unchanged. 

Edit are not permanent at the Clover menu under options, when you reboot its back to what ever you had originally. Just saying for clarity.  I will look into that "set GFX1 in your SSDT/DSDT"

"You do not need to change your SMBIOS for an update" I never said you did. Perhaps I need to edit my post with 

1. First Install update

2. When rebooting at Clover go to options change to smbios 5,1 remove nvda_drv=1 ( the screen will be black if you don't)

3. AGDPfix

4. Install new Nvidia 10.11.4 drivers http://www.insanelym...03222016/page-1

5. update CUDA 

Update fine on my Probook

 Update command

softwareupdate -ia

Id prefer OsxAptioFixDrv if both works

I think I will switch back now that I know I can boot into the system.

what is the difference anyways?

EDIT: Changed back to OsxAptioFixDrv, and it rebooted just fine.

Screen Artifacs with Intel HD3000

never occur with 10.9 10.10 or 10.11.x previous release

Fix with CsrActiveConfig=0x67

ASUS: this time I was unaware of the OsxAptioFixDrv-64.efi thing and went straight trough the App Store update 

I was thinking about trying AptioFix2 again. I used it in the past but something made me drop it for AptioFix. Can't remember what the problem was now.

 

Update 1: Switched to AptioFix2 on the laptop and it's working ok with SIP fully enabled.

 

Update 2: Switched back to AptioFix and CsrActiveConfig=0x40. Boot would occasionally fail with AptioFix2. This is probably why I dropped it last time.

I tried option #2, being a little concerned about CsrActiveConfig=0x40.

So I chose OsxAptioFix2Drv-64.efi + CsrActiveConfig=0x03 as suggested here:

+ CSR_ALLOW_UNRESTRICTED_NVRAM / replace with OsxAptioFix2Drv

So far no KP prohibitory sign.   

Legacy:   NP.

OT: the Monty Python's   ! Never noticed that before 

So I chose OsxAptioFix2Drv-64.efi + CsrActiveConfig=0x03 as suggested here:

So far no KP.   

You won't get a KP with AptioFix2. Instead it will occasionally leave you at the prohibited sign during boot. A reboot will fix it, but it's annoying not being able to boot 100% of the time.

I didn't look to see what the problem was, but I think it's similar to what we get with AptioFix without the nvram fix.

Works fine on my X99

I spent the last 2 hours trying to boot again in my desktop. After update I got the ALT circle. Tried to boot in safe mode and update finished, at reboot I couldn't boot, osxaptio problems. I moved it out of clover drivers directory and nothing worked again until I managed some how to enter recvoery and disable SIP completely, not even setting 0x67 in clover and restoring the aptiofixdriver was enough to boot.

I had to plug my HD in another machine and install the latest clover, after that I could boot from an USB pen into recovery to disable SIP and I was able to boot again. The question is: what is the level of SIP we can use in 10.11.4 ?

true with this fix it can boot again