I fixed my problem using the latest Clover r2652 and this post from @hack.in regarding ntfs.efi.
In my particular case (with uefi installed Windows 7), I mistakenly omitted EFI as the Default Boot Volume (I only entered bootmgfw.efi as Default Loader).
To fix the problem, you need to
Place ntfs.efi in EFI/CLOVER/drivers64 or drivers64UEFI
Delete your current NVRAM settings...in terminal
sudo rm /nvram.plist
sudo nvram -c
Edit your config.plist, entering the Default Boot Volume and ticking IgnoreNVRAMBoot with Clover Configurator...
With the correct config.plist settings, everything works as expected (including timeout countdown!)....
Of course for legacy Windows, the Default Boot Volume would usually be "system reserved"
总结
Clover配置文件config.plist里的和是共同起作用的：指定默认的启动分区，这里我们设置为EFI分区的GUID；指定默认分区中的启动文件，这里因为我们默认的EFI分区里只有一个WIN10 EFI MANAGER(Clover被我放在另一个硬盘的EFI分区里了)，所以不设置该项，Clover可以自动找到启动文件。
设置为，这里不太懂，但这东西或存在BUG或功能缺失。所以必须在 EFI/CLOVER/drivers64UEFI 文件夹下放入文件 NTFS.efi
发布者：admin，转转请注明出处：http://www.yc00.com/web/1733297218a3660810.html
评论列表（0条）