Contribute
Register

10.9.3 and itunes 11.2 released today

Status
Not open for further replies.
Joined
Nov 5, 2012
Messages
143
Motherboard
Asus Rampage IV gene Bios 4802
CPU
i7-3930k
Graphics
GTX 670
Mac
  1. iMac
Classic Mac
  1. Performa
  2. Power Mac
Mobile Phone
  1. iOS
Screen Shot 2014-05-15 at 12.18.49 PM.png

Waiting on news of someone to try it. I'm to chicken to explore install for myself first.


Shaggy
 
Combo update is live now.... http://support.apple.com/kb/DL1746

Follow Stork's advice:


Here's what I do for every update:
Download the latest MultiBeast to ensure you're goint to have latest the audio driver;
Backup your current system with Time Machine or Carbon Copy Cloner or SuperDuper (see this article for more information);
Repair Permissions using the Disk Utility on the drive to be updated;*
Run the Combo Update - don't reboot yet;
Run MultiBeast to reload only the audio driver;
Repair Permissions again;* and
Reboot
 
Any fix for iMessage?
 
Any fix for iMessage?

I've never had a problem with iMessages. but I'm still using filenvram.dylib version 1.1.1 still. Have you tried adding a credit card to your appleID.
 
Bit the bullet, upgrade went smooth only thing I needed to patch was TRIM. - Sorry I don't use iMessage although I do get prompted to sign in.
 
I have a kernel panic with "AppleIntelCPUPowermanagement.kext" in the message after updating.
When I try to boot into safemode (-x), same thing happens.
Tried to boot into Windows and renamed it to kext.bak but it doesn't help (still the same kernel panic)
What can I do?
 
First thing to do is follow the rules and add your specs to your profile... I'm not guessing.
 
Okay, will do this after this post.
Intel i7-3770
Asus P8Z77-i WD
Nvidia GF GTX 770

I managed to get into safemode after renaming the kext
It finishes the update and I could login (still in safemode)
After that I ran Multibeast (6.2.1) with my saved settings and then I ran kextutil.
Reboot.

Now it takes a bit long to boot up but I only get a black screen.
"com_driver_gxxxdriver::probe fails"
I think that wasn't there before.. not sure


Edit: For those who (hopefully not of course) might face the same problem:
1) Get into safe mode (-x)
2) Run Multibeast with your saved configuration
3) I installed the newest FakeSMC.kext CPUSensors.kext and GPUSensors.kext (from HWSensors package) with kextutil
4) Fix permissions with diskutil
5) reboot
I think Step 4 fixed it for me, as I did step 2 before with no success and step 3 is not related I think, not sure though
 

Attachments

  • Foto.jpg
    Foto.jpg
    812.2 KB · Views: 182
Status
Not open for further replies.
Back
Top