[solved] Yosemite USB 3 Problem

[RehabMan]

Sorry for the double post i just wanted to update you with my findings under 10.10.5 (not 10.11)
i was messing around with some dsdt edits and now my usb3 devices show up properly in system information.
without any clover injections or extra kexts.
I don't know if the edits are correct and if this will work in 10.11 maybe someone else could let me know.
First thing i did was to change XHC to XHC1 and then i edited the addresses of usb3 ports like this:

from "Return (Add (XSPA, Zero))" to "Return (Zero)" up to "Return (0x05)"

i tested some usb3 sticks and the speed is good.
If the edits are wrong please let me know.

You'll need to do something different in 10.11...

What was the value of XSPA? (use ACPIDebug.kext).

Try without XHC->XHC1 rename to see if it was a factor or not.

 

[octavecode]

You'll need to do something different in 10.11...

What was the value of XSPA? (use ACPIDebug.kext).

Try without XHC->XHC1 rename to see if it was a factor or not.

XHC > XHC1 doesn't really fix anything in 10.10.5, i got results after adding the addresses.

About ACPIDebug.kext do i have to use a stock dsdt or it doesn't matter?
How can i pull the XSPA value?

 

[RehabMan]

XHC > XHC1 doesn't really fix anything in 10.10.5, i got results after adding the addresses.

That's what I suspected.

About ACPIDebug.kext do i have to use a stock dsdt or it doesn't matter?
How can i pull the XSPA value?

Probably best to test with stock. Although the value may be affected by Windows version (OS Check Fix related).

Note: You can also see the _ADR assignments in IOACPIPlane in ioreg.

 

[octavecode]

Xspa = 10 ?

 

[RehabMan]

Xspa = 10 ?

Post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

 

[octavecode]

its the same thing but ok.

another thing i tried was to manually match the addresses with those from fakexhci and it was a no go.
so i guess dsdt indeed can't do what fakexhci does.

 

[RehabMan]

its the same thing but ok.

another thing i tried was to manually match the addresses with those from fakexhci and it was a no go.
so i guess dsdt indeed can't do what fakexhci does.

Not sure what you're trying to accomplish, but last I checked you were trying to determine the value of XSPA (not sure why...)

Determining XSPA....

Look at the code for SSP1._ADR:

                Device (SSP1)
                {
                    Method (_ADR, 0, NotSerialized)
                    {
                        Return (Add (XSPA, Zero))
                    }
                }

So.. _ADR returns XSPA+0.

Then look at ioreg IOACPIPlane and find SSP1... you'll note that _ADR=0x10. Conclusion: XSPA is 0x10 (16).

 

[octavecode]

i wanted match the addresses in the dsdt with those given by fakexhci so wouldnt have to use fakexhci at all.

 

[RehabMan]

i wanted match the addresses in the dsdt with those given by fakexhci so wouldnt have to use fakexhci at all.

What do you mean by 'fakexhci'?

 

[octavecode]

FakePCIID + FakePCIID_XHCI