Jump to content


  • Content count

  • Joined

  • Last visited

About msm5

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL

Profile Information

  • Location
    United States
  1. msm5

    DSDT fixes for Gigabyte boards

    I hope you figure it out. If you do, please enlighten me!
  2. msm5

    DSDT fixes for Gigabyte boards

    I've been through this exercise 2 weeks ago when I realized my CPU only supported C1E. I use the following for C-states: Name (CST, Package (0x02) { 0x01, Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x000, 0x01,)},1,0x01,0x0384} }) 0x0384 is a value for our mobo based on an FACP table dump. [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 005A [062h 0098 2] C3 Latency : 0384 Where does 03E8 in yours come from? I understood that while the CPU may support certain C-states, the motherboard values are what populates the DSDT based on this FACP table. No matter the value here or the c-state code in the DSDT, my auto sleep still doesn't work. Here are a few shots of my BIOS settings if it helps to shed any light.
  3. msm5

    DSDT fixes for Gigabyte boards

    I've been trying to solve this problem as well. In his DSDT, I had to modify device (DMAC) for my version of the board and BIOS. Device (DMAC) { // *Renamed from (DMA1) and added two IO blocks. Name (_HID, EisaId ("PNP0200")) Name (_CRS, ResourceTemplate () { DMA (Compatibility, BusMaster, Transfer8, ) {4} IO (Decode16, 0x0000, 0x0000, 0x00, 0x10, ) IO (Decode16, 0x0080, 0x0080, 0x01, 0x11, ) IO (Decode16, 0x0094, 0x0094, 0x01, 0x0C, ) IO (Decode16, 0x00C0, 0x00C0, 0x01, 0x20, ) }) // End (_CRS) I have two SATA DVD drives (one LG, one Sony) and other USB devices (no hubs). I've tried every combination of things plugged in and unplugged and still no joy. I have been using netkas 10.5 boot file and the following extensions: fakesmc, IOAHCIBlockStorageInjector, LegacyHDA, OSXRestart, PlatformUUID. I still need to try it out without VoodooMonitor.kext. I have tried different variations of the newer boot files, however none seemed as reliable as netkas 10.5.
  4. msm5

    DSDT fixes for Gigabyte boards

    Kdawg, I have the 1.6 board and just checked this in the past week with FD bios. My code matches yours. No auto-sleep.
  5. Does this apply to other BIOS options related to p and c states? For example, the Gigabyte BIOS gives the option to enable/disable C1E and thermal monitoring (changes core voltage and frequency based on heat) as well. Should these be disabled and do the kexts also control these functions? Thanks.
  6. Hi Aargh-a-Knot, Your DSDT is great, I fixed a few things on mine from yours that I missed. Boot time is faster, speedstepping is great. I'm still baffled why this broke autosleep for me. Thanks for posting your file and looking forward to the next revision!
  7. Nice job, I'll comb through it today. I just reread your post from earlier in the week about idle temps. Mine are about low to mid 30's and my voltage is also set to auto. On Voodoo Monitor, while I see the temps and speed change, but the voltage is usually below the lowest pstate. I'll report back with my results with your DSDT.
  8. I'm right with you buddy, I've been doing the same. I also caught that post about the c-states of the q6600, which I had completely overlooked. I've attached the DSDT version that I'm currently using. Speedstepping is definitely working. I also added in audio and PATA, and adjusted the LPCB for the ICH10R. There's no graphics or LAN since they get injected at boot by netkas 10.5. This is still a work in progress, but I have found my system much more stable. The only curious thing is that sleep only works manually now. I don't know why. I've attached the file below, looking forward to comparing it with yours! msm5_EP45UD3P_Q6600.dsl.zip
  9. I've also wondered about this voltage thing and according to what I've read on this and the Gigabyte DSDT thread a generic or non-speedstepping CPU should be used to get the initial values. It's my understanding that they're dependent not only on CPU, but also frontside bus. I went with p-state calculator values mainly because they seemed to give the lowest values and most "even" spread of values. Really, though, Master Chief mentioned in his P5K PRO thread that it's what he used. So much to learn.
  10. Sorry, it's really no bother at all, it just slipped my mind. This hobby gets last dibs on my time after work, kids, dogs, etc. This DSDT file has mainly the basic fixes applied when using ACPI Patcher to include video and LAN. Are you planning on starting from scratch? EP45UD3PorigDSDT.dsl.zip
  11. Aargh-a-Knot: Glad to hear you're running well. The credit for the DSDT goes to big brains in this thread. For VoodooMonitor, I put VoodooMonitor.kext in my Extra/Extensions folder. After a reboot, you should be able to run the app without a problem. P-state changer is similar, you just have to make sure you're using the correct kext for 10.6. I understand P-state changer is more resource intense, so I uninstalled it after getting the values. They didn't jive with some of the other methods and I ended up settling with p-state calculator. I've attached a comparison of some of the values I obtained while running a generic DSDT with no speedstepping. pstate_calculator.rtf
  12. My EP35 is still a work in progress, but it's posted below. I can confirm that p-states and c-states definitely work. Sleep on the other hand is a problem. No auto sleep and manual sleep leaves the fans running and requires a hard reset. The DSDT posted by camelyasni below is excellent. I believe his C2/C3 numbers are generic. With my CPU, c-state, and p-state parameters in that DSDT, manual sleep works as well as speedstepping. A curious thing about my EP35-DS3R is in the lspci I've attached. There is an ALi USB/firewire controller listed and there has always been 4 USB entries in the system profiler that are listed as "expansion slots" which now I understand must be due to this controller. This board does not have a firewire port or plug. I need to add the ALi USB devices into the DSDT to make them built-in. Perhaps once I do this, sleep will fully work. For reference the EP35 CST info is the following (I found this in this or the Gigabyte thread and confirmed on my own): [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 0065 [062h 0098 2] C3 Latency : 03E9 I am using netkas 10.5 boot file and allowing that to inject my graphics (nvidia). Prior to this, I had it in the DSDT. My current kexts are openhaltrestart, fakesmc, LegacyHDA, PlatformUUID, and IOAHCIBlockStorageInjector. I've also attached my DSDT prior to any mods. dsdt_EP35_E6400.dsl.zip DSDT_EP35_original.dsl.zip
  13. After much reading on this thread and the Gigabyte DSDT thread I wanted to share some success. I truly only know the basics of all this and have learned so much here. Since it was mainly a p-state and c-state victory, I thought I'd post here. First, all of the improvements in this DSDT are due to the advice of many through posts and PM's. I borrowed many of the suggestions from Blackosx's posted DSDT's, so you'll see his annotations throughout the attached file since he has made a wonderful compilation of the recommendations given in both threads. My setup: GA-EP45-UD3P (rev 1.6), Q6600, nvidia 7800GT, netkas 10.5 (no ethernet or video in DSDT). P-states and C-states both work as seen in IOreg, which in addition to temps I understand is the only way to know these have been loaded. Additionally VoodooMonitor shows adjustment to the frequency and voltage. I used p-state calculator for the VID/FID numbers. Sleep works, finally. I found that the key to getting all this to work was: 1. The correct C2 and C3 according to the FACP table 2. The Device (LPCB) being correctly formatted for my motherboard 3. Ticking the "start automatically after power failure" box in system preferences. I've attached my latest DSDT files as well as an IOreg picture. Thanks for the help and hopefully this DSDT will assist someone. I'm also open to suggestions to improving this one. dsdt_EP45_UD3P_Q6600.dsl.zip
  14. I have a 7800GT in both systems listed below and I have had no problems with 10.6.2 running at 32-bit.
  15. I use a Q6600 and RC3 with no issues. Try manual installation of Chameleon...there are instructions included with the binary download.