4 ms·
On your M1 machine, the used kernel is /System/Library/Kernels/kernel.release.t8101. (for T810x processors, A14 is T8101 and M1 is T8103, both share the same ke
by my123 6y ago
On your M1 machine, the used kernel is /System/Library/Kernels/kernel.release.t8101.
(for T810x processors, A14 is T8101 and M1 is T8103, both share the same kernel)
The installation should be bootable by both, but not sure that the flow to bless an install done on another machine to be bootable on an other M1 one is done/fully functional yet. (on M1 machines, you need to bless external volumes before booting from them)
Booting an install done on an M1 on an x86 Mac should work already though.
- marcan_42 6y agoThat's not the kernel. I mean, it's the kernel, but not the kernel that the machine boots from. The built-in bootloader actually boots iBoot2 from /System/Volumes/Preboot/(UUID)/boot/(long hash)/usr/standalone/firmware/iBoot.img4, and that then loads the Darwin kernel from /System/Volumes/Preboot/(UUID)/boot/(long hash)/System/Library/Caches/com.apple.kernelcaches/kernelcache. However, the system firmware can only boot this from the internal SSD, not from any external storage. When you choose an external disk to boot from (the "bless" thing), those files get copied to the internal SSD, and it boots from that instead.
- mrkstu 6y agoSo you literally cannot boot an M1 Mac with a nonfunctional internal drive, even if you’re successfully ’booting’ from an external drive before it fails? The SSD is integral to its functioning?
- my123 6y agoThat's the immutable kernelcache shipped by the machine, and isn't only the kernel but also includes the kexts. You can then rebuild your own kernel cache from /System/Library/Extensions and /System/Library/Kernels. (eventually with a recompiled kernel)
- comex 6y agoBut note that Intel Macs use a similar but completely different system, also redone in Big Sur, with a set of "kext collection" files in a different location and format. Because that makes so much sense.