Z690 Chipset Motherboards and Alder Lake CPU

hneryi said:

...
Yes - so in general I have a 2xDP monitor that has a built in usb hub. And in addition I have a OWC thunderbolt dock with various tb devices connected. The TB dock connects straight to MB and it does have one USB point to it. What I understand, is that - that port does NOT need mapping. OS should and has worked correctly regarldess of mapping in the past. So in the past it was as simple as adding the monitor to that dock. Though I do have my own mapping with internal usb and two ports for usage.

Click to expand...

Thunderbolt USB-C ports support both USB 3.0 and USB 2.0. Technically it is not necessary to map the USB 3.0 protocol on Thunderbolt ports because macOS discovers and configures them automatically. But if you're connecting USB 2.0 devices to those ports, they may not work unless we map the USB 2.0 protocol.

hneryi said:

... Only thing I can't connect is my monitor's hub (only 3.0 hub that I have here) or any thumb/extrnal ssd drive to any USB connections. USB 2.0 hub works fine with other peripherals than drives.

Click to expand...

Are you connecting USB 2.0 or USB 3.0 devices to the USB ports on the monitor? And I assume that a USB 3.0 (blue connector) downstream cable is connected between the Monitor and the Hackintosh?

hneryi said:

...
Will do blank ssd install of Monterey for starters and go from there.
This doesn't seem to be something anyone else is having trouble with, so seems to be isolated just for my case (that's why I'm pretty sure its software related on something old I have installed - that prevents the new version of IOUSBMassStorageDriver.kext to load or something similar).

Click to expand...

Yes, a fresh install of Monterey or any version of macOS prior to 13.2 is a good idea.

hneryi said:

...

Oh and addtion
Now that I think of it. The monitor has a built in card reader. Pretty sure that calls for the same kexts as normal thumb drives.

Click to expand...

SD and micro-SD card reader on monitor does not need a kext. It's handled by the macOS USB driver.

CaseySJ said:

Thunderbolt USB-C ports support both USB 3.0 and USB 2.0. Technically it is not necessary to map the USB 3.0 protocol because macOS discovers and configures USB 3.0 protocol automatically. But if you're connecting USB 2.0 devices, those may not work unless we map the USB 2.0 protocol.

Click to expand...

Wait. I'm probably reading this wrong but are saying that USB 3.0 ports are automatically handled by the OS and that mapping them for the 15 port limit (USBPorts.kext) isn't necessary? That only USB 2.0 ports need to be mapped - or are you only referring to USB-C and/or TB-4? Enquiring minds want to know.

poles said:

@CaseySJ There you go. Please let me know whats wrong.

Click to expand...

Because I don't know the symptoms or issues you experienced with the USB kext, I can only compare it with a USB kext I generated myself using the same USBToolBox app:

Yours is on the left, mine is on the right.

• Line 10 tells us that both maps were generated by USBToolBox
• Yours is using IONameMatch and mine is using IOPropertyMatch
• Yours does not have a model entry, mine does

I'm not an expect on USB port map kexts because I generally use SSDTs and USBInjectAll. So these observations may or may not be relevant.

Superbogey said:

Wait. I'm probably reading this wrong but are saying that USB 3.0 ports are automatically handled by the OS and that mapping them for the 15 port limit (USBPorts.kext) isn't necessary? That only USB 2.0 ports need to be mapped - or are you only referring to USB-C and/or TB-4? Enquiring minds want to know.

Click to expand...

I've revised the previous post as follows:

Thunderbolt USB-C ports support both USB 3.0 and USB 2.0. Technically it is not necessary to map the USB 3.0 protocol on Thunderbolt ports because macOS discovers and configures them automatically. But if you're connecting USB 2.0 devices to those ports, they may not work unless we map the USB 2.0 protocol.

Superbogey said:

Wait. I'm probably reading this wrong but are saying that USB 3.0 ports are automatically handled by the OS and that mapping them for the 15 port limit (USBPorts.kext) isn't necessary? That only USB 2.0 ports need to be mapped - or are you only referring to USB-C and/or TB-4? Enquiring minds want to know.

Click to expand...

MacOS discovers USB ports by itself, but handles only 15 ports by controller. An Intel chipset contains one USB controller, which is typically connected to more than 15 ports; we then need to make a suitable map.
Additional (external) USB controllers usually manage less than 15 ports and autoconfiguration by macOS is adequate. This applies to the USB part of Thunderbolt controllers.

etorix said:

MacOS discovers USB ports by itself, but handles only 15 ports by controller. An Intel chipset contains one USB controller, which is typically connected to more than 15 ports; we then need to make a suitable map.
Additional (external) USB controllers usually manage less than 15 ports and autoconfiguration by macOS is adequate. This applies to the USB part of Thunderbolt controllers.

Click to expand...

And macOS cannot automatically determine which (USB 2.0) ports are internal (type 255) and which are external (type 0).

CaseySJ said:

Because I don't know the symptoms or issues you experienced with the USB kext

Click to expand...

I was facing Shutdown/Restart & Sleep/Wake issue. Thats why I wrote, it was gone after using .aml file.

CaseySJ said:

Yours is using IONameMatch and mine is using IOPropertyMatch

Click to expand...

Yes. We both used USBToolBox. But interestingly the same tool gave me IONameMatch and the Model entry was missing too. I didn't hardcode this or remove anything. I will try USBMap.kext with those entries and let you know. Anyway, Thanks for your help.

CaseySJ said:

I've revised the previous post as follows:

Thunderbolt USB-C ports support both USB 3.0 and USB 2.0. Technically it is not necessary to map the USB 3.0 protocol on Thunderbolt ports because macOS discovers and configures them automatically. But if you're connecting USB 2.0 devices to those ports, they may not work unless we map the USB 2.0 protocol.

Click to expand...

Thanks for revising that. I was hoping that's what you meant but at first, I thought I'd been doing it wrong/misunderstanding it this whole time - which would have really messed me up since I've got my USB port limit working fine that way.

etorix said:

MacOS discovers USB ports by itself, but handles only 15 ports by controller. An Intel chipset contains one USB controller, which is typically connected to more than 15 ports; we then need to make a suitable map.
Additional (external) USB controllers usually manage less than 15 ports and autoconfiguration by macOS is adequate. This applies to the USB part of Thunderbolt controllers.

Click to expand...

Yep. I've got a separate USB 3.1 controller on my MB that I don't include for that reason - although, I think I'm going to add it back into the USBPorts.kext plist just to keep an eye on it.

I have good news for all those who use the latest Intel chipsets. MSI has announced that without changing the BIOS it is compatible with 24GB and 48GB RAM. Thus, the maximum supported memory has increased to 192GB.

CaseySJ said:

I've revised the previous post as follows:

Thunderbolt USB-C ports support both USB 3.0 and USB 2.0. Technically it is not necessary to map the USB 3.0 protocol on Thunderbolt ports because macOS discovers and configures them automatically. But if you're connecting USB 2.0 devices to those ports, they may not work unless we map the USB 2.0 protocol.

Click to expand...

Hmm. I have just noticed that at some point in the last month or so, I have lost USB2 (a joystick) access on my CalDigit TS4. This has worked 100% since I first starting using the dock until very recently. Not sure if one of the last Monterey updates may have broken it. The joystick will operate normally when plugged into one of the active USB2 MB ports. Is there a way to map USB2 on the thunderbolt dock?