Mac Pro 3,1, because that is the default recommended system definition according to the Installation Guide:
...and I had been using it since buying the board from a CustoMac Buyer's Guide years ago without any audio issues.
The only way I was able to remedy broken audio after sleep (GA Z77 DS3H) was by changing the system id to iMac13,2. IMO this is worth adding to the guide. It would have saved a considerable amount of time had I seen such a recommendation in one of these audio guides. Thanks for all your great work.
Thanks, that's what I've been using but still it breaks after sleep. Does it always say "This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state." when you run it?
I have the same board. Have you ever been able to get persistent audio ALC887 working? I.e. that doesn't get overwritten after every update, AND works after sleep? Feel free to PM me. I've tried all toleda's guides and the clover alc script etc.
To summarize what's in that thread -- you need to replace some binaries (mDNSresponder and discoveryd) with Mavericks versions of those files. There are other suggestions such as simply unloading the modules, but that disables networking functionality.
Has anyone tried these methods with any...
No solution currently. Same problem with MultiBeast 6.3 (current as of today).
The only workaround I know of is to keep around MultiBeast 5.4.3 for the express purpose of installing an old audio driver...
Still no audio using the latest Multibeast (current as of this posting) ALC887 Current. Had to use the MultiBeast 5.4.3 version of the same driver to get working audio.
I am having the same problem. I only noticed it recently (post 10.9.2 update) but I cannot say whether it would have occurred before updating or not. Using Chrome 33. (I do not install system-wide Flash.)
Any news?
Just chiming in that I was only able to fix this problem by using the old Multibeast (5.4.3) to install the ALC887 Current audio driver.
I wonder if MacMan is aware of this? Hopefully it can be fixed in a future Multibeast.
Article: Building a CustoMac: Buyer's Guide March 2013
Any comments on whether now is a good time to upgrade, as far as current costs/discounts and hardware product cycle?
Thanks for your reply. That link you sent eventually led me to find this: http://www.tonymacx86.com/mountain-lion-desktop-support/60730-mountain-lion-6xxx-gpu-issues-fix-inside.html
I followed the instructions in that thread and got everything working fine.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.