stuck on `considerRebuildOfPrelinkedKernel com.*.* triggered rebuild`

[sakoula]

Hi,

 

I have a problem that I cannot fix and have not found a solution anywhere. This has happened to more than one hacks I have (Skylake and Sandy Bridge) on both 10.12 and 10.13 . I run both machines with CsrActiveConfig 0x67 (no SIP).

 

When I manually update some kexts in /L/E or /S/L/E and trigger the system cache rebuild with any of the following commands:

 

```

touch /L/E

touch /S/L/E

sudo kextcache -system-prelinked-kernel

sudo kextcache -system-caches

sudo kextcache -v 2 -u /

```

on the next boot I get stucked on a `considerRebuildOfPrelinkedKernel com.*.* triggered rebuild` where the module is usually the FakeSMC (updated in it's latest version) or USBInjectAll or the network kext. It stucks there for ever.

 

In order to boot I have to boot through the recovery partition delete the kexts that I have installed and boot again. Then I get an message `BootCache: too many history clusters (201, limit 200)` and after some seconds I up and running.

 

My understanding is that we cannot boot anymore without the kernel caches using the later Clover or MacOS.

 

Any idea why this is happening and how I can debug it?

 

Thanks!!!!

[artur_pt]

hello

 

why u don't inject the kexts from clover folder ?

 

maybe for the network kext u need the dependencies from ionetworkingfamily kext

 

I use this to rebuild the cache

sudo touch /System/Library/Extensions && sudo kextcache -u /

good hack

[sakoula]

hello Artur, thanks for the reply.

indeed I inject the kexts through clover

however some of them (nvidia alternative drivers) are required to be installed in LE and SLE. when I installed them through the pkg installer it is ok. when I try to install them manually (by cp them and using the kextcache command in any form) I get stuck on boot.

 

There is definitely something wrong with my installation.

 

Is there a chance the absence of SIP to cause these problems?

 

So in any of my hacks I cannot build the kernel next cache manually from the command line.

 

Thanks!