Administrators Hervé Posted March 10, 2017 Administrators Share Posted March 10, 2017 Well, those offending kexts sure aren't in the cache or list of kexts to cache; otherwise, they would be listed in the warning about invalid signature. On that basis, we have to conclude that they are injected by Clover through the EFI/Clover/kexts/10.12 or EFI/Clover/kexts/Other folder. There can be no other explanation. 'might be a good idea to post a zipped copy of your full EFI folder... Link to comment Share on other sites More sharing options...
antrieb Posted March 10, 2017 Author Share Posted March 10, 2017 my EFI folder as of now (after all the clean up work during the last 24h) EFI_CLOVER-from6430U-sierra_.zip Link to comment Share on other sites More sharing options...
Administrators Hervé Posted March 10, 2017 Administrators Share Posted March 10, 2017 Seems Ok. You say you're booting off an external USB disk. Did you try to boot with the internal HDD removed? Link to comment Share on other sites More sharing options...
antrieb Posted March 10, 2017 Author Share Posted March 10, 2017 Are you thinking Clover is taking the files on the other OS partition on the SSD into account somehow? No, I didn't remove SSD. Too much of a hassle to remove the SSD on my 6430u, isn't it? in my case, it is worth it to try the re-install (on USB again) before removing the SSD!? Just wondering if the re-install will solve the problem... Thanks a lot for your great support and ideas so far, guys! I will report the progress and/or outcome. EDIT: Just learned that I actually can disable the SSD in bios. So I did, rebooted (from USB). No SSD visible in Finder. KP is still there. ;( Is it actually possible that those problem kexts are there somewhere but not visible Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted March 10, 2017 Administrators Share Posted March 10, 2017 clover does sometimes Default to the EFI from the internal disk even when booting from usb EFI. Does that drive have those kexts that you know of? What did you use to make the installer? if it's a Distro maybe it's embedded some how. On another note you can try running first aid from recovery disk utility on the drive. One more thing you can check for is if you have hidden files maybe with those names or they start with a "." like .Voodoo also i think if you used one of the boot packs the DSDT might be from bios A11 or A12 do not go past those revs herve might know the exact one. but i guess thats for later discussion as your not at that point yet. Link to comment Share on other sites More sharing options...
antrieb Posted March 12, 2017 Author Share Posted March 12, 2017 I made my USB installer following exactly Jake's Clover Guide. I even created my USB installer again today. Even just right after the fresh re-install with SSD deactivated (installation on USB drive) I see same exact KP and error message. I did not copy either of those problematic kexts to my USB installer, only those that I found in the bootpack. After installation I checked for hidden files. Nothing. Wondering where are all those strange kexts coming from? Below you can see the panic report from the console (to be found under System Reports) which I got after a fresh installation login. ??? Anonymous UUID: 7A4A2747-EED3-D3F0-C6E5-FAB05DFFB836 Sun Mar 12 20:48:50 2017 *** Panic Report *** panic(cpu 3 caller 0xffffff8027afdd68): "Attempting to lookup/free the middle of a kalloc'ed element! (map: 0xffffff80332274f8, addr: 0xffffff81383c3d28, entry: 0xffffff8041c749b0)\n"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.21.4/osfmk/kern/kalloc.c:460 Backtrace (CPU 3), Frame : Return Address 0xffffff81383c3b90 : 0xffffff8027af368c 0xffffff81383c3c10 : 0xffffff8027afdd68 0xffffff81383c3c50 : 0xffffff8027afdc70 0xffffff81383c3c70 : 0xffffff802805815e 0xffffff81383c3c90 : 0xffffff80280bfada 0xffffff81383c3d00 : 0xffffff7facc45c31 0xffffff81383c3d80 : 0xffffff7facc44461 0xffffff81383c3e40 : 0xffffff80280997ed 0xffffff81383c3e80 : 0xffffff802809953e 0xffffff81383c3f10 : 0xffffff8028098af6 0xffffff81383c3f60 : 0xffffff802809a50e 0xffffff81383c3fb0 : 0xffffff8027aa2af7 Kernel Extensions in backtrace: org.rehabman.voodoo.driver.PS2Keyboard(1.8.21)[57FD5E5A-8305-3DA9-BE92-25535CD4FEDB]@0xffffff7facc42000->0xffffff7facc48fff dependency: com.apple.iokit.IOHIDFamily(2.0.0)[1A48D920-280E-36FA-8D48-49B79A5656E6]@0xffffff7fa8530000 dependency: com.apple.iokit.IOReportFamily(31)[B14DC3D3-7250-3DA3-BF50-C666EBEDAF4C]@0xffffff7fa8411000 dependency: org.rehabman.voodoo.driver.PS2Controller(1.8.21)[3097AA12-0801-377B-8A90-2EC609E7C1B1]@0xffffff7facc0c000 BSD process name corresponding to current thread: kernel_task Boot args: -v nv_disable=1 kext-dev-mode=1 container-dmg=file:///Install%20macOS%20Sierra.app/Contents/SharedSupport/InstallESD.dmg root-dmg=file:///BaseSystem.dmg Mac OS version: Not yet set Kernel version: Darwin Kernel Version 16.1.0: Wed Oct 19 20:31:56 PDT 2016; root:xnu-3789.21.4~4/RELEASE_X86_64 Kernel UUID: 75CA1C4D-7BF4-321B-B544-D8F1B6D60EF8 Kernel slide: 0x0000000027800000 Kernel text base: 0xffffff8027a00000 __HIB text base: 0xffffff8027900000 System model name: MacBookPro9,2 (Mac-6F01561E16C75D06) System uptime in nanoseconds: 2147985296 last loaded kext at 1856115199: org.rehabman.voodoo.driver.PS2Keyboard 1.8.21 (addr 0xffffff7facc42000, size 28672) loaded kexts: org.rehabman.voodoo.driver.PS2Keyboard 1.8.21 com.insanelymac.driver.AppleIntelE1000e 3.1.0 org.rehabman.voodoo.driver.PS2Controller 1.8.21 org.netkas.driver.FakeSMC 1723 org.tgwbd.driver.NullCPUPowerManagement 1.0.0d2 com.apple.iokit.IOAHCIBlockStorage 295.20.1 com.apple.driver.AirPort.Atheros40 700.74.5 com.apple.driver.AppleAHCIPort 326 Link to comment Share on other sites More sharing options...
Administrators Hervé Posted March 12, 2017 Administrators Share Posted March 12, 2017 Why don't you try to boot your USB installer without cache? Link to comment Share on other sites More sharing options...
antrieb Posted March 13, 2017 Author Share Posted March 13, 2017 boot USB installer without cache??? how? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted March 13, 2017 Moderators Share Posted March 13, 2017 Where did you get the source to create your USB Installer? Make sure it's downloaded clean from the AppStore and not from some distro. I'm pretty sure 'no cache mode' has been removed from the current Clover version. You might have to go back to an older version. I think v3556 still had it. Link to comment Share on other sites More sharing options...
antrieb Posted March 13, 2017 Author Share Posted March 13, 2017 Like I stated before - I followed the exact Clover Guide from Jake including the source file downloaded from Appstore. Really, I have no clue how the kexts are getting included in the installation or the boot process respectively. I am using Clover v2.4k r4035. Update: Not sure if this is important, but I created my USB installer on my OS X Mavericks which was a myhack install. Sierra installation was successful, Login is working. Checked the folders /S/L/E and /L/E after fresh re-install: as far as I can say there is no "3rd party" kext in there. At least none of those listed at the top of the kernel panic report. Link to comment Share on other sites More sharing options...
Recommended Posts