Clover General discussion

[deeveedee]

7 hours ago, Slice said:

If we can inject one kext (FakeSMC) then the problem will be resolved because all other kexts can be placed into /Library/Extensions of installed system. Also desirable to inject a LAN kext which can be required for success installation.

 

Maybe I'm misunderstanding, but CLOVER injection of FakeSMC and LAN alone is not likely to be sufficient for a macOS installation.  Will probably need to be able to inject Lilu, WhateverGreen and USBInjectAll (or other USB kext), too.

[Slice]

9 hours ago, Jief_Machak said:

As I'm not a great disassembler guy, I'd go for OpenCore way which will have the advantage that THEY will maintain it ! I'm pretty sure I can find a way to integrate OpenCore without changing their sources or the structure, which means that we'll just have to "git pull" to keep be up to date. In that, I'm good 

If we go that way, why would we have a memory problem and they don't ? Because Clover is bigger ?

Do you already know which is function the function that do injection in OpenCore, that should be compiled and integrated ?

 

No rush, answer this evening.

No, I don't know OC structure.

Probably kext injection provided by Library/OcAppleKernelLib/Link.c called somewhere.

About memory problem. It may appear for both OC or Clover no matter of Clover size. The problem is a place where we can allocate our kexts. There is a gap inside KC but of limited size. I don't know if the problem somehow resolved in OC.

[Slice]

This is a bug

2:570  0:001  === [ Found DSDT tables ] =======================
2:571  0:001  - DSDT-1.aml
2:573  0:001  - DSDT-2.aml
2:574  0:001  - DSDT-clean.aml
2:646  0:072  file EFI\CLOVER\KEXTS\10.11\AppleHDADisabler.kext\Contents\Info.plist
2:669  0:022  file EFI\CLOVER\KEXTS\Other\VoodooHDA.kext\Contents\Info.plist
2:715  0:046  file EFI\CLOVER\KEXTS\Other\FakeSMC.kext\Contents\Info.plist

 

[vector sigma]

6 hours ago, Jief_Machak said:

Ah ah. Ok, on me. But I don't see why we couldn't share that header. I don't know why it broke compilation, I thought I compiled and it worked.

 Answered you at github.. but in the meantime Slice fixed it. 

[Jief_Machak]

9 hours ago, Slice said:

This is a bug

2:570  0:001  === [ Found DSDT tables ] =======================
2:571  0:001  - DSDT-1.aml
2:573  0:001  - DSDT-2.aml
2:574  0:001  - DSDT-clean.aml
2:646  0:072  file EFI\CLOVER\KEXTS\10.11\AppleHDADisabler.kext\Contents\Info.plist
2:669  0:022  file EFI\CLOVER\KEXTS\Other\VoodooHDA.kext\Contents\Info.plist
2:715  0:046  file EFI\CLOVER\KEXTS\Other\FakeSMC.kext\Contents\Info.plist

 

What should it be ?

[corint1]

5 hours ago, mifjpn said:

Thank you very much.

Compile was done without errors.

I can boot Catalina.

 

correct , but why is it stuck in apfs driver for big sur?

[Matgen84]

1 hour ago, corint1 said:

 

correct , but why is it stuck in apfs driver for big sur?

 

Because Clover is no ready yet for Big Sur. 

[Slice]

6 hours ago, Jief_Machak said:

What should it be ?

There should not be "file ...Info.plist"

[Jief_Machak]

3 hours ago, Slice said:

There should not be "file ...Info.plist"

Done.

[netgear]

v5122 Entries boot Recovery same problem , hidden OK!

 

Spoiler

<dict>
                    <key>Ignore</key>
                    <false/>
                    <key>Hidden</key>
                    <true/>
                    <key>Volume</key>
                    <string>0D8CCBEC54F7D64F877A237AE7B6157E</string>
                    <key>NoCaches</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>Ripristino</string>
                    <key>Disabled</key>
                    <false/>
                    <key>Path</key>
                    <string>\A4EFE704-DD21-40C0-8D15-92894C553A4C\boot.efi</string>
                    <key>Type</key>
                    <string>OSXRecovery</string>
                    <key>Image</key>
                    <string>os_cata</string>
                    <key>VolumeType</key>
                    <string>Internal</string>
                    <key>InjectKexts</key>
                    <true/>
                </dict>

 

[deeveedee]

Just upgraded my HP EliteDesk 800 G4 Mini from r5119 / AptioMemoryFix.efi to r5122 / OCQuirks.efi.  Upgrade was painless and everything appears to be working perfectly.  Thank you CLOVER team for your great work!

 

EDIT: My steps for migrating from r5119 / AptioMemoryFix to r5122 / OCQuirks is documented here.

Edited September 3, 2020 by tonyx86

[Slice]

Looks like a new bug:

I have a kernel patch in my config but I see no it in Options menu. It was in 5120 or later.

 

[Jief_Machak]

Found a wrong test which could explain. Committed.

[Slice]

22 hours ago, Jief_Machak said:

Found a wrong test which could explain. Committed.

Thanks, now the patch is present in menu.

 

I am trying to install BigSur beta4 which I applied to new apfs container running macOS Install.app.

The installation stops at apfs_module_start:2411 but I think it is not a reason. The reason in next step which is halted.

Before this I see my kexts are not started "couldn't allocate class...". So plist of the kexts were loaded but what? They are prohibited to start?

I made some debug messages about kernel patching and see

143:788  0:183  procedure validateKCFileSetUUID found at 0x78e6d0
143:863  0:075   StartPattern found
143:962  0:099  ==> Success : 1 replaces done

Yes, custom kernel patch succeeded.

 

144:058  0:095  dump begin of WholePlist: <?xml version="1.0" 

This is also success of find PrelinkedKextsInfo.

 

146:154  0:075  cffaedfe07000001030000000b00000007000000

This is success of find macho header on kext AppleRTC. But next lines

148:128  1:974  symCmdOffset=0x418
148:262  0:133  driverKC: AddrVtable=0x3819b40 SizeVtable=0x1ec NamesTable=0x3aa89a8
148:337  0:075  updateChecksum not found
148:528  0:191  updateChecksum at 0x0

means that I still don't know where is the binary of the kext AppleRTC in memory if BooterKernelExtensions.kc loaded.

This patch failure may explain the stop of bigsur installation.

 

Second error I see is "couldn't allocate class AppleIntelPCHSeriesAHCI".

Why Apple's kext is not loaded? My chipset is Z170. Is it bad for bigsur?

Or bigsur can be installed only on SSD and not on HDD? I don't understand.

[jsl2000]

6 hours ago, Slice said:

Thanks, now the patch is present in menu.

 

I am trying to install BigSur beta4 which I applied to new apfs container running macOS Install.app.

The installation stops at apfs_module_start:2411 but I think it is not a reason. The reason in next step which is halted.

Before this I see my kexts are not started "couldn't allocate class...". So plist of the kexts were loaded but what? They are prohibited to start?

I made some debug messages about kernel patching and see

143:788  0:183  procedure validateKCFileSetUUID found at 0x78e6d0
143:863  0:075   StartPattern found
143:962  0:099  ==> Success : 1 replaces done

Yes, custom kernel patch succeeded.

 

144:058  0:095  dump begin of WholePlist: <?xml version="1.0" 

This is also success of find PrelinkedKextsInfo.

 

146:154  0:075  cffaedfe07000001030000000b00000007000000

This is success of find macho header on kext AppleRTC. But next lines

148:128  1:974  symCmdOffset=0x418
148:262  0:133  driverKC: AddrVtable=0x3819b40 SizeVtable=0x1ec NamesTable=0x3aa89a8
148:337  0:075  updateChecksum not found
148:528  0:191  updateChecksum at 0x0

means that I still don't know where is the binary of the kext AppleRTC in memory if BooterKernelExtensions.kc loaded.

This patch failure may explain the stop of bigsur installation.

 

Second error I see is "couldn't allocate class AppleIntelPCHSeriesAHCI".

Why Apple's kext is not loaded? My chipset is Z170. Is it bad for bigsur?

Or bigsur can be installed only on SSD and not on HDD? I don't understand.

I can confirm that Big Sur can be installed on HDD without issues.

You are near the last step to boot Big Sur with Clover which I am waiting for it eagerly.

[SavageAUS]

Hi guys, due to the way OC handles Windows booting (passing through all patches etc) I would like to boot windows with clover and boot OC with clover also. I know I could use refind to do the same thing but once clover can boot and install big sur on both Intel and AMD (I have both) I would prefer to switch back to clover. 

[Jief_Machak]

I configured OpenCore to boot Big Sur installer version 11.0.20A5343j (which beta is that ? 4 ?).

Then, I disabled all the Kernel/Add in OpenCore .plist. Guess the result...

Now finding which kext is needed to go over that.

[Matgen84]

27 minutes ago, Jief_Machak said:

I configured OpenCore to boot Big Sur installer version 11.0.20A5343j (which beta is that ? 4 ?).

Then, I disabled all the Kernel/Add in OpenCore .plist. Guess the result...

Now finding which kext is needed to go over that.

 

Big Sur version 11.0.20A5343j is Beta 5. Latest Beta 6  is 20A5364e 

[Jief_Machak]

Not surprising, when I remove VirtualSMC.kext, I got this stop at apfs_module_start:2411

 

I'm now experimenting OC patching from Clover.

[MICKHAEL]

51 minutes ago, Jief_Machak said:

Not surprising, when I remove VirtualSMC.kext, I got this stop at apfs_module_start:2411

 

I'm now experimenting OC patching from Clover.

not sure... but I think I had the same stop at apfs_module_start:2411 and with VirtualSMC.kext... with Clover 5119(german patched version)/5120 with kernel patches from German forum...

Edited September 5, 2020 by MICKHAEL

[Matgen84]

39 minutes ago, Jief_Machak said:

Not surprising, when I remove VirtualSMC.kext, I got this stop at apfs_module_start:2411

 

I'm now experimenting OC patching from Clover.

 

8 minutes ago, MICKHAEL said:

not sure... but I think I had the same stop at apfs_module_start:2411 and with VirtualSMC.kext... with Clover 5019/5020 with kernel patches from German forum...

 

Kernel patches from German forum works only on Mod Clover 5119 (not on official Clover version 5119, 5120, 5121, or 5122) 

 

[MICKHAEL]

7 minutes ago, Matgen84 said:

 

 

Kernel patches from German forum works only on Mod Clover 5119 (not on official Clover version 5119, 5120, 5121, or 5122) 

 

Thanks. I know that) used 5119 patched

[Slice]

1 hour ago, Matgen84 said:

 

 

Kernel patches from German forum works only on Mod Clover 5119 (not on official Clover version 5119, 5120, 5121, or 5122) 

 

Because of brute force instead of symbolic search.

[yapan4]

Hey boys, do not forget this method https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&amp;comment=2732413 that also successfully boot BS beta3

 

[Slice]

1 hour ago, yapan4 said:

Hey boys, do not forget this method https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&amp;comment=2732413 that also successfully boot BS beta3

 

Nothing new. I know these variables and can set them from Terminal when needed.