Contribute
Register

MSI GP62 7RD and High Sierra

Status
Not open for further replies.
Do you mean 'Kext with invalid signatured…'?
 
Well, binaries exactly match a native 10.13.1:
Code:
--- sha1sums.native.sorted.txt 2017-11-30 14:11:13.800214499 +0300
+++ sha1sums.hack.txt 2017-11-30 13:33:59.665894193 +0300
@@ -243,13 +243,2 @@
a9db378d37a1c0b9e50b5cc5bf771e0e5acac209 /System/Library/Extensions/exfat.kext/Contents/MacOS/exfat
-2db9dd255f1eecb73ade24ba61a9a2f40566a397 /System/Library/Extensions/GeForceAIRPlugin.bundle/Contents/MacOS/GeForceAIRPlugin
-421d29258d0ba8f8be733918e7ea1e57a218d6b2 /System/Library/Extensions/GeForceGA.plugin/Contents/MacOS/GeForceGA
-cbb71a6c62c5bbabd46a399807c20bd25b60c4ae /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriver
-ef1ee7726b5114fb6e9d9ea896890deeba31cbf3 /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/libclh.dylib
-33f66babe8aadc7e6984bb33a7c305965fcfc437 /System/Library/Extensions/GeForce.kext/Contents/MacOS/GeForce
-2a9795694d33d2c8c245ef6b0d5da48ee8ab5b04 /System/Library/Extensions/GeForceMTLDriver.bundle/Contents/MacOS/GeForceMTLDriver
-50e1c21be24e1c4aae6e56321d9ec501e17da1a6 /System/Library/Extensions/GeForceTeslaGLDriver.bundle/Contents/MacOS/GeForceTeslaGLDriver
-e4a1526dd942edd98e0a2df6eb1184cb9b578d1a /System/Library/Extensions/GeForceTeslaGLDriver.bundle/Contents/MacOS/libclh.dylib
-11ccd162417521a20760bfe61896c8a936de8cc5 /System/Library/Extensions/GeForceTesla.kext/Contents/MacOS/GeForceTesla
-8403b7c6c35e98919d524d6ec023e389b014a757 /System/Library/Extensions/GeForceTeslaVADriver.bundle/Contents/MacOS/GeForceTeslaVADriver
-81622d7c177a081d9534a4584ccc4f194557f061 /System/Library/Extensions/GeForceVADriver.bundle/Contents/MacOS/GeForceVADriver
7759d0ef52d5518dc16e1dea6c388b9fc10d8a24 /System/Library/Extensions/HFSEncodings.kext/Contents/MacOS/HFSEncodings
@@ -305,3 +294,2 @@
3cbad52f09a5516ad8e26e34758dde5a37ce8a9e /System/Library/Extensions/iPodDriver.kext/Contents/MacOS/iPodDriver
-d7894ca7f78bbc970ce45a249ff72ed26843f557 /System/Library/Extensions/JMicronATA.kext/Contents/MacOS/JMicronATA
aa0c2f9e919a38ce39baec99192dc0bf9a182226 /System/Library/Extensions/KernelRelayHost.kext/Contents/MacOS/KernelRelayHost
@@ -313,8 +301,2 @@
71934e2bb2ed21d2832348a6b05ea30535309e31 /System/Library/Extensions/ntfs.kext/Contents/MacOS/ntfs
-d80558cd693b40bb46ded1f9f8c65ce4810af049 /System/Library/Extensions/NVDAGF100Hal.kext/Contents/MacOS/NVDAGF100Hal
-22531a55e9d4f2d9aeeba1f989b068a416009007 /System/Library/Extensions/NVDAGK100Hal.kext/Contents/MacOS/NVDAGK100Hal
-75dd3637ea5217d1641515b531bb36eaf69d3c28 /System/Library/Extensions/NVDANV50HalTesla.kext/Contents/MacOS/NVDANV50HalTesla
-5396fb7003f345197c3071afedf6a44bf55714d0 /System/Library/Extensions/NVDAResman.kext/Contents/MacOS/NVDAResman
-db79ef16a025b53ab37d7634b582c2525e215dbc /System/Library/Extensions/NVDAResmanTesla.kext/Contents/MacOS/NVDAResmanTesla
-d2faaba4c1fb940160f9f165a806da59e61ca111 /System/Library/Extensions/NVDAStartup.kext/Contents/MacOS/NVDAStartup
460283c2316eeb07221bd6048a7d89e632da721c /System/Library/Extensions/NVMeSMARTLib.plugin/Contents/MacOS/NVMeSMARTLib
@@ -330,3 +312,2 @@
6b9efcfffa4a159e6577f95299306a64a9669155 /System/Library/Extensions/Radius.ppp/Contents/MacOS/Radius
-5db90e0552b3c771f51097e632f50659a66d3013 /System/Library/Extensions/RemoteVirtualInterface.kext/Contents/MacOS/RemoteVirtualInterface
fc51543f667e85ec7d0daa7f925eb69b8605b05c /System/Library/Extensions/Sandbox.kext/Contents/MacOS/Sandbox

Got this comparing
sha1sum /tmp/osx/System/Library/Extensions/*/Contents/MacOS/*
for my drive mounted in Linux and
shasum /System/Library/Extensions/*/Contents/MacOS/*
for OS X drive in OS X (piped through sed -E -e 's|^(\w+)[^/]+([^\r]+)\r?$|\2 \1|' | sort | sed -E -e 's|^(\S+)| \1 |' on Linux).

Most likely system reports incorrect checksums just because it can't (or haven't) initialize keyring or such. I can only run kextcache very early in the boot, when in single-user mode (-s).
 
May it be worth trying to disable dGPU as described in [FIX] "Window Server Service only ran for 0 seconds" with dual-GPU? I get this error when trying to boot 'recovery' from a neighbor volume.
If I understand this correctly, Devices-AddProperties section in the config_HD615_620_630_640_650.plist tries to accomplish the same, but it may be failing for some reason.
 
Well, binaries exactly match a native 10.13.1:
Code:
--- sha1sums.native.sorted.txt 2017-11-30 14:11:13.800214499 +0300
+++ sha1sums.hack.txt 2017-11-30 13:33:59.665894193 +0300
@@ -243,13 +243,2 @@
a9db378d37a1c0b9e50b5cc5bf771e0e5acac209 /System/Library/Extensions/exfat.kext/Contents/MacOS/exfat
-2db9dd255f1eecb73ade24ba61a9a2f40566a397 /System/Library/Extensions/GeForceAIRPlugin.bundle/Contents/MacOS/GeForceAIRPlugin
-421d29258d0ba8f8be733918e7ea1e57a218d6b2 /System/Library/Extensions/GeForceGA.plugin/Contents/MacOS/GeForceGA
-cbb71a6c62c5bbabd46a399807c20bd25b60c4ae /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriver
-ef1ee7726b5114fb6e9d9ea896890deeba31cbf3 /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/libclh.dylib
-33f66babe8aadc7e6984bb33a7c305965fcfc437 /System/Library/Extensions/GeForce.kext/Contents/MacOS/GeForce
-2a9795694d33d2c8c245ef6b0d5da48ee8ab5b04 /System/Library/Extensions/GeForceMTLDriver.bundle/Contents/MacOS/GeForceMTLDriver
-50e1c21be24e1c4aae6e56321d9ec501e17da1a6 /System/Library/Extensions/GeForceTeslaGLDriver.bundle/Contents/MacOS/GeForceTeslaGLDriver
-e4a1526dd942edd98e0a2df6eb1184cb9b578d1a /System/Library/Extensions/GeForceTeslaGLDriver.bundle/Contents/MacOS/libclh.dylib
-11ccd162417521a20760bfe61896c8a936de8cc5 /System/Library/Extensions/GeForceTesla.kext/Contents/MacOS/GeForceTesla
-8403b7c6c35e98919d524d6ec023e389b014a757 /System/Library/Extensions/GeForceTeslaVADriver.bundle/Contents/MacOS/GeForceTeslaVADriver
-81622d7c177a081d9534a4584ccc4f194557f061 /System/Library/Extensions/GeForceVADriver.bundle/Contents/MacOS/GeForceVADriver
7759d0ef52d5518dc16e1dea6c388b9fc10d8a24 /System/Library/Extensions/HFSEncodings.kext/Contents/MacOS/HFSEncodings
@@ -305,3 +294,2 @@
3cbad52f09a5516ad8e26e34758dde5a37ce8a9e /System/Library/Extensions/iPodDriver.kext/Contents/MacOS/iPodDriver
-d7894ca7f78bbc970ce45a249ff72ed26843f557 /System/Library/Extensions/JMicronATA.kext/Contents/MacOS/JMicronATA
aa0c2f9e919a38ce39baec99192dc0bf9a182226 /System/Library/Extensions/KernelRelayHost.kext/Contents/MacOS/KernelRelayHost
@@ -313,8 +301,2 @@
71934e2bb2ed21d2832348a6b05ea30535309e31 /System/Library/Extensions/ntfs.kext/Contents/MacOS/ntfs
-d80558cd693b40bb46ded1f9f8c65ce4810af049 /System/Library/Extensions/NVDAGF100Hal.kext/Contents/MacOS/NVDAGF100Hal
-22531a55e9d4f2d9aeeba1f989b068a416009007 /System/Library/Extensions/NVDAGK100Hal.kext/Contents/MacOS/NVDAGK100Hal
-75dd3637ea5217d1641515b531bb36eaf69d3c28 /System/Library/Extensions/NVDANV50HalTesla.kext/Contents/MacOS/NVDANV50HalTesla
-5396fb7003f345197c3071afedf6a44bf55714d0 /System/Library/Extensions/NVDAResman.kext/Contents/MacOS/NVDAResman
-db79ef16a025b53ab37d7634b582c2525e215dbc /System/Library/Extensions/NVDAResmanTesla.kext/Contents/MacOS/NVDAResmanTesla
-d2faaba4c1fb940160f9f165a806da59e61ca111 /System/Library/Extensions/NVDAStartup.kext/Contents/MacOS/NVDAStartup
460283c2316eeb07221bd6048a7d89e632da721c /System/Library/Extensions/NVMeSMARTLib.plugin/Contents/MacOS/NVMeSMARTLib
@@ -330,3 +312,2 @@
6b9efcfffa4a159e6577f95299306a64a9669155 /System/Library/Extensions/Radius.ppp/Contents/MacOS/Radius
-5db90e0552b3c771f51097e632f50659a66d3013 /System/Library/Extensions/RemoteVirtualInterface.kext/Contents/MacOS/RemoteVirtualInterface
fc51543f667e85ec7d0daa7f925eb69b8605b05c /System/Library/Extensions/Sandbox.kext/Contents/MacOS/Sandbox

Got this comparing
sha1sum /tmp/osx/System/Library/Extensions/*/Contents/MacOS/*
for my drive mounted in Linux and
shasum /System/Library/Extensions/*/Contents/MacOS/*
for OS X drive in OS X (piped through sed -E -e 's|^(\w+)[^/]+([^\r]+)\r?$|\2 \1|' | sort | sed -E -e 's|^(\S+)| \1 |' on Linux).

Most likely system reports incorrect checksums just because it can't (or haven't) initialize keyring or such. I can only run kextcache very early in the boot, when in single-user mode (-s).
May it be worth trying to disable dGPU as described in [FIX] "Window Server Service only ran for 0 seconds" with dual-GPU? I get this error when trying to boot 'recovery' from a neighbor volume.
If I understand this correctly, Devices-AddProperties section in the config_HD615_620_630_640_650.plist tries to accomplish the same, but it may be failing for some reason.

Do a fresh install.
Follow guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 
From what I understood, we have to tweak ACPI to not power on dGPU on boot. I still have to do this too.
 
Status
Not open for further replies.
Back
Top