Clover General discussion

[nexusneko]

9 hours ago, Andres ZeroCross said:

I have made fresh install macOS Catalina Beta 9 several days ago and install CLOVER r5089 succesfully. But now i want to update to r5091, and this errors come again.
There is no corrupt file system here, there is no electricity problem too. 

Can you give me "the light" @vector sigma 

Installer Log 29-Sep-2019.txt

 

Same here.

 

 

[vector sigma]

11 hours ago, Andres ZeroCross said:

I have made fresh install macOS Catalina Beta 9 several days ago and install CLOVER r5089 succesfully. But now i want to update to r5091, and this errors come again.
There is no corrupt file system here, there is no electricity problem too. 

Can you give me "the light" @vector sigma 

Installer Log 29-Sep-2019.txt

 

2 hours ago, nexusneko said:

Same here.

Sorry guys I can't enlighten any one because internet is full of "An unexpected error occurred while moving files to the final destination". The only solution appear to be, if you read those articles, is to repairing your disk permissions...

[SavageAUS]

I'm not sure if this is the correct place to post this but i believe its a CLOVER issue or CLOVER config error on my end.

In my laptop i have HD4400 iGPU and according to intel its base frequency should be 200MHz but when running in macOS my iGPU is idling at 550MHZ (0.55).

I am assuming this is not an issue? but surely this will drain my battery faster than it should.

Any help would be appreciated.

 

CLOVER.zip

[Slice]

Clover has nothing to do with GFX frequency. Clover has a possibility to patch something if we will know what and where.

Otherwise see if you use Lilu+WhateverGreen. There are not my kexts.

[n.d.k]

It seems there's an incompatibles with macOS 10.15 headers that caused the gcc 9 fail to compile. It's explained here in detail and how to patch it https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835

 

 

PS.  I think Catalina beta 10 already included the fix, I see the patch already in Availability.h

Edited October 1, 2019 by n.d.k

[Slice]

Big thanks for the link.

I just have to say that beta-Catalina is not reliable platform to build Clover.

[n.d.k]

Just tried to compile it with beta 10, still no go, same old failure.    .

[chris1111]

No problème compilation of Clover on macOS Catalina Beta 10  compilation from Source Forge even in Github no issue here

 

Edited October 1, 2019 by chris1111

[n.d.k]

XCODE8 mode worked just fine for Clover, just the GCC is having problem compiling with Catalina and XCODE 11.

[vector sigma]

5 hours ago, n.d.k said:

It seems there's an incompatibles with macOS 10.15 headers that caused the gcc 9 fail to compile. It's explained here in detail and how to patch it https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835

 

 

PS.  I think Catalina beta 10 already included the fix, I see the patch already in Availability.h

That was an old patch for another error by Apple before in Xcode 11 beta1. Catalina is and was ok, it is Xcode 11 GM (or the equivalent CLT) and their respective ../include path the problem. In fact using Xcode 11 beta 2 is it still good.

 

EDIT
Yes the fixincludes is a possible solutions, may be also gcc/darwing.c is a good place. Any way I'm sure that anything will be done until Catalina and Xcode will be in a pre-release state due to their license agreement.

 

Edited October 1, 2019 by vector sigma

[Andres ZeroCross]

15 hours ago, vector sigma said:

That was an old patch for another error by Apple before in Xcode 11 beta1. Catalina is and was ok, it is Xcode 11 GM (or the equivalent CLT) and their respective ../include path the problem. In fact using Xcode 11 beta 2 is it still good.

 

EDIT
Yes the fixincludes is a possible solutions, may be also gcc/darwing.c is a good place. Any way I'm sure that anything will be done until Catalina and Xcode will be in a pre-release state due to their license agreement.

 

Finally i can install CLOVER in my system without error,, the solution is "I must tick install in UEFI only". Why??? Did clover pkg not support legacy in Catalina???

[Slice]

1 hour ago, Andres ZeroCross said:

Finally i can install CLOVER in my system without error,, the solution is "I must tick install in UEFI only". Why??? Did clover pkg not support legacy in Catalina???

As well as on older systems. The problem is installing PBR sector which is system protected.

Usual solution is to run installer from other system for root folder will not be protected by this system. So run from other drive.

[n.d.k]

1 hour ago, Slice said:

As well as on older systems. The problem is installing PBR sector which is system protected.

Usual solution is to run installer from other system for root folder will not be protected by this system. So run from other drive.

sudo mount -uw /

This will do before installing clover.

[vector sigma]

1 hour ago, n.d.k said:

sudo mount -uw /

This will do before installing clover.

What do you think the installer doing when ask "Clover wants to make the root file system read-write. The change is temporary until the next reboot" ?

[vector sigma]

6 hours ago, Andres ZeroCross said:

Finally i can install CLOVER in my system without error,, the solution is "I must tick install in UEFI only". Why??? Did clover pkg not support legacy in Catalina???

 

4 hours ago, Slice said:

As well as on older systems. The problem is installing PBR sector which is system protected.

Usual solution is to run installer from other system for root folder will not be protected by this system. So run from other drive.

The log Andres posted, show that the problem is when the Payload that contains boot sectors is expanded and things should be moved to /usr/standalone/i386/, so for that, I'm sure is not a problem installing the partition boot sector (that per se, should not cause the failure of the installer, but instead a failure at boot..). Only it cannot move files to the destination: this happen when the files or the containing directory have wrong permissions or is busy because used by the system (no surprises as in Catalina this is a know bug when updates are turned on).... why the installation continue without errors selecting "UEFI only" i.e. due to the fact that bios sectors aren't, in this case, selected to be installed. Solutions?

 

- Wait for Catalina GM and see if Apple turned off some additional observers active during the beta stage.

or

- rewrite the installer to not install boot sectors in /usr/standalone/i386/

 

The second require multiple changes, but no one can say if we can solve the problem since we are installing other things in other locations inside the System partition. It would be interesting to know also if the problem happens when boot0af, boot0ss, boot1h, boot6, boot7, boot1f32 etc. needs to be overwritten and/or the package succeded when no one of them are present.

 

Edited October 2, 2019 by vector sigma
typo

[chris1111]

I dont have anny issue for Catalina to Install Legacy ESP of course 

 

The only known issue is the Legacy install non ESP ON apfs file system. this issue is known since first Beta of Mojave

Edited October 2, 2019 by chris1111
this issue is known since first Beta of Mojave

[Andres ZeroCross]

22 minutes ago, chris1111 said:

I dont have anny issue for Catalina to Install Legacy ESP of course 

 

The only known issue is the Legacy install non ESP ON apfs file system. this issue is known since first Beta of Mojave

I always install CLOVER in ESP



With selected options above it will fail,,




With selected options above, it will success

Edited October 2, 2019 by Andres ZeroCross

[vector sigma]

4 minutes ago, Andres ZeroCross said:

I always install CLOVER in ESP

...but bootsectors are always installed in /usr/standalone/i386 even if you select the ESP..... if you install Clover EFI.

[Andres ZeroCross]

6 minutes ago, vector sigma said:

...but bootsectors are always installed in /usr/standalone/i386 even if you select the ESP..... if you install Clover EFI.

But why @chris1111 got no problem with Legacy ESP installation CLover in Catalina??

[chris1111]

18 minutes ago, Andres ZeroCross said:

But why @chris1111 got no problem with Legacy ESP installation CLover in Catalina??

 

[vector sigma]

1 hour ago, Andres ZeroCross said:

But why @chris1111 got no problem with Legacy ESP installation CLover in Catalina??

in truth I see only two guys with this problem..

Can you remove boot sectors from /usr/standalone/i386 and retry?

[chris1111]

5 hours ago, vector sigma said:

in truth I see only two guys with this problem..

Can you remove boot sectors from /usr/standalone/i386 and retry?

Is this possible to correct the Pure Legacy boot file and the Legacy script for installing in APFS System ?

Edited October 3, 2019 by chris1111

[arsradu]

About the ports issue I was mentioning above, this is what the user gets when it can't access the site due to restricted ports.

 

This is why I was suggesting switching from ftp:// to https:// so it can access the URLs.

 

buildme, Clover v2.5k r5093 (SHA: 9ee0998f)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) make pkg
 3) make iso
 4) build all
 5) test build (no autogen, no boot files)
 6) status
 7) update Clover
 8) update Clover (reset changes)
 9) show diff
10) open drivers directory
11) clean BaseTools
12) quit
Please enter your choice: 4
[CHECK XCODE]
- Building GCC 9.2.0 toolchain for x64
- to /Users/jimmy/src/opt/local/cross/bin/x86_64-clover-linux-gnu
  Running on Mac OS X 10.15, with x86_64 architecture.
  Using Xcode SDK: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
Status: gmp-6.1.2 not found.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:02:36 --:--:--     0
curl: (7) Failed to connect to ftp.gnu.org port 21: Operation timed out
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...35 completed.

[Process completed]

This issue does not occur when building with ".buildme XCODE8", I'm guessing probably because it's not using those URLs in this case.

 

Also, there might be a fix to the forever known "screen flashes on boot" for AMD video cards. The issue seems to occur due to mode switching from ARGB8888 to ARGB2101010. And it might require something similar to RadeonDeInit which was already implemented a while ago. So it needs Clover devs' help. So...anyone willing to help fix this ancient issue once and for all?

 

If you guys already know what I'm talking about, then I guess you don't need more details. If not, I can provide more info, if anyone's interested in helping with a fix.  

Edited October 3, 2019 by arsradu

[artur_pt]

hello Slice

 

last commit in git give me this

 

 

thanks

[chris1111]

1 hour ago, zkingtut said:

Why I have this boot arg: amfi_get_out_of_my_way=1 

It doesn't exist in Config.plist/boot

I see it only in clover option when boot up 

Thank you 

See maybe is in nvram ?