Jump to content

[GUIDE] USB Fix El Capitan 10.11

pokenguyen

By pokenguyen,
in OSx86 10.11 (El Capitan)

 Share
829 posts in this topic

Recommended Posts

mnfesq
mnfesq
Posted
Posted

 

Can somebody remove the two errors... i don't know a lot about DSDT... i would love to get my USB3 working....

 

Or can someone explain what the 2 errors are? I can not compile it....

 
Like most of us... the USB3 ports are working .... only with usb2 devices... when connecting a usb3 device, it is just not found...

 

 

Upload the .dsl, not the .aml.  When I complied what you uploaded, I had over 200 errors.  That's common.

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

@shot - i had a similar issue not long ago - seems like i got a newer IASL compiler and was able to decompile without getting a bunch of lines "zero" lines and errors. it maybe that the compiler is too old to decompile the .aml file properly so i would try that.  the IASL in the MacIASL you used is from 2012.

 

you may want create a port injector to define your ports vs doing it in DSDT.

Link to comment
Share on other sites
schot
schot
Posted
Posted

@shot - i had a similar issue not long ago - seems like i got a newer IASL compiler and was able to decompile without getting a bunch of lines "zero" lines and errors. it maybe that the compiler is too old to decompile the .aml file properly so i would try that.  the IASL in the MacIASL you used is from 2012.

 

you may want create a port injector to define your ports vs doing it in DSDT.

Thanks, I downloaded the now the version on Insanely Mac..... and update my new DSDT.dsl

 

 

Upload the .dsl, not the .aml.  When I complied what you uploaded, I had over 200 errors.  That's common.

 

 

this is the .dsl file... i can not make an .aml file of it... got errors....

@shot - i had a similar issue not long ago - seems like i got a newer IASL compiler and was able to decompile without getting a bunch of lines "zero" lines and errors. it maybe that the compiler is too old to decompile the .aml file properly so i would try that.  the IASL in the MacIASL you used is from 2012.

 

you may want create a port injector to define your ports vs doing it in DSDT.

I tried that with the dummy kext but no USB worked then at all no USB2 nor USB3 ... i renamed it in my dummy kext to XHC and removed te ports.

Normally al ports works even the USB3 ones only not with USB3 devices... Also tried with different smbios

MSI H87-G41 PCMate NEW DSDT.zip

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

@schot 

 

are you decompiling something like this?

 

# iasl -dl -e ssdt*.aml -d dsdt.aml

 

which means you decompile in context of all ACPI tables. and it will spit out legacy code which is less likely to emit errors upon recompile.

 

see the comment in your .dsl file

 

 

 

   /*

     * iASL Warning: There were 12 external control methods found during
     * disassembly, but additional ACPI tables to resolve these externals
     * were not specified. This resulting disassembler output file may not
     * compile because the disassembler did not know how many arguments
     * to assign to these methods. To specify the tables needed to resolve
     * external control method references, the -e option can be used to
     * specify the filenames. Note: SSDTs can be dynamically loaded at
     * runtime and may or may not be available via the host OS.
     * Example iASL invocations:
 
     *     iasl -e ssdt*.aml -d dsdt.aml
Link to comment
Share on other sites
schot
schot
Posted
Posted

 

@schot 

 

are you decompiling something like this?

 

# iasl -dl -e ssdt*.aml -d dsdt.aml

 

which means you decompile in context of all ACPI tables. and it will spit out legacy code which is less likely to emit errors upon recompile.

 

see the comment in your .dsl file

 

 

 

   /*

     * iASL Warning: There were 12 external control methods found during
     * disassembly, but additional ACPI tables to resolve these externals
     * were not specified. This resulting disassembler output file may not
     * compile because the disassembler did not know how many arguments
     * to assign to these methods. To specify the tables needed to resolve
     * external control method references, the -e option can be used to
     * specify the filenames. Note: SSDTs can be dynamically loaded at
     * runtime and may or may not be available via the host OS.
     * Example iASL invocations:
 
     *     iasl -e ssdt*.aml -d dsdt.aml

 

 

Well.... i don't know i used MaciASL here in the downloads from september 2015 and clicked on new -> from DSDT

and then tried to compile it, so i can use it with Clover....

 

 

for the injector where is this placed? In the root of /S/L/E or elsewhere within the IOUSB kext ?

 

thanks

in S/L/E otherwise it won't work at all.

post-77462-0-56417300-1445005296_thumb.png

Link to comment
Share on other sites
bOLEMO
bOLEMO
Posted
Posted

Extremely confused about getting USB working on El Capitan with Asus X99 Deluxe MB.
 
I read that ASMedia chipsets are not supported yet, period.
I read somewhere else that someone had it working OOB on the ASMedia ports.
 
Anyway, I have an Asus X99 Deluxe with i7 5820K and working great under Yosemite (GenericUSBXHCI + Clover USBFix). All USB ports are working as they are supposed.
 
Under El Capitan, it is a totally different story… Only two USB3.0/2.0 rear ports are working, all others are off. I thought that it was the Intel USB ports from the X99 chipset, and all the non working ones the ASMedia controlled ones.
 
It appears that it is not the case!
 
The Asus X99 Deluxe has 8 rear USB 3.0/2.0 ports and 2 USB2.0 ports. There is 2 internal USB3.0 headers and 2 USB2.0 headers. I am using both USB3.0 internal header for the front panel of my PC case, giving me 3 USB3.0 plugs and a SD card reader.
 
Here is the back of the Asus X99 Deluxe: 
wireless.jpg
 
Here are the official specifications: https://www.asus.com/Motherboards/X99DELUXE/specifications/ where we can read:

Intel® X99 chipset :
4 x USB 3.0/2.0 port(s) (4 at mid-board
Intel® X99 chipset :
6 x USB 2.0/1.1 port(s) (2 at back panel, , 4 at mid-board)
ASMedia® USB 3.0 controller :
10 x USB 3.0/2.0 port(s) (10 at back panel, blue)

 
And here: http://techreport.com/review/26973/asus-x99-deluxe-motherboard-reviewed an interesting article indicating that:

Another ASMedia controller powers the two USB 3.0 ports on the left side of the rear cluster. The other eight ports are driven by just two USB connections in the chipset, each of which is shared via a four-way ASMedia hub.

 

I also tried every port with a USB3.0 thumbdrive, and found this:

MB rear USB ports (cf picture):
                            ___
USB2.0:                   5|___|                   \
                            ___                     | Intel X99 chipset (direct)
USB2.0:                   6|___|                   /
--------------------------------------------------
        |   ___    ___  |   ___    ___  |   ___  
USB3.0: | 9|___| 7|___| | 5|___| 3|___| | 1|___|   \
        |   ___    ___  |   ___    ___  |   ___     | ASMedia Controller
USB3.0: |10|___| 8|___| | 6|___| 4|___| | 2|___|   /
        |               |               |
        |  ASM107x HUB  |  ASM107x HUB  | direct (no hub)
        |               |               |

On Yosemite, I was able to figure out that USB3.0 ports 1 and 2 are direct ports to the ASMedia controller, and they are the only ones working on El Capitan (USB2 and USB3 devices)!!!

USB3.0 ports 3, 4, 5 and 6 are under an ASM107x hub. Hub is shown under Yosemite (System Info), not under El Capitan.

USB3.0 ports 7, 8, 9 and 10 are under another ASM107x hub. Again showing under Yosemite, not El Capitan.

USB2.0 ports 5 and 6 are direct Intel X99 chipset, not working under El Capitan.

USB3.0 front ports (from mid-board) are direct Intel X99 chipset, not working under El Capitan.

 

I know from reading the forums that the ASM107x can be recognized, since it is only a hub, and someone got it working OOB.

I know that the Intel chipset should be recognized by El Capitan.

The ASMedia chipset is not supposed to be working under El Capitan, but the only 2 ports working for me are controlled by ASMedia chipset (not hub).

 

I use the same DSDT under Yosemite and El Capitan. I removed port limitations editing El Capitan kext, without success.

 

Any idea on how to fix that?

Thank you for your attention and your help.

 

Attached is the original BIOS DSDT.

DSDT-or.aml.zip

Link to comment
Share on other sites
Lord Kamina
Lord Kamina
Posted
Posted

Has anybody made progress getting Renesas chipsets to work? Mine are detected but are unusably slow. Am trying some tweaks with the injector kexts but not much in the way of progress yet.

 

Does anybody have a chipset (any, ideally not-intel though) that works properly and via AppleUSBXHCIPCI proper (there are several different iomatch sections in that kext)? I need an IOReg so I can see how it looks on a working machine.

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

@xenophon

 

really? what is wrong with it?

 

# iasl -h

Supports ACPI Specification Revision 6.0

 

Usage: iasl [Options] [Files]

Options:

 

General:

  -@ <file>         Specify command file

  -I <dir>          Specify additional include directory

  -T <sig>|ALL|*    Create table template file for ACPI <Sig>

  -p <prefix>       Specify path/filename prefix for all output files

  -v                Display compiler version

  -vo               Enable optimization comments

  -vs               Disable signon

 

Help:

  -h                This message

  -hc               Display operators allowed in constant expressions

  -hf               Display help for output filename generation

  -hr               Display ACPI reserved method names

  -ht               Display currently supported ACPI table names

 

Preprocessor:

  -D <symbol>       Define symbol for preprocessor use

  -li               Create preprocessed output file (*.i)

  -P                Preprocess only and create preprocessor output file (*.i)

  -Pn               Disable preprocessor

 

Errors, Warnings, and Remarks:

  -va               Disable all errors/warnings/remarks

  -ve               Report only errors (ignore warnings and remarks)

  -vi               Less verbose errors and warnings for use with IDEs

  -vr               Disable remarks

  -vw <messageid>   Disable specific warning or remark

  -w1 -w2 -w3       Set warning reporting level

  -we               Report warnings as errors

 

AML Code Generation (*.aml):

  -oa               Disable all optimizations (compatibility mode)

  -of               Disable constant folding

  -oi               Disable integer optimization to Zero/One/Ones

  -on               Disable named reference string optimization

  -cr               Disable Resource Descriptor error checking

  -in               Ignore NoOp operators

  -r <revision>     Override table header Revision (1-255)

 

Optional Source Code Output Files:

  -sc -sa           Create source file in C or assembler (*.c or *.asm)

  -ic -ia           Create include file in C or assembler (*.h or *.inc)

  -tc -ta -ts       Create hex AML table in C, assembler, or ASL (*.hex)

  -so               Create offset table in C (*.offset.h)

 

Optional Listing Files:

  -l                Create mixed listing file (ASL source and AML) (*.lst)

  -lm               Create hardware summary map file (*.map)

  -ln               Create namespace file (*.nsp)

  -ls               Create combined source file (expanded includes) (*.src)

 

Data Table Compiler:

  -G                Compile custom table that contains generic operators

  -vt               Create verbose template files (full disassembly)

 

AML Disassembler:

  -d  <f1 f2 ...>   Disassemble or decode binary ACPI tables to file (*.dsl)

                      (Optional, file type is automatically detected)

  -da <f1 f2 ...>   Disassemble multiple tables from single namespace

  -db               Do not translate Buffers to Resource Templates

  -dc <f1 f2 ...>   Disassemble AML and immediately compile it

                      (Obtain DSDT from current system if no input file)

  -df               Force disassembler to assume table contains valid AML

  -dl               Emit legacy ASL code only (no C-style operators)

  -e  <f1 f2 ...>   Include ACPI table(s) for external symbol resolution

  -fe <file>        Specify external symbol declaration file

  -in               Ignore NoOp opcodes

  -vt               Dump binary table data in hex format within output file

 

Debug Options:

  -bf               Create debug file (full output) (*.txt)

  -bs               Create debug file (parse tree only) (*.txt)

  -bp <depth>       Prune ASL parse tree

  -bt <type>        Object type to be pruned from the parse tree

  -f                Ignore errors, force creation of AML output file(s)

  -m <size>         Set internal line buffer size (in Kbytes)

  -n                Parse only, no output generation

  -ot               Display compile times and statistics

  -x <level>        Set debug level for trace output

  -z                Do not insert new compiler ID for DataTables

Link to comment
Share on other sites
xenophon
xenophon
Posted
Posted

I'm probably wrong on this, but it did throw an error on my system.

 

If you have a minute, can you please update me on MacIASL installation (the /usr/bin/iasl command I'm talking about) - can't figure it out :-(

 

(Sorry for the off-topic remark).

 

TIA

 

Xen

Link to comment
Share on other sites
TheRacerMaster
TheRacerMaster
Posted
Posted

I use the same DSDT under Yosemite and El Capitan. I removed port limitations editing El Capitan kext, without success.

 

Any idea on how to fix that?

Thank you for your attention and your help.

 

Attached is the original BIOS DSDT.

Try this DSDT. All I did was rename EHC1/EHC2 to EH01/EH02 & change _OSI to simulate OS X as Windows 8.1. Post an IOReg afterwards.

DSDT-or 2.aml.zip

Link to comment
Share on other sites
bOLEMO
bOLEMO
Posted
Posted

Try this DSDT. All I did was rename EHC1/EHC2 to EH01/EH02 & change _OSI to simulate OS X as Windows 8.1. Post an IOReg afterwards.

I did try the EHC1/EHC2 to EH01/EH02, with a kext_injector and IOJones shows the change is successful. Does not change my problem (only 2 ports working).

However, I did not change _OSI, so I will try that, and post IOReg afterwards.

 

Just tried the provided DSDT. Not working, same problem.

It is like all USB ports from intel chipset are not activated, and all ports behind the ASM107x hubs are not activated either.

 

IOReg is attached.

 

IOReg.ioreg.zip

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

@Larx

 

decompile the aml file and the search for EUSB and USBE -- those seem to be your USB2 devices on address 1D and 1A.

 

if i were you, I would just create an usb port injector type kext vs mucking with DSDT.

  • Like 1
Link to comment
Share on other sites
Larx
Larx
Posted
Posted

@Larx

 

decompile the aml file and the search for EUSB and USBE -- those seem to be your USB2 devices on address 1D and 1A.

 

if i were you, I would just create an usb port injector type kext vs mucking with DSDT.

 

Thx for advice. I will try that !

Link to comment
Share on other sites
TheTourist
TheTourist
Posted
Posted

Can someone explain how to properly inject hubs like this?

Thanks

 

 

Hello!

Trying to make port restriction on laptop.

 

Added ports to dummy kext, but USB still not working.

Can someone tell what i doing wrong?

 

SMBIOS is MacBookPro 9,2

Attached DSDT and Info.plist from DummyEHCI

 

Thanks!

 

Snymok_ekrana_2015_10_04_v_19_42_46_500.

 

Snymok_ekrana_2015_10_04_v_19_47_44_800.

 

Link to comment
Share on other sites
Maniac10
Maniac10
Posted
Posted (edited)

I'm not sure if I'm doing this right but for my Z68AP-D3 it works like this:

 

post-158318-0-29799900-1445381422_thumb.png  post-158318-0-17206200-1445381934_thumb.png

 

For this you'll need to remove all ports from "MacBookPro9,2-EHC1" but "PRT1", that correspond to the higher level one on your DSDT. Then create another section called MacBookPro9,2-EHC1-PRT1-hub with all your ports inside. Beware the keys on this hub are a bit different, here's an example:

		<key>MacBookPro8,3-EH01-PR10-hub</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AppleUSBMergeNub</string>
			<key>IOClass</key>
			<string>AppleUSBMergeNub</string>
			<key>IOProbeScore</key>
			<integer>5000</integer>
			<key>IOProviderClass</key>
			<string>AppleUSB20InternalHub</string>
			<key>IOProviderMergeProperties</key>
			<dict>
				<key>port-count</key>
				<data>
				CAAAAA==
				</data>
				<key>ports</key>
				<dict>
					<key>PRT1</key>
					<dict>
						<key>UsbConnector</key>
						<integer>255</integer>
						<key>port</key>
						<data>
						AQAAAA==
						</data>
					</dict>
                                        . . . 
				</dict>
			</dict>
			<key>locationID</key>
			<integer>487587840</integer>
			<key>model</key>
			<string>MacBookPro8,3</string>
		</dict>

I'm not sure about having 2 PRT1 items, perhaps you'll have to rename one on your DSDT and plist to something else. And remember that if you rename the higher PRT1 one then MacBookPro9,2-EHC1-PRT1-hub must be renamed accordingly.

Edited by Maniac10
Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

I'm not sure if I'm doing this right but for my Z68AP-D3 it works like this:

 

attachicon.gifioreg.png  attachicon.gifplist.png

 

For this you'll need to remove all ports from "MacBookPro9,2-EHC1" but "PRT1", that correspond to the higher level one on your DSDT. Then create another section called MacBookPro9,2-EHC1-PRT1-hub with all your ports inside. Beware the keys on this hub are a bit different, here's an example:

		<key>MacBookPro8,3-EH01-PR10-hub</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AppleUSBMergeNub</string>
			<key>IOClass</key>
			<string>AppleUSBMergeNub</string>
			<key>IOProbeScore</key>
			<integer>5000</integer>
			<key>IOProviderClass</key>
			<string>AppleUSB20InternalHub</string>
			<key>IOProviderMergeProperties</key>
			<dict>
				<key>port-count</key>
				<data>
				CAAAAA==
				</data>
				<key>ports</key>
				<dict>
					<key>PRT1</key>
					<dict>
						<key>UsbConnector</key>
						<integer>255</integer>
						<key>port</key>
						<data>
						AQAAAA==
						</data>
					</dict>
                                        . . . 
				</dict>
			</dict>
			<key>locationID</key>
			<integer>487587840</integer>
			<key>model</key>
			<string>MacBookPro8,3</string>
		</dict>

I'm not sure about having 2 PRT1 items, perhaps you'll have to rename one on your DSDT and plist to something else. And remember that if you rename the higher PRT1 one then MacBookPro9,2-EHC1-PRT1-hub must be renamed accordingly.

Do your USB3 ports work?

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

Yes but only with USB3 devices.

Interesting. According to the specifications, you have Etron EJ168 chipset. Nonetheless I'll try it with my board, when I'm at home again.

iMac16,x and iMac17,x are still no where to be found in the 10.11.1 USB kexts.

What are their board-id's?

Link to comment
Share on other sites
Lord Kamina
Lord Kamina
Posted
Posted

Is it possible to use XHCIUsbMux + FakePCIId with not-intel chips? I'm not asking whether it wil work; I'm asking whether it's possible to use it to inject properties for other chips (By modifying the IOMatch to make it attach to said device, obviously)

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...