- Joined
- Jun 24, 2016
- Messages
- 158
- Motherboard
- Alienware 15 R2
- CPU
- i7 6700HQ
- Graphics
- Skylake 530 + gtx 970m (4k panel)
ProbeScore is now 0x3e8 = 1000 and CFBundleIdentifier is now com.apple.driver.Hack16X50Serial so it looks like our kext loaded but it also looks like the code was executed because some other properties exist that are not in the Info.plist. I don't know why it doesn't hinder the boot process.On the contrary, it did work it seems.
Although the device is showing up in the ioreg, while verbose booting, it is no longer hindering the boot process.
That is what we were intending to do right?
Also, Thanks a LOT.
Attaching the debug files again, and attaching the kext as well.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildMachineOSBuild</key>
<string>17A405001</string>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleIdentifier</key>
<string>com.hack.driver.Hack16X50Serial</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>Hack16X50Serial</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>3.2</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleSupportedPlatforms</key>
<array>
<string>MacOSX</string>
</array>
<key>CFBundleVersion</key>
<string>1.9</string>
<key>DTCompiler</key>
<string>com.apple.compilers.llvm.clang.1_0</string>
<key>DTPlatformBuild</key>
<string>10P70r</string>
<key>DTPlatformName</key>
<string>macosx</string>
<key>DTPlatformVersion</key>
<string>10.14</string>
<key>DTSDKBuild</key>
<string>18G101</string>
<key>DTSDKName</key>
<string>macosx10.14internal</string>
<key>DTXcode</key>
<string>1020</string>
<key>DTXcodeBuild</key>
<string>10P70r</string>
<key>IOKitPersonalities</key>
<dict>
<key>PCI 16X50 Serial Port</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.hack.driver.Hack16X50Serial</string>
<key>IOClass</key>
<string>com_hack_driver_16X50PCI</string>
<key>IOPCIClassMatch</key>
<string>0x07000000&0xFFFF0000</string>
<key>IOProbeScore</key>
<integer>1000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
</dict>
</dict>
<key>LSMinimumSystemVersion</key>
<string>10.14</string>
<key>OSBundleCompatibleVersion</key>
<string>1.9</string>
</dict>
</plist>
sudo kextunload -b com.apple.driver.Apple16X50Serial
sudo kextunload -b com.hack.driver.Hack16X50Serial
cd /Volumes/Storage/Downloads/
sudo rm -R Hack16X50Serial.kext/Contents/MacOS
sudo chown -R root:wheel Hack16X50Serial.kext
sudo find Hack16X50Serial.kext -type d -exec /bin/chmod 0755 {} \;
sudo find Hack16X50Serial.kext -type f -exec /bin/chmod 0644 {} \;
sudo kextutil -v 6 /Volumes/Storage/Downloads/Hack16X50Serial.kext
ProbeScore is now 0x3e8 = 1000 and CFBundleIdentifier is now com.apple.driver.Hack16X50Serial so it looks like our kext loaded but it also looks like the code was executed because some other properties exist that are not in the Info.plist. I don't know why it doesn't hinder the boot process.
I suggested removing the MacOS folder from the kext. Then try kextload to verify the kext. Then when the kext is verified successfully, move it to the Clover kexts folder.
First, change the Info.plist to this:
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>BuildMachineOSBuild</key> <string>17A405001</string> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleIdentifier</key> <string>com.hack.driver.Hack16X50Serial</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>Hack16X50Serial</string> <key>CFBundlePackageType</key> <string>KEXT</string> <key>CFBundleShortVersionString</key> <string>3.2</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleSupportedPlatforms</key> <array> <string>MacOSX</string> </array> <key>CFBundleVersion</key> <string>1.9</string> <key>DTCompiler</key> <string>com.apple.compilers.llvm.clang.1_0</string> <key>DTPlatformBuild</key> <string>10P70r</string> <key>DTPlatformName</key> <string>macosx</string> <key>DTPlatformVersion</key> <string>10.14</string> <key>DTSDKBuild</key> <string>18G101</string> <key>DTSDKName</key> <string>macosx10.14internal</string> <key>DTXcode</key> <string>1020</string> <key>DTXcodeBuild</key> <string>10P70r</string> <key>IOKitPersonalities</key> <dict> <key>PCI 16X50 Serial Port</key> <dict> <key>CFBundleIdentifier</key> <string>com.hack.driver.Hack16X50Serial</string> <key>IOClass</key> <string>com_hack_driver_16X50PCI</string> <key>IOPCIClassMatch</key> <string>0x07000000&0xFFFF0000</string> <key>IOProbeScore</key> <integer>1000</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> </dict> </dict> <key>LSMinimumSystemVersion</key> <string>10.14</string> <key>OSBundleCompatibleVersion</key> <string>1.9</string> </dict> </plist>
Then with the following commands or similar: unload existing drivers, remove the MacOS folder, fix permissions, then kextutil to verify and load the kext.
Code:sudo kextunload -b com.apple.driver.Apple16X50Serial sudo kextunload -b com.hack.driver.Hack16X50Serial cd /Volumes/Storage/Downloads/ sudo rm -R Hack16X50Serial.kext/Contents/MacOS sudo chown -R root:wheel Hack16X50Serial.kext sudo find Hack16X50Serial.kext -type d -exec /bin/chmod 0755 {} \; sudo find Hack16X50Serial.kext -type f -exec /bin/chmod 0644 {} \; sudo kextutil -v 6 /Volumes/Storage/Downloads/Hack16X50Serial.kext
kextutil will have a warning that the kext does not point to a kext that has an executable. I'm not sure if that will make the kext unusable (I haven't made a codeless kext in awhile).
So you're saying the problem you had has gone away without using any kext?Tried multiple times, although with the kext im not able to boot at all. Whereas without any kexts, somehow, im able to boot. So im gonna keep this running as long as it does, if it stops, ill get back.
Thanks a lot for all the help, Truly!
<key>CFBundleIdentifier</key>
<string>com.apple.kpi.iokit</string>
<key>IOClass</key>
<string>IOService</string>