Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

iCanaro
iCanaro
Posted
Posted
1 hour ago, Jief_Machak said:

If you have 11.0, put kext in Other and in 11, all will be injected.

excuse me but in my case it's not as you describe
I only finished installing bigsur 11.0.1 when I put the kexts in other (which was previously empty)
then once i finished installing with the folder of big sur name 11.0 or 11.x i didn't start
using instead the previous 11 now you start bs 11.0.1 correctly on the z68

  • Like 2
kushwavez
kushwavez
Posted
Posted
15 minutes ago, Matgen84 said:

 


@Slice @Jief_Machak

 

 

I could be wrong. But before, we could use the Other folder alone and the kexts were injected. This allowed installations, for example, of a macOS version before it was supported by Clover. This function was of particular interest to users. If it was activated again, that would be good. :)

For Big Sur 11.0.1, I used Other and 11.0 folders instead of just Other folder, for the kexts injection. And boot the new Beta.

 

 

I only used Other since Sierra, I never had any problem with that but yeah If you use for example 10.9 that would cause problems. In my opinion: 10.x or 11.x for particular versions (for example 10.15 should inject kexts only for 10.15-10.15.x), Other for unsupported versions, and AllOSX for every OS versions. 

PG7
PG7
Posted
Posted
16 minutes ago, kushwavez said:

I only used Other since Sierra, I never had any problem with that but yeah If you use for example 10.9 that would cause problems. In my opinion: 10.x or 11.x for particular versions (for example 10.15 should inject kexts only for 10.15-10.15.x), Other for unsupported versions, and AllOSX for every OS versions. 

I also used Mavericks and Yosemite in the Others folder "only one I use" and it always worked with the kext injection!
22 minutes ago, kushwavez said:

 

I only used Other since Sierra, I never had any problem with that but yeah If you use for example 10.9 that would cause problems. In my opinion: 10.x or 11.x for particular versions (for example 10.15 should inject kexts only for 10.15-10.15.x), Other for unsupported versions, and AllOSX for every OS versions. 

 

Spoiler

1689267487_Capturedecran2020-10-29a16_27_50.thumb.png.86df790e4dd71fd540dad8178796696b.png

 

 

even older, Snow Leopard that I have to play with and use only the Others folder ...

 

Asus Z92JC-Q073H

  • Like 2
STLVNUB
STLVNUB
Posted
Posted

Can't compile 

Geoffs-iMac ~ % /Users/STLVNUB//BobTheBuilder/CloverBootloader/Clover.dsc(291): error 000E: File/directory not found in workspace

/Users/STLVNUB/BobTheBuilder/CloverBootloader/OpenCorePkg/Library/OcGuardLib/OcGuardLib.inf

      

  • Sad 1
Guest
Guest
Posted
Posted (edited)

About Preboot problem:

if you can try this with an OSX like High Sierra or Mojave

check in Preboot  you should have only one folder with inside also /S/L/CoreServices/SystemVersion.plist for your OS

A folder named like this:

42B6DF39-2F83-3B14-96C9-450F7280FCD0

 

Update to greater OSX and then inside it you will find another folder similar but different like:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx

inside you will find in S/L/CoreServices/SystemVersion.plist properly compiled for your OS

 

Now when the update of OS end you do not have any more HighSierra or Mojave..but new system installed

 

Clover in debug.log detect with GetOS always /S/L/CoreServices/SystemVersion.plist of the old and no more existent OS

And this, for AMD users is a problem when we have different Kernel Patches to apply..

 

How I have solved this? deleting manually not more useful OS reboot folder

 

With Opencore bootloader no need to do this step

Edited by Guest
Slice
Slice
Posted
Posted
1 hour ago, STLVNUB said:

Can't compile 

Geoffs-iMac ~ % /Users/STLVNUB//BobTheBuilder/CloverBootloader/Clover.dsc(291): error 000E: File/directory not found in workspace

/Users/STLVNUB/BobTheBuilder/CloverBootloader/OpenCorePkg/Library/OcGuardLib/OcGuardLib.inf

      

You forget to load OpenCore

git pull --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git

  • Like 1
  • Thanks 1
STLVNUB
STLVNUB
Posted
Posted
32 minutes ago, Slice said:

You forget to load OpenCore

git pull --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git

still no go

STLVNUB
STLVNUB
Posted
Posted (edited)

 

14 minutes ago, Slice said:

I compiled just now without problems with the script ./buildme

Could be a problem with my BobTheBuilder as I use git to get source

Does ./buildme git the repo?

my bad it does

 

Edited by STLVNUB
Slice
Slice
Posted
Posted
1 minute ago, STLVNUB said:

 

Could be a problem with my BobTheBuilder as I use git to get source

Does ./buildme git the repo?

 

Does your script get sources as

git clone --recurse-submodule...?

Jief_Machak
Jief_Machak
Posted
Posted
3 minutes ago, Slice said:

Does your script get sources as

git clone --recurse-submodule...?

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.

  • Like 1
  • Thanks 1
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

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
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
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
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
 Share
Go to topic listing
×
×
  • Create New...