Clover General discussion

[SavageAUS]

It is possible I mixed mem alloc.

Try this 4088 version

BOOTX64.efi.zip

Patch:

 

apfs2.patch.zip

I reinstalled 4088 today and replaced BOOTX64, it made no difference.

Im unsure what or if i need to do with apfs2.patch so ill just test 4089 and report back.

 

EDIT: 4089 works perfectly, also showing additional apfs volumes.

[SavageAUS]

You can ad to your Own Build Package 

I would like to know how 

[chris1111]

I would like to know how 

before Create the PKG put the drivers in /src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI

Ok for Build Package

 

For Legacy and (ESP no UEFI) you can also put in /drivers-Off/drivers64 but Rename apfs-64.efi

because you can not build two drivers with the same name

[LockDown]

What made you say that you cant build 2 drivers with the same name

[Cyberdevs]

before Create the PKG put the drivers in /src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI

Ok for Build Package

 

For Legacy and (ESP no UEFI) you can also put in /drivers-Off/drivers64 but Rename apfs-64.efi

because you can not build two drivers with the same name

Thanks @Chris1111

 

This solved my problem

[chris1111]

Thanks @Chris1111

 

This solved my problem

Depending on your method of build, you have to put the driver back every time because there is a make clean that is done

[Cyberdevs]

Depending on your method of build, you have to put the driver back every time because there is a make clean that is done

Thanks

 

I kind of figured it out

But it's always good to know something for sure

[SavageAUS]

Thanks

 

I kind of figured it out

But it's always good to know something for sure

I havnt been able to get my builds to include the driver that i put into /src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI.

I would like to include apfs in my clover pkgs.

[Cyberdevs]

@SavageAUS

 

/Users/cyberdevs/src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI/apfs.efi this is the path I copied all the drivers including apps.efi and after I built the package it is in the installer as an option to install.

 

The folder was not there so I just created it.

[chris1111]

@SavageAUS

 

/Users/cyberdevs/src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI/apfs.efi this is the path I copied all the drivers including apps.efi and after I built the package it is in the installer as an option to install.

 

The folder was not there so I just created it.

So your not have the same builder like me I have the manual build (with scrip build ) for long time

better to ask  Philip petev for solution if you are used the Clover command

[Cyberdevs]

I just downloaded the Clover Builder app from the download section. http://www.insanelymac.com/forum/files/file/542-clover-builderapp/

 

So there is a script too that you are using?

[chris1111]

I just downloaded the Clover Builder app from the download section. http://www.insanelymac.com/forum/files/file/542-clover-builderapp/

 

So there is a script too that you are using?

You can try  Clover command in Clover section ?  

http://www.insanelymac.com/forum/forum/327-clover/

[Cyberdevs]

I found something called: Build_Clover.command v4.3.7

 

is that the command that you are talking about?

[chris1111]

I found something called: Build_Clover.command v4.3.7

 

is that the command that you are talking about?

Yes but i said i use a method diferant since long time a ago already

[Cyberdevs]

Well I'm really new to this and I have to do a lot of catching up to do

I'm a noob

I havnt been able to get my builds to include the driver that i put into /src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI.

I would like to include apfs in my clover pkgs.

Did you find what you were looking for?

[SavageAUS]

I use the build_clover.command. have done for quite some time.

 

Sent from my SM-G930F using Tapatalk

[Guest ricoc90]

I'm not sure if it's Clover or High Sierra related so I'll post it here too 
 

I installed High Sierra on an empty SSD formatted as APFS. It mounts and boots fine, but when Clover is scanning for entries it shows me
 

nx_dev_init:705: Warning: superblock indicates jumpstart record but this driver was not loaded from that partition
container_kb_get:544: Invalid on disk range pr_start_paddr 0 pr_block_count 0
keybag_operation:353: missing APFS/Container keybag (2)
apfs_keybag_get:831: Failed to get apfs volume keybag, err = 2
er_state_obj_get_for_recovery:3539: No ER state object - rolling is not happening, nothing to recover
APFSStart:1132: Mounting with apfs_efi_osx-621.0.0.1.32
efi_container_create:795: -efi_container_create, Status = 0000000000000007

and macOS is showing me the exact same thing in verbose mode. Anyone else with this issue or is it normal?

I'm using r4089

[SavageAUS]

Well I'm really new to this and I have to do a lot of catching up to do

I'm a noob

 

Did you find what you were looking for?

I'll try again shortly and let you know.

 

Sent from my SM-G930F using Tapatalk

[chris1111]

I use the build_clover.command. have done for quite some time.

 

Sent from my SM-G930F using Tapatalk

Ask Philip petev thats better to know how 

[SavageAUS]

I'm not sure if it's Clover or High Sierra related so I'll post it here too

 

I installed High Sierra on an empty SSD formatted as APFS. It mounts and boots fine, but when Clover is scanning for entries it shows me

 

nx_dev_init:705: Warning: superblock indicates jumpstart record but this driver was not loaded from that partition
container_kb_get:544: Invalid on disk range pr_start_paddr 0 pr_block_count 0
keybag_operation:353: missing APFS/Container keybag (2)
apfs_keybag_get:831: Failed to get apfs volume keybag, err = 2
er_state_obj_get_for_recovery:3539: No ER state object - rolling is not happening, nothing to recover
APFSStart:1132: Mounting with apfs_efi_osx-621.0.0.1.32
efi_container_create:795: -efi_container_create, Status = 0000000000000007

and macOS is showing me the exact same thing in verbose mode. Anyone else with this issue or is it normal?

I'm using r4089

Are you using just the apfs.efi or do you have the jumpstart driver as well?

 

Sent from my SM-G930F using Tapatalk

Ask Philip petev thats better to know how

I've already picked his brain about a different issue I had with the script lol.

 

Sent from my SM-G930F using Tapatalk

[Guest ricoc90]

Are you using just the apfs.efi or do you have the jumpstart driver as well?

 

Sent from my SM-G930F using Tapatalk

I've already picked his brain about a different issue I had with the script lol.

 

Sent from my SM-G930F using Tapatalk

I need to admit that I'm not sure what a jumpstart driver is but apfs.efi is in Drivers64 and Drivers64UEFI 

[Cyberdevs]

I need to admit that I'm not sure what a jumpstart driver is but apfs.efi is in Drivers64 and Drivers64UEFI 

I think it depends on the system that you are using, If you are using the UEFI BIOS settings then Drivers64UEFI will jumpstart it. If you are using a Legacy BIOS then Drivers64 will jumpstart the apps.efi.

Right?

[Guest ricoc90]

I think it depends on the system that you are using, If you are using the UEFI BIOS settings then Drivers64UEFI will jumpstart it. If you are using a Legacy BIOS then Drivers64 will jumpstart the apps.efi.

Right?

I think so. I used an 4089 installer, so the drivers were already there  I'm on Legacy by the way,

 

This is what Clover shows shortly before the boot entries show up:

 

 

And this is the SSD:

 

 

 

It looks like the missing keybag error is for vm, Preboot and Recovery. But the actual partition (Naamloos) is fine.

[Cyberdevs]

I get the same message with UEFI, and I guess it's because clover is loading the apps.efi rather that the macOS, the default path for apfs.efi is /usr/standalone/i386/apfs.efi and macOS will load it in the boot process and since we need to override the default path for clover to be able to load the apfs volumes during the boot, we get that message.

 

But regardless the end result is the same. Clover initializes the APFS partition and macOS High Sierra will load.

 

At least this what I think.

[Philip Petev]

before Create the PKG put the drivers in /src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI

Ok for Build Package

 

For Legacy and (ESP no UEFI) you can also put in /drivers-Off/drivers64 but Rename apfs-64.efi

because you can not build two drivers with the same name

 

That can be done with the Build_Clover.command. It seems this is the only working method of adding those drivers to the package (putting the files in Clover/FileSystems/HFSPlus doesn't seems to work). I'll see what I can do about that.