Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Matthew L.

  • Content count

  • Joined

  • Last visited

About Matthew L.

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  1. Master Chief's P5K PRO ACPI Warfare

    My guess is Master Chief, the source this snippet for our DSDTs. It looks like you do. Anyways, I will, as soon as Chief replies on this thing.
  2. Master Chief's P5K PRO ACPI Warfare

    Well, I'll stick to my statement until someone proves otherwise. If I'm right, and our CPUPM kext strictly follows the ACPI Specification, there should be no problems, because we (our ACPI tables) tell OSPM what and how to do, but let's wait for a really experienced guy's reply on this.
  3. Master Chief's P5K PRO ACPI Warfare

    IMHO it's the exact opposite, and to prove it, take a peek at the Example in the ACPI Spec rev. 4.0 page 329, where it says "[...] OSPM will be required to coordinate the P-state transitions between the two processors and can initiate a transition on either processor to cause both to transition to the common target P-state." and the value in the example code is 0xFD.
  4. DSDT fixes for Gigabyte boards

    Hmm... Unfortunately power still doesn't go off when going to S5. As I've been reading some info in the ACPI spec and the ICH9 datasheet I've found that _PRW and _PSW are responsible per device for choosing the correct device state depending on global state. It looks like that OS X thinks USB devices should wake up the sleeping (S5) system, therefore it doesn't cut power and leaves the USB in D2 (or D1? and it stays like this till the next power on's USB re-init by the BIOS), even if the corresponding function in the BIOS is off. It should be the USBW's value that does this, shouldn't it? P.S: I have the Wake for Ethernet network access option turned off in Energy Saver, does that really wake the PC occasionally, and can it make a difference in this kind of problem?
  5. DSDT fixes for Gigabyte boards

    Well, yeah, I've noticed this similarity in all of the devices that are part of the GPE scope, but I wasn't sure you can just grab any unused value and use it. Thanks! Original _WAK method: Method (\_WAK, 1, NotSerialized) { Store (0xFF, DBG1) If (LEqual (Arg0, 0x03)) { Store (0x8F, SCP) } If (LEqual (Arg0, 0x04)) { If (LEqual (OSFL, 0x00)) { If (LEqual (OSFX, 0x03)) { Store (0x59, SMIP) } Else { Store (0x58, SMIP) } } If (LEqual (OSFL, 0x01)) { Store (0x56, SMIP) } If (LEqual (OSFL, 0x02)) { Store (0x57, SMIP) } If (LEqual (OSFX, 0x03)) { Store (0x59, SMIP) } } If (LEqual (Arg0, 0x01)) {} If (OSFL) { Notify (\_SB.PWRB, 0x02) } Else { If (LEqual (RTCW, 0x00)) { Notify (\_SB.PWRB, 0x02) } } Notify (\_SB.PCI0.USB0, 0x00) Notify (\_SB.PCI0.USB1, 0x00) Notify (\_SB.PCI0.USB2, 0x00) Notify (\_SB.PCI0.USB3, 0x00) Notify (\_SB.PCI0.USB4, 0x00) Notify (\_SB.PCI0.USB5, 0x00) } Current method: Method (_WAK, 1, NotSerialized) { Store (Zero, \_SB.PCI0.LPCB.EC.ECSS) \_SB.PCI0.SBUS.ENAB () Store (0xFF, DBG1) Notify (\_SB.PWRB, 0x02) PNOT () Notify (\_SB.PCI0.UHC1, Zero) Notify (\_SB.PCI0.UHC2, Zero) Notify (\_SB.PCI0.UHC3, Zero) Notify (\_SB.PCI0.UHC4, Zero) Notify (\_SB.PCI0.UHC5, Zero) Notify (\_SB.PCI0.UHC6, Zero) Notify (\_SB.PCI0.POP2, Zero) Return (Package (0x02) { Zero, Zero }) } As I see there shouldn't be anything that does anything like this. (SCP is about thermal policy and SMIP is about the SMBus controller's interrupt pin.) So are there any users whose keyboards/mice LEDs light up as they press a key after the computer has been shut down by Snow Leo? (Negatives are important too, so please, report, but in a non-polluting way, so make your posts have something else in them.) @ FormerlyKnownAs: You've been trying dropssdt=no and enabling c-states + EIST in your bios while your model was MacPro3,1 right? Then if that's the case, the only (maybe) relevant differences in our DSDTs are the PNOT method and the defined PDCns, nothing else (except the defined frequencies and power). You may need a wizard to help you, because it really should work. (BTW, how was it working earlier?)
  6. DSDT fixes for Gigabyte boards

    Thanks, it works great! (I've finally banished DTGP from my DSDT.) How do I know which GPE values can I use for the firewire device?
  7. DSDT fixes for Gigabyte boards

    How come now you allow the first core to go deeper than C1? Hehe, okay. Let me ask you something about MCDP: how can I use it for device customizations longer than a package of 2? (For example, HDEF.)
  8. DSDT fixes for Gigabyte boards

    One more thing guys! At the first CPU's C-states I'm seeing different entries. There are two types: Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x9D, 0x03E8 }, }) } and Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, 0x9D, 0x03E8 } }) } Which one is correct?
  9. DSDT fixes for Gigabyte boards

    Hehe, okay, we'll see. Understood, thanks! Oh Sir, you aren't the one who should apologize. I'm a student, a young dude, sometimes with too much free time, and you are the one who's got a job, family, etc. so I'm the one who shouldn't bother you with all those lil' unimportant things.
  10. DSDT fixes for Gigabyte boards

    Hello fellow hack(intosh)ers! I have some questions there, mostly strange ones. Here comes the most important one: If I tell OS X to shutdown my PC, after shutdown, USB power will be still on, so if I press a key on my keyboard I see its' numlock led lighting up (as long as I hold the key pressed), or if I click with my mouse I can see its' red light (just for a fraction of a second, then it goes off). Any ideas there? (And of course, using windows there is no such problem.) I've got a bit of coder's questions, which should be easy ones: in my DSDT there are some really idiotic _CRS methods in device FWHB and PCI0.EXPL, the thing I'm asking you is the return's importancy - wouldn't it be more logical if the code would be there without the need to return? near the above mentioned devices there is a MEM device too. Is there any use of it on Mac OS X, or can I just remove it? I've attached my DSDT there, and thanks in advance to the readers and helpers! P.S: Ah, and Master Chief, thanks for your great methods, especially MCDP! Matthew Source.dsl.zip
  11. Ok then, I was starting to think that I was torturing my CPU for days... BTW, is there any good explanation for the bold part? It's strange, but does happen with mine too. (How come it doesn't hurt the CPU if it changes voltages for nothing so often?)
  12. Uh-oh. Something must be wrong at me, can you please upload your DSDT? (My cpu's cores always change states simultaneously, and really often.) Stupid speedstep jumps up and down while just browsing the web (no flash content) with playing music and downloading torrents in the background.
  13. DSDT fixes for Gigabyte boards

    Exactly, Chief, that did the job! Defined PDCs 0-3 as external variables, and done! Thanks a million, again!
  14. DSDT fixes for Gigabyte boards

    So, the problem starts at PDCs. You said I've turned my _PR scope into a worse one, from my 'most perfect' one. (See your post #141 in this thread.) Then if I want to change it back to the good one, I have to add 3 more PDCs, namely PDC1, PDC2 and PDC3 (which aren't defined, because you defined only one when writing that 'most perfect' _PR scope for me, PDC0), because PNOT checks 4 PDCs, not only 1. So that's where the question starts: just remove all other PDC statements in PNOT, or remove the PNOT method itself, or what is the solution in this case? (I've sent you my wild guess in a PM.)
  15. DSDT fixes for Gigabyte boards

    I've been asking Master Chief for a working PNOT implementation with this type of _PR scope too, so we're going to get a suggestion from him a bit later I think.