Hey All

I have done it GFX are now fully working through through DSDT it seems the main issue was EFI strings. Let me explain I run a lot of different partitions for different reasons I have 3 snow leopard partitions 1 leopard partition there is also Linux and Windows 7 in the mix as well (see attached pic). I know its not the best but is just how things have gone as times gone by. Now I was trying to install the DSDT GFX to my SNOWGUID partition. First of all I did not remove the EFI strings from this partition's extra com.apple.Boot.plist but did remove the graphics enabler string. No joy the card would be in system profiler but i just had no QE/OpenGL working as such. So i spent some time working with DSDTSE.app as my DSDT is a bit strange any way. I try'd to many different with not much luck of inserting the graphics code with this great app (a big thank you to EvOSX86 for the app). Then I all most gave up and went back to EFI strings I say all most. My next step was thinking I have to be vanilla as possible so I disconected all of my drives apart from one and reinstalled Snow Leopard on a GUID partition and then I try'd a fresh DSDT.aml with USB SATA and GFX fix it worked how happy was I. Then I reconected my other two drives and it stopped working. So from there I applied the same fixes to my other Snow partitions, but it didn't work on my main MBR Snow partition why? It seems at some time I had written my GFX string to my Library/Preferences/SystemConfiguration/com.apple.Bootplist once deleted I had working QE/OpenGL on all my partitions. I have feel have learned a lot from from doing this and just wanted to share my experience with others may be it could be of some use. For me I have learned EFI and DSDT do not mix but maybe thats just me. Am going to finish with a question though, how does Chameleon reference Boot.plists files from other partitions it is not booting though. And before you think it yes Chameleon was separately installed on all partitions. Thank you to wwbosx and all who have posted in this thread on to my next project speedstepping and sleep thank you again to all OSX86 fans

Attached Images

Partition.jpg (8.0 KB, 71 views)

Attached Files

dsdt.dsl.zip (15.2 KB, 35 views)

So I just got a BT Apple KB, and can't wake from sleep with it. Also, doesn't even re-connect or stay connected (however it's supposed to work) after waking. I have to manually disconnect and re-connect it.
I have this UHCI/EHCI implemented, is there something else I can try? Or should I just try another BT adapter. This is the second one I've tried, the first one is an old BT v1.1, and this is a v2.1.
I believe Apple only officially supports a D-Link, and even that one has some revisions that don't allow this functionality. I have found a Kensington that's known to work for someone else, and they are using the UHCI/EHCI fix implemented in Chameleon2. I'd hate to just go out and buy it and it still not work for me.
Any ides are welcomed, thanks guys.

Hey EnzoFX,

i've got a Targus ACB10US-B (the silver 4cm one)
bought it in the US for 7$...(shipping to europe was very expensive...)

wake from sleep works via mouse, wired apple alu KB and wireless BT apple KB.
i'm on a Gigabyte G33M-DS2R on 10.6.2 via DSDT mods.




to all who have problems with wake from sleep with a USB 2.0 device:

check your _WAK section in DSDT.
after various tests, i found the solution for me:

the section for "If (LEqual (Arg0, 0x04))" should look like this:
(maybe this works only on my board...)
....
If (LEqual (Arg0, 0x04))
{
If (LEqual (OSFL, Zero))
{
Store (0x58, SMIP)
}

If (LEqual (OSFL, One))
{
Store (0x56, SMIP)
}

If (LEqual (OSFL, 0x02))
{
Store (0x57, SMIP)
}

If (LEqual (OSFX, 0x03))
{
Store (0x59, SMIP)
}
}
...

Before patching, there were some nested if clauses... i deleted them and left only the code above. Maybe this helps someone
sorry for my english.

greets

xzeroGx

Those look like operating system checks.

---

10.6.3 @ Asus P5K-SE : BIOS 1104
>>[email protected] :: 4Gb RAM Corsair :: Asus-EN8800GT@512
10.6.3 @ Asus G60Vx RBBX05 : BIOS 205
>>[email protected] :: 4Gb RAM :: GTX 260M@1024
DOS, Windows 7, OSX 10.6.2 via AsereBLN 1.1.9

You are the man. This fixed my issues on p35-DS3L and now i can wake my 10.6.4 hack using the keyboard !

No problem... Its been sooo long since I have been on this board. Glad to see some people are still using the information. I just finished putting together a machine for a friend that is having this exact problem. Hopefully it will work for his too.

---

GA EP35-DS3P - Intel Q9550 - 2 X 2GB Dominator 1066Mhz, EVGA 8800GTS 512MB
2x320Gb SATA in Software Raid 0, 1x1.5TB for Time machine and storage (Geekbench 6293)
10.6 Retail 64bit Using DSDT for audio-889a, video-8800gts, ethernet w/TM fix, USB fix, and SATA fix.
MacBook 2,1 - 10.6 Retail
MacBook 3,1 - 10.6 Retail

Hi folks!
Any idea if this fix can work on a hackintosh netbook? (It dismounts/crashes USB disks after sleep.) Any ideas? I realize this is an old thread.
thanks. Peace.

Hi all, well good news, it fix a part of the issue.

Now i can wake from an usb mouse directly connected to the mobo.

But i cant from the apple alu keyboard, although it is detected during sleep !!!

16/08/10 08:10:28 kernel Wake reason =
16/08/10 08:10:28 kernel System Wake
16/08/10 08:10:28 kernel USB (EHCI):Port 3 on bus 0xfd has remote wakeup from some device
16/08/10 08:10:28 kernel The USB device Keyboard Hub (Port 3 of Hub at 0xfd000000) may have caused a wake by issuing a remote wakeup
16/08/10 08:10:28 kernel The USB device Apple Keyboard (Port 2 of Hub at 0xfd300000) may have caused a wake by issuing a remote wakeup

but i had to wake up using power button or mouse to do this, then in the console, i see the USB controller saw the tries to wake up from USB keyboard !


Help ! what can i do to fix this ?


I've got GA P35 DS3R

here"s my DSL

Attached Files

DSDT.aml.zip (6.6 KB, 6 views)

Wow, 2 years later and @wwbsox's original post of the DSDT USB fix worked for me on a Gigabyte EP45-UD3P ... I believe it's ICH10R. Had success doing this method twice, once for the same board under 10.6.8 and one under 10.5.8.

I used these basic instructions http://tonymacx86.blogspot.com/2009/...r-dsdtaml.html to extract, modify, and compile my DSDT but had to add two fixes. Steps 1-4, 7, 8, 9.

Here's the general idea:
1) You get the DSDT tool, install it, and use it to extract your DSDT
2) You use Tonymac blog instructions about adding "Method DGTP" before the _WAK area... you only use part of the fix he mentions so don't copy/paste the whole thing...the important part of the "method" is at the beginning and then it has a sample area.
3) You find the USB section that starts with "Device (USB0)" and you'll replace the entire USB sections with the text from @wwbsox's fix in the first post here. You're basically swapping out the USB sections. I left a one-line space before and after my insertion.
4) If you just try to compile now, you'll probably get some warnings and errors so
5) One of the TonyMac comments tells you the first fix 'The gigabyte-included DSDT is flawed and will not compile. In the two error lines, change the first Local0 parameter to "Zero" (without the quotes).' What they mean is that there are two areas where you will see (Local0, Local0) and you want it to look like (Zero, Local0)
6) And add this at the end of the _WAK Method:
Return(Package(0x02){0x00, 0x00})
7) If you do it right, when you go to compile your DSDT you won't get any warnings.
8) I moved mine to /Extra, renamed it from dsdt.aml to DSDT.aml... and did a sudo chown 0:0 on the DSDT.aml file (or sudo chown root:wheel if you prefer) and sudo chmod 755 on it for good measure... and repaired permissions.... then I restarted.
9) This enabled me to sleep/wake USB drives with no device removal errors! Wooohoooo! I have used some alternative IOUSBFamily.kexts before but believe I can remove them now... If your system hangs or something, you can probably boot into single user mode (-s) and remove the DSDT.aml file from there (rename it to DSDT.bak if you want)

Good luck everybody!