Clover General discussion

[naiclub]

29 minutes ago, Jief_Machak said:

This debug.log starts with an old version and has some messages from 2 commits ago. So there is a mixup.
Could delete debug.log, make sure you have free space on your EFI partition and restart with this efi : CloverX64-2020-10-21-17-52-39-1803805-dirty-jief.zip

 

@iCanaro Could you try it too : I just restored the re-ordering feature to have main, preboot and recovery grouped.

This one, I can not boot at the same place.

[Jief_Machak]

15 minutes ago, naiclub said:

This one, I can not boot at the same place.

Each time you cannot boot, please do : 

- delete debug.log

- make sure you have free space on your EFI partition

- try to boot

- send me the debug.log (no need to generate preboot.log)

[Matgen84]

56 minutes ago, Jief_Machak said:

This debug.log starts with an old version and has some messages from 2 commits ago. So there is a mixup.
Could delete debug.log, make sure you have free space on your EFI partition and restart with this efi : CloverX64-2020-10-21-17-52-39-1803805-dirty-jief.zip

 

@iCanaro Could you try it too : I just restored the re-ordering feature to have main, preboot and recovery grouped.

@Jief_Machak I can boot CloverX64-2020-10-21-17-52-39-1803805-dirty-jief.efi on my Z390 Big Sur. All volumes are showing and I can mount EFI using ESP Mounter Pro.

 

Spoiler

 

debug.log

[naiclub]

35 minutes ago, Jief_Machak said:

Each time you cannot boot, please do : 

- delete debug.log

- make sure you have free space on your EFI partition

- try to boot

- send me the debug.log (no need to generate preboot.log)

Has done as you say everything But it cannot save the debug log. Symptoms like this

Spoiler

 

1 hour ago, naiclub said:

debug.log

  Reveal hidden contents

Edited October 21, 2020 by naiclub

[Dragster27]

Hi guys,

 

Thanks to the developers for keeping Clover up to date to support BigSur... 

 

I've had BS working until Beta 9 with OC 0.6x and Clover 5123... decided to wipe out the partition as it was kind of a mess already and to reinstall BS Beta 10 from scratch using Clover 5125 (release version, I'm not compiling the latest commits myself)  but I'm having a few issues...

 

I created a Usb installer which boots properly, I can select the HD to install... after the first reboot I'm selecting the BS preboot partition to continue the installation process but that's where the problems begin... I'm getting  the "couldn't allocate class appleIntelPCHSeriesAHCI" error... according to the Haswell guide in Dortania, some SATA controller support was dropped so I installed the CtlnaAHCIPort.kext in EFI\CLOVER\kexts\11 and bumped the version to 999 to force it to load.. however this isn't working.. I'm still getting the error... I have been closely following the thread and trying to avoid to ask simple questions so not to waste other people's time but I'm afraid I'm stuck at this point needing some help.

 

I'm attaching my config.plist and debug.log.. hopefully someone can help me getting it installed... 

 

Thank you,

D.

 

I'm going to update my signature with computer specs.. but here they are quickly: Toshiba Qosmio X75-A7298 intel Core i7 GFX: intelHD 4600 

debug.log

config.plist

Edited October 21, 2020 by Dragster27

[Funky frank]

21 hours ago, Jief_Machak said:

Did you create and fill with proper values the Quirks section in config.plist ?

 

@everyone : to avoid having main BS  partition in Clover menu, use this (or compile last commit) : CloverX64-RELEASE_GCC53-2020-10-20-22-44-34-d17d02b-dirty-jief.zip

 

Do I have to put OpenRuntime.efi and qcquirks.efi(?) to the drivers64UEFI and drivers/UEFI dirs?

 

Now I can see the Apple logo a very short time after selecting the boot drive, I added the quirk settings accordingly to here: https://dortania.github.io/OpenCore-Install-Guide/config.plist/haswell.html#booter

 

Then the computer resets. Still haven't installed an openruntime.efi and so.

 

I have a haswell core i7 4770. I remember my board needed OsxAptioFix2Drv-64.efi for some time, until Clover or so could do that by itself...

 

Here is my config

config.plist

 

EDIT: Ok, after copying openruntime.efi, it loads, but now my haswell GPU HD4600 is gone (without connector, only as opencl device, and h264 encoder).

 

Also usb stuff doesn't work like beofre, keyboard was newly detected.

 

The bootup is a bunch slower than with old clover.

Edited October 21, 2020 by Funky frank

[D-an-W]

Can't seem to boot Big Sur with the latest commits (Catalina is ok), one of the Big Sur entries is now hidden which I know @Jief_Machak was working on doing.

 

Going to try and create a debug log now (The last time I tried it was empty).

 

debug.log

 

Edited October 21, 2020 by D-an-W

[Funky frank]

What is the last clover build without opencore integration? Since I don't need that.

[iCanaro]

3 hours ago, iCanaro said:

4 hours ago, Jief_Machak said:

@iCanaro Could you try it too : I just restored the re-ordering feature to have main, preboot and recovery grouped.

done, here are the logs

preboot.logdebug.log

I will auto cite 

the same configuration that just now worked, now does not start bigsur, these is started with the configs where the MatchOS fields are left empty ... I would call it random behavior
 

[kushwavez]

1 hour ago, Dragster27 said:

I created a Usb installer which boots properly, I can select the HD to install... after the first reboot I'm selecting the BS preboot partition to continue the installation process but that's where the problems begin... I'm getting  the "couldn't allocate class appleIntelPCHSeriesAHCI" error... according to the Haswell guide in Dortania, some SATA controller support was dropped so I installed the CtlnaAHCIPort.kext in EFI\CLOVER\kexts\11 and bumped the version to 999 to force it to load.. however this isn't working.. I'm still getting the error... I have been closely following the thread and trying to avoid to ask simple questions so not to waste other people's time but I'm afraid I'm stuck at this point needing some help.

I've had a similar issue with Clover v5125. My Acer notebook (notebook 1 in signature) needs CtlnaAHCIPort.kext to load my SATA drives. I cannot even get the USB installer loaded because of that (even Catalina installer didn't work with that), the log said it's loaded so idk what was the problem. A simple v5124 CLOVERX64.efi reverting solved the problem, succesfully installed BS 10 with Clover v5124.

[D-an-W]

I thought I had booted into Big Sur with at least one commit of r5125 but currently can't get it to boot with either of the two backups I have to hand, r5124 still works ok (r5125 works fine with Catalina).

 

Is this behaviour what others are seeing?

[gerard71]

17 hours ago, SavageAUS said:

Try this one.

config.plist

ok it works we must remove
Check that in the Config -> GUI -> hide
the preboot entry must not be present
in the config.plist that you made me for the beta 10 of big

thanks a lot for your help

[Jief_Machak]

3 hours ago, naiclub said:

Has done as you say everything But it cannot save the debug log. Symptoms like this

  Hide contents

 

That's good so far. Can't see the white line but if it's \EFI\CLOVER\CloverX64-2020-10-21-17-52-39-1803805-dirty-jief.efi, that's good too.

What happens when you press enter ?

[Jief_Machak]

@everyone : if you have a successful boot with a previous version and not with that last one I'm sending here, send me (PM if you'd like), a debug.log of a successful boot and the debug.log of the unsuccessful one.

I can't do anything with just a "it doesn't work".

 

Also : have a look at log yourself before posting.

1) near the top, you have the version and the build ID. Check them before sending.

2) it's not so hard to check if you're patches are taken into account, what kext are really injected.

3) delete the log before making one for me. I sometimes receive log with 4/5 boots chained together. How am I supposed to know which one is the right one ?

[Jief_Machak]

@kushwavez If 5124 works and not the latest, it should be too hard to find the commit to broke it and understand it.

Can I send clover efi file and you try them ?

[kushwavez]

9 minutes ago, Jief_Machak said:

@kushwavez If 5124 works and not the latest, it should be too hard to find the commit to broke it and understand it.

Can I send clover efi file and you try them ?

Yes of course, I'll test if you send them and I'll report back if it's okay or not with debug.logs. 

 

I attached a debug.log from the latest git v5125 non-working Clover, I didn't see any suspicious tho, but take a look if you need.

On 10/17/2020 at 2:34 PM, kushwavez said:

Installer USB's aren't working on Clover v5125 for me. (Notebook 1)

The process always hangs at IOAHCIBlockStorage because my ICH 100 series chipset needs "CtlnaAHCIPort.kext" in order to use SATA drives. 

 

Tested trice, results:

Big Sur Beta 10 Installer USB - Clover v5125: Hangs at IOAHCIBlockStorage, can't boot. However installed system is fine.

Catalina 10.15.7 Installer USB - Clover v5125: Stalling, but after a while proceeds to the Install screen, However my trackpad and keyboard aren't working, my drives aren't showing up in Disk Util. Installed system boots fine.

According to the debug.log the kexts (ApplePS2SmartTouchpad.kext, CtlnaAHCIPort.kext) are successfully loaded, but they're not working on v5125.

 

Then I replaced v5125 CLOVERX64.efi with v5124, results:

Big Sur Beta 10 Installer USB - Clover v5124: Will test in 30 minutes.  Tested, working. Installing now.

Catalina 10.15.7 Installer USB - Clover v5124: Booted the installer fine, drives are okay, trackpad ok, system ok.

debug.log

 

Edited October 21, 2020 by kushwavez

[Jief_Machak]

3 minutes ago, kushwavez said:

debug.log

That seems to be the debug.log for when it's not working ? If so, please rename it clearly before sending. Please understand that I have zillion of debug.log.

Ok, for this one.

Please confirm to me that when you switch from 5124 to 5125 (and back) you did it in the exact same CLOVER folder. That's means the exact same config.plist, kexts, drivers, ACPI ?

If confirmed, send the debuglog 5124 (booted from that same folder than the 5125, you got it now, right ?)

[naiclub]

Just now, Jief_Machak said:

That's good so far. Can't see the white line but if it's \EFI\CLOVER\CloverX64-2020-10-21-17-52-39-1803805-dirty-jief.efi, that's good too.

What happens when you press enter ?

Spoiler

Will stop at this picture

Yes it is this one

Edited October 21, 2020 by naiclub

[Jief_Machak]

Just now, naiclub said:

  Reveal hidden contents

Will stop at this picture

Totally unreadable ! What do you want me to do with that ? Re-take it, please.

[D-an-W]

@Jief_Machak I tried to provide a debug.log from a working r5124 but it is zero bytes.

 

I can't recall how to compile specific versions but will try and find out and work back until one works.

 

I do know that with this version to boot Big Sur I do not choose Preboot option from the Clover menu.

[naiclub]

57 minutes ago, Jief_Machak said:

Totally unreadable ! What do you want me to do with that ? Re-take it, please.

video

I understand that debug.log. Will it save only if it can boot well up to the GUI page? There will be 2 boot files. The top will boot completely. The lower one will freeze as the clip image.

debug.log CloverX64-2020-10-21-17-19-01-1803805-dirty-jief.efi Boot and record well.

CloverX64-2020-10-21-17-52-39-1803805-dirty-jief.efi This one does not boot to the GUI page.

video This is an example to make it clear that The main drive is hidden. Only preboot drivers left

Edited October 21, 2020 by naiclub

[JorgeMax]

28 minutes ago, naiclub said:

video

I understand that debug.log. Will it save only if it can boot well up to the GUI page? There will be 2 boot files. The top will boot completely. The lower one will freeze as the clip image.

debug.log CloverX64-2020-10-21-17-19-01-1803805-dirty-jief.efi Boot and record well.

CloverX64-2020-10-21-17-52-39-1803805-dirty-jief.efi This one does not boot to the GUI page.

 

I have the same result

[D-an-W]

For me using CloverX64-2020-10-21-17-19-01-1803805-dirty-jief.efi I get a crash just after choosing the Big Sur Preboot entry (Other entry is hidden).

 

CloverX64-2020-10-21-17-19-01-1803805-dirty-jief.efi - debug.log

 

Does r5125 (Or any files / folders) require any changes to the Config.plist to work with Big Sur when compared to r5124?

[SavageAUS]

11 hours ago, polyzargone said:

@SavageAUS

 

Are you sure you're booting from Preboot and not Big Sur main partition?

In my screenshots, I use Preboot 10.16 to boot Big Sur. If I choose macOS Big Sur I also have a KP and instant reboot.

Are you using the latest clover master? One that removes the Big Sur main partition from clover GUI? Even on my intel laptop adding a custom entry for the preboot volume results getting stuck at STARTBS. 
No other changes made just a custom entry and if I disable that entry I can boot. 

[mnfesq]

I had been successful using v5124 to boot to Catalina and BS Beta 10.  Then, I tried v5125 and it did not work.  As soon as I selected it, I got a black screen and no activity.  I reverted to v5124 and now it also does not work.  When I boot to Catalina or BS, it hangs at pretty much the same place.  Here's a screenshot:

Spoiler

 

Any ideas what might be causing this?  I am reluctant to start tinkering with my config.plist since it worked previously with v5124.  I have manually installed/checked that the efi files for Boot and Clover are from v5124.  I have not changed any kexts.