UHCI/EHCI Built in with dsdt fix - Page 12

EnzoFX · #**111** 09-23-2009, 12:47 AM

If you get your 9800gt working perfectly in Snow LMK your method!

I got it enabled through DSDT and for some reason, switching between spaces is noticeably choppy.

I also have an initialization issue/display sleep issue. It only arises when: The display is about to sleep and before the monitor even finishes going into standby mode, quickly move the mouse to wake it up, and I get this grey static image for a few seconds or more.
So only in this instant does it happen, maybe with Chameleon's vga rom injection this could be fixed? I should look into that.

wwbsox · #**112** 09-23-2009, 01:21 AM

@Jedric

I added the fixes for usb0-usb6. I did not change the EHCI area as you stated that was working for you. It compiled with no errors. There were a few warning... related to section in your DSDT that has something to do with vcore voltage settings, but this did not prevent it from compiling. Attached is the .dsl and compiled .aml. Give them a try. If you compare the usb sections you will notice the changes. Good luck.

wwbsox · #**113** 09-23-2009, 01:49 AM

@osxfr33k

I compiled a dsdt using the latest bios rom for your board. Had some overflow error while compiling it. Might be a thing with the Asus board?? But the graphics section was added.

I am attaching the graphics section of the dsdt in a text format. Also, I am including the .dsl generated by ACPI patcher in windows (for reference) so that you can see exactly where this portion belongs in the PCI0 section. Hope this works for you.

Jedric · #**114** 09-23-2009, 02:23 AM

Quote:

Originally Posted by wwbsox

@Jedric

I added the fixes for usb0-usb6. I did not change the EHCI area as you stated that was working for you. It compiled with no errors. There were a few warning... related to section in your DSDT that has something to do with vcore voltage settings, but this did not prevent it from compiling. Attached is the .dsl and compiled .aml. Give them a try. If you compare the usb sections you will notice the changes. Good luck.

BIG THANKS wwbsox. Works great

sylvester328 · #**115** 09-23-2009, 02:46 AM

Quote:

Originally Posted by wwbsox

@ohwhyme

The problem is... trying to get the keyboard registered as USB1. This will fix wake from sleep issue.

I think even if you manage to do that, it is not really a solution. The Apple aluminium keyboard is a USB2 device because it is in fact a USB hub with two USB ports at both end. Will making it a USB1 device crapple the transfer speed of those ports? If so, I'll rather connect my mighty mouse (USB1 device) to a separate port on the motherboard and click on the mouse to wake up my hac.

wwbsox · #**116** 09-23-2009, 03:27 AM

@sylvester328

Yes, that would reduce the usb ports on the keyboard to USB1 also. Not sure... but I think those ports are usb1 anyways. The reason I say this is that when I plug a USB2 device into them, I get a message that the device needs more power than the port can provide, SL automatically ejects the device after that. Hmmm?

Yet, I have many request however from individuals that need the wake from keyboard function enabled on an apple aluminum kb. This is only one solution.

As I have stated before. I believe there is a way to patch the EHCI section of the dsdt to enable this on a high speed usb port. Just havent found it yet.

My keyboard wakes the system just fine on a EP45-DS3L with no patching at all. Not so on the EP35-DS3P.

osxfr33k · #**117** 09-23-2009, 04:48 AM

wwbsox Thanks so much. Couple quick questions. I inserted the audio part where you have it but I get an error?

This stuff here was right after PCI0 but now I noticed its at the end of the graphics script and the number in "Name (_HID, EisaId ("PNP0A03"))
Name (_ADR, Zero)
Method (^BN00, 0, NotSerialized)"

which was PNP0A08 is now PNP0A03. if I change it back to 8 I get an error so I left it alone. SO what happened to this section below? LIke I said I see it at the end of the graphics script now with a "3" instead of 8?

Name (_HID, EisaId ("PNP0A08"))
Name (_ADR, Zero)
Method (^BN00, 0, NotSerialized)
{

I even compiled your dsdt and OSX stops at the 4096 cluster and io something.

Here is the log.

wwbsox · #**118** 09-23-2009, 11:59 AM

@osxfr33k

First, keep your audio where it was. ACPI Patcher only inserts audio for alc888 and 889a codecs. Which your board doesn't have. I only generated it to see the graphics info.

Next, as far as the exact placement of the graphics info... This is where ACPI patcher put it. I don't know if it makes a difference and I don't have this board to test it.

Next, as far as the 8 or 3 thing. Don't know either. I compiled the DSDT from the bios rom file for your mother board (v1302). I have checked a few others (both Asus and Gigabyte) and all the ones I have worked on have: Name (_HID, EisaId ("PNP0A03")) under this device.

Lastly, I attached the .dsl, I forgot... For some reason, if I create a .dsl with ACPI patcher in windows, it will not compile using iasl in macOSX. Yet, if I create the .aml in windows... it will decompile and recompile fine. So this attachment has the .aml (for reference).

The best method for you is to use the DSDT you have that works. And add/change it with fixes/patches, instead of trying to use this .aml. I have no way of testing this DSDT without having the MB.

Good Luck

osxfr33k · #**119** 09-23-2009, 04:22 PM

Thanks will work on it some more. Is this extracting/patching etc similar to true hacking where one takes a compiled source code and dissasembles it, then uses a debuger to watch where the program lands it for example when the program asks for a serial then the hacker knows where ithat part of the code is being used? Then they do some trial and error changes and then assemble it and test it?

Are these DSDT.dsl files basically the same thing, starting out originally as source code that was compiled into a BIOS ROM and flashed to the MB.

We are dissasembling what was once source code but now machine code that is dissasembled??

Am I way off base with this analogy?

Because if this is kinda what we are doing no wonder it difficult to get things right.

CyCLoBoT · #**120** 09-23-2009, 05:56 PM

I am having a problem with waking my computer up using USB keyboard/mouse. I tried to replace the USB fix code in my DSDT file but I started getting KP. Anyone know how I can fix the USB wake issue on a Gigabyte EP45-DQ6 board?

I have attached my current DSDT file that I'm using.

http://www.mediafire.com/?mol3mzimzmz