Well I do indeed have an intel chipset.The author posted it in a thread for my motherboard over at insanelymac.... It's working for me....

Thanks for the info...

I removed it as it did nothing for the Wind. I guess it was a failed patch.

That patch is only for people who's computers have issues and failures when being told to shutdown or restart (you know, like NOT doing either of those?). Since our Wind's have always worked fine in that regard, the patch is useless to us

Yeah I never did it on the Wind. I keep it on my desktop though

Its simply a matter of setting a flag value for reset that some crappy bios left out in FADT (ours is enabled thus no issue). I disabled it, in FADT, as a test and yes it did in fact break reboot. The semi-useful end of the mechanics behind this is allowing users to override tables beyond DSDT from /Extra, what my previously mentioned test was really for.

ditched it (was busy) , realised that we did not need that in the first place

OK, I've never gotten into this stuff, but now that my Wind is running oh so smooth, I'm about to wipe all my machines and start fresh for real.

I've read all 18 pages of this thread and it's pretty difficult to follow to say the least. So much is in flux or testing/experimentation.

I wonder if anyone has written up a concise read-only repository of the DSDT patches including a fool-proof how-to, a list of patches and what KEXTs if any they obsolete?

Doing a little testing and I have figured out the USB removal error only exists on the two ports on the left hand USB ports. The right port works perfect when waking from sleep! What's weird is that all 3 ports are on ECH1. I am faking Device ID, but what I am wondering about is the following....

Code: Select all

            Device (EHC1)
            {
                Name (_ADR, 0x001D0007)
                Method (_S3D, 0, NotSerialized)
                {
                    If (LEqual (OSFL (), 0x02))
                    {
                        Return (0x02)
                    }

                    Return (0x03)
                }

                Name (_PRW, Package (0x02)
                {
                    0x0D,
                    0x03
                })
                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x0F)
                        {
                            "device-id",
                            Buffer (0x04)
                            {
                                0x3A, 0x3A, 0x00, 0x00
                            },

                            "AAPL,clock-id",
                            Buffer (One)
                            {
                                0x0A
                            },

                            "built-in",
                            Buffer (One)
                            {
                                0x00
                            },

                            "device_type",
                            Buffer (0x05)
                            {
                                "EHCI"
                            },

                            "AAPL,current-available",
                            0x05DC,
                            "AAPL,current-extra",
                            0x03E8,
                            "AAPL,current-in-sleep",
                            0x01F4,
                            Buffer (One)
                            {
                                0x00
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }

Wondering specifically about the code below. Now I see these values in IORegistryExplorer.app, but I am seeing them because they were injected by dsdt at boot, I am saying if I remove dsdt would I still see these values below in IORegistryExplorer.app ? can these values be played around with at all ....

Code: Select all

                           "AAPL,current-available",
                            0x05DC,
                            "AAPL,current-extra",
                            0x03E8,
                            "AAPL,current-in-sleep",
                            0x01F4,
                            Buffer (One)

On my Wind I am almost sure it is all the USB ports that get the error. Sorry I can't help you with the code.

I definitely get the error on all 3 ports.

All 3 for me.

Everyone who has patched EHCI to fake Device ID's try this.... I noticed this when doing some tests the other day.

When plugging in a usb stick to the right hand port and shutting the lid right away on my Wind resulted in me getting the USB removal error. But try this.

Step 1. Plug in USB Stick into right hand USB Port.
Step 2. Now click on the USB Stick in Finder and just select something.
Step 3. Now shut the lid on your wind and see what happens when you wake.

I found the initial shutting of the lid without actually selecting something on the USB Stick I got the error or it could be the fact it just works the 2nd time.... after that I can confirm I do not get the removal error after shutting the lid numerous times....

I don't quite understand the first part of the guide (Sleep on lid close).
Where am i supposed to write/paste the changes? Above the other changes it says something like: Find Scope (\_GPE), and modify it to look like the below:

What part of the DSDT should I find and change?


- and BTW, am I supposed to write the "snip... ...snap" parts and the comment that says "add another closing bracket"?

Download TextWrangler and when you load the DSDT.dsl do a search for what it asks, and it will jump to the area. Then edit and save. After you save the changes recompile and take the resulting DSDT.aml and put that in the Extra folder in EFI.

If you remove em , its gone. It would not show up DSDT. You can play these values if you want. These values were taken from a MacBook Air1,1 , what basically it does is that it tells the OSX on how much current the port actually has , how much it can do and how much to maintain when the laptop is on sleep. Some say its useless , some say it enables Bluetooth to work out of sleep

Trial and error it would say

Hmmm the reliability of sleep working when waking from sleep is not that good. Out of all the tests I have done BT is really intermittent, sometimes it will work, sometimes it won't....

Code: Select all

                           "AAPL,current-available",
                            0x05DC,
                            "AAPL,current-extra",
                            0x03E8,
                            "AAPL,current-in-sleep",
                            0x01F4,
                            Buffer (One)

Is BT on EHC1 ? Not that I remember, though I could be way off..... or are you just saying that the code could potentially help ?

Thanks for the reply

I have applied the Sleep on lid close patch, and it works fine with sleep.

But when I have Hibernation enabled, closing the lid still makes it sleep. On my old DSDT, it used to work. What am I doing wrong this time?

Did you get the patch to work for USB removal ?

MistaBishi

this is not a dsdt related issue. secure memory probably still is broke so disable that. Also, you may want to sudo rm /var/vm/sleepimage first.

check your settings
pmset -g

default
sudo pmset -a hibernatemode 3

0 = sleep only
1 - Hibernation only
3 - RAM contents written to disk before sleeping but will not read from ram unless power was lost.

@Sull, solution is to disable overclock.
@18seven, I'll have a look when I get on my Wind later.