Sherlocks Posted August 18, 2018 Share Posted August 18, 2018 Yes it is. AppleImageLoader not released yet. So boot order not implemented currentlygood news. i have a 10.6.8. i can test your driver later after you ready. thanks나의 LG-F800S 의 Tapatalk에서 보냄 2 Link to comment Share on other sites More sharing options...
cecekpawon Posted August 18, 2018 Share Posted August 18, 2018 7 minutes ago, savvamitrofanov said: Yes it is. AppleImageLoader not released yet. So boot order not implemented currently @savvamitrofanov Would you like t create dedicated thread for AppleSupportPkg? Cannot make it work to boot with Ozmosis, and dunno where to report. Thanks 2 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted August 18, 2018 Share Posted August 18, 2018 3 hours ago, WinstonAce said: Try drivers command in efi shell drivers > 1.txt that's what I did without success Link to comment Share on other sites More sharing options...
WinstonAce Posted August 18, 2018 Share Posted August 18, 2018 You tried to load the driver, I suggested to list loaded drivers.Sent from my SM-G960F using Tapatalk Link to comment Share on other sites More sharing options...
chris1111 Posted August 18, 2018 Share Posted August 18, 2018 from my compilation The Drivers load after ApfsDriverLoader.efi so looks ok here Link to comment Share on other sites More sharing options...
WinstonAce Posted August 18, 2018 Share Posted August 18, 2018 Appleimageloader should load first, no? 1 Link to comment Share on other sites More sharing options...
chris1111 Posted August 18, 2018 Share Posted August 18, 2018 5 minutes ago, WinstonAce said: Appleimageloader should load first, no? Ok so not good for me I just need rename with 1 ? right Link to comment Share on other sites More sharing options...
chris1111 Posted August 18, 2018 Share Posted August 18, 2018 ok 1 Link to comment Share on other sites More sharing options...
Slice Posted August 18, 2018 Share Posted August 18, 2018 Loading order depends on position in partition which you can’t control. ApfsDriverLoader must be smart enough to wait for AppleLoder. I am not sure it is. 2 Link to comment Share on other sites More sharing options...
Sherlocks Posted August 18, 2018 Share Posted August 18, 2018 3 minutes ago, Matgen84 said: @Sherlocks tell me to test with this method in shell GUI to verify something for binary (look at his post). I already show load appleimageloader.efi status success in bdmesg. don't consider bdmesg log. i'm focused log in shell when clover get GUI. like this "AppleImageLoader: Binary isn't AppleEfiFat". it is that i replied previous. you have to add AppleImageLoader.efi file in root on ESP. then In GUI, go shell. then type "fsX:" ->X is your ESP partition "important" then, you have to type "load AppleImageLoader.efi > 1.txt" if you correctly selected ESP partition. you can get 1.txt file on ESP. and type "reboot" -> to return Clover Gui, then try to boot your macos. then mount ESP, and check 1.txt file 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted August 18, 2018 Share Posted August 18, 2018 (edited) 53 minutes ago, Sherlocks said: don't consider bdmesg log. i'm focused log in shell when clover get GUI. like this "AppleImageLoader: Binary isn't AppleEfiFat". it is that i replied previous. you have to add AppleImageLoader.efi file in root on ESP. then In GUI, go shell. then type "fsX:" ->X is your ESP partition "important" then, you have to type "load AppleImageLoader.efi > 1.txt" if you correctly selected ESP partition. you can get 1.txt file on ESP. and type "reboot" -> to return Clover Gui, then try to boot your macos. then mount ESP, and check 1.txt file I type load 1.efi > 1.txt Shell is stuck without going back to FS3: So I can't type reboot. txt file generated is empty of course. Edit: I try again with load AppleImageLoader.efi > 1.txt. ---------> I waited 15 minutes. Same Issue. I don't understand why. Edited August 18, 2018 by Matgen84 Link to comment Share on other sites More sharing options...
Sherlocks Posted August 18, 2018 Share Posted August 18, 2018 1 hour ago, Matgen84 said: I type load 1.efi > 1.txt Shell is stuck without going back to FS3: So I can't type reboot. txt file generated is empty of course. Edit: I try again with load AppleImageLoader.efi > 1.txt. ---------> I waited 15 minutes. Same Issue. I don't understand why. hmm. i don't know it on your system. @savvamitrofanov i will test your driver with 10.6.8 without OsxFatBinaryDrv.efi tomorrow. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted August 18, 2018 Share Posted August 18, 2018 13 minutes ago, Sherlocks said: hmm. i don't know it on your system. I don't know too. I tried both High Sierra HD and Mojave HD with Clover r4649 Link to comment Share on other sites More sharing options...
LockDown Posted August 20, 2018 Share Posted August 20, 2018 (edited) what happened to ApfsDriverLoader-64.efi? i compiled clover's source, and it was missing. Edited August 20, 2018 by ellaosx Link to comment Share on other sites More sharing options...
arsradu Posted August 22, 2018 Share Posted August 22, 2018 Guys, I've got a pretty interesting issue on two different systems. On one of them (the one in my sig), only during OS updates, the computer doesn't reach Clover GUI until I press any key (I usually press Enter, but I guess it can be any key). Until then, it's just a blank screen. On another system (Skylake build), it does exactly the same thing as the Haswell system, only it does that with every boot up, not just for updates (this could be related to one having native NVRAM, whereas the other one uses MemoryFix for that). But the actual issue is the same: doesn't enter Clover GUI until you press a key. Not sure if this is an OS issue (though it doesn't look like it, since at that point, no OS is even loaded) or a Clover issue. It started probably one or two releases ago. So it's a pretty new issue. Clover version is the same one on both systems. I'm thinking this could potentially be an APFS issue....? I use ApfsDriverLoader with both. I could try apfs.efi, as well (without the loader) if you guys think this could make a difference. It's not a huge issue. As I said, all you need is to just press Enter, and it will continue. But it's kind of annoying. Especially for updates, where it needs to restart to complete the installation. And it just hangs there. Any idea? Link to comment Share on other sites More sharing options...
Cyberdevs Posted August 22, 2018 Share Posted August 22, 2018 8 minutes ago, arsradu said: Guys, I've got a pretty interesting issue on two different systems. On one of them (the one in my sig), only during OS updates, the computer doesn't reach Clover GUI until I press any key (I usually press Enter, but I guess it can be any key). Until then, it's just a blank screen. On another system (Skylake build), it does exactly the same thing as the Haswell system, only it does that with every boot up, not just for updates (this could be related to one having native NVRAM, whereas the other one uses MemoryFix for that). But the actual issue is the same: doesn't enter Clover GUI until you press a key. Not sure if this is an OS issue (though it doesn't look like it, since at that point, no OS is even loaded) or a Clover issue. It started probably one or two releases ago. So it's a pretty new issue. Clover version is the same one on both systems. I'm thinking this could potentially be an APFS issue....? I use ApfsDriverLoader with both. I could try apfs.efi, as well (without the loader) if you guys think this could make a difference. It's not a huge issue. As I said, all you need is to just press Enter, and it will continue. But it's kind of annoying. Especially for updates, where it needs to restart to complete the installation. And it just hangs there. Any idea? Have you seen this post and few posts after? It might be the same issue. https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&comment=2630394 1 Link to comment Share on other sites More sharing options...
arsradu Posted August 22, 2018 Share Posted August 22, 2018 10 minutes ago, Cyberdevs said: Have you seen this post and few posts after? It might be the same issue. https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&comment=2630394 A-ha! I was on vacation last week. Looks like I missed this one. And I saw some discussions about it in the previous posts. I was just not sure if it was about this issue or not. So I decided to ask anyway, in case it's a different one. Many thanks! 1 Link to comment Share on other sites More sharing options...
Cyberdevs Posted August 22, 2018 Share Posted August 22, 2018 13 minutes ago, arsradu said: A-ha! I was on vacation last week. Looks like I missed this one. And I saw some discussions about it in the previous posts. I was just not sure if it was about this issue or not. So I decided to ask anyway, in case it's a different one. Many thanks! Welcome back And I guess it is the same issue, which was resolved short after I posted the issue thanks to @savvamitrofanov 1 Link to comment Share on other sites More sharing options...
arsradu Posted August 22, 2018 Share Posted August 22, 2018 (edited) 36 minutes ago, Cyberdevs said: Welcome back And I guess it is the same issue, which was resolved short after I posted the issue thanks to @savvamitrofanov Yep, confirmed. It is the same issue. And it is fixed by adding that AppleImageLoader.efi to Clover drivers folder. Now all we need is to include that functionality (either by adding it to one of the existing drivers, or including this specific driver by default) with the Clover installer itself. Also, I guess the log message below is kind of to be expected? :)) Edited August 22, 2018 by arsradu 1 Link to comment Share on other sites More sharing options...
Cyberdevs Posted August 22, 2018 Share Posted August 22, 2018 1 minute ago, arsradu said: Yep, confirmed. It is the same issue. And it is fixed by adding that AppleImageLoader.efi to Clover drivers folder. Now all we need is to include that functionality (either by adding it to one of the existing drivers, or including this specific driver by default) with the Clover installer itself. Also, I guess the log message below is kind of to be expected? :)) For now we have to include the driver manually it hasn't been added to clover as far as I know and the logs are to be expected for now. Maybe @savvamitrofanov fix the logs in the near future. 1 Link to comment Share on other sites More sharing options...
arsradu Posted August 22, 2018 Share Posted August 22, 2018 4 minutes ago, Cyberdevs said: For now we have to include the driver manually it hasn't been added to clover as far as I know and the logs are to be expected for now. Maybe @savvamitrofanov fix the logs in the near future. Yep, makes perfect sense not to include it so far. It needs some proper testing before deploying it by default with the installer. Link to comment Share on other sites More sharing options...
Badruzeus Posted August 22, 2018 Share Posted August 22, 2018 Get no issue here.. but, oh I just realized that I'm no longer using Mojave with APFS Spoiler 0:996 0:000 === [ LoadDrivers ] ======================================= 1:001 0:004 Loading ApfsDriverLoader-64.efi status=Success 1:017 0:015 - driver needs connecting 1:017 0:000 Loading AppleImageCodec-64.efi status=Success 1:018 0:000 Loading AppleKeyAggregator-64.efi status=Success 1:019 0:000 Loading AppleUITheme-64.efi status=Success 1:019 0:000 Loading AptioMemoryFix-64.efi status=Success 1:020 0:000 Loading CsmVideoDxe-64.efi status=Success 1:021 0:000 - driver needs connecting 1:021 0:000 Loading DataHubDxe-64.efi status=Success 1:025 0:004 Loading FirmwareVolume-64.efi status=Success 1:026 0:000 Loading FSInject-64.efi status=Success 1:027 0:000 Loading HashServiceFix-64.efi status=Success 1:027 0:000 Loading OsxFatBinaryDrv-64.efi status=Success 1:028 0:000 Loading SMCHelper-64.efi status=Success 1:029 0:000 Loading VBoxHfs-64.efi status=Success 1:030 0:000 - driver needs connecting 1:030 0:000 Loading AppleImageLoader.efi status=Success 1:041 0:011 3 drivers needs connecting ... 1:041 0:000 PlatformDriverOverrideProtocol not found. Installing ... Success 1:041 0:000 APFS driver loaded Link to comment Share on other sites More sharing options...
Cyberdevs Posted August 22, 2018 Share Posted August 22, 2018 13 minutes ago, arsradu said: Yep, makes perfect sense not to include it so far. It needs some proper testing before deploying it by default with the installer. Exactly 4 minutes ago, Badruzeus said: Get no issue here.. but, oh I just realized that I'm no longer using Mojave with APFS So what do you use then? High Sierra? 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted August 22, 2018 Share Posted August 22, 2018 (edited) 10 minutes ago, Cyberdevs said: Exactly So what do you use then? High Sierra? HFS+ Mojave with @crazybirdy script. BTW, I remember wanna asking this question: When entering "UEFI Shell 64" function (or tool) on Clover GUI, it always freezes my system.. or just greets me with "BestLanguage" log. But has no problem with Legacy Shell 64. And, it seems.. I found no solution (neither link) yet #atm. Any idea? Edited August 22, 2018 by Badruzeus Link to comment Share on other sites More sharing options...
Cyberdevs Posted August 22, 2018 Share Posted August 22, 2018 9 minutes ago, Badruzeus said: HFS+ Mojave with @crazybirdy script. BTW, I remember wanna asking this question: When entering "UEFI Shell 64" function (or tool) on Clover GUI, it always freezes my system.. or just greets me with "BestLanguage" log. But has no problem with Legacy Shell 64. And, it seems.. I found no solution (neither link) yet #atm. Any idea? I haven't used the UEFI Shell in a very long time so I have no idea what can be the cause! 1 Link to comment Share on other sites More sharing options...
Recommended Posts