Jump to content
30960 posts in this topic

Recommended Posts

It might just be me BUT why is there a BOOTX64.efi AND CloverX64.efi

I know they are both the same file but surely Legacy can boot BOOTX64.efi

or am I missing something, besides a brain

18 minutes ago, STLVNUB said:

It might just be me BUT why is there a BOOTX64.efi AND CloverX64.efi

I know they are both the same file but surely Legacy can boot BOOTX64.efi

or am I missing something, besides a brain

BOOTX64.efi exists for lazy users who don't know what to do with CLOVERX64.efi.

In my case BOOTX64.efi is windows bootloader while my BIOS has a priority to boot /EFI/CLOVER/CLOVERX64.EFI. In this case I am not afraid windows updates and permit him to change bootx64.efi.

  • Like 2
6 hours ago, 5T33Z0 said:

So I came across this new build of clover: https://github.com/CloverHackyColor/CloverBootloader/actions/runs/1700957781

 

I am wondering what this Description actually means: "check default extended features for more models"

Clover has an ability to set some default values for keys absent in config.plist.

Where it takes the value? Sometimes from hardware characteristics, sometimes from model set.

In this case for model iMacPro1,1 it should set one value for ExtendedFirmwareFeatures and another value for iMac20,2, for example.

This commit defines new values for new models.

  • Like 2
On 1/14/2022 at 7:10 AM, mnfesq said:

@Hervé I will check out the Windows 11 thread.  I have been in the fast lane of the Windows Insider Program for years and would love to put Windows 11 on my desktop and the 3 virtual machines I run on it.  I am aware of patches that have attempted to bypass with system check that Windows 11 installer uses but, like with macOS, it would be nice to make all the changes in the boot loader so that I could install vanilla versions of Windows 11 and not have to patch each preview version I test out.

I read somewhere that the newest version of the Win11 installer will allow you to install on older CPUs like Haswell. 

And indeed, I just installed vanilla Win11 just two days ago on my Lenovo T440 without any modifications. 

Edited by kushwavez
  • Like 1
  • Thanks 2
On 1/19/2022 at 3:33 AM, SavageAUS said:

So I’m not seeing anyone else report the fast animations with clover. Any chance@slice you can take another look into this and see what was wrong?


Sent from my iPhone using Tapatalk

It is AMD CPU, yes? Check again kernel patches for AMD. May be you made a mistake here. I see no Clover problems.

It is AMD CPU, yes? Check again kernel patches for AMD. May be you made a mistake here. I see no Clover problems.

There has been an issue raised for this on GitHub from fabiosun.


Sent from my iPhone using Tapatalk
On 1/5/2022 at 9:23 PM, PG7 said:

@Slice 

 

hello, good year to the whole team

 

Slice with this boot did NOT work

 

but then i followed your idea and tested it with the r5142 boot6 and it worked

it would be possible to fix the next Clover with this boot6 that is working on pkg r5142

 

thanks for the solution

 

* google translate

logs boot 

2022-01-05_20-03_CLOVERX64.EFI.log 199.16 kB · 3 downloads preboot.log 52.24 kB · 3 downloads

Hi!

 

Could you share your Efi folder with Clover5143and the changed boot6.

 

Thanks!

From time to time I tested boot6 in Qemu and in very rare cases on my main computer. Usually it works in UEFI mode.

Sometime new boot6 is not working and I take older version.

ALL VERSIONS DO THE SAME FUNCTION. It was never changed in functionality. 

I tested the version from 5143. Yes, it is not working in Qemu and I know the bad commit.

Then I tested the version "boot6-replacement". It works again.

What else the question?

In the most cases users do mistakes and claim "it is not working". But I wait some proof for this.

20 hours ago, chris1111 said:

latest commit Update clover build failled

 

 

yeah seeing this: -- so seems like more replacements of "Signature" to "SignatureCommon.Signature" are needed.

 

[SLINK] ConPlatformDxe

[CC] PcatPciRootBridge

[DLINK] ConPlatformDxe

[CC] fsw_efi

[CC] AutoGen

/opt/Source/Clover/rEFIt_UEFI/Platform/AcpiPatcher.cpp:191:34: error: no member named 'Signature' in 'EFI_ACPI_DESCRIPTION_HEADER'

    if (0 == Signature || Table->Signature == Signature) {

                          ~~~~~  ^

/opt/Source/Clover/rEFIt_UEFI/Platform/AcpiPatcher.cpp:223:34: error: no member named 'Signature' in 'EFI_ACPI_DESCRIPTION_HEADER'

    if (0 == Signature || Table->Signature == Signature) {

                          ~~~~~  ^

Building ... /opt/Source/Clover/FileSystems/GrubFS/src/UDF.inf [X64]

/opt/Source/Clover/rEFIt_UEFI/Platform/AcpiPatcher.cpp:244:29: error: no member named 'Signature' in 'EFI_ACPI_DESCRIPTION_HEADER'

  CopyMem(&sign[0], &Table->Signature, 4);

                     ~~~~~  ^

/opt/Source/Clover/rEFIt_UEFI/Platform/AcpiPatcher.cpp:249:33: error: no member named 'Signature' in 'EFI_ACPI_DESCRIPTION_HEADER'

  DropTable->Signature = Table->Signature;

                         ~~~~~  ^

/opt/Source/Clover/rEFIt_UEFI/Platform/AcpiPatcher.cpp:320:31: error: no member named 'Signature' in 'EFI_ACPI_DESCRIPTION_HEADER'

    CopyMem(&sign[0], &Table->Signature, 4);

                       ~~~~~  ^

/opt/Source/Clover/rEFIt_UEFI/Platform/AcpiPatcher.cpp:323:32: error: no member named 'Signature' in 'EFI_ACPI_DESCRIPTION_HEADER'

 

Edited by tluck
  • Like 3

hello team
 

Does anyone get the complete installation of Monterey with Clover on PC Legacy?

as I already reported I can't complete a complete installation by Clover on my PC with Legacy bios

the history of the error that presents me here
 

any solution for me to test?

2 Historique de Programme d’installation 24-Jan-2022.txt

To install Monterey we should have NVRAM working. We can't have it with PC Legacy. And we can't use nvram.plist as workaround.

But I don't know if we can install Monterey by manually choose volume at reboot as follow sequence: Install, Preboot MacOS, and next.

On 1/24/2022 at 4:26 AM, chris1111 said:

latest commit Update clover build failled

 

 

I know. Just wait next commit.

  • Like 3
  • Thanks 1
5 minutes ago, Slice said:

To install Monterey we should have NVRAM working. We can't have it with PC Legacy. And we can't use nvram.plist as workaround.

But I don't know if we can install Monterey by manually choose volume at reboot as follow sequence: Install, Preboot MacOS, and next.



 

thank you for the explanation
 

if you do this step it even goes to the end of install but does not finish and returns the same error!

  • Like 1
2 hours ago, Slice said:

To install Monterey we should have NVRAM working. We can't have it with PC Legacy. And we can't use nvram.plist as workaround.

But I don't know if we can install Monterey by manually choose volume at reboot as follow sequence: Install, Preboot MacOS, and next.

I know. Just wait next commit.

Fix thanks

On 1/26/2022 at 1:31 AM, PG7 said:

hello team
 

Does anyone get the complete installation of Monterey with Clover on PC Legacy?

as I already reported I can't complete a complete installation by Clover on my PC with Legacy bios

the history of the error that presents me here
 

any solution for me to test?

2 Historique de Programme d’installation 24-Jan-2022.txt 152.23 kB · 2 downloads

I can confirm that legacy Clover 5141 can update my ASUS P5Q PRO & GA-965P-DS4 two LGA 775 hackintoshs without reboot loop. The config.plist of P5Q PRO was posted for your reference.

But legacy Clover always got reboot loop during update of ASUS P6TSE & M5A (FX-6300) hackintoshs.

Looking forward to the new Clover to fix this issue ASAP.

Screen Shot 2022-01-27 at 11.12.52 AM.png

config.plist

Edited by jsl2000
  • Confused 1
On 1/27/2022 at 4:15 AM, jsl2000 said:

I can confirm that legacy Clover 5141 can update my ASUS P5Q PRO & GA-965P-DS4 two LGA 775 hackintoshs without reboot loop. The config.plist of P5Q PRO was posted for your reference.

But legacy Clover always got reboot loop during update of ASUS P6TSE & M5A (FX-6300) hackintoshs.

Looking forward to the new Clover to fix this issue ASAP.


hello 

how do you outline this ?
 

 

On 1/25/2022 at 7:44 PM, Slice said:

To install Monterey we should have NVRAM working. We can't have it with PC Legacy. And we can't use nvram.plist as workaround.



here I have two that I can't pass the step without a firmware error where even with the SMBIOSiMac17,1 it goes around

* with OpenCore I can install and update them in Legacy

Edited by PG7
On 1/28/2022 at 9:05 PM, PG7 said:


hello 

how do you outline this ?
 

 



here I have two that I can't pass the step without a firmware error where even with the SMBIOSiMac17,1 it goes around

* with OpenCore I can install and update them in Legacy

I'll test it with enabled telemetrap.kext  in P6TSE to see whether's any chance to fix it.

[Edit]

Enabled telemetrap.kext  in P6TSE can not fix this reboot loop issue !

I think it need newer Clover to solve it.

[Edit on 2022-01-30]

Good news: ProvideCurrentCpuInfo Quirk could be enabled in my FX-6300 hackintoshs by legacy Clover 5144 now, that means it can use brief kernel patches as in my Ryzen 1700X hackintoshs.

Although Clover 5144 includes ProvideCurrentCpuInfo Quirk, I found it can not fix reboot loop issue in my P6TSE & FX-6300 as well as Z97 hackintoshs yet booted by legacy Clover 5144.

Edited by jsl2000

is this something in my environment? python3 is 3.9.10

build.py...

: error C0DE: Unknown fatal error when processing [/opt/Source/Clover/OpenCorePkg/Library/OcDebugLogLibOc2Clover/OcDebugLogLibOc2Clover.inf [X64, XCODE8, RELEASE]]

 

(Please send email to devel@edk2.groups.io for help, attaching following call stack trace!)

 

(Python 3.9.10 on darwin) Traceback (most recent call last):

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2582, in Main

    MyBuild.Launch()

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2379, in Launch

    self._MultiThreadBuildPlatform()

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2216, in _MultiThreadBuildPlatform

    Wa, self.BuildModules = self.PerformAutoGen(BuildTarget,ToolChain)

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2105, in PerformAutoGen

    CmdListDict = self._GenFfsCmd(Wa.ArchList)

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2002, in _GenFfsCmd

    GenFfsDict = GenFds.GenFfsMakefile('', GlobalData.gFdfParser, self, ArchList, GlobalData)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/GenFds.py", line 542, in GenFfsMakefile

    FvObj.AddToBuffer(Buffer=None, Flag=True)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/Fv.py", line 127, in AddToBuffer

    FileName = FfsFile.GenFfs(MacroDict, FvParentAddr=BaseAddress, IsMakefile=Flag, FvName=self.UiFvName)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/FfsInfStatement.py", line 518, in GenFfs

    InputSectList, InputSectAlignments = self.__GenComplexFileSection__(Rule, FvChildAddr, FvParentAddr, IsMakefile=IsMakefile)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/FfsInfStatement.py", line 969, in __GenComplexFileSection__

    SectList, Align = Sect.GenSection(self.OutputPath, self.ModuleGuid, SecIndex, self.KeyStringList, self, IsMakefile = IsMakefile)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/EfiSection.py", line 218, in GenSection

    GenFdsGlobalVariable.GenerateSection(OutputFile, [], 'EFI_SECTION_USER_INTERFACE',

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/GenFdsGlobalVariable.py", line 462, in GenerateSection

    SectionData.fromstring(Ui.encode("utf_16_le"))

AttributeError: 'array.array' object has no attribute 'fromstring'

5144 latest Clover 👋

clover.png.3970a9df021c3b79be85e83903932f5a.png

Untitled.thumb.png.430d65c49609abfef76601e56d8908ac.png

 

@tluck I dont have any probleme, compiling in macOS Monterey 12.2 (21D49)

Installed package on sierra 10.12.6

Edited by chris1111
9 hours ago, tluck said:

is this something in my environment? python3 is 3.9.10

build.py...

: error C0DE: Unknown fatal error when processing [/opt/Source/Clover/OpenCorePkg/Library/OcDebugLogLibOc2Clover/OcDebugLogLibOc2Clover.inf [X64, XCODE8, RELEASE]]

 

(Please send email to devel@edk2.groups.io for help, attaching following call stack trace!)

 

(Python 3.9.10 on darwin) Traceback (most recent call last):

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2582, in Main

    MyBuild.Launch()

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2379, in Launch

    self._MultiThreadBuildPlatform()

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2216, in _MultiThreadBuildPlatform

    Wa, self.BuildModules = self.PerformAutoGen(BuildTarget,ToolChain)

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2105, in PerformAutoGen

    CmdListDict = self._GenFfsCmd(Wa.ArchList)

  File "/opt/Source/Clover/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2002, in _GenFfsCmd

    GenFfsDict = GenFds.GenFfsMakefile('', GlobalData.gFdfParser, self, ArchList, GlobalData)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/GenFds.py", line 542, in GenFfsMakefile

    FvObj.AddToBuffer(Buffer=None, Flag=True)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/Fv.py", line 127, in AddToBuffer

    FileName = FfsFile.GenFfs(MacroDict, FvParentAddr=BaseAddress, IsMakefile=Flag, FvName=self.UiFvName)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/FfsInfStatement.py", line 518, in GenFfs

    InputSectList, InputSectAlignments = self.__GenComplexFileSection__(Rule, FvChildAddr, FvParentAddr, IsMakefile=IsMakefile)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/FfsInfStatement.py", line 969, in __GenComplexFileSection__

    SectList, Align = Sect.GenSection(self.OutputPath, self.ModuleGuid, SecIndex, self.KeyStringList, self, IsMakefile = IsMakefile)

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/EfiSection.py", line 218, in GenSection

    GenFdsGlobalVariable.GenerateSection(OutputFile, [], 'EFI_SECTION_USER_INTERFACE',

  File "/opt/Source/Clover/BaseTools/Source/Python/GenFds/GenFdsGlobalVariable.py", line 462, in GenerateSection

    SectionData.fromstring(Ui.encode("utf_16_le"))

AttributeError: 'array.array' object has no attribute 'fromstring'

./ebuild.sh -clean

./buildme

 

  • Like 1

Do you guys have any idea why the 12.2 update won't show up?
 

Here is my config. I've set HWtarget to j160, tried x86legacy too, but that did not help, still the same. What else should I change? Maybe delete MLB and ROM?

The fun fact is that I was able to update from 12.0.1 to 12.1 just fine without using HWtarget or any other setting.

272649844_397866135446587_3340231833308547626_n.thumb.png.a174dc3b0913c08a60ea696be87c9d34.png

 

Spoiler

272357656_423632092874275_2296935736264880031_n.thumb.png.d4d42965a466b2434ab54f954b8e56ce.png

It's a Lenovo X1 Extreme with MacBookPro15,3 SMBIOS. 

 

The same is happening on my X1 Carbon 6th with MacBookPro15,2 SMBIOS

Edited by kushwavez
×
×
  • Create New...