클로버 부트로더 UEFI 부팅 방법과 테스트 순서
- Mactopia
- 5852
- 1
Mactopia님의 기기정보
사실 해킨이라는 것이 결국 널려 있는 정보들 사이에서 나의 시스템과 꼭 맞는 상황을 찾아가는 것인데 (= 삽질)
클로버 부트로더 UEFI 방식으로 설치 하는데 있어 간략한 테스트 순서를 찾아서 올려 봅니다. 아래 바이너리들의 하는 역활에 대해서는 바로 아래 클로버 FAQ 글을 참조 하시면 됩니다.
산사자를 사용하시는 분들은 보통 3번 단계를 적용하면 다 된다고 보시면 될 것 같습니다. (파일 설치 장소는 /EFI/Drivers64UEFI 입니다.)
When trying UEFI boot, try with following combination of drivers in /EFI/Drivers64UEFI folder:
1. HFSPlus.efi, OsxFatBinaryDrv-64.efi
if this does not work, then2. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxLowMemFixDrv-64.efi
and then if this does not work then
3. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi (with slide=0 in boot args in config.plist)
and if even this does not work, then try:
4. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi (with slide=0 in boot args in config.plist), EmuVariableRuntimeDxe.efi
More details
1. HFSPlus.efi, OsxFatBinaryDrv-64.efi
This works on boards with Gigabyte Hybrid EFI. This is the best option for UEFI boot, in the sense that no special fixes are required. Any OSX should boot fine, unless some big change happens that will stop working boot here.
2. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxLowMemFixDrv-64.efi
This works on Insyde H2O UEFI. Some small memory issue will be fixed by LowMemFix, and then everything should be equal to case 1.
3. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi (with slide=0 for ML)
This works for all other boards ... well, where works. This is not so good solution because it depends on current functioning of boot.efi and current structures that are passed between boot.efi (boot loader) and kernel, like boot args and device tree. Meaning: if structure of boot args changes, like it changed when Lion came out, which caused Chameleon to fail to boot Lion, this will again break Chameleon and UEFI boot with AptioFix - until somebody fixes it. This is the most annoying thing to me because the major point for having UEFI boot is to use boot.efi as bootloader and to avoid such things. Well, if this happens, the first solution will be to fall back to standard Clover until the thing is resolved. The small issue is that standard Clover is also dependent on kernel boot args when kernel and kext patching or kext injection is used - this would also need to be turned off in that case.
4. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi, EmuVariableRuntimeDxe.efi
This works on Dell Vostro, some ThinkPad's - some laptops with Phoenix UEFI. All mentioned in 3. is applicable here.
All other drivers may or may not be needed. Drivers listed above are required minimum. The best way to test if the driver is needed or not is to try without it - if the thing still works, then it is not needed. Well, more or less ... since for example normal boot works without FSInject, but that one can be needed sometimes.
https://www.skyo.co.kr/forum/50186
설치 관련 질문 글타래 입니다