Dell Inspiron Auto Restart After 10.13.6 Update

[Samasemo]

Hello Hackintoshers
Yesterday I have updated my laptop from 10.13.5 to 10.13.6, but a new behaviour appears which is auto restart after about 1 - 2 mins from operation.

can someone helps me figure out the issue?
Thanks in advance.

 

[Feartech]

Hello Hackintoshers
Yesterday I have updated my laptop from 10.13.5 to 10.13.6, but a new behaviour appears which is auto restart after about 1 - 2 mins from operation.

can someone helps me figure out the issue?
Thanks in advance.

your kexts should be installed to /Library/Extensions

remove from /System/Library/Extensions

also missing clover folder from your problem reporting files

 

[Sunshine83]

In Rehabman's guide, he says to put all the kexts in S/L/E...

 

[Feartech]

In Rehabman's guide, he says to put all the kexts in S/L/E...

i don't think so

 

[Sunshine83]

i don't think so

Installing Kexts

You should install all kexts you need (including FakeSMC, VoodooPS2Controller, etc) to /Library/Extensions (/L/E) or /System/Library/Extensions (/S/L/E) for 10.10.x and prior using a kext installer or Terminal. Think carefully about "kexts you need". For example, if you needed HPRAIDInjector.kext for a SATA chip locked in RAID mode, you'll need to install it in order to boot (without it, the system would be unable to mount root and would get stuck early in the boot process).

Of course, essential kexts should be installed to EFI/Clover/kexts/Other as they are needed to boot the installer (during updates) or the recovery partition.

It is a mistake to install everything to Clover/kexts. Contrary to popular hackintosh myth, it does not result in a cleaner install (the opposite is true). Many kexts will not work from Clover/kexts, so installing them to /S/L/E where they can be included in kernel cache is the best approach.

People often ask me why I install kexts to /S/L/E (or /L/E on 10.11).

I have many reasons:
- placing them in /S/L/E (or /L/E on 10.11+) and including in kernel cache, makes kextcache do a lot of error checking.
- if you develop kexts, error checking is very important!
- some kexts don't work from Clover/kexts (AppleHDA injector, CodecCommander, BrcmFirmware*)
- the idea behind Clover/kexts is to have a set of *stable* and *minimalistic* kexts that will allow booting of the installer/recovery, not full functionality
- so...the kexts there I tend to not update as often and the full set is not there (less unneeded kexts, less problems)
- placing kexts into kernel cache for day-to-day use is "more native" (as it would be on a real Mac) vs. injection (which is very non-Mac)

IMO, placing kexts in Clover/kexts for injection when not needed is like "flying blind." I don't know about you, but I would not board a plane with a blind pilot (no offense to the blind).

You might be wondering if this will result in duplicate kexts being loaded due to the kexts in EFI/Clover/kexts being injected when they are also installed to the system volume. The answer is no, not generally. With config.plist/SystemParameters/InjectKexts="Detect", kexts in EFI/Clover/kexts are not injected when FakeSMC.kext is in kernel cache. Because FakeSMC.kext is always a "kext you need", you will always install it to the system volume, which will put it in kernel cache. Kernel cache, of course, will not have FakeSMC.kext when booting the installer or recovery, so in these cases the kexts in EFI/Clover/kexts *will* be injected as you would expect.

 

[Feartech]

Installing Kexts

You should install all kexts you need (including FakeSMC, VoodooPS2Controller, etc) to /Library/Extensions (/L/E) or /System/Library/Extensions (/S/L/E) for 10.10.x and prior using a kext installer or Terminal. Think carefully about "kexts you need". For example, if you needed HPRAIDInjector.kext for a SATA chip locked in RAID mode, you'll need to install it in order to boot (without it, the system would be unable to mount root and would get stuck early in the boot process).

Of course, essential kexts should be installed to EFI/Clover/kexts/Other as they are needed to boot the installer (during updates) or the recovery partition.

It is a mistake to install everything to Clover/kexts. Contrary to popular hackintosh myth, it does not result in a cleaner install (the opposite is true). Many kexts will not work from Clover/kexts, so installing them to /S/L/E where they can be included in kernel cache is the best approach.

People often ask me why I install kexts to /S/L/E (or /L/E on 10.11).

I have many reasons:
- placing them in /S/L/E (or /L/E on 10.11+) and including in kernel cache, makes kextcache do a lot of error checking.
- if you develop kexts, error checking is very important!
- some kexts don't work from Clover/kexts (AppleHDA injector, CodecCommander, BrcmFirmware*)
- the idea behind Clover/kexts is to have a set of *stable* and *minimalistic* kexts that will allow booting of the installer/recovery, not full functionality
- so...the kexts there I tend to not update as often and the full set is not there (less unneeded kexts, less problems)
- placing kexts into kernel cache for day-to-day use is "more native" (as it would be on a real Mac) vs. injection (which is very non-Mac)

IMO, placing kexts in Clover/kexts for injection when not needed is like "flying blind." I don't know about you, but I would not board a plane with a blind pilot (no offense to the blind).

You might be wondering if this will result in duplicate kexts being loaded due to the kexts in EFI/Clover/kexts being injected when they are also installed to the system volume. The answer is no, not generally. With config.plist/SystemParameters/InjectKexts="Detect", kexts in EFI/Clover/kexts are not injected when FakeSMC.kext is in kernel cache. Because FakeSMC.kext is always a "kext you need", you will always install it to the system volume, which will put it in kernel cache. Kernel cache, of course, will not have FakeSMC.kext when booting the installer or recovery, so in these cases the kexts in EFI/Clover/kexts *will* be injected as you would expect.

i already know all this, maybe you should read it a bit more

as you are in a High Sierra Laptop support then you need to install kexts in /Library/Extensions

 

[Samasemo]

ok check now..

 

[Feartech]

ok check now..

from your kextcache:

Kext rejected due to improper filesystem permissions: <OSKext 0x7ff604ceca10 [0x7fff8435caf0]> { URL = "AppleHDA.kext/ -- file:///System/Library/Extensions/", ID = "com.apple.driver.AppleHDA" }
Kext rejected due to improper filesystem permissions: <OSKext 0x7ff604cdd430 [0x7fff8435caf0]> { URL = "IOHDAFamily.kext/ -- file:///System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/", ID = "com.apple.iokit.IOHDAFamily" }
Kext rejected due to improper filesystem permissions: <OSKext 0x7ff604cddfc0 [0x7fff8435caf0]> { URL = "AppleMikeyDriver.kext/ -- file:///System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/", ID = "com.apple.driver.AppleMikeyDriver" }
Kext rejected due to improper filesystem permissions: <OSKext 0x7ff604cdf620 [0x7fff8435caf0]> { URL = "AppleHDAHardwareConfigDriver.kext/ -- file:///System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/", ID = "com.apple.driver.AppleHDAHardwareConfigDriver" }
Kext rejected due to improper filesystem permissions: <OSKext 0x7ff604cef690 [0x7fff8435caf0]> { URL = "DspFuncLib.kext/ -- file:///System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/", ID = "com.apple.driver.DspFuncLib" }
Kext rejected due to improper filesystem permissions: <OSKext 0x7ff604cf1e40 [0x7fff8435caf0]> { URL = "AppleHDAController.kext/ -- file:///System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/", ID = "com.apple.driver.AppleHDAController" }

your AppleHDA.kext is not installed correctly

not saying that this will fix your issues, just an observation

 

[RehabMan]

Installing Kexts

You should install all kexts you need (including FakeSMC, VoodooPS2Controller, etc) to /Library/Extensions (/L/E) or /System/Library/Extensions (/S/L/E) for 10.10.x and prior using a kext installer or Terminal. Think carefully about "kexts you need". For example, if you needed HPRAIDInjector.kext for a SATA chip locked in RAID mode, you'll need to install it in order to boot (without it, the system would be unable to mount root and would get stuck early in the boot process).

Of course, essential kexts should be installed to EFI/Clover/kexts/Other as they are needed to boot the installer (during updates) or the recovery partition.

It is a mistake to install everything to Clover/kexts. Contrary to popular hackintosh myth, it does not result in a cleaner install (the opposite is true). Many kexts will not work from Clover/kexts, so installing them to /S/L/E where they can be included in kernel cache is the best approach.

People often ask me why I install kexts to /S/L/E (or /L/E on 10.11).

I have many reasons:
- placing them in /S/L/E (or /L/E on 10.11+) and including in kernel cache, makes kextcache do a lot of error checking.
- if you develop kexts, error checking is very important!
- some kexts don't work from Clover/kexts (AppleHDA injector, CodecCommander, BrcmFirmware*)
- the idea behind Clover/kexts is to have a set of *stable* and *minimalistic* kexts that will allow booting of the installer/recovery, not full functionality
- so...the kexts there I tend to not update as often and the full set is not there (less unneeded kexts, less problems)
- placing kexts into kernel cache for day-to-day use is "more native" (as it would be on a real Mac) vs. injection (which is very non-Mac)

IMO, placing kexts in Clover/kexts for injection when not needed is like "flying blind." I don't know about you, but I would not board a plane with a blind pilot (no offense to the blind).

You might be wondering if this will result in duplicate kexts being loaded due to the kexts in EFI/Clover/kexts being injected when they are also installed to the system volume. The answer is no, not generally. With config.plist/SystemParameters/InjectKexts="Detect", kexts in EFI/Clover/kexts are not injected when FakeSMC.kext is in kernel cache. Because FakeSMC.kext is always a "kext you need", you will always install it to the system volume, which will put it in kernel cache. Kernel cache, of course, will not have FakeSMC.kext when booting the installer or recovery, so in these cases the kexts in EFI/Clover/kexts *will* be injected as you would expect.

In Rehabman's guide, he says to put all the kexts in S/L/E...

You are clearly not reading very carefully.

 

[Samasemo]

ok check one more time ^_^