Clover General discussion

[Sherlocks]

14 minutes ago, Slice said:

It is for 10.7 which has fatbinary images. Not needed for 10.13.

 

therefore is it for OsxFatBinaryDrv replacement?

 

[Sherlocks]

1 hour ago, Matgen84 said:

 

How to verify appleefifat binary is load or not? I don't know how to do.

Thanks

 

copy efi files in root on ESP

then, go shell option in GUI

and type fsX: X is your ESP

then load efi filename

if you want to save txt file,

load efi filename > filename.txt

and reboot

[Matgen84]

17 minutes ago, Sherlocks said:

 

copy efi files in root on ESP

then, go shell option in GUI

and type fsX: X is your ESP

then load efi filename

if you want to save txt file,

load efi filename > filename.txt

and reboot

 

Ok. One more precision: how to load efi fllename? 

 

sorry for my bad english

Edited August 18, 2018 by Matgen84

[Sherlocks]

 
Ok. One more precision: how to load efi fllename? 

you can rename filename as simple or short.
appleimageloader.efi to 1.efi
then copy in root on ESP
go shell.
type fsX: X is your ESP(need check)
type load 1.efi or type load 1.efi > 1.txt
then type reboot
return GUI. boot macos. then mount ESP. and check txt file



나의 LG-F800S 의 Tapatalk에서 보냄

[Matgen84]

1 hour ago, Sherlocks said:

you can rename filename as simple or short.
appleimageloader.efi to 1.efi
then copy in root on ESP
go shell.
type fsX: X is your ESP(need check)
type load 1.efi or type load 1.efi > 1.txt
then type reboot
return GUI. boot macos. then mount ESP. and check txt file



나의 LG-F800S 의 Tapatalk에서 보냄
 

 

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.

 

I try again

EDIT: same issue. I don't understand why

Edited August 18, 2018 by Matgen84

[WinstonAce]

Try drivers command in efi shell
 drivers > 1.txt

Edited August 18, 2018 by WinstonAce

[savvas]

3 hours ago, Sherlocks said:

 

therefore is it for OsxFatBinaryDrv replacement?

 

Yes it is. 

AppleImageLoader not released yet. So boot order not implemented currently

[Sherlocks]

Yes it is. 
AppleImageLoader not released yet. So boot order not implemented currently

good news. i have a 10.6.8. i can test your driver later after you ready. thanks

나의 LG-F800S 의 Tapatalk에서 보냄

[cecekpawon]

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

[Matgen84]

3 hours ago, WinstonAce said:

Try drivers command in efi shell
 drivers > 1.txt

 

that's what I did without success

[WinstonAce]

You tried to load the driver, I suggested to list loaded drivers.

Sent from my SM-G960F using Tapatalk

[chris1111]

from my compilation 

 

The Drivers load after ApfsDriverLoader.efi

so looks ok here

 

 

[WinstonAce]

Appleimageloader should load first, no?

[chris1111]

5 minutes ago, WinstonAce said:

Appleimageloader should load first, no?

Ok so not good  for me

I just need rename with 1 ? right

[chris1111]

ok  

[Slice]

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.

[Sherlocks]

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

[Matgen84]

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

[Sherlocks]

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.

[Matgen84]

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

[LockDown]

what happened to ApfsDriverLoader-64.efi? i compiled clover's source, and it was missing.

Edited August 20, 2018 by ellaosx

[arsradu]

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?

[Cyberdevs]

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

 

[arsradu]

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!  

[Cyberdevs]

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