Yes weird and yes I noticed the increased use of iOS based libraries (UIKit). Part of Apple's plan to merge the two OSes (this summer?). I'm not sure I agree with their direction but anyhow are you using the same HS IO kexts for your .5 beta1 testing?
BOARD_ID=`ioreg -c IOPlatformExpertDevice | awk '/board-id/ {print $4}' | awk -F '\"' '{print $2}'`
MODEL=`sysctl hw.model | awk '{print $2}'`
DIR=`pwd`
cp PlatformSupport.plist PlatformSupportBackup.plist
sudo defaults write ${DIR}/PlatformSupport.plist "SupportedBoardIds" -array-add "<string>${BOARD_ID></string>"
sudo defaults write ${DIR}/PlatformSupport.plist "SupportedModelProperties" -array-add "<string>${MODEL}</string>"
sudo plutil -convert xml1 ${DIR}/PlatformSupport.plist
You just need to NOP one call statement at nvVirtualAddressSpaceTesla::free() + 183. I'll do it myself later if you can't figure it out.
The shim kext is because there is no _VSLGestalt function in the Mojave kexts, and the Tesla kexts need it. It shouldn't affect you in any way if you have other GPU.
Apple is not merging macOS and iOS. Tim Cook specifically said that during WWDC 2018.
Believe me, there's a lot of code I recognize from my iOS development days...So under the hood there's a lot of cross-platform development going on. 10.15 will bring more. News+ is just the beginning.
i delete MRT and disable Spotlight. it doesn't help(
10.14.4 version of system ofcourse. fsck also doesn't help(
Oh yes, I know that iOS/watchOS/tvOS (bridgeOS too, I suppose?) are very close internally to macOS. And with this Marzipan business, there will certainly be more cross-platform apps. But macOS and iOS won't be combined into one system.
Agreed. Combined into one system no (yet?). Can you imagine the update nightmare if they did?
But if the rumors of ARM based Macs are true, the urge to unify certain frameworks and architectures will be great. To me this means even less care for macs than ever before. The macrumors front page is already reporting more cross-platform support in 10.15. This summer will be full of surprises...
I'd suggest having the script unmount the recovery disk, too. For users who run the script from a terminal, use "pushd" when changing directories, and then "popd" before you unmount the disk.
Also, I think you can have the script update PlatformSupport.plist instead of moving it out of the way and disabling the compatibility check. At least, that works on my MacBook Pro 5.3.
Code:BOARD_ID=`ioreg -c IOPlatformExpertDevice | awk '/board-id/ {print $4}' | awk -F '\"' '{print $2}'` MODEL=`sysctl hw.model | awk '{print $2}'` DIR=`pwd` cp PlatformSupport.plist PlatformSupportBackup.plist sudo defaults write ${DIR}/PlatformSupport.plist "SupportedBoardIds" -array-add "<string>${BOARD_ID></string>" sudo defaults write ${DIR}/PlatformSupport.plist "SupportedModelProperties" -array-add "<string>${MODEL}</string>" sudo plutil -convert xml1 ${DIR}/PlatformSupport.plist
It could be made a bit fancier, by detecting if the board id and model are already listed, and skip adding them in that case.
I would recommend using 10.14.3 for now. Unless you have new AirPods or something I would stick with the more stable version. The kernel panics are not dosdude1’s fault and I’m sure he appreciates your donation. You should be able to reinstall 10.14.3 right over 10.14.4 with no issues. Worst case just do a fresh install of 10.14.3.
Yes indeed, that's why I was wondering why I needed it on my machine anymore. None of those .4 kexts need the Gestalt function that Shim provides ( I actually downloaded the source for .4 IOKit on Apple's open source website to triple check) But, doesn't seem to hurt (as @ASentientBot noted) just an opportunity to trim down the patcher post-install footprint for my particular machine (mbp 5,3), unless I'm missing something.
