Intel DH77DF Motherboard

[Flavio]

This is what I could find:

30-11-12 14:21:27,000 kernel[0]: Wake reason: XHC EHC2 EHC1

After that it is:
30-11-12 14:24:20,000 kernel[0]: Wake reason: EHC2 EHC1

So XHC is the culprit for the initial immediate wake, whatever it weans.

 

[macbirdie]

Not related to your wake reasons, attaching latest DSDT that adds necessary strings for the Intel graphics driver, so HD4000 works fine without the device-properties entry in org.chameleon.Boot.plist

This time I gave it a proper extension to indicate that it's a DSDT source that needs to be compiled into a DSDT.aml file.

 

[Flavio]

Not related to your wake reasons, attaching latest DSDT that adds necessary strings for the Intel graphics driver, so HD4000 works fine without the device-properties entry in org.chameleon.Boot.plist

This time I gave it a proper extension to indicate that it's a DSDT source that needs to be compiled into a DSDT.aml file.

Tried it but doesn't work on my setup with the HD4000/HD5450 combination. With the new DSDT and without the device-properties entry in org.chameleon.Boot.plist the HD4000 graphics is not recognized.

 

[macbirdie]

Try the updated version that I reuploaded. If not, then just don't bother. I just wanted to get rid of some more stuff from the boot plist.

 

[Flavio]

What's the wake reason when machine wakes up immediately?

RE: No DSDT - that's even more interesting. That may be because of your old bios. I have latest Intel BIOS and only basics work without the DSDT tweaks. Maybe the machine even sleeps, but then it wakes up immediately, every time.

Your org.chameleon.Boot.plist file can be reduced to this I think:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>AtiConfig</key>
<string>Eulemur</string>
<key>GraphicsEnabler</key>
<string>Yes</string>
<key>Kernel Flags</key>
<string>darkwake=0 PCIRootUID=1</string>
<key>Legacy Logo</key>
<string>Yes</string>
<key>Timeout</key>
<string>2</string>
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000005006201140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
</dict>
</plist>

But you'd have to check with MSRDumper if at least the P-States are generated without the chameleon options.

Ethernet is configured as built-in in DSDT, so no need for that option. You're loading the default kernel anyway, so no need for that switch as well, just like using kernel cache - it's yes by default.

If I remove the Kernel Cache = Yes entry I lose my sound??

 

[lukechip]

I tried using your latest DSDT, but got KPs at boot. Also noticed that I had both AppleIntelCPUPowerManagement (10.8.x) and NullCPUPowerMangaement in place, and that when I removed NullCPUPowerManagement, I also started getting the KPs that I've always experienced with trying to use AppleIntelCPUPowerManagement (10.8.x) - regardless of whether I had your DSDT in place or not. I haven't tried the 10.7.4 version of AppleIntelCPUPowerManagement.

I'm on BIOS v100, and didn't want to update that until I was ready to spend some time making the system stable on the new BIOS. I note MacBirdie said that with latest BIOS (which is now at v104) very little works out of the box without a DSDT.

Perhaps I need to systematically move to BIOS v104, use your DSDT, and use the latest MultiBeast to get to a stable position. Currently things are stable, but Sleep and SpeedStep are not working (states 16 and 34 only on my i7-3770). Ideally I'd like to get both Sleep and SpeedStep working.

Will post an update once I get some time to do this.

One question for MacBirdie - if I'm just using HD4000, and don't have a discrete GPU, is the DSDT you've posted still good for me ? Or does it contain specific info relevant to your other GPU ?

 

[Flavio]

Try the updated version that I reuploaded. If not, then just don't bother. I just wanted to get rid of some more stuff from the boot plist.

Does your latest DSDT work with the latest 104 BIOS?

 

[macbirdie]

I updated my bios to 104 and machine doesn't wake from sleep any more. The hardware starts back up, but the system is dead. Also, after my OS X crapping out due to installing the Late 2012 Macs update, I reinstalled it over my current installation and USB 3.0 ports stopped responding as well, even at 103 BIOS.

Back to square one!

lukechip - on the DH77DF machine I have only the HD4000, so my edits are solely for that GPU.

It's my other hackintosh that has GTX 660Ti on board. That one is based on a ASUS motherboard (P8H67M-EVO) so it's a 'little' less problematic.

Have you noticed what the KP are related to? Maybe try running the machine with dart=0 kernel option, since you have the i7 CPU that's VT-d capable. And this is known to cause some problems with 10.8.2 as Apple is putting some more security regarding attacks against virtualization into recent ACPI platform drivers.

 

[macbirdie]

I quickly started from scratch with 104's DSDT and after applying fixes regarding _T_0 (=>T_0), RTC, TIMR, HPET, renaming XHC to XHC1, adding SATA device-id so chipset is recognized and also modifying GFX0's _DSM, so the proper graphics identifier strings are added, sleep/wake is back, with vengeance! Waking up works with my keyboard and mouse, USB 3.0 is fully functional again. As always - YMMV.

Depending on whether you have an additional graphics card, you might have to change the onboard-1 to onboard-2, but I'm not sure.

Method (_DSM, 4, NotSerialized)
            {
                Store (Package (0x08)
                    {
                        "AAPL,gray-page", 
                        Buffer (0x04)
                        {
                             0x01, 0x00, 0x00, 0x00
                        }, 
                        "AAPL,gray-value", 
                        Buffer (0x04)
                        {
                             0xC3, 0x8C, 0x64, 0x00
                        }, 
                        "AAPL,ig-platform-id", 
                        Buffer (0x04)
                        {
                             0x05, 0x00, 0x62, 0x01
                        }, 
                        "hda-gfx", 
                        Buffer (0x0A)
                        {
                            "onboard-1"
                        }
                    }, Local0)
                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                Return (Local0)
            }

If that doesn't work for you at all, just change this method to the default one:

            Method (_DSM, 4, Serialized)
            {
                Name (DRET, Buffer (0x04)
                {
                     0x00
                })
                If (LEqual (Arg0, Buffer (0x10)
                        {
                            /* 0000 */   0xE1, 0x75, 0x39, 0x6F, 0x82, 0x7A, 0x67, 0x4F,
                            /* 0008 */   0x8B, 0x97, 0x15, 0xBE, 0xE0, 0x60, 0xBE, 0xDF
                        }))
                {
                    If (LEqual (Arg2, Zero))
                    {
                        CreateWordField (DRET, Zero, F0SS)
                        Store (0x02, F0SS)
                        Return (DRET)
                    }
                    If (LEqual (Arg2, One))
                    {
                        If (LEqual (^^PEG0.PEGP.LNKV, 0x03))
                        {
                            Return (Zero)
                        }
                        Return (One)
                    }
                }
                Return (DRET)
            }

Edit: Ok, I was a little too optimistic. Machine wakes up automatically after all, but at least it does wake up - wake reason EHC1 EHC2. I'll try to fix that soon. For now I have to get to work. Hopefully I won't lose the ability to wake from sleep by keyboard and mouse. Now that I have the Gmyle Bluetooth 4.0 dongle, additional problems with sleep/wake might appear. Even though it's better than yesterday.

 

[Flavio]

Did you use a special USB 3.0 motherboard cable to get USB 3.0 working?
The motherboard has three options to connect front panel USB ports:

* Blue USB 3.0 Front Panel Connector
* Yellow High Current USB 3.0 Front Panel Connector
* Black USB 2.0 Dual Port Header

Which one did you use?

I am asking because I have problems getting the front panel USB ports on my Streacom FC08 EVO case working correctly.