Contribute
Register

Working on my SSDT for USB right now; usb 3.0 header share the same string??

Status
Not open for further replies.
Ericarthurc

Ericarthurc

Joined
May 9, 2012
Messages
151
Motherboard
Acer Predator PH517-51
CPU
i7 8750H
Graphics
GTX 1070 G-Sync Panel
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. Android
So I followed Rehabman's guide and used an usb 2.0 and usb 3.0 flash drive and went through all my ports to find the correct string for them all to make a SSDT-UIAC-ALL.aml. Here is my layout;

Front

{ //Both under the same HS01 and SS01: different HubPort numbers
Front Left Blue: AppleUSB30HubPort@15110000
USB 2: HS01@14100000
USB 3: SS01@15100000

Front Right Blue: AppleUSB30HubPort@15120000
USB 2: HS01@14100000
USB 3: SS01@15100000
}

Back

Top Left Yellow
USB 2: HS03@14300000
USB 3: SS03@15300000

Top Right Yellow
USB 2: HS04@14400000
USB 3: SS04@15400000

Middle Left Blue
USB 2: HS05@14500000
USB 3: SS05@15500000

Middle Right Blue
USB 2: HS06@14600000
USB 3: SS06@15600000

{ //Both of these work though, haven't tested thunderbolt on the usb type-c though
USB3.1 Type-C
(Under RP05@1C,4)??

Bottom Left Red 3.1
(Under RP05@1C,4)??
}

Bottom Right Blue
USB 2: HS02@14200000
USB 3: SS02@15200000


I want to start making the .aml file but the problem I am having is the front usb header. Both the left and right usb ports share the same strings: HS01 for usb 2 and SS01 for usb 3. It is supposed to be like this?? From the different guides I have looked at the front headers share different strings. Is there a specific way to write this correctly in my .aml?

I attached a photo showing it as well; as you can see I plugged an extreme sandisk and patriot memory usb (both usb 3.0 btw) into the two different ports.

Thanks in advance!
 

Attachments

  • Screen Shot 2018-05-02 at 2.17.29 PM.png
    Screen Shot 2018-05-02 at 2.17.29 PM.png
    1.7 MB · Views: 138
firebat said:
So I followed Rehabman's guide and used an usb 2.0 and usb 3.0 flash drive and went through all my ports to find the correct string for them all to make a SSDT-UIAC-ALL.aml. Here is my layout;

Front

{ //Both under the same HS01 and SS01: different HubPort numbers
Front Left Blue: AppleUSB30HubPort@15110000
USB 2: HS01@14100000
USB 3: SS01@15100000

Front Right Blue: AppleUSB30HubPort@15120000
USB 2: HS01@14100000
USB 3: SS01@15100000
}
Click to expand...

It means HS01/SS01 is connected to a hub (assume your case has an internal hub).

{ //Both of these work though, haven't tested thunderbolt on the usb type-c though
USB3.1 Type-C
(Under RP05@1C,4)??

Bottom Left Red 3.1
(Under RP05@1C,4)??
}
Click to expand...

Your USB-type C is connected to your Thunderbolt controller.

I want to start making the .aml file but the problem I am having is the front usb header. Both the left and right usb ports share the same strings: HS01 for usb 2 and SS01 for usb 3. It is supposed to be like this?? From the different guides I have looked at the front headers share different strings. Is there a specific way to write this correctly in my .aml?
Click to expand...

Ports are connected to the hub. Hub is internal, so HS01/SS01 would be marked UsbConnector=255 (connected to internal/proprietary device).
 
RehabMan said:
It means HS01/SS01 is connected to a hub (assume your case has an internal hub).



Your USB-type C is connected to your Thunderbolt controller.



Ports are connected to the hub. Hub is internal, so HS01/SS01 would be marked UsbConnector=255 (connected to internal/proprietary device).
Click to expand...
Thanks Rehabman, it all worked out! Maybe you know of this issue, but sometimes on boot my keyboard and or the mouse will not work (leds light up on them but no input) and I will either have to reboot or change what USB port there in. I thought maybe a correct ssdt-uiac would resolve the issue, but it has happened twice since adding it?
 
firebat said:
Thanks Rehabman, it all worked out! Maybe you know of this issue, but sometimes on boot my keyboard and or the mouse will not work (leds light up on them but no input) and I will either have to reboot or change what USB port there in. I thought maybe a correct ssdt-uiac would resolve the issue, but it has happened twice since adding it?
Click to expand...

No idea without PR files...

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.
 

Attachments

  • Logs.zip
    3.2 MB · Views: 44
RehabMan said:
This ioreg seems to show keyboard/mouse working (both are related at HS02).
Do you have an ioreg that shows the failure scenario?

You did not implement USB power properties correctly (USBX missing).
See guide:
https://www.tonymacx86.com/threads/guide-usb-power-property-injection-for-sierra-and-later.222266/
Click to expand...
In relation to the USBX;
I haven't been able to figure it out, been having a rough time with this one. I have a desktop; z370 motherboard. I was trying to use an apple superdrive DVD drive and it keeps asking to be plugged into a Mac USB port because it requires power. So I read through that whole guide and was some what lost. I only use an ssdt and a ssdt-uiac. I am going to spend today working on it.

As for ioreg in the failure, I will try to get one today when it does it again. It happens about 20% of the time on a fresh stratup. Off the top of my head IOReg showed the device as if it's connected, no difference. There both Corsair gaming branded keyboard and mouse, and the LEDs light up on them like there receiving power, just no input.
 
Last edited:
RehabMan said:
This ioreg seems to show keyboard/mouse working (both are related at HS02).
Do you have an ioreg that shows the failure scenario?

You did not implement USB power properties correctly (USBX missing).
See guide:
https://www.tonymacx86.com/threads/guide-usb-power-property-injection-for-sierra-and-later.222266/
Click to expand...
I booted it up about 10 minutes ago and no mouse input; I got some screenshots of IOReg showing the mouse under HS02. The mouse had no input during all of those screen shots, I unplugged and replugged a couple times in that same port. (moving it to HS05 gave it input again, but in the past sometimes only a restart will work)
 

Attachments

  • screenshots.zip
    98.8 MB · Views: 48
RehabMan said:
This ioreg seems to show keyboard/mouse working (both are related at HS02).
Do you have an ioreg that shows the failure scenario?

You did not implement USB power properties correctly (USBX missing).
See guide:
https://www.tonymacx86.com/threads/guide-usb-power-property-injection-for-sierra-and-later.222266/
Click to expand...
Hey I am an idiot haha, almost had the usb power set up correctly; I spent some time this morning really reading your guide. My system doesn't have an EC, it has the H_EC in the dsdt, so I used the SSDT-EC.aml for fake EC and then added the _SB.USBX device to my SSDT-UIAC.aml and now the superdrive works, and hopefully my keyboard and mouse wont have any more issues. I used smbois 17,1 power levels for the USBX:
{
"kUSBSleepPortCurrentLimit",
0x0834,
"kUSBSleepPowerSupply",
0x13EC,
"kUSBWakePortCurrentLimit",
0x0834,
"kUSBWakePowerSupply",
0x13EC
})
My system is using smbios 18,3 but I couldn't find the correct levels for 18,3. 17,1 is most like my system and its working. Hopefully thats okay?
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top