Clover General discussion

[deeveedee]

On 12/13/2020 at 3:03 AM, Slice said:

Sorry that DisableRtcChecksum is still present in config-sample.plist. It will be excluded in next release.

Use AppleRTC

 

EDIT: I think I just answered my own question.  It's been a while since I manually patched ACPI (instead of using CLOVER's on-the-fly patches).  I think I remember that CLOVER's FixRTC patch also changes the RTC memory length to 0x02 which explains why the ACPI FixRTC patch address RTC corruption.  The alternative to changing RTC memory length to 0x02 would be to use RTCMemoryFixup.kext with a custom rtcfx-exclude region.

 

Thanks, everyone, for letting me think out loud.  

 

------------------------------------------

 

@Slice  - Thank you for this explanation.  I understand that CLOVER's AppleRTC kext patch addresses the RtcChecksum issue (by blocking regions 0x58-0x59).  Does CLOVER's FixRTC ACPI patch do anything other than address the IRQ conflict?  I have seen others report that they need CLOVER's FixRTC ACPI patch to resolve RTC corruption issues and I don't understand why that would be the case.  Thank you.

Edited December 14, 2020 by tonyx86

[Slice]

1 hour ago, tonyx86 said:

 

@Slice  - Thank you for this explanation.  I understand that CLOVER's AppleRTC kext patch addresses the RtcChecksum issue (by blocking regions 0x58-0x59).  Does CLOVER's FixRTC ACPI patch do anything other than address the IRQ conflict?  I have seen others report that they need CLOVER's FixRTC ACPI patch to resolve RTC corruption issues and I don't understand why that would be the case.  Thank you.

FixRTC provides two patches, exclude IRQ and change length. Changing length leads to using one CMOS bank which leads to preventing corruption.

But in this case using RTC will be restricted. Acidanthera thinks that's bad idea. I don't.

[deeveedee]

28 minutes ago, Slice said:

Acidanthera thinks that's bad idea. I don't.

 

I remember adding my 2-cents to the CLOVER vs OC discussion not long ago.  CLOVER's (and Slice's) philosphical differences with OC are another reason why two bootloaders is still a good idea.

Edited December 14, 2020 by tonyx86

[jsl2000]

On 12/13/2020 at 10:38 PM, tonyx86 said:

Migrate to OpenCore?  Blasphemy!

Legacy boot of Clover 5126 or 5127 can not boot Big Sur in my FX-6300, P6TSE, P5Q PRO, or GA 775 hackintoshs yet because these have no UEFI. Put OpenRuntime.efi in EFI/CLOVER/drivers/BIOS not working !

But legacy boot with OpenCore worked in these hackintoshs from 10.13.6 to 11.1 smoothly.

Is there anyone who can confirm this issue or provide solution to fix it ?

[Slice]

1 hour ago, jsl2000 said:

Legacy boot of Clover 5126 or 5127 can not boot Big Sur in my FX-6300, P6TSE, P5Q PRO, or GA 775 hackintoshs yet because these have no UEFI. Put OpenRuntime.efi in EFI/CLOVER/drivers/BIOS not working !

But legacy boot with OpenCore worked in these hackintoshs from 10.13.6 to 11.1 smoothly.

Is there anyone who can confirm this issue or provide solution to fix it ?

I tested legacy boot a week ago with Clover 5127. BigSur 11.1 works.

OpenRuntime is not needed. But you have to replace ApfsDriverLoader to simple apfs.efi.

[SavageAUS]

On 12/8/2020 at 1:06 AM, iCanaro said:

 

use XCODE 12.2

terminal

cd cloverbootloader

git -f -f -d -x

select 10 enter

./buildme XCODE8

 

 

I’ve tried that but I get unknown option git -f

Edited December 15, 2020 by SavageAUS

[jsl2000]

5 hours ago, Slice said:

I tested legacy boot a week ago with Clover 5127. BigSur 11.1 works.

OpenRuntime is not needed. But you have to replace ApfsDriverLoader to simple apfs.efi.

Thank you very much for your help and advice.

It can boot installed Big Sur now, but I need add 10.13.6 to MatchOS for kernel patch at 11.x.

At 10.15.7 crack sound quite bothered me by legacy Clover in FX-6300 hackintosh.

Another bug is quite unstable at Big Sur in which about 2 minutes after login desktop I always got frozen screen and not moving mouse & keyboard.

No such issue legacy booted by OpenCore with clear sound in FX-6300 hackintosh.

Edited December 15, 2020 by jsl2000

[iCanaro]

@Slice i have compilation errors in both hacks where i tried

i try to update xcode by installing version 12.3

Spoiler

/Users/utente/src/clover/rEFIt_UEFI/Platform/plist/plist.cpp:859:5: error: no matching function for call to 'CopyMem'

    CopyMem(Data, Prop->getData()->dataValue(), Size);

    ^~~~~~~

/Users/utente/src/clover/MdePkg/Include/Library/BaseMemoryLib.h:35:1: note: candidate function not viable: no known conversion from 'INTN' (aka 'long long') to 'void *' for 1st argument; take the address of the argument with &

CopyMem(

^

1 error generated.

make: *** [/Users/utente/src/clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/plist/plist.obj] Error 1

 

 

build.py...

 : error 7000: Failed to execute command

make tbuild [/Users/utente/src/clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]

 

 

build.py...

 : error F002: Failed to build module

/Users/utente/src/clover/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

 

- Failed -

Build end time: 11:00:33, Dec.15 2020

Build total time: 00:00:28

 

utente@iMacTRyZo clover % 

 

Edited December 15, 2020 by iCanaro

[Matgen84]

Hi @Slice

Sorry for my stupid question: I don't understand latest commit d68d53a: some posts ago, it was about the possibility of using <data> instead of <string> for the CsrActiveConfig. This is the purpose of this commit !

But there is an <interger> in the title of the commit, which means that I no longer know. Can you enlighten me, Please.

[Slice]

1 hour ago, iCanaro said:

@Slice i have compilation errors in both hacks where i tried

i try to update xcode by installing version 12.3

  Reveal hidden contents

/Users/utente/src/clover/rEFIt_UEFI/Platform/plist/plist.cpp:859:5: error: no matching function for call to 'CopyMem'

    CopyMem(Data, Prop->getData()->dataValue(), Size);

    ^~~~~~~

/Users/utente/src/clover/MdePkg/Include/Library/BaseMemoryLib.h:35:1: note: candidate function not viable: no known conversion from 'INTN' (aka 'long long') to 'void *' for 1st argument; take the address of the argument with &

CopyMem(

^

1 error generated.

make: *** [/Users/utente/src/clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/plist/plist.obj] Error 1

 

 

build.py...

 : error 7000: Failed to execute command

make tbuild [/Users/utente/src/clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]

 

 

build.py...

 : error F002: Failed to build module

/Users/utente/src/clover/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

 

- Failed -

Build end time: 11:00:33, Dec.15 2020

Build total time: 00:00:28

 

utente@iMacTRyZo clover % 

 

Yes, I expected this post. Will be corrected asap.

58 minutes ago, Matgen84 said:

Hi @Slice

Sorry for my stupid question: I don't understand latest commit d68d53a: some posts ago, it was about the possibility of using <data> instead of <string> for the CsrActiveConfig. This is the purpose of this commit !

But there is an <interger> in the title of the commit, which means that I no longer know. Can you enlighten me, Please.

My mistake. The <data> was not possible for CsrActiveConfig. There must be <integer> for decimal value or <string> for hexadecimal.

This commit I added the possibility to use <data> up to 8 digits.

But there is a little mistake, it must be

CopyMem(&Data....

[chris1111]

12 hours ago, jsl2000 said:

Legacy boot of Clover 5126 or 5127 can not boot Big Sur in my FX-6300, P6TSE, P5Q PRO, or GA 775 hackintoshs yet because these have no UEFI. Put OpenRuntime.efi in EFI/CLOVER/drivers/BIOS not working !

But legacy boot with OpenCore worked in these hackintoshs from 10.13.6 to 11.1 smoothly.

Is there anyone who can confirm this issue or provide solution to fix it ?

Are you talking about being able to boot BS already install or boot a USB key from Big Sur? I ask because on my DELL Optiplex 790 legacy boot I cannot install BS with OC or Clover but if the system is already installs it boots very well . It boot well on USB installer but it reboot at the second stage on the Time line 

Do you please share both OC and Clover EFI Folder of  P5Q PRO

thanks

Edited December 15, 2020 by chris1111

[Matgen84]

22 minutes ago, Slice said:

Yes, I expected this post. Will be corrected asap.

My mistake. The <data> was not possible for CsrActiveConfig. There must be <integer> for decimal value or <string> for hexadecimal.

This commit I added the possibility to use <data> up to 8 digits.

But there is a little mistake, it must be

CopyMem(&Data....

 

Thanks @Slice. If I understand well: there are now 3 possibilities for CsrActiveConfig:

• <string>
• <data>
• <integer>
   

That's right. Sorry but my english is bad

Edited December 15, 2020 by Matgen84

[Slice]

23 minutes ago, Matgen84 said:

 

Thanks @Slice. If I understand well: there are now 3 possibilities for CsrActiveConfig:

• <string>
• <data>
• <integer>
   

That's right. Sorry but my english is bad

This is a common rule for any setting requires a number.

[iCanaro]

compilation fixed, thanks

[jsl2000]

On 12/15/2020 at 5:41 PM, jsl2000 said:

Thank you very much for your help and advice.

It can boot installed Big Sur now, but I need add 10.13.6 to MatchOS for kernel patch at 11.x.

At 10.15.7 crack sound quite bothered me by legacy Clover in FX-6300 hackintosh.

Another bug is quite unstable at Big Sur in which about 2 minutes after login desktop I always got frozen screen and not moving mouse & keyboard.

No such issue legacy booted by OpenCore with clear sound in FX-6300 hackintosh.

Solved by editing kernel patches for FX-6300 as the following:

Enabled "mtrr_update_action - fix PAT" and disabled "Shaneee - mtrr_update_action - fix PAT [TEST 2 Performance GPU]"

No more crack sound and system became very stable after this change.

[jsl2000]

On 12/15/2020 at 7:29 PM, chris1111 said:

Are you talking about being able to boot BS already install or boot a USB key from Big Sur? I ask because on my DELL Optiplex 790 legacy boot I cannot install BS with OC or Clover but if the system is already installs it boots very well . It boot well on USB installer but it reboot at the second stage on the Time line 

Do you please share both OC and Clover EFI Folder of  P5Q PRO

thanks

I can boot installed Big Sur and update it with legacy Clover and Opencore.

Unable to upload whole EFI folders due to size limits (>50 MB) even after compression.

Only config.plist posted here for your reference.

According to my experience automatic reboot means incorrect config.plist.

 

config-CLOVER.plist

config-OC-062-P5Q.plist

Edited December 16, 2020 by jsl2000

[chris1111]

1 hour ago, jsl2000 said:

I can boot installed Big Sur and update it with legacy Clover and Opencore.

Unable to upload whole EFI folders due to size limits (>50 MB) even after compression.

Only config.plist posted here for your reference.

According to my experience automatic reboot means incorrect config.plist.

 

config-CLOVER.plist

 

config-OC-062-P5Q.plist

Its not a incorrect config.plist lots of Legacy System like HP Z and Dell Optiplex can not Installed BS but when system is Installed its boot ok

Verry strange and already check by Mald0n Big Mystery of BS

 

What is AppleGenericInput.efi ?

I see some kext in your config I never see before 

Why not share a complet EFI? anyway I will try with the config you have shared but its hard without all peace of the puzzle

thank you

Edited December 16, 2020 by chris1111

[jsl2000]

8 minutes ago, chris1111 said:

Its not a incorrect config.plist lots of Legacy System like HP Z and Dell Optiplex can not Installed BS but when system is Installed its boot ok

Verry strange and already check by Mald0n Big Mystery of BS

 

What is AppleGenericInput.efi ?

I see some kext in your config I never see before 

Why not share a complet EFI? anyway I will try with the config you have shared but its hard without all peace of the puzzle

thank you

Please PM me for any kext or .efi you need for test your system.

If you have gmail I can send whole EFI folder via email too.

[deeveedee]

26 minutes ago, jsl2000 said:

Please PM me for any kext or .efi you need for test your system.

If you have gmail I can send whole EFI folder via email too.

ASUS P5Q Pro?  Impressive.  I see you're using NullCPUPowerManagement.kext.  I'm still using -no_compat_check / MacPro5,1 for native CPU power management with my Socket 1156 (still running Catalina).  How is power management with NullCPUPowerManagement.kext and SMBIOS iMac19,1?

Edited December 16, 2020 by tonyx86

[chris1111]

5 hours ago, jsl2000 said:

Please PM me for any kext or .efi you need for test your system.

If you have gmail I can send whole EFI folder via email too.

Please read your PM

[PG7]

 

 

On 12/15/2020 at 10:41 AM, jsl2000 said:

Thank you very much for your help and advice.

It can boot installed Big Sur now, but I need add 10.13.6 to MatchOS for kernel patch at 11.x.

At 10.15.7 crack sound quite bothered me by legacy Clover in FX-6300 hackintosh.

Another bug is quite unstable at Big Sur in which about 2 minutes after login desktop I always got frozen screen and not moving mouse & keyboard.

No such issue legacy booted by OpenCore with clear sound in FX-6300 hackintosh.

 

 

here clover r5127 i can use and install even if my video cards are no longer supported on BigSur on Laptop Legacy using OpenRuntime.efi

check with my comments with Chris1111 where I was having a problem on one of my HP DV6 2140EF laptops and managed to fix and use it!

[PG7]

- I have an HP Envy Recline 23 Haswell that until Catalina I never had any problems with installation but with Big Sur everything jumped, I can do the first installation, reboot et enter the second phase so that then it reboots without any kernel panic so much with OpenCore as with Clover !!!! but funny that I can always update Big Sur directly by him without problems and pass!

- I have a Lenovo M93 desktop Haswell i5-4460S with Nvidia GTX760 and the same installation has always been normal until Catalina already in Big Sur I enter the installation and at 12 minutes between the error and nothing more! tests with OpenCore and Clover same error, even trying to update directly does not pass after 15 minutes makes an error and if it is for the complete installer then worse than after two minutes there makes an error!

- I had an All In One Lenovo M93p Haswell also i5-4430S and I always managed to install without problems even on Big Sur

- I have an Elitebook 820 G2 i5-5300U installation goes smoothly with Big Sur

- I have a Probook 430 G2 i3-4010U installation goes smoothly like Big Sur
- I have a Dell Latitude E6330 i7-3520M installation passes without Big Sur problems
- I have a Dell Vostro 2520 with i5-3310M Big Sur installation
- I have a SamSung NP350V5C-S06FR intel i3-3110M HD4000-HD7670M installation passes Big Sur without any problems
- I have an asus A42J with i5-480M ati HD5730 I can't even install the direct Catalina but the High Sierra passes and then I even update Big Sur

.....

to say that with the arrival of Big Sur there is still a lot of dark part in certain machines and certain NVRAM of some that complicated but even so the team did a lot of work where we managed to get and use Big Sur even if we have to use other PCs the installation and then use the HDD / SSD on these machines that will not let you do the installation!

with himself the complete installation on a Fujitsu S760 with Sandybridge direct by him (with HD3000 disabled of course)

even a HD DV6 1340SF with an intel P7450 and ATI HD4650 with kext telemetrap.kext and with ATI disabled I can use MAL Big Sur (just for testing nothing more)

with time we will go further I am almost sure, I believe in what the community can do!

Thanks to everyone who has made all this possible

Spoiler

 

[jsl2000]

3 hours ago, PG7 said:

 

 

 

 

here clover r5127 i can use and install even if my video cards are no longer supported on BigSur on Laptop Legacy using OpenRuntime.efi

check with my comments with Chris1111 where I was having a problem on one of my HP DV6 2140EF laptops and managed to fix and use it!

My current Clover 5126 or OpenCore 0.6.2 can not install Big Sur via USB installer in my P5Q PRO (LGA-775) hackintosh.

Where can I get your r5127 version for testing ?

9 hours ago, tonyx86 said:

ASUS P5Q Pro?  Impressive.  I see you're using NullCPUPowerManagement.kext.  I'm still using -no_compat_check / MacPro5,1 for native CPU power management with my Socket 1156 (still running Catalina).  How is power management with NullCPUPowerManagement.kext and SMBIOS iMac19,1?

In P5Q PRO wake up from S3 only working lower than Sierra (10.12.6).

Higher than High Sierra (10.13.6) only S1 sleep/wakeup working.

NullCPUPowerManagement.kext can give extra performance score by GeekBench 5 in my P6TSE and P5Q PRO hackintoshs.

[iCanaro]

Z68 GO!

 

[Matgen84]

Hi @Slice @Jief_Machak

The BigSur's recovery partition is detected by Clover. Do you plan it to be bootable ! Please.