OS X 10.7.4 Software Update

So I waited a few days to gather some information from users on what has gone wrong with this one before posting if it is safe or if caution is advised. The verdict – caution is advised.

This is the first update that I myself have encountered a problem with so I will attempt to cover what I know as well as what others have found, and how to fix what we’ve seen break.

First problem report I heard was – a kernel panic when running the combo update.

This was related to ApplePolicyControl.kext – when the update loaded it, the system panicked and left things in a non functional state. The users resolution was to re run the combo update from a separate OS X installation, remove the problematic kext when it was done and to then run myFix. This extension is removed by the myHack “Remove Problematic Extensions” feature but that won’t help if it is loaded on a running system by a combo update.

This can be avoided however – if you have an smbios.plist that identifies your system as something that ApplePolicyControl.kext will not panic on – no panic will happen, this was the case with my own system. So you have two options:

  1. Create an smbios.plist for your system that ApplePolicyControl.kext will not panic on
  2. Run combo update from another OS X installation, targeting the 10.7.x OS X installation you want to update, when finished, run “Remove Problematic Extensions” function from myHack.

Ok, next problem – This happened on my system. When the update was completed, I rebooted. The system panicked on IOPCIFamily.kext. So I rebooted again with -f -v, no panic this time, but the system hung when trying to load AppleHDA, and claimed that kextd was not running. So first I attempted to boot into my ‘fail-safe partition’ which is basically an extra myHack OS X Install Disk for 10.7 that I have on my internal boot partition so I don’t have to dig out my USB stick every time something goes wrong. It hung at the same point….

While I am not entirely sure why the separate partition with a 10.7.0 OS X installer on it was effected by the update the reason for it happening isn’t really important – the solution is simple – I plugged in my USB myHack OS X Install Disk, ran myFix – a full one, not a quick one – and rebooted – everything works fine now. So to sum it up:

  1. Ensure your myHack OS X Install Disk is not attached or mounted on the system
  2. Run the 10.7.4 update and reboot when it is finished
  3. Boot to your myHack OS X Install Disk
  4. Run myFix, select full not quick, run, and reboot when it is finished
  5. Boot your OS X 10.7.4 installation

The last problem I have seen was reported by a user on the forum. His Nvidia GTX295 stopped working after the update. This is a problem I have seen in past updates and why in the myHack guide I always advise users to backup at minimum their /S/L/E directory prior to running any OS X updates. You may read the thread he opened on the forum HERE

The solution for this problem is as follows, and the following method can be adapted to virtually any hardware device that no longer functions after an OS X update due to Apple’s modifications of the System Extensions:

  1. Prior to running an OS X update, always backup /System/Library/Extensions
  2. In his case his NVidia graphics no longer work due to updates of the Nvidia graphics so he could either determine exactly which kext is the problem and replace only that one with the one from his 10.7.3 backup, or he could replace all of the nvidia graphics extensions including the frame-buffers
  3. Determine which extensions you want to override in /System/Library/Extensions in his case he took all of the Nvidia extensions and frame-buffers
  4. Place the extensions from 10.7.3 backup in /Extra/Extensions
  5. Run myFix, reboot
  6. Boot to OS X 10.7.4

A full list of the NVidia extensions and frame-buffers is in the thread I linked to, the clean way to do it would be to just grab the ones for your card specifically – I will be explaining to him how to figure out which ones he needs in the forum thread.

So there you have it, that is how to avoid the 3 most common problems I have seen thus far with this update. If you encounter a new one please let me know via the forum – I will update this post if needed.

Additionally, keep in mind 10.7.4 is pulling code in from 10.8 so there might be a number of issues for users who are still relying on older graphics or i386 libraries…

myHack 3.1

This version is now deprecated, consult the myHack guide for a link to the latest version.

This version was downloaded 15553 times.

This release was made ahead of my planned schedule due to a couple of bugs being brought to my attention that I wanted to fix immediately. Since I was going to make this release anyway I used the opportunity to polish off a few other things that I had on the todo list, a few things that were suggested by users, and update a couple things in the bundle.

I’ve also added a new feature to the extra installation function, thanks to a suggestion by blackosx. It will install the Extra directory as usual, it will then check to see if you have an /Extra/10.(6/7/8)/Extensions directory – not just /Extra/Extensions. If one exists for the OS X version that exists on the target device, it will merge it with /Extra and then remove all the 10.(6/7/8) subdirectories from Extra. This will prove even more useful in the near future but for the time being it just helps users with this particular Extra schema to have a smoother ride while using myHack to update their systems.

Changelog:

  • Bugfix: Correct issue with myhack OS X post install patch of OSInstall.pkg when myHack OS X Install Disk is created on a Snow Leopard system
  • Bugfix: lspcidrv.kext and RemovedExtras won’t get moved to ExtraBackups when installing a new Extra
  • Extra/10.(6/7/8) subdirectories will now be merged based on target OS version
  • Disabled the Create OS X Installer option from myHack while running on an OS X Installer
  • Disabled Cancel buttons on myHack OS X post install dialogs
  • If cancel button is pressed on Extra file selection dialog, return to Generic Extra/Use Your Own menu instead of exiting myHack
  • Revised Snow Leopard installation source detection – Instead of looking in /Volumes/Mac OS X Install DVD/ all volumes mounted in /Volumes/* are scanned
  • Fix permissions on /bin, /usr/bin, and /usr/sbin on osx installers so that all the binaries can be executed properly
  • Disable kernelcache on OS X Installers
  • Enable kernelcache on user supplied extras instead of just the generic one
  • When running myFix, check that myHack.kext is latest version, if not, update it
  • Removed log output for enabling ownership on devices
  • Minor cosmetic fix to DMG – attempt to prevent the text from being cut off on the bottom
  • Removed pkgutil and strings binaries from bundled utilities
  • Stripped ppc arch from bundled utilities
  • Updated myFix to version 2.1
  • Updated FakeSMC to version 4.2
  • Updated Chameleon

Make sure to read the release page for myHack 3.0 if you have not done so already, for a complete list of changes, contents and features.

Additional details of the myHack app’s contents, credits, and instructions are maintained on the guide page.

Feel free to post thank you comments and whatnot on this post but for support or to report a problem you encounter – please use the Forum or the #hackintosh channel on SojuGarden IRC.

myFix 2.1

There has been this persistent thorn in my side since some other not so tech savvy people out there started releasing their own Chameleon installers and unlucky users attempted to use them – Boot sector corruption from incorrect installation of boot0.

The issue is not one that is immediately apparent, it is only when you attempt a normal manual installation of chameleon or installation of chameleon using myHack that the problem reveals itself and the system fails to boot.

I attempted to resolve the issue in myHack 2.0 RC2, and while the fix worked for some people, the issue has proven to be a continued problem for others, and the fix itself apparently causes problems for a few other users that use unique installation schema’s as well.

I have revised the method used to ‘Flush’ the boot sector and repair the corruption in this release of myFix. It is my hope that this will solve the problem once and for all, otherwise more extreme measures may be required.

Changelog:

  • Revised chameleon installation – using new method to repair damaged boot sectors
  • Clean up temp files after running tests during chameleon install
Make sure to read the release page for myFix 2.0 if you have not done so already, for a complete list of changes, contents and features.

Feel free to post thank you comments and whatnot on this post but for support or to report a problem you encounter – please use the Forum or the #hackintosh channel on SojuGarden IRC.