UHCI/EHCI Built in with dsdt fix - Page 12

wwbsox · #1 09-22-2009, 11:07 AM

@ohwhyme

No.... Unfortunately on my board, when I disable USB2 Controller in the bios, only 2 of the rear usb ports work (USB1) and no USB2 at all. I didn't test it much, just moved the mouse from port to port. The mouse worked in only the 2 bottom ports on the board. Didn't test the 2 front usb ports. And of course the 2 USB ports on the keyboard work.

USB2 is not port specific (that would be great), its device specific. No matter what USB port you use if you plug in a USB2 device, it will register as such. Same for USB1.

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

sylvester328 · #2 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.

osxfr33k · #3 09-22-2009, 02:06 AM

wwbsox here ya go. The DSDT.dsl is the one that works I would say 100% except for the graphics not being inserted. I used DSDTSE to create the DSDT.dsl. The dropdown had separate fixes for DTGP, HPET and RTC etc and it seems that they must have gotten put into place or maybe not? I am not sure if powermanagement is working but I have sleep/awake/restart/shutdown is flawless. USB no problems.

Graphics is 7300GT 256mb, which I have changed a few things as you will see in the dsdt-graphics.dsl file. Also will be putting in a 9800 GT 512MB one day to

I would like to incorporate that into the DSDT.dsl and remove the EFI string from the com.apple.boot.plist if its possible. The Marvell Lan's work Great!! I do see kexts for the marvel in my Extra/extensions so I would like to have that ready made in the DSDT so I don't have to load them unless its not being used and its already fixed in the DSDT file?

I am unsure if the CMOS fix was done but I don't suffer any changes in my Bios? I am in Snow 10.6.1 using an Asus Maximus Formula X38 chipset with the latest Bios. I also have the GA-EP35-DS4 gigabyte that I willbe working on next after I solve the remaining minor details on this ASus Board.

I am attaching now. Hope you can help and greatly appreciated to. dsdt.dsl's generated by DSDTSE.

CAn you let me know exactly where the Graphics-dsdt.dsl script should be placed or maybe place it for me so I can see. I think I shoul dhave maybe put it further down the Device (PCI0) script or not? I got scripting erros when I merged it between the Device (PCI0) and Name (_HID, EisaId ("PNP0A08")).

Should it be placed somewhere else?

Thanks

EDITED a Few Minutes later.

It does not look like I have the RTC, CMOS nor PWRB fix? I assumed it was put into place with DSDTSE. Now I wonder if HPET and DTGP fixes are in place? If not its weird how well the DSDT is working so far except a major crash when I launch Chess is OSX. I verfied with other utils etc that acceleration is working fine.

wwbsox · #4 09-22-2009, 10:55 AM

@osxfr33k

Not all MB need the CMOS reset fix for Snow (Your Gigabyte will though)

I looked at it real quick. Method DTGP is in your DSDT, but i dont think think the placement of the graphics section looks correct. So lets get that fixed so you can remove the string from your boot.Plist.

I downloaded the latest bios rom for your board from Asus. I am going to generate a DSDT with ACPI Patcher in windows with all the fixes and graphics included.

Using that... I can compare the graphics sections and fix your DSDT. I will also upload the newly generated DSDT for you to try (after work).

EnzoFX · #5 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 · #6 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.

Jedric · #7 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

wwbsox · #8 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.

wwbsox · #9 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 · #10 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.