Started partitioning on disk1
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk1s1 as MS-DOS (FAT32) with name CLOVER EFI
512 bytes per physical sector
/dev/rdisk1s1: 403266 sectors in 403266 FAT32 clusters (512 bytes/cluster)
bps=512 spc=1 res=32 nft=2 mid=0xf8 spt=32 hds=32 hid=2 drv=0x80 bsec=409600 bspf=3151 rdcl=2 infs=1 bkbs=6
Mounting disk
Formatting disk1s2 as Mac OS Extended (Journaled) with name install_osx
Initialized /dev/rdisk1s2 as a 7 GB case-insensitive HFS Plus volume with a 8192k journal
Mounting disk
Finished partitioning on disk1
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *8.0 GB disk1
1: DOS_FAT_32 CLOVER EFI 209.7 MB disk1s1
2: Apple_HFS install_osx 7.8 GB disk1s2
选项2的方案:
输入 diskutil partitionDisk /dev/disk1 1 GPT HFS+J "install_osx" R
会得到这样的输出
Started partitioning on disk1
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk1s2 as Mac OS Extended (Journaled) with name install_osx
Initialized /dev/rdisk1s2 as a 7 GB case-insensitive HFS Plus volume with a 8192k journal
Mounting disk
Finished partitioning on disk1
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *8.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS install_osx 7.7 GB disk1s2
安装到本地硬盘的一些注意事项:
-你可能想要勾选"EmuVariableUefi-64.efi",但是否勾选它取决于你的本地NVRAM是否工作(大部分Skylake平台的硬件在OS X/macOS 系统下本地的NVRAM不具有正常功能的)
-当安装到本地硬盘的时候,勾选上“安装RC scripts到目标磁盘(Install RC scripts on target volume)“,”安装RC scripts到全部可开机的OSX磁区(Install all RC scripts on all other boot volumes)“可以勾选,也可以不勾选,但是安装到U盘的时候不要勾选
-“安装 Clover系统偏好设置 面板“是可选的,就是在系统设置增加一个Clover设置
-“选择安装RC Scripts“里的一些脚本可以选择安装
-如果是安装Legacy方式引导的Clover是,要勾选上“安装Clover到EFI系统区(Install Clover in the ESP)“
Always use a plist editor (such as Xcode or PlistEdit Pro) when making changes to config.plist.
Note: HD4200, HD4400, and HD4600 on 10.10+ needs special patches/injections, thus the separate config_HD4600_4400_4200.plist. If you're installing Mavericks, use the
config_HD5000_5100_5200.plist instead even for HD4200, HD4400 and HD4600. Actually, either one will work, but there is less work arounds (FakeID) required in 10.9.x. Of course, if you ever update beyond 10.9.x, you will need the appropriate changes to FakeID.
Note: HD5600 on 10.11+ needs special patches/injections, thus the separate config_HD5600.plist. If you're installing Yosemite (not recommended with Broadwell), use config_HD5300_5500_6000.plist.
Copy your selected configuration file, and paste it to /EFI/Clover, make sure it is re-named as config.plist. Clover will only load configurations from /EFI/Clover/config.plist.
DVMT-prealloc on Broadwell/Skylake/Kaby Lake
The Broadwell and Skylake graphics kexts provided by Apple require DVMT-prealloc to be set 64mb or larger. Many laptops set it by default to 32mb, which is not large enough and will cause a KP (kernel panic).
There are ways to set it even if your BIOS does not provide the option, but they are somewhat risky. You can find links to these methods in the laptop FAQ.
Since most laptops come with inadequate DVMT-prealloc, all the plists linked by this guide have a patch for 32MB DVMT-prealloc, enabled by default. You can read about how that patch works here: [url=https://www.tonymacx86.com/threads/guide-alt]https://www.tonymacx86.com/threads/...lensize-patch-with-32mb-dvmt-prealloc.221506/
If your laptop has DVMT-prealloc set as required (64MB or 128MB), you should disable or remove the 32MB patch.
Also, once you enable the patch, you still may have panic... It is because Clover cannot patch a kext that loads outside of kernel cache, and these graphics kexts may not be in cache. To work around this problem, use an invalid ig-platform-id (0x12345678). DO NOT use a bogus FakeID, as that will defeat the purpose. Once you are able to boot with the invalid ig-platform-id, rebuild cache, then boot normally with your intended ig-platform-id.
If you're getting a panic in AppleIntelCPUPowerManagement and/or SMC_ACPI_PlatformPlugin it may be related to your OEM CPU power management related SSDTs.
Some systems may need to drop some of the OEM SSDTs. This happens most frequently with Sandy Bridge systems (but not all). There are two configurations for DropTables in the provided config.plist files. The default is minimal. The alternate is named #DropTables and is a bit more aggressive. Each configuration resides in config.plist/ACPI. You can use the alternate by renaming DropTables->##DropTables and renaming #DropTables->DropTables (in that order). Depending on how the OEM labels the tables, this may or may not work. If you still have issues, set config.plist/ACPI/SSDT/DropOem=true. You will need to set config.plist/ACPI/SSDT/Generate=true (or the individual CStates/PStates=true) to use DropOem=true or the alternate DropTables.
El Capitan系统:
# copy installer image
sudo "/Applications/Install OS X El Capitan.app/Contents/Resources/createinstallmedia" --volume /Volumes/install_osx --applicationpath "/Applications/Install OS X El Capitan.app" --nointeraction
# rename
sudo diskutil rename "Install OS X El Capitan" install_osx
Yosemite系统:
# copy installer image
sudo "/Applications/Install OS X Yosemite.app/Contents/Resources/createinstallmedia" --volume /Volumes/install_osx --applicationpath "/Applications/Install OS X Yosemite.app" --nointeraction
# rename
sudo diskutil rename "Install OS X Yosemite" install_osx
Mavericks系统:
# copy installer image
sudo "/Applications/Install OS X Mavericks.app/Contents/Resources/createinstallmedia" --volume /Volumes/install_osx --applicationpath "/Applications/Install OS X Mavericks.app" --nointeraction
# rename
sudo diskutil rename "Install OS X Mavericks" install_osx
# mount InstallESD.dmg in installer package
hdiutil attach "/Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg" -readonly -mountpoint /tmp/install_esd -nobrowse
# restore it to target
sudo asr restore --source /tmp/install_esd/BaseSystem.dmg --target /Volumes/install_osx -erase --format HFS+ --noprompt
# rename the target to be less unwieldy
diskutil rename "OS X Base System" install_osx
注:接下来就可以启动U盘进行安装了,一般是按F12进入启动菜单,选择你的U盘,进入Clover,然后选择Install OS X from *** 回车进入安装程序,只要制作正确,一般电脑都可以正常进入到系统中,如果进入系统后出现花屏,可以尝试睡眠电脑,再立即唤醒(Y50就这样),如果无法进入到安装程序,就在选择Install OS X from *** 时按空格,勾选上-v模式,然后启动,查看代码,排查错误