Front USB ports not working

[errevi]

I'm struggling with 2 USB ports not working, the ports (2 front case USB ports) are working and mapped using Windows 11 and USBToolBox, but are not working with OSX.
Many thanks for your helping
EFI and ACPI Dump

 

[leesurone]

Hello @errevi . I took the liberty to visit Gigabyte website and the two pages uploaded are from your motherboard manual. Your UTBMap.kext identifies 5 different USB controllers, which may be correct, 3 of them call out a type C USB port and in some cases more than one per controller. Gigabyte shows one available from the motherboard which can enable the one of your computer case, the other is one the back panel for a total of 2.

Your UTBMap.kext shows at least 4 type C's, type 9, which is incorrect. You also do not have any ports listed as internal, type 255, which should include 1 for the RGB controller and 1 for Bluetooth if you are using an onboard card. If you have a Pcie based card for Wifi/ Bluetooth then it would be type 0.

To make a long story short your USB Port mapping is incorrect. USBToolBox is a great tool but it rarely gets it 100% right, no port mapping tool usually does, and requires the user to edit the the results by port type. Here is a blip I stole from @Edhawk that summarizes how ports should be characterized. See if it helps.

To discover the correct connector type for each Type-C port/header you need to do the following:

• Plug in a Type-C device to a type-c port and a specific port will be highlighted.
• Eject the Type-C device, flip it 180° and reinsert the device in the same port.
  • If the same port is highlighted then the connector is Type-c+switch (9)
  • If a different port is highlighted then the connector is Type-c without switch (10).
• Any virtual USB2 ports served by the Type-C port or header would need to match the physical attribute of the port or header when a Type-C device is used.
• You may not activate or use the virtual USB2 ports on the Type-C ports/header, in which case you can ignore them and leave them out of your USB configuration.
• Your PC case may not have a front Type-C port, in which case the Type-C header would not be used and can be ignored.

You need to remember the following when undertaking the USB port discovery,

1. Only Type-A USB2 physical ports (black tang) should be set with connector type USB2 (0).
2. Any Type-A USB3 physical port (red or Blue tang) should be set with connector type USB3 (3), no matter which Gen.
3. Any USB2 virtual port served from a Physical USB3 port should be set with the connector type USB3 (3) to match the physical port characteristics.
4. Any USB3 or USB2 ports served from a USB3 motherboard header should be set with connector type USB3 (3).
5. Any port or device served from a USB2 motherboard header should be set with connector type 'Internal' (255), never as USB2 (0).

Type-C ports and headers have been explained above

 

[errevi]

Thanks @leesurone, much clear now, I have only 2 USB C ports, one on the back and one on the front of the case close to the two USB 3 ports that are actually not working,
so I assume the controller is working too, will try to adjust the ports setting as you described.
I usually follow @Edhawk posts, he helped me in the past, but apparently I've missed the one you have summarized

 

[leesurone]

Thanks @leesurone, much clear now, I have only 2 USB C ports, one on the back and one on the front of the case close to the two USB 3 ports that are actually not working,
so I assume the controller is working too, will try to adjust the ports setting as you described.
I usually follow @Edhawk posts, he helped me in the past, but apparently I've missed the one you have summarized

No worries, I believe he originally posted that on a different site we also both visit.

 

[errevi]

Ok, then... I went through all the mapping process again from Windows 11 and fixed port types and names, activating only the used ones, without companions.
From config.plist I have removed the patch to rename XHC1 to SHCI as using SystemProductName = MacPro7,1 I should not need it,
XhciPortLimit is setted to FALSE.
Still the 2 front ports are not working, when I plug a USB Key it lights up once but nothing else.
Also the rear USB C port is not working.
Digging a bit more I noticed that all the ports that are not working belongs to this controller: _SB.PCI0.GPP7.UP00.DP40.UP00.DP60.XH00
All the other ports are working.
I leave here my new UTBMap.kext and updated config.plist that reflects the changes mentioned above maybe you can take a look, thanks.

 

[leesurone]

Ok, then... I went through all the mapping process again from Windows 11 and fixed port types and names, activating only the used ones, without companions.
From config.plist I have removed the patch to rename XHC1 to SHCI as using SystemProductName = MacPro7,1 I should not need it,
XhciPortLimit is setted to FALSE.
Still the 2 front ports are not working, when I plug a USB Key it lights up once but nothing else.
Also the rear USB C port is not working.
Digging a bit more I noticed that all the ports that are not working belongs to this controller: _SB.PCI0.GPP7.UP00.DP40.UP00.DP60.XH00
All the other ports are working.
I leave here my new UTBMap.kext and updated config.plist that reflects the changes mentioned above maybe you can take a look, thanks.

It could be the controller for those ports is not mapped correctly. If you see multiples listings for the same port, three is typical, then you also are seeing the controller which needs to be enabled and properly identified. That won't show in the kext but the one thing I noticed in your mapping is front port 1 and 2 are mapped as 0 and 3. If it's a USB3 port both should be identified as 3.

 

[errevi]

Thanks @leesurone , will change those ports to '3' and try as soon as I will be home.
What if the controller needs to be enabled and properly identified? Where and what have I to check?

 

[leesurone]

Thanks @leesurone , will change those ports to '3' and try as soon as I will be home.
What if the controller needs to be enabled and properly identified? Where and what have I to check?

If should show in USBToolBox. You might see several devices sharing the same set of ports, the one you didn’t plug a device into is probably the host controller. Follow the guidelines for how to map the port type.

 

[errevi]

Ok I have setted all USB3 port with value '3' but still not working, probably I do not get it...
What I see is that I have two different XH00 controllers but only one of them is working.
I took some pictures to describe the behaviour, I also attach the revised Kext:

 

[leesurone]

Ok I have setted all USB3 port with value '3' but still not working, probably I do not get it...
What I see is that I have two different XH00 controllers but only one of them is working.
I took some pictures to describe the behaviour, I also attach the revised Kext:
View attachment 15009
View attachment 15014
View attachment 15015

Wish I could be of more help. I know you shouldn't have two controllers with the same name ( 2 x XH00 ) and that may be the issue.

 

[errevi]

Many thanks for all your precious help @leesurone, this is actually above my knowledge and I don't know how to proceed...

 

[keef247]

@leesurone is a legend and very friendly/helpful.

 

[Edhawk]

A Leg end isn't that a Foot!

 

[errevi]

Hi @Edhawk
I admit I had a tough day at work and I don’t get it

 

[errevi]

ok ok, I guess I need a SSDT to rename the controller that is not working =
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/GPP7@2,1/IOPP/UP00@0/IOPP/DP60@C/IOPP/XH00@0
Am I wrong? ...Hope not
so... I got my DSDT from acpidump.exe in Windows (booted from bios boot menu, not using OpenCore to boot), rebooted in Mac, downloaded MaciASL, opened the DSDT and...
SURPISE! NOTHING HAPPENS! Nothing!
So I checked MaciASL logs to find out that...
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200925/psobject-372)
Firmware Error (ACPI): Failure creating named object [\_SB.PCI0.GPP7.UP00], AE_ALREADY_EXISTS (20200925/dswload-495)
Could not parse ACPI tables, AE_ALREADY_EXISTS

I spent hours googling... I'm lost and maybe really heading in the wrong direction, I need some hints

 

[Edhawk]

Questions:

1. Have you created an SSDT-USB-Reset.aml table?
   1. What does it show in the way of USB controllers?
2. Does Corpnewt’s SSDTTime script recommend that you Rename any of the USB controllers, i.e. XHC1?
   1. Have you added the ACPI Rename patch to your config.plist?
   2. Have you regenerated the SSDT-USB-Reset.aml table after using the ACPI Rename patch?
   3. Or manually edited the SSDT to reflect the renaming of the USB controller?
3. Are you using the Ryzen version of GenericUSBXHCI.kext?
   1. Does it make any difference to your USB port configuration?

 

[errevi]

Questions:

1. Have you created an SSDT-USB-Reset.aml table?

yes

1. 1. What does it show in the way of USB controllers?

• Does Corpnewt’s SSDTTime script recommend that you Rename any of the USB controllers, i.e. XHC1?

yes:
Gathering RHUB/HUBN/URTH devices...
- Found 5
--> \_SB.PCI0.GP17.XHC0
--> \_SB.PCI0.GP17.XHC1
----> Needs rename!
--> \_SB.PCI0.GP19.XHC2
--> \_SB.PCI0.GPP7.UP00.DP60.XH00
--> \_SB.PCI0.GPP7.XH00
----> Needs rename!

1. 1. Have you added the ACPI Rename patch to your config.plist?

yes

1. 1. Have you regenerated the SSDT-USB-Reset.aml table after using the ACPI Rename patch?

yes from ssdttime, but no changes apparently

1. 1. Or manually edited the SSDT to reflect the renaming of the USB controller?

no, I do not know from where to start honestly

• Are you using the Ryzen version of GenericUSBXHCI.kext?

not at the moment but tested it 5 minutes ago

1. 1. Does it make any difference to your USB port configuration?

yes,
IOService:/IOResources/AppleUSBHostResources/AppleUSBLegacyRoot/AppleUSBXHCI@01000000
was red so I removed the kext

@Edhawk I'm frustrated at the moment, I feel incapable to understand something probably obvious, too much info in the past days, so many searches and tries and... no results, understand me.

I attach my files down here (DSDT, OpenCore ACPI folder, OpenCore config and usbmap kext) maybe you could take a look if you have some time and tell me what I'm doing wrong,
I'd appreciate it, thanks.

 

[Edhawk]

I am happy to look at your EFI and DSDT.aml . But would rather use your full EFI for the review, Drivers and Tools folders are missing from the EFI you provided above.

 

[Edhawk]

Can you also post a fully expanded Screenshot showing your Hackintool > PCIe tab, as shown in the example below. Use the Green coloured button in the top left hand corner to expand the tab so it fits the width of your display.

Hackintool > PCIe Tab fully expanded.

 

[Edhawk]

First thing if note is that your SSDT-CPUR.aml is not matching with your Processor.

1. The SSDT uses CP00, CP01, CP02 etc for your processor.
2. Your DSDT uses C000, C001, C002, etc for your processor.
   1. DSDT Processor ID's
3. The HID device name for your processor in the SSDT is 'ACPI0007'. This device is not present in your DSDT.
   1. SSDT-CPUR Processor ID's

So if the Front USB ports are provided by the CPU then this may be part of the reason for them not working.


You need a new SSDT-CPUR.aml table that matches with your AMD Processor ID's.