The New Beginner's Guide to USB Port Configuration

Edhawk said:

Some motherboard LED connectors have a USB side to them, which needs to be included in the USBPorts.kext, USBMap.kext or UTBMap.kext, whichever you have created.

Otherwise you can end up with Sleep/Wake issues.

Click to expand...

Is there any way that I can find out if my motherboard LED connector is of this type?

Anunnaki said:

Is there any way that I can find out if my motherboard LED connector is of this type?

Click to expand...

Given that you have a 500-series Gigabyte board, I would definitely expect the LED controller to use USB. It will show up in Hackintool/USB as an "ITE Device", probably around the HS13 area.

It will need to be set with the Connector Type 'Internal' (255).

UtterDisbelief said:

Given that you have a 500-series Gigabyte board, I would definitely expect the LED controller to use USB. It will show up in Hackintool/USB as an "ITE Device", probably around the HS13 area.

Click to expand...

Thanks for your help

I used Hackintool and as you said there was an ITE device in HS11. it was set to usb2.

Edhawk said:

It will need to be set with the Connector Type 'Internal' (255).

Click to expand...

I changed the connector type to internal and exported to see what is changed in the usbports info.plist. it only changed the integer entry from 0 to 255. so in the usbports info.plist in the kexts folder I changed the integer entry to 255.

I will try to see if the problem is fixed or not. thanx a gain

Hello, thanx for your help again...
unfortunately setting connector type to internal didn't solve the issue. even the issue got worse. now sometimes after tap on sleep the system reboots.

I was kind of disappointed with this motherboard because I think it dosen't compatible with hack. I tested many ways but none of the worked. I had asus motherboard but not high end and I didn't have any of this problem. switching to the gigabyte board was a big mistake. even the xmp doesn't work properly to set the ram speed to 3600.

Any B, H or Q series motherboards are always going to be less compatible than the Z series boards using the same chipset. That is a given, and usually means you need to do more work to get it working 100% with macOS.

Apple have never used the Intel 500 Chipset or a Rocket Lake CPU in any of their systems, so this adds another layer of complexity/difficulty to your task.

It doesn't mean the motherboard isn't compatible with macOS, just that it requires more work and perseverance on your part to get it working right.

Did you follow a guide when putting your system components together and installing macOS, if yes, which guide?

Anunnaki said:

Hello, thanx for your help again...
unfortunately setting connector type to internal didn't solve the issue. even the issue got worse. now sometimes after tap on sleep the system reboots.

I was kind of disappointed with this motherboard because I think it isn't compatible with a hack. I tested many ways but none of them worked. I had Asus motherboard but not high end and I didn't have any of this problem. Switching to the Gigabyte board was a big mistake. Even the XMP doesn't work properly to set the ram speed to 3600.

Click to expand...

First,
I realize there is a language barrier that may or may not hinder our help being understood but I will reiterate the following information:
1. You have not attached or posted your USB port kext for us to look at and you have not posted a screenprint of your USB port screen from Hackintool after using the INJECT command at the bottom (the syringe) so we can see all of your ports before you have blocked or deleted them.

2. The original USB port kext in the EFI you took off of GitHub has the following ports unblocked with the following designators:HS04 0, HS07 0, HS08 0, HS09 0. HS10 0, HS11 0, SS01 9, SS03 3 SS05 3 SS06 3. THIS IS ONLY 10 PORTS OUT OF A MAXIMUM OF 15 which tells me this person does not know what he is doing although it will work with 10, even with the wrong designations, but your rear IO alone, has 14 or 15 ports so no internal ports could be used if all the rear ports are functioning as a choice.

3. XMP is not guaranteed on any manufacturer's boards with chipsets that are not Z5xx rather than B5xx whether it be Asus or Gigabyte (as Edhawk noted) and it also depends on the quality of the brand of ram. Cheap ram usually does not work at XMP speeds, the ram needs a stable/compatible chipset to perform at overclock speeds.
Since we cannot see what you are running in your EFI and You have not posted a screen-print of your Hackintool screen, we can only tell you what ports you have available, not what you may have blocked and designated in your port kext.

4. And finally what do you really need sleep for? Your machine should be fast enough that you really do not need the sleep function which was really made for slow machines in the old days. Using sleep is overrated.

UtterDisbelief thanks again lot for the guide Bro. I've used it before but somehow after having to switch from MacPro1,1 to iMac19,1 to run Ventura on my rig my USB ports were all messed up (non working USB 3.0 ports)
Re-did the guide and all is well again!

Snowy said:

UtterDisbelief thanks again lot for the guide Bro. I've used it before but somehow after having to switch from MacPro1,1 to iMac19,1 to run Ventura on my rig my USB ports were all messed up (non working USB 3.0 ports)
Re-did the guide and all is well again!

Click to expand...

Well done!

Thanks for the feedback. Much appreciated.

You need to edit the USBPorts.kext/Contents/Info.plist to reflect the SMBIOS change. As there are two places in the Info.plist where the SMBIOS Model name are used in the kext. So if you created the USBPorts.kext while using one SMBIOS, then change the SMBIOS to another Apple System, the kext needs to be edited to match this change.

This is a screenshot showing the Info.plist from the USBPorts.kext on my Asus Z97-K system, which uses the iMacPro1,1 SMBIOS.



It previously used the iMac15,1 SMBIOS. But when I installed macOS Ventura I had to change the SMBIOS to get the Haswell system working.

Without these changes only the first 15 ports macOS discovers will be active, i.e. 14 x USB2 and 1 x USB3 (usually).

So while re-creating the kext is good practice and allows you to recheck your previous work, it is not necessary to create a new USBPorts.kext when changing the SMBIOS.