Jump to content

Help: Poor DSDT is root cause of sleep problems on X58 mobo


journey63
 Share

2 posts in this topic

Recommended Posts

I have an EVGA X58 motherboard that is running Snow Leopard. Everything works great except for sleep and the 2 gigabit ethernet ports. I don't care about the Ethernet since I have a cheap PCI card that works just fine. However, sleep would be nice to have.

 

I've created a patched DSDT file that I'm using with Chameleon RC 2 w/ PC EFI 10.3 boot loader. When Snow Leopard boots, I see the following message:

ACPI: System State [S0 S4 S5] (S0)

I have both S1 and S3 enabled on my motherboard, so they should have been detected. They weren't.

 

On a hunch, I removed the DSDT.aml file from my /Extra partition. Everything booted, and I now had both S1 and S3 modes available! Not only that, I could put the computer fully to sleep and wake it up with the USB keyboard!

 

Unfortunately, I still had problems. Without the DSDT file, I couldn't move the mouse or hit a key when the computer woke up. I could telnet into it, so it was working. I just couldn't use anything attached to a USB port. Furthermore, when I rebooted the computer, my CMOS had been cleared.

 

So it appears that a poor DSDT file is the root cause of my computer's sleep issues. Here's the question: is it possible to extract out the default DSDT file that Snow Leopard uses if a DSDT.aml file isn't found? If I can do that, I can then add the patches to the DSDT file to fix the CMOS issue and the USB issue (based on other posts).

 

So, how would you go about getting the default DSDT values used by Snow Leopard when no DSDT file is present?

 

Thanks in advance!

 

UPDATE: I just got the system to recognize S3! It turns out that my DSDT was using _S0 and _S4 for states S0 and S4, but for S3 it was using SS3. I did a global replace of SS3 with _S3, recompiled the DSDT file, installed, and rebooted. Now S3 mode is recognized. Unfortunately, it won't wake up after going to sleep. The fans start and it makes the right noises. However, there's no display, and I can't telnet into it. I'm forced to reboot by holding down the power key. Plus I have to turn off the power supply and remove the USB keyboard & mouse for a few seconds because, if I didn't, it would boot up without finding a keyboard.

Link to comment
Share on other sites

  • 1 month later...
 Share

×
×
  • Create New...