OS X 10.10.2 Update

[chopperpl]

Worked like a charm on Clover bootloader!!!! Had to reapply TRIM patch from Multibeast 7.2...

 

[spick1923]

AHHA!

The problem is that now with 10.10.2
AppleTyMCEDriver.kext

No longer causes a kernel panic it sit's there sneakily in the background causing
system freezes always's used to remember to get rid of this guy lol!.

Deleted on mac pro 6,1 back to perfect stability

Hope this helps others

 

[J.P. Cain]

Been using Mac 6,1 profile for 6 months on all the mavericks updates

And all the Yosemite updates until now zero issues

Installed update 10.10.2

Computer boots up normally runs for 2-5 minutes before it freezes.

I have deduced the problem is not system definitions but a new kext or change
to osx 10.10 in 10.10.2

Any one have any ideas? or am I stuck with 10.10.1 until the next update?

I was in the same camp. There is an updated kext in Mac 5,1 and 6,1 that has some sort of issue. If you use 3,1 you won't have that problem but you will need to use safe mode to get past your cache.

 

[mcharles]

I have an older system and simple NVIDIA card.

Smooth as silk upgrade from 10.10.1 to 10.10.2 on Gigabyte P55M-UD4. Stork's step by step worked flawlessly.

Repairing permissions before and after seems to ensure success.

Thanks again.

 

[Selective]

Hi there

The update to 10.10.2 went smoothly using apple update.

Intel I5-3570k 3.4Ghz / MSI Z77A-G45 / 16GB DDR3 1600Mhz / Intel HD4000 / 128 GB Kingston V300

Only had to apply again sound and trim from the new Multibeast 7.2.

Thanks and keep up the great work

Selective

 

[Chanks]

Hi, I´ve also updated and no my Audio dosn´t work anymore

I tried many times to reinstall the audio kext, but it dosnt work


I´m running a 4770k with a Z87x-UD3H

Thanks!

 

[pcpaul]

I think I got this too, though now I experience this on every partition, I've ML, Mavericks and Yosemite, up until this update, I think, I was having no issues with sleep, but after this update once computer wakes up it freezes, though I can click around, but I can't open any new app or anything what wasn't loaded into ram while going into sleep mode, I have to forcefully restart by reaching for a reset button.
Before sleep I opened Console and after waking up here's an error reported multiple times

SATA WARNING[COLOR=#666600]:[/COLOR] [COLOR=#660066]Enable[/COLOR] [COLOR=#000088]auto[/COLOR][COLOR=#666600]-[/COLOR]activate failed[COLOR=#666600].[/COLOR] 
disk3s3[COLOR=#666600]:[/COLOR] I[COLOR=#666600]/[/COLOR][COLOR=#006666]0[/COLOR] error

Here I posted more info http://www.tonymacx86.com/general-h...ng-enable-auto-activate-failed-i-0-error.html

Let me know if you've figured it out or if it's similar to your problem at all.

Solved it After wake up SATA WARNING: Enable auto-activate failed. I/0 error

 

[pcpaul]

Having issues with 10.10.2. Everything works beautifully. The only issue is when I put the system to sleep it wakes up but if a I do a screen zoom (control + scroll wheel) (when enabled in accessibility), the system freezes and crashes.

It only happens after a sleep state. This was not an issue previous to 10.10.2

Anyone else having this issues?

Z77X-UD5H, 32GB, 570HD GTX, 3770K

Check out console for errors, might be having something similar to mine, which I've solved, though doubt it.

 

[phlob]

System:
- i7-4790k
- GA-Z97X-UD3H
- GTX 780 Ti

Clover Bootloader
toleda audio + HDMI audio SSDT

everything work fine after update from 10.10.1 to 10.10.2

 

[SlimJimi]

GA-Z77X-UP5-TH, i7 3770, HD4000 -->ACD with usb sound

usbmsc identifier (non-unique) error (fix found?)

Used Chimera v4.0.1 Multibeast 7.1 and most recent Unibeast.

Since upgrading from Maverick to Yosemite I have had nothing but problems. I did a fresh install of Yosemite. I have done several fresh installs. They work for a while then when I restart they lock up at the apple screen. Using -v boot flag. I usually find usbmsc identifier (non-unique) error. I can boot using -x and try to modify multibeast and nothing worked. I was considering giving up and just using the windows 8.1 which is part of my build and wait for upgrades in the future or reformat and go back to Maverick.

Alas, I found that adding the boot flag -f enabled me to boot right into my mac and everything that matters to me seems to work. I don't use imessage or hibernate my mac since I prefer to keep it on to stream audio to sonos and media to plex.

My question is what does the boot flag -f do?
Is there another way to add this so I don't have to type it in with each restart.
Is there a better way to solve this problem?

Thanks of the help

Thanks Dadeli,

I was able to get my z77x-up5-th booting again normally using the -f flag. I followed the comments in this thread by dddirtman and FishCow (edit /Extra/org.chameleon.Boot.plist to set UseKernelCache to no) to avoid having to type the -f flag at boot.

Got no audio, but at least I can finally reboot.