OS X 10.11.5 Update

[esparzatomas18]

Update went perfect, no problems

Edit#1 Spelling

 

[bran1m1r]

Combo update fine here for the Z170 build in signature.

1. Run combo installer
2. Boot with nv_disable=1
3. Install latest NVIDIA drivers
4. Boot with nv_disable=1
5. Run AGDPFix app (to fix black screen bug with 6,1 and 15,1 and 17,1 definitions)
6. Done!

step 2,3,4,5 are only for computers using Nvidia graphics cards or everybody? my Laptop has a Intel HD 520..

 

[Orangeade]

Hey guys,
So I had a completely fine installation of .11.4 and decided to install the update.
Update installed and I downloaded and installed the new nvidia drivers.
After that, i couldnt boot anymore, kernel panic relating to process "init"...

I decided to try out if os x would boot if i removed one of my gtx 670 gpus which I ran in dual-sli.
Kernel panic was somehow fixed like that, but now I get the "still waiting for root device" error.
Sata mode is on ahci.

Has anybody got ideas how to fix this? Thx alot!

 

[Yoga]

step 2,3,4,5 are only for computers using Nvidia graphics cards or everybody? my Laptop has a Intel HD 520..

Yes, and a specific (unsupported by OSX natively) type of NVIDIA card too.

 

[mac2win]

Have you tried Clover's FireWire DSDT mask fix?

Sorry missed your message, no i have not tried it but will take a look and try it, thanks for the input,

 

[stator]

Since 10.11.6 is in beta2, and I had a difficult time with updating to 10.11.5 that I will document here on why. I used the combo update, but the issue was caused by updating Clover to 35xx version right beforehand. Once I ran the combo update and rebooted, it would not boot due to the OsxAptioFix error.

Previouus upgrade to 10.11.4, I had the same error, recovered, and changed to OsxAptioFix2Drv which solved that issue. However, I accidently left the OsxAptioFixDrv in the Clover boot along. The old Clover 32xx used ...Fix2Drv while the new version fell back to using the older ...FixDrv.

Moral of this story is don't just rely on the Clover Configurator utility as it is poorly written and should be moved into open source so it can be fixed. Mount your EFI partition and use finder to look it over and confirm.

Another example of how poorly written Clover Configurator is using it safe mode. It should check the mode and report something meaningful rather than trying to mount a MSDOS partitition in safe mode and receiving some generic error instead.

 

[chaosdesigns]

Updated. Working without a glitch. Z77mx-D3h, GTX660, VT2021 audio chip.

I have the same board but I cannot get audio to work. Can you provide details? Thanks, in advance.

 

[Sabanet]

Work's fine!!

 

[Walril]

Since 10.11.6 is in beta2, and I had a difficult time with updating to 10.11.5 that I will document here on why. I used the combo update, but the issue was caused by updating Clover to 35xx version right beforehand. Once I ran the combo update and rebooted, it would not boot due to the OsxAptioFix error.

Previouus upgrade to 10.11.4, I had the same error, recovered, and changed to OsxAptioFix2Drv which solved that issue. However, I accidently left the OsxAptioFixDrv in the Clover boot along. The old Clover 32xx used ...Fix2Drv while the new version fell back to using the older ...FixDrv.

Moral of this story is don't just rely on the Clover Configurator utility as it is poorly written and should be moved into open source so it can be fixed. Mount your EFI partition and use finder to look it over and confirm.

Another example of how poorly written Clover Configurator is using it safe mode. It should check the mode and report something meaningful rather than trying to mount a MSDOS partitition in safe mode and receiving some generic error instead.

This was exactly what happened to me. I think Ill leave clover at whatever version it is.

 

[TorontoDave]

Installed smoothly from app store - after the install I was prompted to updated Nvidia driver - boom everything works.

HD4000 Video, Nvidia GTX 970, on a Gigabyte Z77x-UP4-TH. Even the on-board audio worked without re-upgrading clover or installing drivers.