Clover General discussion

[oSxFr33k]

Ran into two problems for legacy bios (non EFi).  After creating a second volume inside the same APFS container and installing Catalina it won’t boot, clover installed in EFI.  The first volume is Mojave no issues.  Is it possible clover in EFI won’t boot 2nd 3rd etc volumes in same container?  I should say it starts to boot but its never able to complete the boot process. I see from verbose boot it stops in my case at the IOUSBHost Interface and the last thing I see before the screen text becomes frozen and shattered with the prohibited sign is the message ‘still waiting for root device’.  I have to assume that the kexts in the EFI partition are not being read?
 

The second problem is when I partition the single hard drive which creates two containers and install Catalina into the 2nd container’s volume, it only goes through the initial first part of the install process after which a reboot there is no second phase to install to MacOS from clover GUI even though the data install folder does exist with the correct size and files inside the 2nd container’s volume. 

 

i just now tried this on a SSD with legacy bios same results so it’s not related to the hard drive versus SSD.  

 

Is there something more I need to do to have multiple MacOS Installs on the same APFS Hard Drive non SSD?  
 

I have not tried this on a modem EFI bios machine just legacy.  Should there only be one EFI partition even after you partition the drive into multiple containers?
 

Has anyone tried this on their legacy bios machines getting the same results as me?

 

 

Edited:

This is definitely related to legacy bios I tried the same hard drive in an EFI bios machine no problems booting either volume from the same container, and was able to complete the install if the volume was on the 2nd container.  Maybe only related to this motherboard GA-G41M-ES2L?

 

Edited Again:

I can confirm with another legacy bios machine some issue between the Bios and more current clover revisions from r5093 through r5097 is what I tested so far.  

 

 

Edited October 21, 2019 by oSxFr33k

[LockDown]

Compiling clover using GCC53 all good now?

[Slice]

4 hours ago, ellaosx said:

Compiling clover using GCC53 all good now?

No problem in Mojave. Catalina requires patches for headers.

[Badruzeus]

14 hours ago, oSxFr33k said:

I can confirm with another legacy bios machine some issue between the Bios and more current clover revisions from r5093 through r5097 is what I tested so far.

I have no issue, just dd boot0ss to disk0 && boot1f32 to disk0s1 with Legacy (GPT + EFI). Having 2 macOS(es) inside APFS Container: Mojave 10.14.6 + Catalina 10.15 and they're able to boot. Not really sure with IOUSBHost issue, OS version specific may be? I remember still need "FixOwnership" under Device if booting Clover Legacy (I use patched ACPI for USB btw)

Edited October 21, 2019 by Badruzeus

[oSxFr33k]

4 hours ago, Badruzeus said:

I have no issue, just dd boot0ss to disk0 && boot1f32 to disk0s1 with Legacy (GPT + EFI). Having 2 macOS(es) inside APFS Container: Mojave 10.14.6 + Catalina 10.15 and they're able to boot. Not really sure with IOUSBHost issue, OS version specific may be? I remember still need "FixOwnership" under Device if booting Clover Legacy (I use patched ACPI for USB btw)

 

 

It just stops booting at that point nothing wrong with USB because the other drive has Catalina on it and it boots just fine.   I also have a second Catalina installed onto 2nd volume of first container and first volume of 2nd container.   I have to try this instead I have been using boot0af forever with legacy bios, never tried boot0ss, and maybe now with new APFS need boot0ss?.  Are you using the legacy only clover installer or the latest clover package that allows for legacy settings?  During clover install you chose boot0ss then reboot then in terminal ran dd command?  What if I have a second container what would the command be for that, just change to "&& to boot1s1' for example?  Is there a new thread going on about this with new APFS and legacy boot would like to get more information on it.  Thanks!

Edited October 21, 2019 by oSxFr33k

[Slice]

21 minutes ago, oSxFr33k said:

 

 

It just stops booting at that point nothing wrong with USB because the other drive has Catalina on it and it boots just fine.   I also have a second Catalina installed onto 2nd volume of first container and first volume of 2nd container.   I have to try this instead I have been using boot0af forever with legacy bios, never tried boot0ss, and maybe now with new APFS need boot0ss?.  Are you using the legacy only clover installer or the latest clover package that allows for legacy settings?  During clover install you chose boot0ss then reboot then in terminal ran dd command?  What if I have a second container what would the command be for that, just change to "&& to boot1s1' for example?  Is there a new thread going on about this with new APFS and legacy boot would like to get more information on it.  Thanks!

It looks like a bug. We shouldn't install boot1*** into disk1 volume because it is APFS container, not real disk.

Otherwise I have one drive disk0 with installed boot sectors. I have EFI folder on it with legacy Clover boot (it was boot6) and it successfully starts Mojave from APFS container in legacy mode. Computer #1 in my signature.

[smolderas]

Is there a how to to migrate from sourceforge to GitHub? What do I need to do to re-initialise the gitlab locally on Mac?

 

Edit: I see, there is a buildme script.

Edited October 21, 2019 by smolderas

[Matgen84]

1 hour ago, smolderas said:

Is there a how to to migrate from sourceforge to GitHub? What do I need to do to re-initialise the gitlab locally on Mac?

 

Edit: I see, there is a buildme script.

 

You can use 'clovergit' by @Sherlocks to create local Clover Github Repo (file in attachment): this script is a pre-script that starts buildme after cloning 

clovergit

[oSxFr33k]

13 hours ago, Slice said:

It looks like a bug. We shouldn't install boot1*** into disk1 volume because it is APFS container, not real disk.

Otherwise I have one drive disk0 with installed boot sectors. I have EFI folder on it with legacy Clover boot (it was boot6) and it successfully starts Mojave from APFS container in legacy mode. Computer #1 in my signature

 

 

So explain what I need to do to fix this, run clover as usual choosing the boot0af or boot0ss option, which one?  After clover install reboot then run the dd command after clover is installed and which one will I install with the dd command?

 

Can you reply with the complete dd command here please or a link to the procedure. 

I remember now some bug for legacy bios in some clover legacy installs, requiring the dd command to be run and only the one command not both as Badruzeus had replied with?
 

Thanks!

 

Edited October 22, 2019 by oSxFr33k

[Slice]

9 hours ago, oSxFr33k said:

 

 

So explain what I need to do to fix this, run clover as usual choosing the boot0af or boot0ss option, which one?  After clover install reboot then run the dd command after clover is installed and which one will I install with the dd command?

 

Can you reply with the complete dd command here please or a link to the procedure. 

I remember now some bug for legacy bios in some clover legacy installs, requiring the dd command to be run and only the one command not both as Badruzeus had replied with?
 

Thanks!

 

First find your drives

iMac-Sergey:~ sergey$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         271.2 GB   disk0s2
   3:                  Apple_HFS HighHD                  118.3 GB   disk0s3
   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4
   5:                        EFI NO NAME                 104.9 MB   disk0s5
   6:       Microsoft Basic Data Data                    109.7 GB   disk0s6

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +271.2 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume MacHD                   63.3 GB    disk1s1
   2:                APFS Volume Preboot                 46.5 MB    disk1s2
   3:                APFS Volume Recovery                1.0 GB     disk1s3
   4:                APFS Volume VM                      5.4 GB     disk1s4

In my case there is disk0s1 as EFI partition.

Install MBR boot sector:

cd src/Clover/CloverPackage/CloverV2/BootSectors/
dd if=/dev/rdisk0 count=1 bs=512 of=origMBR
cp origMBR newMBR
dd if=boot0af of=newMBR bs=1 count=440 conv=notrunc
dd if=newMBR of=/dev/rdisk0 count=1 bs=512

Then install PBR boot sector

dd if=/dev/rdisk0s1 count=1 bs=512 of=origbs
cp boot1f32 newbs
dd if=origbs of=newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=newbs of=/dev/rdisk0s1 count=1 bs=512

Then copy boot file into EFI partition

sudo diskutil mount EFI
cd ../Bootloaders/x64
cp boot6 /Volumes/EFI/boot

Then copy EFI folder and tune it.

[ryanroy837]

Thanks for this information. It useful. also to lower your burden of derivatives calculations  Derivative Calculator might be useful.

Edited November 9, 2019 by ryanroy837

[Slice]

7 hours ago, telepati said:

can't open in safe mode? Always getting this verbose;

 

Are you using Whatevergreen? AFAIK it is their bug.

[telepati]

13 hours ago, Slice said:

Are you using Whatevergreen? AFAIK it is their bug.

Yes, good point. And also with a DP connection. I must move this to WEG thread then. Thanks @Slice

[Pene]

I added some gcc9 building workarounds for Catalina with latest commit, it should now be able to produce a working gcc9 build on Catalina.

To do this, first completely delete your old attempts (delete ~/src/opt/) and start fresh.

[Pene]

On 10/12/2019 at 3:32 AM, Sherlocks said:

....build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/devicetreelib.h not found in /Users/sherlocks/src/CloverBootloader/Library/DeviceTreeLib/DeviceTreeLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/devicetreelib.h not found in /Users/sherlocks/src/CloverBootloader/Library/DeviceTreeLib/DeviceTreeLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/ocguardlib.h not found in /Users/sherlocks/src/CloverBootloader/Library/OcGuardLib/OcGuardLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/ocguardlib.h not found in /Users/sherlocks/src/CloverBootloader/Library/OcGuardLib/OcGuardLib.inf

.build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/macholib.h not found in /Users/sherlocks/src/CloverBootloader/Library/MachoLib/MachoLib.inf

build: : warning: Module MetaFile [Sources] is missing local header!

    Local Header: /users/sherlocks/src/cloverbootloader/include/library/macholib.h not found in /Users/sherlocks/src/CloverBootloader/Library/MachoLib/MachoLib.inf

These warnings were due to inverse include order of MdePkg.dec and CloverPkg.dec.

I corrected it with latest commit.

Edited October 23, 2019 by Pene

[chris1111]

big big problem on latest Catalina 10.15 (19A603) and Clover Legacy /esp

 

if you have already the boot file in usr/standalonbe/i386

 

the package failed!  You need delete this for make it work

sudo rm -r "${3}/usr/standalone/i386/boot1h"

sudo rm -r "${3}/usr/standalone/i386/boot1f32"

sudo rm -r "${3}/usr/standalone/i386/boot1f32alt"

sudo rm -rf "${3}/usr/standalone/i386/boot1h2"

sudo rm -rf "${3}/usr/standalone/i386/boot0af"

sudo rm -rf "${3}/usr/standalone/i386/boot0ss"

sudo rm -rf "${3}/usr/standalone/i386/boot1x"

sudo rm -rf "${3}/usr/standalone/i386/boot1xalt"

sudo rm -rf "${3}/usr/standalone/i386/Description.txt"

sudo rm -rf "${3}/usr/standalone/i386/Installation.txt"

sudo rm -rf "${3}/usr/standalone/i386/x64

[Pene]

40 minutes ago, chris1111 said:

big big problem on latest Catalina 10.15 (19A603) and Clover Legacy /esp

 

if you have already the boot file in usr/standalonbe/i386

 

the package failed!  You need delete this for make it work

sudo rm -r "${3}/usr/standalone/i386/boot1h"

sudo rm -r "${3}/usr/standalone/i386/boot1f32"

sudo rm -r "${3}/usr/standalone/i386/boot1f32alt"

sudo rm -rf "${3}/usr/standalone/i386/boot1h2"

sudo rm -rf "${3}/usr/standalone/i386/boot0af"

sudo rm -rf "${3}/usr/standalone/i386/boot0ss"

sudo rm -rf "${3}/usr/standalone/i386/boot1x"

sudo rm -rf "${3}/usr/standalone/i386/boot1xalt"

sudo rm -rf "${3}/usr/standalone/i386/Description.txt"

sudo rm -rf "${3}/usr/standalone/i386/Installation.txt"

sudo rm -rf "${3}/usr/standalone/i386/x64

When are you getting this error? Some more details please.

[chris1111]

5 hours ago, Pene said:

When are you getting this error? Some more details please.

here the details @pene

Installer is the one from Github

and its the same result with my compilling package

Attaching complete Log file

 

 

What I see as an error in the Log is this

Spoiler

Oct 24 05:05:25 iMac-de-chris installd[595]: PackageKit: Shoving /Library/InstallerSandboxes/.PKInstallSandboxManager/562FEAE5-CE2E-4B7E-B6DE-8B02B02E3FAF.activeSandbox/Root (4 items) to /
Oct 24 05:05:25 iMac-de-chris shove[4569]: [source=file] failed _RelinkFile(/Library/InstallerSandboxes/.PKInstallSandboxManager/562FEAE5-CE2E-4B7E-B6DE-8B02B02E3FAF.activeSandbox/Root/usr/standalone/i386/boot1h2, /usr/standalone/i386/boot1h2): Directory not empty
 

 

 

 

edit ******

Also whenever it fails must also delete this on the root disk because the process does not know how to complete

Spoiler

 

 

Historique de Programme d’installation 24-Oct-2019.txt.zip

Edited October 24, 2019 by chris1111

[Sherlocks]

3 hours ago, chris1111 said:

here the details @pene

Installer is the one from Github

and its the same result with my compilling package

Attaching complete Log file

 

 

What I see as an error in the Log is this

  Reveal hidden contents

Oct 24 05:05:25 iMac-de-chris installd[595]: PackageKit: Shoving /Library/InstallerSandboxes/.PKInstallSandboxManager/562FEAE5-CE2E-4B7E-B6DE-8B02B02E3FAF.activeSandbox/Root (4 items) to /
Oct 24 05:05:25 iMac-de-chris shove[4569]: [source=file] failed _RelinkFile(/Library/InstallerSandboxes/.PKInstallSandboxManager/562FEAE5-CE2E-4B7E-B6DE-8B02B02E3FAF.activeSandbox/Root/usr/standalone/i386/boot1h2, /usr/standalone/i386/boot1h2): Directory not empty
 

 

 

 

edit ******

Also whenever it fails must also delete this on the root disk because the process does not know how to complete

  Reveal hidden contents

 

 

Historique de Programme d’installation 24-Oct-2019.txt.zip

 

there is no problem.

latest commits.

i cleaned src folders and 

try it again

clovergit_v1.1.zip

 

15 hours ago, Pene said:

These warnings were due to inverse include order of MdePkg.dec and CloverPkg.dec.

I corrected it with latest commit.

 

thank you for fix

[Pene]

7 hours ago, chris1111 said:

here the details @pene

Installer is the one from Github

and its the same result with my compilling package

I see, now I understand that this error appears for you when using the installer... Never really got into details regarding the installer, so perhaps someone else can help there.

Edited October 24, 2019 by Pene

[ameenjuz]

I have recently this issue on Catalina 10.15 with Clover_v2.5k_r5097  sometime my laptop occurs automatically reboot

when I boot again from start  this screenshot I captured

I solved this issue with OpenCore bootloader Using this option (Kernel->Quirk->PowerTimeoutKernelPanic=true)  on OpenCore 0.5.2 

but this (PowerTimeoutKernelPanic=true} option does not exist in clover bootloader

how to fix this issue on Catalina using Clover bootloader

 

 

[Andres ZeroCross]

9 hours ago, chris1111 said:

here the details @pene

Installer is the one from Github

and its the same result with my compilling package

Attaching complete Log file

 

 

What I see as an error in the Log is this

  Reveal hidden contents

Oct 24 05:05:25 iMac-de-chris installd[595]: PackageKit: Shoving /Library/InstallerSandboxes/.PKInstallSandboxManager/562FEAE5-CE2E-4B7E-B6DE-8B02B02E3FAF.activeSandbox/Root (4 items) to /
Oct 24 05:05:25 iMac-de-chris shove[4569]: [source=file] failed _RelinkFile(/Library/InstallerSandboxes/.PKInstallSandboxManager/562FEAE5-CE2E-4B7E-B6DE-8B02B02E3FAF.activeSandbox/Root/usr/standalone/i386/boot1h2, /usr/standalone/i386/boot1h2): Directory not empty
 

 

 

 

edit ******

Also whenever it fails must also delete this on the root disk because the process does not know how to complete

  Reveal hidden contents

 

 

Historique de Programme d’installation 24-Oct-2019.txt.zip

 

My Old Problem, but fix with tick "Install in UEFI Only"

[chris1111]

8 hours ago, Sherlocks said:

 

there is no problem.

latest commits.

i cleaned src folders and 

try it again

clovergit_v1.1.zip

 

 

thank you for fix

Issue is remain Clover Legacy ESP to internal drive package failled

Install to external drive no issue, install to another Internal drive no issue. Issue is on the Catlina main drive

Clover Legacy ESP

 

I fix issue I install Clover Legacy ESP to my Mojave SSD  Boot to Catalina from Mojave EFI  

 

Edited October 24, 2019 by chris1111

[n.d.k]

On 10/23/2019 at 3:55 PM, Pene said:

I added some gcc9 building workarounds for Catalina with latest commit, it should now be able to produce a working gcc9 build on Catalina.

To do this, first completely delete your old attempts (delete ~/src/opt/) and start fresh.

Is this really working?...because, i forgot how many times i tried to compile this thing on Catalina using all kind of fixes method i found on internet.  It doesn't seems to get it compiled on my computer. It crashed my hackintosh every time when i tried to make it. I am gonna give it try with your work around. And will report back!...Thanks..finger cross!..lol

 

Ok..no go, same crashing and 31mb boot log..wow..case close!...no more attempt, period.

Edited October 25, 2019 by n.d.k
Update result

[Pene]

11 hours ago, n.d.k said:

Is this really working?...

Building gcc9 toolchain, and also building Clover with it on Catalina should indeed be working now. It works on my system, and I have several other reports that it is working, as long as you start fresh (delete your old toolchain, as I mentioned before, as GMP has to be recompiled). I'm sure others can confirm it is working also with the latest commits from git repository. I think you should check something local at your end. Unclean src, Xcode, something else. Especially as you are saying it is crashing your system when you compile.

Edited October 25, 2019 by Pene