Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,059 posts in this topic

Recommended Posts

STLVNUB
STLVNUB
Posted
Posted
1 hour ago, Jief_Machak said:

Yes, if you didn't clone with recurse submodule, a "git pull --recurse-submodule" won't do anything.

after clone without --recurse-submodule, you can do "git submodule update --init", or re-clone.

Still error

unknown option: --recurse-submodule

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
1 minute ago, STLVNUB said:

Still error

unknown option: --recurse-submodule

You have to do a bit of research on your own !

 

Here's what I have 

error: unknown option `rescurse-submodule'
usage: git clone [<options>] [--] <repo> [<dir>]

    -v, --verbose         be more verbose
    -q, --quiet           be more quiet
    --progress            force progress reporting
    -n, --no-checkout     don't create a checkout
    --bare                create a bare repository
    --mirror              create a mirror repository (implies bare)
    -l, --local           to clone from a local repository
    --no-hardlinks        don't use local hardlinks, always copy
    -s, --shared          setup as shared repository
    --recurse-submodules[=<pathspec>]
                          initialize submodules in the clone
    -j, --jobs <n>        number of submodules cloned in parallel
    --template <template-directory>
                          directory from which templates will be used
    --reference <repo>    reference repository
    --reference-if-able <repo>
                          reference repository
    --dissociate          use --reference only while cloning
    -o, --origin <name>   use <name> instead of 'origin' to track upstream
    -b, --branch <branch>
                          checkout <branch> instead of the remote's HEAD
    -u, --upload-pack <path>
                          path to git-upload-pack on the remote
    --depth <depth>       create a shallow clone of that depth
    --shallow-since <time>
                          create a shallow clone since a specific time
    --shallow-exclude <revision>
                          deepen history of shallow clone, excluding rev
    --single-branch       clone only one branch, HEAD or --branch
    --no-tags             don't clone any tags, and make later fetches not to follow them
    --shallow-submodules  any cloned submodules will be shallow
    --separate-git-dir <gitdir>
                          separate git dir from working tree
    -c, --config <key=value>
                          set config inside the new repository
    -4, --ipv4            use IPv4 addresses only
    -6, --ipv6            use IPv6 addresses only
    --filter <args>       object filtering

It's not extremely hard to see that I just forgot the s 

    --recurse-submodules[=<pathspec>]

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted
11 minutes ago, Jief_Machak said:

You have to do a bit of research on your own !

 

Here's what I have 


error: unknown option `rescurse-submodule'
usage: git clone [<options>] [--] <repo> [<dir>]

    -v, --verbose         be more verbose
    -q, --quiet           be more quiet
    --progress            force progress reporting
    -n, --no-checkout     don't create a checkout
    --bare                create a bare repository
    --mirror              create a mirror repository (implies bare)
    -l, --local           to clone from a local repository
    --no-hardlinks        don't use local hardlinks, always copy
    -s, --shared          setup as shared repository
    --recurse-submodules[=<pathspec>]
                          initialize submodules in the clone
    -j, --jobs <n>        number of submodules cloned in parallel
    --template <template-directory>
                          directory from which templates will be used
    --reference <repo>    reference repository
    --reference-if-able <repo>
                          reference repository
    --dissociate          use --reference only while cloning
    -o, --origin <name>   use <name> instead of 'origin' to track upstream
    -b, --branch <branch>
                          checkout <branch> instead of the remote's HEAD
    -u, --upload-pack <path>
                          path to git-upload-pack on the remote
    --depth <depth>       create a shallow clone of that depth
    --shallow-since <time>
                          create a shallow clone since a specific time
    --shallow-exclude <revision>
                          deepen history of shallow clone, excluding rev
    --single-branch       clone only one branch, HEAD or --branch
    --no-tags             don't clone any tags, and make later fetches not to follow them
    --shallow-submodules  any cloned submodules will be shallow
    --separate-git-dir <gitdir>
                          separate git dir from working tree
    -c, --config <key=value>
                          set config inside the new repository
    -4, --ipv4            use IPv4 addresses only
    -6, --ipv6            use IPv6 addresses only
    --filter <args>       object filtering

It's not extremely hard to see that I just forgot the s 


    --recurse-submodules[=<pathspec>]

 

Trouble wos it worked before 

Something has changed

  • Like 1
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted (edited)

Clover and BS begin to approach :D
after downloading full installer of large hole 11.0.1
http://swcdn.apple.com/content/downloads/34/14/001-58883-A_X44PVH3RKY/loxggyh4g06lfvijpw4uxr2u7jht9spza8/InstallAssistant.pkg
after having fixed the kexts of the various macOS releases, that is, I left each version with its kexts, except
Lilu
Weg
FakeSMC/VirtualSMC 
that I put in the other folder
with Clover 5126 I tried updating BS beta10 to the new release
3 restarts
all as smooth as oil
here's the result on the Z370 :thumbsup_anim:

1495870306_Schermata2020-10-29alle22_31_

Edited by iCanaro
  • Like 5
  • Haha 1
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted (edited)
30 minutes ago, Jief_Machak said:

No I don't. But I have an advantage : I made this change (submodule) !

how you building it?

I'm a brain dead old fella

Edited by STLVNUB
  • Haha 1
Link to comment
Share on other sites
tluck
tluck
Posted
Posted

FWIW this is the essence of my build clover script with xcode

 

EDK2DIR="/opt/Source/edk2"

CLOVERDIR="${EDK2DIR}"/Clover

EBUILD_OPTIONAL_ARGS="-t XCODE8 -fr"

 

git --git-dir=${CLOVERDIR}/.git -C ${CLOVERDIR} pull --force --recurse-submodules

 

cd ${CLOVERDIR}

 

source ./edksetup.sh

./ebuild.sh $EBUILD_OPTIONAL_ARGS 2>&1 | grep -v Werror

  • Thanks 1
  • Haha 1
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted (edited)

I have updated 11.01, have to go through OC only, can't update via clover V.5126, why is that? Can someone please tell me

Edited by Slice
don't use red color. It is for moderators
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
12 hours ago, iCanaro said:

Clover and BS begin to approach :D
after downloading full installer of large hole 11.0.1
http://swcdn.apple.com/content/downloads/34/14/001-58883-A_X44PVH3RKY/loxggyh4g06lfvijpw4uxr2u7jht9spza8/InstallAssistant.pkg
after having fixed the kexts of the various macOS releases, that is, I left each version with its kexts, except
Lilu
Weg
FakeSMC/VirtualSMC 
that I put in the other folder
with Clover 5126 I tried updating BS beta10 to th

Spoiler

 

e new release
3 restarts
all as smooth as oil
here's the result on the Z370 :thumbsup_anim:

 

Spoiler

1495870306_Schermata2020-10-29alle22_31_

 

Can you tell me a tip or not.
With boot cloverV.5126
Thank you dear friend

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
8 hours ago, STLVNUB said:

how you building it?

I'm a brain dead old fella


Hi @STLVNUB Have a nice day

As usual, you have to make a <DIR>

git clone --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git <DIR>

To update and build new Clover: use Buildme.sh script inside cloverbootloader directory.This script can update cloverbootloader and OC modules. Of build Clover and make a pkg.
That's all :)

  • Thanks 1
Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted

And one thing,,

OpenCore has quirck namely "IgnoreInvalidFlexRatio",

Some Lenovo Notebook need this quirk (I have found this case in Lenovo X250 and X240).

Same booter config with Clover just stuck at "end random seed xxxxxx / BS Exit services" but in OpenCore need to enable this quirk to bypass the "end randomseed/BS Exit services" log.

But CLOVER doesn't have this quirck,,

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
2 hours ago, Andres ZeroCross said:

And one thing,,

OpenCore has quirck namely "IgnoreInvalidFlexRatio",

Some Lenovo Notebook need this quirk (I have found this case in Lenovo X250 and X240).

Same booter config with Clover just stuck at "end random seed xxxxxx / BS Exit services" but in OpenCore need to enable this quirk to bypass the "end randomseed/BS Exit services" log.

But CLOVER doesn't have this quirck,,

Clover has this quirk since the first version. It was developed by bcc9 in 2009 for Chameleon and used in Clover without any quirks.

  • Like 2
Link to comment
Share on other sites
Denisuu
Denisuu
Posted
Posted (edited)
20 hours ago, kushwavez said:

Kp shows that the cause is the BrcmPatchRAM3. Make sure you have the newest version all of your kexts, also make sure you use the correct ones for your Bluetooth. (BrcmPatchRAM3 and BrcmFirmwareData)

 

I'm using BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext, BrcmNonPatchRAM2.kext and BrcmPatchRAM3.kext on Clover r5122.

Switching BrcmFirmwareRepo.kext with BrcmFirmwareData.kext results in the same kpanic.

 

I even tried to remove all the Brcm kexts but then booting halts on prohibited sign with scrambled text.

 

 

image.png

Edited by Denisuu
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted
3 hours ago, Andres ZeroCross said:

Maybe this is a stupid questions, 

But, how did you all install CLOVER to Big Sur??

I always fail install clover.pkg in Big Sur,, I always use manual Copy files.


 

I've only been running a manual copy for a long time.
But actually putting the procedure by hand so you don't have a problem installing from any macOS, that would be a good idea.
Have you tried installing Clover using Clover App???

5 hours ago, naiclub said:

Can you tell me a tip or not.
With boot cloverV.5126
Thank you dear friend

what made the difference from me was putting in OTHER the top 3 kexts to start hacks
Lilu
Whatevergreen
Slice FakeSMC or VirtualSMC
then all the other kexts you can keep them in folder 11

  • Like 3
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted
31 minutes ago, Denisuu said:

I'm using BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext, BrcmNonPatchRAM2.kext and BrcmPatchRAM3.kext on Clover r5122.

Switching BrcmFirmwareRepo.kext with BrcmFirmwareData.kext results in the same kpanic.

 

I even tried to remove all the Brcm kexts but then booting halts on prohibited sign with scrambled text.

to use for catalina and BigSur:

BrcmBluetoothInjector.kext

BrcmFirmwareData.kext

BrcmPatchRAM3.kext

  • Like 2
Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted (edited)
1 hour ago, Denisuu said:

 

I'm using BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext, BrcmNonPatchRAM2.kext and BrcmPatchRAM3.kext on Clover r5122.

Switching BrcmFirmwareRepo.kext with BrcmFirmwareData.kext results in the same kpanic.

 

I even tried to remove all the Brcm kexts but then booting halts on prohibited sign with scrambled text.

You should use only BrcmBluetoothInjector, BrcmFirmwareData and BrcmPatchRAM3 if they're in Clover/kexts. BrcmFirmwareRepo is only for L/E. 

 

Also I can't really see the texts correctly but for me it saying "Still waiting for root device" That means the system can't see your internal drives. 

 

Here I made you a new EFI. 

Deleted unused kexts:

- CpuTscSync.kext (I think it's do nothing for you)

- HWPEnabler.kext (not needed)

- BrcmFirmwareRepo.kext (wrong, replaced with BrcmFirmwareData.kext)

- BrcmNonPatchRAM2.kext (wrong, use BrcmPatchRAM3 only)

 

Added new ones, also added CtlnaAHCIPort.kext for your internal drives, not sure if it's needed or not, I did that because you had "Still waiting for root device" error which is most likely because of an unsupported chipset and your drives aren't recognised.

 

Clover is now v5126 so CLOVERX64.efi is replaced with the new one

 

your config.plist have lot's of unused variables or unnecessary changes, so I modified mine instead, but the old one is also included (config_old.plist)

- In your "new" config.plist in ACPI/DSDT/Patches you have two EC renames (EC0 to EC and ECDV to EC) you should figure out which one do you need, and delete the unnecessary ones. 

- Your SMBIOS is wrong. According to your signature it's a 7700HQ, exactly the same as MacBookPro14,3 so I changed that.

- Boot args deleted: dart=0 (not needed), nv_disable=1 (you already disabled it by SSDT), -shikioff (idk why), gfxrst=1

I did not remove -disablegfxfirmware but I think it's not necessary, try to remove and boot. 

 

Replaced your drivers with the new one. You also had SMCHelper (for FakeSMC) and VirtualSMC.efi, you should use jsut one. In your case it's VirtualSMC.efi. 

 

I had to delete FlashProgrammingTool.efi, FWUpdLcl.efi, MEInfo.efi, MEManuf.efi, ACPI/origin, and themes/minimal because of the zip size is too big to upload because of them, if you want to use them you have to readd them.

 

Take a look

 

EDIT: if you have DSDT errors pls change ACPI/DSDT/Name from "BIOS.aml" to "DSDT.aml"

I forgot that.

 

N580VD Clover r5126.zip

Edited by kushwavez
BIOS.aml should be DSDT.aml
  • Like 2
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted (edited)
Spoiler

820122704_ScreenShot2563-10-30at19_30_07.png.3541585bc757a4148d667eb8687634ab.png

Now I am trying to update via clover V5126.
Will be reported after this

 

After the download is complete It will reboot up to the first installation step. Then reboot again. Available in 2 drivers, 1 driver update or 1..macosXinstall-via% preboot 2.macosX formvia% preboot. I try to choose number 1. Immediately after that restart Next, choose the second option. It will go to the main page prior to the latest update.
The result of the update was not successful. Does anyone have a better way?

!!Accept That the development of this version is so delayed
However, I will wait for the success to come.

Do not curse me, OC has developed very far now.

clip

Edited by naiclub
  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Guest
Guest
Posted
Posted (edited)

For AMD Users:

installing Catalina 10.15.7 (19H4) from usb full installer is fine (clover 5126 release master, commit 9e7b4311c)

 

installing Big Sur 11.0.1 (20B5012d) from usb full installer NO (clover 5126 release master, commit 9e7b4311c)

 

first installation step is fine

but when system reboot and you choose Preboot icon to do the second part, system reboots

The reason is that GetOs does not recognise Big Sur system in that step (preboot problem?) and in debug it is blank..

In this way system applies KernelPatches that Big Sur does Not need and it reboots

 

There is a trick to continue the installation using a great and unique Clover feature..Option/disable patches not for Big Sur

In this way Installation went fine...

I have applied this only for first installation steps..maybe for second and third part GetOS did its job fine

 

opened an issue on GitHub :

https://github.com/CloverHackyColor/CloverBootloader/issues/289

Edited by Guest
Typo
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...