journeyman
09-30-2009, 05:47 PM
I have an EVGA X58 motherboard w/ an i7 920 CPU. It's currently running Snow Leopard 10.6.1, and almost everything works as expected. The two things that don't work are the built-in Ethernet and sleep. I've gotten around the Ethernet issue by buying a cheap PCI Ethernet card. I don't have a solution for the sleep problem.
One of the things that I noticed when booting Snow Leopard is that the S3 state wasn't listed. S0, S4, and S5 were detected, but not S3, even though it is enabled in the BIOS. I decided to remove my hacked DSDT.aml file to see what would happen, and I was surprised to see S3 detected! Furthermore, I could put the computer to sleep and wake it up again. However, without the DSDT file, I had 2 issues: (1) the CMOS was hosed on a reboot (the RTC length issue, I'm sure) and (2) the USB peripherals (like my mouse and keyboard) were unresponsive when I work the computer up from sleep. However, the computer was functioning -- I could even telnet into it.
I looked at my DSDT file and noticed that I had _S0, _S4, and _S5 entries, but my S3 entry was named SS3. I did a global replace of SS3 with _S3 in my DSDT file, compiled, installed, and rebooted. Suddenly S3 was seen. Unfortunately, while I could put the computer to sleep, it won't wake up.
It's pretty apparent to me that I have a lousy DSDT file. I don't know exactly what's wrong with it, but booting without one is almost better than booting with one. I get the same DSDT contents whether I extract the DSDT under Snow Leopard or whether I dual boot into Linux and extract it, so I don't think the quality of the DSDT is a result of the extraction program or the operating system. I think that the DSDT data associated with the motherboard is just lousy.
So, is there a way to find out what the equivalent DSDT file is that the system would use if I don't have a DSDT.aml file? Whatever the system has in place when there's no DSDT.aml file seems to be 98% of the way there. I'd like to try starting with that content and making the USB and RTC fixes to see if I can get my system fully functional. Trying to patch my existing DSDT file to account for all of the sleep issues has proven to be quite frustrating since I don't have a reference for my system to show what a good one looks like and what I'm missing.
Is this possible? I want to dump the DSDT contents from a running Snow Leopard session and NOT the contents of the BIOS. Does this even make sense? I assume that there are some compiled DSDT contents somewhere in Snow Leopard's memory....
Thanks!
One of the things that I noticed when booting Snow Leopard is that the S3 state wasn't listed. S0, S4, and S5 were detected, but not S3, even though it is enabled in the BIOS. I decided to remove my hacked DSDT.aml file to see what would happen, and I was surprised to see S3 detected! Furthermore, I could put the computer to sleep and wake it up again. However, without the DSDT file, I had 2 issues: (1) the CMOS was hosed on a reboot (the RTC length issue, I'm sure) and (2) the USB peripherals (like my mouse and keyboard) were unresponsive when I work the computer up from sleep. However, the computer was functioning -- I could even telnet into it.
I looked at my DSDT file and noticed that I had _S0, _S4, and _S5 entries, but my S3 entry was named SS3. I did a global replace of SS3 with _S3 in my DSDT file, compiled, installed, and rebooted. Suddenly S3 was seen. Unfortunately, while I could put the computer to sleep, it won't wake up.
It's pretty apparent to me that I have a lousy DSDT file. I don't know exactly what's wrong with it, but booting without one is almost better than booting with one. I get the same DSDT contents whether I extract the DSDT under Snow Leopard or whether I dual boot into Linux and extract it, so I don't think the quality of the DSDT is a result of the extraction program or the operating system. I think that the DSDT data associated with the motherboard is just lousy.
So, is there a way to find out what the equivalent DSDT file is that the system would use if I don't have a DSDT.aml file? Whatever the system has in place when there's no DSDT.aml file seems to be 98% of the way there. I'd like to try starting with that content and making the USB and RTC fixes to see if I can get my system fully functional. Trying to patch my existing DSDT file to account for all of the sleep issues has proven to be quite frustrating since I don't have a reference for my system to show what a good one looks like and what I'm missing.
Is this possible? I want to dump the DSDT contents from a running Snow Leopard session and NOT the contents of the BIOS. Does this even make sense? I assume that there are some compiled DSDT contents somewhere in Snow Leopard's memory....
Thanks!