I have been putting off updating for a while and I haven't been following best practices at all. =/. I got hasty and didn't back up because I still had an el capitain install that I could use to login to fix things. I can't remember what version I'm upgrading from, heh.
As my profile mentions...
lol, I had an almost exact opposite experience, visoneer. I had a previous install of mavericks but I was on very different hardware. I tried getting that up and running but got no such luck unless I was using -x. I had little trouble getting unibeast mavericks install working off of USB. I used...
No, I have a gtx 660, I just kept trying solutions at random to get into setup.
I still need GraphicsEnabler=No but I no longer use PCIRootUID=1 and I just leave it to default (0 I think).
vlad, eddy, are you seeing sound assertions like I did?
I get stuck at the same message if I see sound assertions. (I also saw the bluetooth messages but I ignored them). The only way around it for me is removing the applehda kext from /S/L/E/. I can then come up but not have audio working...
Yea, it's no use. I get one set of sound assertions or another depending on what solution I try. I cleared out all non-Apple kexts and reran Multibeast (v6.2.2). I still get the same assertions:
May 23 04:37:15 Amrs-Mac-Pro kernel[0]: Sound assertion in AppleHDACodecGeneric at line 1276
May 23...
How did you "update your Audio driver" ?? I'm running a Z97X-UD3H and I can't seem to get the Audio working. I'm getting a LOT of Sound assertions and it won't boot after that. Only way around it is by going into single user mode and deleting/moving AppleHDA.kext. Any ideas?
Thanks
Thanks for the tip.
I tried installing both the framework and the latest kext from the 10.8.2 directory in the link you posted as per aolive's instructions.
Still no luck, same symptoms.
It's sad but I think I've given up on getting sleep to work on this machine. =(
The baffling thing is that many people got it to work with my exact same hardware. and it works with my exact same hardware for 10.6.8.
I've posted this on other forums without any luck of getting an answer.
No...
I disconnected my second monitor and thought I would try with just 1 monitor. Also, this is how my system.log looks like when I try to put it to sleep.
Aug 9 18:34:01 Kuroi.local WindowServer[101]: Created shield window 0xbd for display 0x2b284bd1
Aug 9 18:34:01 Kuroi.local...
I tried switching out the GTX 260 card for an older ATI 3870 just to test if it is the video card. Still the same behavior, this is really getting to me, :banghead:
Any more ideas? Any ideas of things I should check?
Unfortunately, still no luck...
I installed the CUDA drivers successfully.
I cut down org.chameleon.Boot.plist to look like tot's.
I repatched a fresh AppleRTC.kext
I'm using tot's dsdt.aml (I had to use a patched AppleACPIPlatform.kext to prevent the 2 min wait time during boot with this dsdt)...
dyezak:
Here's what I did for my NIC. I used an old method used in 10.5 and it worked great for me. I got it from this thread:
http://www.insanelymac.com/forum/index.php?showtopic=144639&hl=&fromsearch=1
Basically, you use a stock IONetworkFamily.kext in S/L/E and do the following:
sudo nano...
Asus + Mountain Lion = Can't wake from sleep
Ok, I think I have everything working except for wake from sleep (which works on my SL install). I can put the computer to sleep, but when I bring it up from sleep using mouse, keyboard or power button, the following happens:
Case/CPU fans spin...
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.