Clover General discussion

[Jief_Machak]

1 hour ago, Deadpool said:

if I try to clean install big sur not using via preboot,

I'm sure to understand that. The installer I have is on a HFS partition = no preboot.

After I run the installer, Clover is supposed to show, by default, only the preboot boot.

So what do you mean exactly by : clean install big sur not using via preboot ? How is that even possible ? Older version of Clover ?

1 hour ago, kushwavez said:

in my case the "main" partition is not automatically hidden. I have to Hide via config.plist/GUI/Hide

I'd like to understand that. Could you send me your config.plist and a preboot.log ?

[Deadpool]

8 minutes ago, Jief_Machak said:

I'm sure to understand that. The installer I have is on a HFS partition = no preboot.

After I run the installer, Clover is supposed to show, by default, only the preboot boot.

So what do you mean exactly by : clean install big sur not using via preboot ? How is that even possible ? Older version of Clover ?

I'd like to understand that. Could you send me your config.plist and a preboot.log ?

@Jief_Machak let me explain:

 

1 - I have created Big Sur USB installer and used clover 5128 to boot it

2 - Once booted, I have selected to boot from usb and reached the installer screen, formatted the hard disk and started the installation

3 - When the installer automatically reboot the system to continue the installation, at the clover screen I had just the Data and my normal HD volumes (no preboot).

4 - If I continue the installation selecting the normal HD volume, it continue to install but at the next autmatic reboot, it blocks with the error: too many corpses being created..... (I can see it as I have always the verbose mode active)

5 - At the point 3, I had to press F3 to show the hidden volumes and select the preboot in order to be able to clean install Big Sur otherwise just the data and normal HD volumes would appear. That's why I was thinking that maybe is a problem related to my config as I always manually copy and paste the single files when I update clover.

 

Hope it helps and await for your comments.

 

[Slice]

7 minutes ago, Deadpool said:

@Jief_Machak let me explain:

 

1 - I have created Big Sur USB installer and used clover 5128 to boot it

2 - Once booted, I have selected to boot from usb and reached the installer screen, formatted the hard disk and started the installation

3 - When the installer automatically reboot the system to continue the installation, at the clover screen I had just the Data and my normal HD volumes (no preboot).

4 - If I continue the installation selecting the normal HD volume, it continue to install but at the next autmatic reboot, it blocks with the error: too many corpses being created..... (I can see it as I have always the verbose mode active)

5 - At the point 3, I had to press F3 to show the hidden volumes and select the preboot in order to be able to clean install Big Sur otherwise just the data and normal HD volumes would appear. That's why I was thinking that maybe is a problem related to my config as I always manually copy and paste the single files when I update clover.

 

Hope it helps and await for your comments.

 

Step 3 is wrong. You must choose Preboot.

[Jief_Machak]

4 minutes ago, Deadpool said:

I always manually copy and paste the single files when I update clover.

In my whole life, I never used the clover installer package !

 

5 minutes ago, Deadpool said:

at the clover screen I had just the Data and my normal HD volumes (no preboot).

That is what is not ok and looks like a bug in my automatic hiding algorithm.

Problem is, to debug that, you would have to delete everything, complete the installer once, reboot Clover (so we are now at your step 3) and then generate the preboot.log

1 minute ago, Slice said:

Step 3 is wrong. You must choose Preboot.

Yes, I think he knows. The problem is why Clover is letting doing that.

[Deadpool]

6 minutes ago, Jief_Machak said:

In my whole life, I never used the clover installer package !

 

That is what is not ok and looks like a bug in my automatic hiding algorithm.

Problem is, to debug that, you would have to delete everything, complete the installer once, reboot Clover (so we are now at your step 3) and then generate the preboot.log

Yes, I think he knows. The problem is why Clover is letting doing that.

@Jief_Machak could it be a problem with my config? when I have updated from last clover without quirks to the first release that uses quirks, I have just manually added the quirks section to my config using the plist editor. the rest of the config is remained as before. Should I create a new config using the sample one that comes with clover 5129? I'm thinking that maybe this could be the problem that took me to the situation where I was not seeing the preboot volume in the clover screen and just the data and the normal HD ones.

[Jief_Machak]

7 minutes ago, Deadpool said:

'm thinking that maybe this could be the problem

Pretty sure it's not. I did the same.

Use the validator to check your config.plist. The meaning of keys didn't change; that's why old config + quirks is ok.

[Deadpool]

7 minutes ago, Jief_Machak said:

Pretty sure it's not. I did the same.

Use the validator to check your config.plist. The meaning of keys didn't change; that's why old config + quirks is ok.

@Jief_Machak this is the output of the validator:

 

Warning: Unknown key '/KernelAndKextPatches/KernelCpu:931'. Skipped.

Warning: Unknown key '/Quirks/DisableRtcChecksum:1144'. Skipped.

 

what should I change in the config to avoid these warnings?

[Jief_Machak]

You can just delete them. These are unknown keys ignore by Clover already.

[Deadpool]

2 minutes ago, Jief_Machak said:

You can just delete them. These are unknown keys ignore by Clover already.

@Jief_Machak ok. So I don't know why I wasn't able to see the preboot. To normally boot big sur, I have deleted the preboot from the hidden volumes using clover configurator. Now just the recovery one is hidden by default and at the startup in the clover screen I have 2 volumes: the preboot and the normal HD when, if I understand properly, I should have just the preboot one, right?

[Jief_Machak]

33 minutes ago, Deadpool said:

I should have just the preboot one

Yes.

 

I'm trying to install in a virtual machine BS Beta10 (I'm downloading 11.1 currently). Install is on a virtual CD. At first reboot, I have

"Boot Mac OS X Install for [my volume name] via Preboot"

AND

"Boot Mac OS X Install for [my volume name]"

 

which seems wrong. I'll fix that later.

[kushwavez]

2 hours ago, Jief_Machak said:

I'd like to understand that. Could you send me your config.plist and a preboot.log ?

Of course here you are:

 

Preboot:

Spoiler

 

"main" normal partition, should be hidden by default (but it's not):

Spoiler

 

I have to manually hide the normal partition by config.plist/GUI/Hide. I also created a custom entry for Big Sur:

Spoiler

 

2021-1-29_13-45-17_CLOVERX64.efi.log

Edited January 29, 2021 by kushwavez

[Deadpool]

1 hour ago, Jief_Machak said:

Yes.

 

I'm trying to install in a virtual machine BS Beta10 (I'm downloading 11.1 currently). Install is on a virtual CD. At first reboot, I have

"Boot Mac OS X Install for [my volume name] via Preboot"

AND

"Boot Mac OS X Install for [my volume name]"

 

which seems wrong. I'll fix that later.

@Jief_Machak thank you very much. I'm happy to have helped you to solve this little issue

[chris1111]

2 hours ago, Jief_Machak said:

In my whole life, I never used the clover installer package !

 

So you have always have a UEFI machine in your whole life 

[MacKonsti]

@Jief_Machak thanks for looking into the issue. Few pages back it was reported that the PluginType parameter was no longer working and that it was advised by many to totally remove it from Clover config.plist and/or use/combine instead SSDT-PLUG.aml (obviously compatible with the CPU name on each hackintosh).

 

Please see @tonyx86 last post on this and his testing: 

So since we are no coders and cannot understand the great work you all developers do, we rely totally on your feedback and information, especially when a release is made and reading the Release Notes (on GitHub).

Was this an issue confirmed and/or resolved, therefore? What is the correct, working parameter in config.plist in latest Clover releases, please, regarding PluginType? TRUE or a number "1"?

 

Were we mislead and confused some days ago about this "apparent" bug? I ask because a few started advising to use SSDT-PLUG.aml from Dortania... Hence my insisting questions to you and Slice, mate....

 

I won't flood the thread anymore on this, I promise. Just wanted to know what we were talking about few pages back  Kindly check @iCanaro's post here and the subsequent posts: 

Thanks again, have a good weekend everyone.

Edited January 29, 2021 by MacKonsti

[iCanaro]

the advice to use SSDT for power management, is due to the fact that if you use OC and Clover in the same EFI, as I do in 4 hacks, in my opinion it makes the system more homogeneous regardless of which boot loader you use.
Having arranged plugin types is vital for the majority of users who use Clover without ssdt x PM

[Jief_Machak]

57 minutes ago, chris1111 said:

So you have always have a UEFI machine in your whole life

Absolutely not. But I still did the installation myself. fdisk, dd, etc... 

[chris1111]

7 minutes ago, Jief_Machak said:

Absolutely not. But I still did the installation myself. fdisk, dd, etc... 

fdisk, dd, etc with new Clover It's a lot of trouble when you know that the Package works perfectly on all Mac version . It's been a bit archaic; apple uses PKG to install macOS

But I respect your choice 

Edited January 29, 2021 by chris1111
apple uses PKG to install macOS 

[Jief_Machak]

11 minutes ago, chris1111 said:

fdisk, dd, etc with new Clover It's a lot of trouble when you know that the Package works perfectly

Sure. But I just have to do it once. And at that time, the package installer refused to install on the volume I wanted. So I had to it by hand. I also had to modify the first stage boot sector (the 512 bytes piece of code that loads boot6).

[chris1111]

5 minutes ago, Jief_Machak said:

Sure. But I just have to do it once. And at that time, the package installer refused to install on the volume I wanted. So I had to it by hand. I also had to modify the first stage boot sector (the 512 bytes piece of code that loads boot6).

I can confirm that currently the first stage boot sector boot 6 and boot 7 is working perfectly on any macOS. If you have to do it again it should work fine

Edited January 29, 2021 by chris1111

[PG7]

5 hours ago, chris1111 said:

I can confirm that currently the first stage boot sector boot 6 and boot 7 is working perfectly on any macOS. If you have to do it again it should work fine

Edited 5 hours ago by chris1111

 

I confirm that here also works normal!

 

Chris1111 a question for you who also use GT 210, with the new FULL Clover r5129 using the pkg config.plist you have no problems using the Nvidia inject?

here I can't do it again .. it is always playing with me with each new version (maybe because it is a 1gen laptop with GT 320M) but it is complicated and I had to abandon PStates and CStates to eliminate the kernel panic cpupm

 

I kidnapped @Slice and @Jief_Machak so they can analyze it, but I'm also open to other solutions!

 

in relation to processor management I am really satisfied with it

remember is an i5-M430 look at the print!

Spoiler

 

[deeveedee]

15 hours ago, PG7 said:

 

Iremember is an i5-M430 look at the print!

 

Why do you need VoodooTSCSync with Arrandale?

[PG7]

8 minutes ago, tonyx86 said:

 

Why do you need VoodooTSCSync with Arrandale?

I don't need it, but I don't break it either ... I can delete it and it doesn't have the least impact!

[chris1111]

15 hours ago, PG7 said:

 

I confirm that here also works normal!

 

Chris1111 a question for you who also use GT 210, with the new FULL Clover r5129 using the pkg config.plist you have no problems using the Nvidia inject?

here I can't do it again .. it is always playing with me with each new version (maybe because it is a 1gen laptop with GT 320M) but it is complicated and I had to abandon PStates and CStates to eliminate the kernel panic cpupm

 

Hi @PG7 I have no problem with inject Nvidia it works well 

5129 i didn't test it on my optiplex, i have a lot of update with Big Sur for my other pc and laptop. I do not test Clover at each revision for the old NV and HD 3000 cards 

[deeveedee]

24 minutes ago, PG7 said:

I don't need it, but I don't break it either ... I can delete it and it doesn't have the least impact!

I'd be curious to see your full IORegistryExplorer 2.1 dump.  Do you mind posting it?  You can see my full Arrandale system here.

[PG7]

1 hour ago, tonyx86 said:

I'd be curious to see your full IORegistryExplorer 2.1 dump.

 

PG7’s MacBook Pro High Sierra.zip PG7’s MacBook Pro Catalina .zip