RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,015
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Heh
Ok. I finally added the remove-usb3-port-limit-kext-patch, and HP15/HP16 are now discovered as SSP5/SSP6.
So next step for me would be to nuke away most of the other USB3 ports, e.g. HS07-HS15, is that correct? And afterwards remove the remove-limit...?
Do I have to add the SSDT-UIAC to clovers "sortedOrder" section, and if so, do I have to add all other SSDTs there, too?
Since my edits in SSDT-UIAC do not seem to be activated, though I can see it via MaciASL...
Your ioreg here still shows SSxx port truncation (15-port port limit in effect).
Your Clover bootlog (extracted from ioreg), shows the port limit patch is disabled:
Code:
1:540 0:000 KextsToPatch: 5 requested
1:540 0:000 - [00]: com.apple.driver.usb.AppleUSBXHCIPCI (change 15 port limit to 20 in XHCI kext (9-series)) :: MatchOS: 10.12.x :: BinPatch :: data len: 7
1:540 0:000 - patch disabled at config
1:540 0:000 - [01]: com.apple.driver.usb.AppleUSBXHCIPCI (change 15 port limit to 26 in XHCI kext (100-series)) :: MatchOS: 10.12.x :: BinPatch :: data len: 7
1:540 0:000 - patch disabled at config
1:540 0:000 - [02]: IOAHCIBlockStorage (TRIM Enabler) :: BinPatch :: data len: 10
1:540 0:000 - patch disabled at config
1:540 0:000 - [03]: AppleTyMCEDriver (Boot smbios w/o ECC) :: BinPatch :: data len: 24
1:540 0:000 - [04]: IOAHCIBlockStorage (TRIM Enabler2) :: BinPatch :: data len: 11
1:540 0:000 - patch disabled at config
After you fix that...
Next step is to trim ports... unused HPxx, PRxx, and HSxx, and SSxx.
If you're using SortedOrder, then yes... you would have to add the SSDT to the list. When using SortedOrder, only the SSDTs listed there are loaded by Clover. If you're not using SortedOrder, then Clover loads all SSDTs in ACPI/patched in random order.
Your Clover bootlog shows unsorted loading:
Code:
6:559 0:000 === [ ACPIPatchedAML ] ====================================
6:559 0:000 Unsorted
6:559 0:000 Inserting SSDT-XOSI.aml from EFI\CLOVER\OEM\B85M-G\ACPI\patched ... Success
6:560 0:001 Inserting SSDT-UIAC.aml from EFI\CLOVER\OEM\B85M-G\ACPI\patched ... Success
6:563 0:002 Inserting SSDT-SMBUS.aml from EFI\CLOVER\OEM\B85M-G\ACPI\patched ... Success
6:565 0:001 Inserting SSDT-7.aml from EFI\CLOVER\OEM\B85M-G\ACPI\patched ... Success
6:567 0:002 Inserting SSDT-5.aml from EFI\CLOVER\OEM\B85M-G\ACPI\patched ... Success
6:569 0:002 Inserting SSDT-1.aml from EFI\CLOVER\OEM\B85M-G\ACPI\patched ... Success
Which, of course, is not a good idea, especially if SSDT-7.aml, SSDT-5.aml and SSDT-1.aml are patched OEM SSDTs.
In the case of patched OEM SSDTs, you should include all static OEM SSDTs in ACPI/patched, DropOem=true, and SortedOrder to specify correct order.
I have no idea why you have those patched SSDTs in ACPI/patched... they are being ignored by the system due to DropOem=false (duplicate symbols in SSDTs are ignored).
Note also that dropping individual OEM tables so you can replace them with content in ACPI/patched is also a mistake as it changes the effective order of the SSDTs.
Last edited: