An iDiot's Guide To Lilu and its Plug-ins

[jaymonkey]

Thanks for the guide JayMonkey. I may be wrong but wasn't originally a usb fixing guide some time ago too on the list?

@anibalin,

Nope not from me .....

This guide only deals with Lilu and its plug-in's which has nothing to do with resolving USB issues. For correct USB port naming and port types i personally use the SSDT hot patch method which is covered in the guide written by @RehabMan here :-

https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/

Or you can use the kext injector method which uses HD-Patcher and is covered in the guide @headkaze wrote here :-

https://www.tonymacx86.com/threads/release-intel-fb-patcher-v1-6-5.254559/

See the section titled USB Port Patching.

Cheers
Jay

 

[jaymonkey]

I have tried to install Lilu.kext, AirportBrcmFixup.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, but none of the kexts are loading. I am on Mojave 10.14 and have tried using kext beast and terminal to install the kexts to /Library/Extensions. I have also repaired permissions using Kext Utility and have used terminal as well. My SIP is disabled, 0x67.

@rishi44,

Not possible to diagnose your issues with out PR Files .... please provide Problem Reporting files using the gen_debug script as detailed in this post :-

https://www.tonymacx86.com/threads/tool-generate-proper-problem-reporting-files.235953/

Cheers
Jay

 

[rishi44]

@rishi44,

Not possible to diagnose your issues with out PR Files .... please provide Problem Reporting files using the gen_debug script as detailed in this post :-

https://www.tonymacx86.com/threads/tool-generate-proper-problem-reporting-files.235953/

Cheers
Jay

Thanks jaymonkey
requested files are attached below.

 

[jaymonkey]

Thanks jaymonkey
requested files are attached below.

@rishi44,

If you look at the text file "sudo kextcache" you can see that all your 3rd party kext's are failing to load with the error :-

Untrusted kexts are not allowed
Kext with invalid signature (-67062) denied:XXXXXXX

This is usually cased by two things .. SIP is not disabled and not booting with the argument "kext-dev-mode=1"

However .. looking at your config.plist I can see that you have SIP correctly disabled :-

• BooterConfig = 0x28
• CsrActiveConfig = 0x67

And you have "kext-dev-mode=1" included in your boot arguments.

So I'm a bit confused as to why your seeing those errors .. its very strange ...
The only thing i can think of is that somehow your /L/E folder has got some invalid file properties defined ... ?

cd /Library/Extensions
sudo chown *.kext -R root:wheel
sudo touch /Library/Extensions

Also as detailed in the How to Install section of my guide, I recommend running version 2.6.6 of cVad's Kext Utility (click here to download) which will repair any broken kext permissions and rebuild the caches. Simply run the app and enter your admin password when prompted, then wait while Kext Utility does it's work. You will know when it's finished once you see "Quit" in bold black text at the bottom of the app window.

Once it's finished .. reboot and see if it's helped ....

Failing that the only other suggestion i can think of is to create a new help thread in the Post Install section of the forum, attach your debug_files zip archive and explain the above ....

Hopefully one of the other gurus can shine some light on the problem for you ...

Cheers
Jay

 

[rishi44]

@rishi44,

If you look at the text file "sudo kextcache" you can see that all your 3rd party kext's are failing to load with the error :-

Untrusted kexts are not allowed
Kext with invalid signature (-67062) denied:XXXXXXX

This is usually cased by two things .. SIP is not disabled and not booting with the argument "kext-dev-mode=1"

However .. looking at your config.plist I can see that you have SIP correctly disabled :-

• BooterConfig = 0x28
• CsrActiveConfig = 0x67

And you have "kext-dev-mode=1" included in your boot arguments.

So I'm a bit confused as to why your seeing those errors .. its very strange ...
The only thing i can think of is that somehow your /L/E folder has got some invalid file properties defined ... ?

cd /Library/Extensions
sudo chown *.kext -R root:wheel
sudo touch /Library/Extensions

Also as detailed in the How to Install section of my guide, I recommend running version 2.6.6 of cVad's Kext Utility (click here to download) which will repair any broken kext permissions and rebuild the caches. Simply run the app and enter your admin password when prompted, then wait while Kext Utility does it's work. You will know when it's finished once you see "Quit" in bold black text at the bottom of the app window.

Once it's finished .. reboot and see if it's helped ....

Failing that the only other suggestion i can think of is to create a new help thread in the Post Install section of the forum, attach your debug_files zip archive and explain the above ....

Hopefully one of the other gurus can shine some light on the problem for you ...

Cheers
Jay

ok thanks jay, I am running kext utility now. I just tried the terminal command you mentioned, but I am getting this when I enter my password.
chown: ACS6x.kext: illegal user name

Any suggestions?
Thanks

 

[rishi44]

@rishi44,

If you look at the text file "sudo kextcache" you can see that all your 3rd party kext's are failing to load with the error :-

Untrusted kexts are not allowed
Kext with invalid signature (-67062) denied:XXXXXXX

This is usually cased by two things .. SIP is not disabled and not booting with the argument "kext-dev-mode=1"

However .. looking at your config.plist I can see that you have SIP correctly disabled :-

• BooterConfig = 0x28
• CsrActiveConfig = 0x67

And you have "kext-dev-mode=1" included in your boot arguments.

So I'm a bit confused as to why your seeing those errors .. its very strange ...
The only thing i can think of is that somehow your /L/E folder has got some invalid file properties defined ... ?

cd /Library/Extensions
sudo chown *.kext -R root:wheel
sudo touch /Library/Extensions

Also as detailed in the How to Install section of my guide, I recommend running version 2.6.6 of cVad's Kext Utility (click here to download) which will repair any broken kext permissions and rebuild the caches. Simply run the app and enter your admin password when prompted, then wait while Kext Utility does it's work. You will know when it's finished once you see "Quit" in bold black text at the bottom of the app window.

Once it's finished .. reboot and see if it's helped ....

Failing that the only other suggestion i can think of is to create a new help thread in the Post Install section of the forum, attach your debug_files zip archive and explain the above ....

Hopefully one of the other gurus can shine some light on the problem for you ...

Cheers
Jay

Just tried running kext utility, but still same errors are appearing in sudo kext cache. I'll try posting in the post install section of the forum to see what they recommend. I may have to reinstall OS X perhaps. Actually, I am running a restore of a time machine backup, so I wonder if it has anything to do with the issues I am having with /Library/Extensions.

 

[jaymonkey]

I just tried the terminal command you mentioned, but I am getting this when I enter my password. chown: ACS6x.kext: illegal user name

Hummm ... well that error would suggest an issue with the root user or the wheel group.
root is the system super user and wheel is the group of super users.

If thats the case then it would suggest your MacOS install is corrupted.

Cheers
Jay

 

[rishi44]

Hummm ... well that error would suggest an issue with the root user or the wheel group.
root is the system super user and wheel is the group of super users.

If thats the case then it would suggest your MacOS install is corrupted.

Cheers
Jay

Ok do you think I could fix the issue with a reinstall on top of my existing installation? Like rerunning mojave. Or I could revert back to Sierra using time machine and try to update to mojave again.

 

[jaymonkey]

Ok do you think I could fix the issue with a reinstall on top of my existing installation? Like rerunning mojave. Or I could revert back to Sierra using time machine and try to update to mojave again.

A reinstall on top of the existing system should fix the issue.
Make sure you have a backup first .... just incase ...

Cheers
Jay

 

[rishi44]

Ok will do that thanks