Page 9 of 9

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 14:48
by tthdm
I can't use the RunME app, becuse it fails at the IORegistry section and can't continue the progress. Only the USB's freeze, the build is running (e.g. i watched a youtube wideo, the usb just freezed and the video continued, so..). All usb ports not working. I tried to unplug the mouse, and keyboard, then plug in again, but it didn't work. I'm just using the build as usual, and random all of the usb ports stop working and the only thing i can do is restart my computer. Then this happens again.

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 14:54
by onemanosx
tthdm, I cant tell off hand what is going on without dump files. Not sure if you have any 3rd party kexts in SLE or LE which might be the culprit. Or how you got your build installed. I say, do a fresh vanilla install and see if the problem arises again.

It is strange that your modern build is acting this way, tho.

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 15:01
by erroruser
tthdm, make sure to open your system pref then go to security an privacy select privacy look for accessability an add run me app to that an try the run me app again

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 15:20
by tthdm
I added every permission that i could but still stucks at this:
Saving IOReg...
IOREG dump failed. Retrying
Increased delay x2 for IOREG dump. This will take a while...(33 sec)

I'm using your 10.4.4 distro, I installed that, and used the EFI that I copied there previously.

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 15:28
by erroruser
reinstall as a distro will cause issues reinstall with the olarila image

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 15:28
by onemanosx
tthdm, you also mentioned you are using efi from a github repo. So I dont know which is true. And definitely you dont need battery kext for a desktop?

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 15:36
by erroruser
tthdm, open a new thread as your post is not related to port limits

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 15:40
by tthdm
I'm using this image: [Local Link Removed for Guests]

Yes, I'm using EFI from a github repo, and the second repo is my efi. I didn't know that i don't need battery kext, I just put everything to my efi folder, because I thought this will work, because the repo's owner has a working build with same parts with this EFI. I can't run any RunME app, because any version I use, it will give me the same error, because IORegistryTool freezes and I don't know what i shloud do with this problem.

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 14 Apr 2019, 15:42
by erroruser
the proper clover folder you need is here for your coffeelake cpu [Local Link Removed for Guests]

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 21 Apr 2019, 19:34
by kollegha
[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]
02 Nov 2018, 12:50
onemanosx

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 02 May 2019, 11:19
by MacintoshHealer
On a 8 Series mobos under Sierra it was enough to edit the DSDT to exclude the unused HS+SS ports to have the total number of 15 ports and rename the device to XHC. This way no kexts or patches were needed.
Could you clear me up how it is under Mojave 10.14.4?
Why do you need kexts? What is the new UIAC device for? Isn't it enough to just delete the unused ports anymore in the XHC.RHUB?
Thank you!

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 02 May 2019, 11:26
by onemanosx
[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]
02 May 2019, 11:19
On a 8 Series mobos under Sierra it was enough to edit the DSDT to exclude the unused HS+SS ports to have the total number of 15 ports and rename the device to XHC. This way no kexts or patches were needed.
Could you clear me up how it is under Mojave 10.14.4?
Why do you need kexts? What is the new UIAC device for? Isn't it enough to just delete the unused ports anymore in the XHC.RHUB?
Thank you!

1. Kext is just like device driver in Windows.
2. Yes, you can edit your DSDT to remove unused ports instead of using UIAC-SSDT.aml
3. Yes, you can also omit using kext if you are able to call the needed device-id via DSDT.

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 02 May 2019, 11:55
by MacintoshHealer
Ok, thanks - so the theory did not change from Sierra to Mojave and from 8x to 3xx series...
In the past we had to rename XHC1 device to XHC in order to omit the Apple's own USB injector and to force macOS to inject USB ports from ACPI. Than all the ports from ACPI within the 15 ports limit were automatically injected by macOS.
I suppose that the _DSM with the right device-id is still needed than, so the right USB kext can attach to this device...
Can you confirm that by doing this 3 steps in the DSDT USB2/3 will work without any kexts or patches:
device is named to XHC,
ports number is reduced to the total of 15 in the XHC.RHUB,
_DSM with the right device-id is injected to XHC

???

How to Stay within 15 ports limit using UsbInjectall and Clover boot argument

Posted: 02 May 2019, 12:09
by onemanosx
[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]
02 May 2019, 11:55
Ok, thanks - so the theory did not change from Sierra to Mojave and from 8x to 3xx series...
In the past we had to rename XHC1 device to XHC in order to omit the Apple's own USB injector and to force macOS to inject USB ports from ACPI. Than all the ports from ACPI within the 15 ports limit were automatically injected by macOS.
I suppose that the _DSM with the right device-id is still needed than, so the right USB kext can attach to this device...
Can you confirm that by doing this 3 steps in the DSDT USB2/3 will work without any kexts or patches:
device is named to XHC,
ports number is reduced to the total of 15 in the XHC.RHUB,
_DSM with the right device-id is injected to XHC

???
The method works as how I did with my MSI build (read in guide section). Though I used ssdt with DSM method.