解決問題帖子:
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里的<DefaultVolume>和<DefaultLoader>是共同起作用的:<DefaultVolume>指定默認的啟動分區,這里我們設置為EFI分區的GUID;<DefaultLoader>指定默認分區中的啟動文件,這里因為我們默認的EFI分區里只有一個WIN10 EFI MANAGER(Clover被我放在另一個硬盤的EFI分區里了),所以不設置該項,Clover可以自動找到啟動文件。
設置<IgnoreNVRAMBoot>為<true>,這里不太懂,但這東西或存在BUG或功能缺失。所以必須在 EFI/CLOVER/drivers64UEFI 文件夾下放入文件 NTFS.efi