After struggling a lot to get the main things up and running with a Sony Vaio that a borrowed for this month while my 1201n is being fixed, I get at the point almost everything is running like it should. Since it's a 2nd-gen I3 lappie with integrated HD3000, Atheros 9285 and Realtek 8168, I was lucky enough to get everything working without dongles or part replacements (which I couldn't do since the device is not mine).
Now I came to the fine-tuning phase, where things like power management matter. I found a patched AICPUPM that let me boot without NCPUPM without a kernel panic, and I generated a SSDT with Pike's script. I didn't measure it, but since the performance is being great since then, I assume speedstep is working fine. However, it won't sleep, and if I put it to sleep manually, the HDD less will keep showing normal activity, as well as the fans, but I won't be able to "wake" the laptop, needing a hard reboot.
I just ran the pmset -g assertions command and got this output:
Screen Shot 2013-11-12 at 7.59.37 PM.png 136.4KB 3 downloads
Since I'm working with Logic at the moment, I'll ask you to disregard any Logic/Coreaudio related stuff, as they are absolutely normal and have no relation with my system sleep issues. Earlier, when i ran the same command (unfortunately I wasn't sharp-minded enough to remember taking a screenshot at the moment) I got all the assertion status showing as zero (0) but also got the same kernel assertion at the bottom, and I'm pretty sure I got a problem with EHCI.
So that's my question: which of the EHCI patches should I apply to my DSDT? EHCI sleep or EHCI ownership (or both)? I'll attach also and IOREG and my current DSDT, just in case anyone want to take a look and see if there's something else harming system sleep that I should have noticed.
All the best!
Archive.zip 333.35KB 1 downloads