Clover General discussion

[Cyberdevs]

@Slice and @Jief_Machak

 

Thanks a lot for all your efforts and hard work to make clover work with Big Sur, kudos to you guys 

 

Hi guys I have a question.

In the prereleased version of clover 5123 installer there is no OpenRuntime.efi and OcQuircks.efi, I only have the old Aptio drivers which result in KP when I try to boot Catalina or Big Sur; if I remove the AptioMemeoryFix.efi and add the those two drivers system boots normally.

 

The question is did you OpenRuntime and OcQuircks drivers by design and should we use the old Aptio drivers or I'm missing something?

[SavageAUS]

@Jief_Machak Yeah mate it’s me with Arch Linux issue, take a break, rest and reset. 
I’ll create some new repos for us to work with and we will go from there. 
Strange my logs only show macOS, I’ll see what I can work out and add it to the readme’s on the repos as a guide.

All I do know at the moment is official 5122 release boots Arch but CLOVERX64-458d071-reloc.efi will not. 

[Slice]

5 minutes ago, Cyberdevs said:

@Slice and @Jief_Machak

 

Thanks a lot for all your efforts and hard work to make clover work with Big Sur, kudos to you guys 

 

Hi guys I have a question.

In the prereleased version of clover 5123 installer there is no OpenRuntime.efi and OcQuircks.efi, I only have the old Aptio drivers which result in KP when I try to boot Catalina or Big Sur; if I remove the AptioMemeoryFix.efi and add the those two drivers system boots normally.

 

The question is did you OpenRuntime and OcQuircks drivers by design and should ww use the old Aptio drivers or I'm missing something?

OpenRuntime.efi must be present. It looks like build script error. Took it anywhere it is the same for a year.

[tikizondo94]

34 minutes ago, MICKHAEL said:

 

hello @Jief_Machak, again with my problems)
i'm trying without success to boot Big Sur beta 9
attached config and debug for laptop Acer Aspire A315-53
thanks

config.plist

debug.log

Im locking in a similar spot. Im trying to just boot my Catalina drive with the new Clover OC integration. Still no luck. Normal 5122 boots normally. config attached 

config.plist

[D-an-W]

Could someone please share the Quirks section of their config.plist as I am not sure I have all the entires in there. 

 

EDIT: I think Slice already committed it, checking now...

Edited October 4, 2020 by D-an-W

[Cyberdevs]

1 minute ago, Slice said:

OpenRuntime.efi must be present. It looks like build script error. Took it anywhere it is the same for a year.

Thanks for the reply, I was banging my head for two days to no avail until I decided to test with OpenRuntime.efi which made it work. Once again thanks for the confirmation.

[Cyberdevs]

2 hours ago, D-an-W said:

Could someone please share the Quirks section of their config.plist as I am not sure I have all the entires in there. 

Here is the EFI folder that I was able to boot Catalina, Big Sur and the installer successfully, just make sure to remove the contents of the ACPI folder and unnecessary kexts.

 

GA-H97-D3H-Haswell - Clover r.5123 .zip

[Slice]

13 minutes ago, tikizondo94 said:

Im locking in a similar spot. Im trying to just boot my Catalina drive with the new Clover OC integration. Still no luck. Normal 5122 boots normally. config attached 

config.plist

 

The stop at this place usually mean a problem with one of your kext.

[Matgen84]

Hi Guys,

Sorry for my bad english. I just compile latest 5123 commit.

On Clover GUI, I don't see Big Sur icons at all when I boot from USB Catalina 10.15.7 Installer. Even if the kexts are in 10.15 and 11.0 folders.

Any ideas ! Please

EDIT: USB Catalina or USB Big Sur Installer: same issue, don't detect my Big Sur SATA Disk (only Windows is seen)

 

Spoiler

 

Edited October 4, 2020 by Matgen84

[tikizondo94]

46 minutes ago, Slice said:

The stop at this place usually mean a problem with one of your kext.

Thanks for the reply. I wonder why it boots normal when using the same kexts with r5122? They're all the latest builds. Should i try release versions instead maybe?

[pico joe]

thank you @Slice & @Jief_Machak for your hardwork

maybe not important or false in hackintool still detect OC 

 

Spoiler

Edited October 4, 2020 by pico joe

[Jief_Machak]

Interesting and good to know : if it hangs when you boot OpenCore (It stops after Watchdog status is 0, HDD led is blinking constantly), it maybe because of your EFI partition full.

In my case, it was full of OC logs.

[Cyberdevs]

The only issue that I'm having so far is that the USB port limit doesn't seem to be working properly not on Big Sur nor on Catalina. I'm using SSDT-EC-USBX.aml and SSDT-UIAC.aml along with USBPorts.kext generated by Hackintool. I don't have any issues with OC or Clover 5119 though.

 

P.S.

My issue with the USB 3.0 port was my own negligence to remove unused ports. 

[iCanaro]

5 hours ago, Jief_Machak said:

In your logs, there is more than one boot. Could you delete the debug.log before making the test, so I only got one boot ?

ok I re-created the debug logs by deleting it for each boot
at your convenience when you have time.

if you need anything else, for all I can, ask.

With Clover 5120 - OcQuirks rev24, I can start catalina on my MSI X570 unify
instead with CLOVERX64-458d071-reloc.efi strangely I can not start, the config should have the same settings, obviously with the full Quirks section, kexts and kernel patches are the same

 

thank you for your commitment and work 

X570 MSI UNIFY CLOVER debug log.zip

[deeveedee]

2 hours ago, Cyberdevs said:

The only issue that I'm having so far is that the USB port limit doesn't seem to be working properly not on Big Sur nor on Catalina. I'm using SSDT-EC-USBX.aml and SSDT-UIAC.aml along with USBPorts.kext generated by Hackintool. I don't have any issues with OC or Clover 5119 though.

 Just to clarify: you are using SSDT-UIAC.aml AND USBPorts.kext at the same time?  I didn't think SSDT-UIAC.aml was necessary unless you were using USBInjectAll.kext.

Edited October 4, 2020 by tonyx86

[deeveedee]

I apologize that this is off-topic, but it appears to be relevant to @Cyberdevs CLOVER/BS testing.  Can someone else confirm proper use of USBPorts.kext?  I've been doing USBPort patching as follows:

1. Install USBInjectAll.kext and Port Limit Patch (config.plist)
2. Run Hackintool and generate USBPorts.kext and SSDT-UIAC.aml
3. Choose and install one of the following: USBPorts.kext -OR- USBInjectAll.kext & SSDT-UIAC.am
4. Disable Port Limit Patch

Edited October 4, 2020 by tonyx86

[PG7]

8 hours ago, Matgen84 said:

Hi Guys,

Sorry for my bad english. I just compile latest 5123 commit.

On Clover GUI, I don't see Big Sur icons at all when I boot from USB Catalina 10.15.7 Installer. Even if the kexts are in 10.15 and 11.0 folders.

Any ideas ! Please

EDIT: USB Catalina or USB Big Sur Installer: same issue, don't detect my Big Sur SATA Disk (only Windows is seen)

 

  Hide contents

 

 

 

 

 

put the EFI folder to see what's missing!

[SavageAUS]

4 hours ago, tonyx86 said:

I apologize that this is off-topic, but it appears to be relevant to @Cyberdevs CLOVER/BS testing.  Can someone else confirm proper use of USBPorts.kext?  I've been doing USBPort patching as follows:

1. Install USBInjectAll.kext and Port Limit Patch (config.plist)
2. Run Hackintool and generate USBPorts.kext and SSDT-UIAC.aml
3. Choose and install one of the following: USBPorts.kext -OR- USBInjectAll.kext & SSDT-UIAC.am
4. Disable Port Limit Patch

Only 1 is needed. Either kext or .aml not both. Port limit patch should only be used to map ports then disabled. 

[tluck]

@Jief_Machak  hope you are enjoying time off.

 

figured out the issue - all the kexts load from OEM/<board>/kexts when it finds the OEM subdirectory AND finds config.plist in there. (per SelfOem.cpp) so it makes this change ok to load config and kexts from OEM

- but what is not happening is the proper loading of ALL ACPI files from OEM/.../ACPI

- currently I had to duplicate the ACPI folders - in both /EFI/CLOVER/ACPI/patched and /EFI/CLOVER/OEM/<board>/ACPI/patched

Note: also maybe remove the panic if no Kexts folder is found (in SelfOem.cpp)?

 

12:084  0:002  DSDT found in Clover volume OEM folder: \EFI\CLOVER\OEM\4236ED7\ACPI\patched\\DSDT.aml

12:087  0:002  Apply DsdtFixMask=0x10000000

12:088  0:001  === [ FixBiosDsdt ] =============================

12:091  0:002  PreCleanup XSDT: count=16, length=164

12:092  0:001  PreCleanup XSDT, corrected XSDT: count=16, length=164

12:097  0:001  Drop tables from XSDT, SIGN=SSDT TableID=CpuPm Length=2454

12:098  0:001   Table[12]: SSDT  CpuPm  2454 dropped

12:099  0:001  Drop tables from XSDT, SIGN=SSDT TableID=Cpu0Ist Length=2599

12:101  0:001   Table[11]: SSDT  Cpu0Ist  2599 dropped

12:102  0:001  Drop tables from XSDT, SIGN=SSDT TableID=SataAhci Length=1943

12:103  0:001   Table[4]: SSDT  SataAhci  1943 dropped

12:106  0:002  === [ DropSSDT ] ================================

12:108  0:001  Drop tables from XSDT, SIGN=SSDT TableID= Length=0

12:110  0:001   Table[2]: SSDT  TP-SSDT2  585 dropped

12:111  0:001   Table[3]: SSDT  TP-SSDT1  51 dropped

12:115  0:001  Inserting SSDT-CpuPm.aml from ACPI\patched: size=1515 ... Success

12:119  0:004  Inserting SSDT-PNLF.aml from ACPI\patched: size=1128 ... Success

12:123  0:003  Inserting SSDT-RMCF.aml from ACPI\patched: size=911 ... Success

12:129  0:006  Inserting SSDT-T420-PS2K-keys.aml from ACPI\patched: size=1418 ... Success

 

 

[Guest]

@Matgen84

for your missing icon problem

check if you have all efi driver you need in your efi folder and if they are updated

i have had same probkem with a weird combinations of both

[Matgen84]

6 hours ago, PG7 said:

 

 

 

 

put the EFI folder to see what's missing!

 

Thanks. Problem solved 

[naiclub]

8 hours ago, LIMITANT said:

I'm using only USBPorts.kext without SSDT-UIAC.aml all time and everything is fine ..  nothing more is needed no port limit patch .. nothing 

Like me No hassle patching, hassle free kext, my USB works with all ports Because i'm using dsdt Force to work

[pico joe]

13 hours ago, Jief_Machak said:

Interesting and good to know : if it hangs when you boot OpenCore (It stops after Watchdog status is 0, HDD led is blinking constantly), it maybe because of your EFI partition full.

In my case, it was full of OC logs.

yes .. hang with OC when switch from clover

[yapan4]

Hi
About efi drivers (for information only)
In my case,

Spoiler

this set of efi drivers is enough to run Catalina and Big Sur installer from the installation flash drive.
I know that the ApfsDriverLoader.efi is built into OpenCore, but currently in Clover a separate ApfsDriverLoader.efi must be in the Drivers / UEFI folder (verified)

Edited October 5, 2020 by yapan4

[Jief_Machak]

3 hours ago, tluck said:

12:115  0:001  Inserting SSDT-CpuPm.aml from ACPI\patched: size=1515 ... Success

12:119  0:004  Inserting SSDT-PNLF.aml from ACPI\patched: size=1128 ... Success

12:123  0:003  Inserting SSDT-RMCF.aml from ACPI\patched: size=911 ... Success

 12:129  0:006  Inserting SSDT-T420-PS2K-keys.aml from ACPI\patched: size=1418 ... Success

 

The message show the path UNDER oem path. I improved it in the last commit the display the full path.

I've just tried, and everything is loaded from the right place.

Could you compile the latest commit, remove the ACPI folder duplication and try ?

 

3 hours ago, tluck said:

Note: also maybe remove the panic if no Kexts folder is found (in SelfOem.cpp)?

Yes, to still be able to load Windows or Linux... macOS cannot be started without kexts.