Jump to content
30960 posts in this topic

Recommended Posts

Hi @Slice @Jief_Machak

I have a look to the latest commit d0388ee before building it. I don't understand why:

 

The new GUI/ProvideConsoleGop is introduced while ProvideConsoleGopEnable already exists in the Quirks section. ProvideConsoleGopEnable is always present in sample.plist despite of Provideconsole in GUI section.
Modestly (just my opinion), I think that the right place is in Quirks section because this setting is necessary (or don't be forgot to put to TRUE) for Openruntime, I suppose.

Edited by Matgen84
  • Like 1
13 minutes ago, Slice said:

I think the setting must always be "true".

It is not a quirks as it doesn't performed by OpenRuntime.

It was present in GUI section just before OC integration.


@Slice I understand what you say: always set to true. But after this commit ProvideConsoleGop is present two times in config.sample.plist: in GUI section and in Quirks ! Can you also post this change in Clover explanations sub-forum for those who migrate from old Clover, Please.

Edited by Matgen84
57 minutes ago, ellaosx said:

Can we also add this for BTL4ContinuityFixup in quirkmask:  

ExtendBTFeatureFlags 

Next version, I guess...

1 hour ago, Denisuu said:

Is there a guide to migrate from Clover r5122 to 5125?

Also does a sanity checker exist like this https://opencore.slowgeek.com/ for Clover?

Documentation is a big problem we haven't started to address.

Answer is no, just post scattered everywhere.

I would love something like that https://opencore.slowgeek.com/  for clover.

 

If you have a working OC configuration. It should be quite easy. Just create a Quirks section. People from this forum will help, I'm sure.

  • Like 5
  • Thanks 1
3 hours ago, Denisuu said:

Is there a guide to migrate from Clover r5122 to 5125?

Also does a sanity checker exist like this https://opencore.slowgeek.com/ for Clover?

Usually copying & pasting Quirks from 5125's config-sample.plist to your own 5122 config.plist should work.

Edited by Henry2010
6 hours ago, Denisuu said:

Is there a guide to migrate from Clover r5122 to 5125?

Also does a sanity checker exist like this https://opencore.slowgeek.com/ for Clover?

@Denisuu, there is a config.plist validation tool very similar to the OC Sanity Check which was recently developed and shared in this thread by @Jief_Machak. Not sure if the attached file is the latest one, but you can check in previous posts.

CloverConfigPlistValidator0.6

  • Like 1
  • Thanks 1
2 hours ago, jlrycm said:

@Denisuu, there is a config.plist validation tool very similar to the OC Sanity Check which was recently developed and shared in this thread by @Jief_Machak. Not sure if the attached file is the latest one, but you can check in previous posts.

CloverConfigPlistValidator0.6

This is the latest. But a quirk has moved. So you might get a false warning about console GOP.

  • Like 1

I see on Wikipedia that the latest dev beta is "11.0.1 developer beta", and not "11.0 developer beta 11". Apple we love you !.

4 minutes ago, fabiosun said:

but i have the same behaviour before and in that preboot i have had always big sur preboot stuff

Not sure what that mean.

Please, to talk about your issue, let's do it on github. If you'd like to add something to help, good, but on github. If you do it here, the history will be mixed and it's harder.

 

@everyone : from now on, I'll help with issue if they are open on Github. Thanks.

 

on the X570 I tried to upgrade BS beta 10 to beta 11 with (master, commit 9e7b4311c) but on the first restart then when in the Clover GUI you select the continuation of the installation, it restarts immediately
here are the logs of the upgrade attempt that ended with OC 062 and the first start of beta11 with Clover

 

X570_ 5125 (master, commit 9e7b4311c)_BSb11_install_NOK_debug.log

X570_ 5125 (master, commit 9e7b4311c)_BSb11_boot_OK_debug.log

  • Sad 1
41 minutes ago, iCanaro said:

on the X570 I tried to upgrade BS beta 10 to beta 11 with (master, commit 9e7b4311c) but on the first restart then when in the Clover GUI you select the continuation of the installation, it restarts immediately
here are the logs of the upgrade attempt that ended with OC 062 and the first start of beta11 with Clover

 

X570_ 5125 (master, commit 9e7b4311c)_BSb11_install_NOK_debug.log

X570_ 5125 (master, commit 9e7b4311c)_BSb11_boot_OK_debug.log

What would be good is to have a zip of your preboot. At first restart, instead of trying to boot BS, boot something else and zip the BS preboot.

  • Thanks 1
18 minutes ago, Jief_Machak said:

What would be good is to have a zip of your preboot. At first restart, instead of trying to boot BS, boot something else and zip the BS preboot.

 

OK I see to memorize the advice and next time if an update happens that doesn't go, then start from other macOS and compress the BS Preboot and post it on MEGA

  • Like 1
10 hours ago, Jief_Machak said:

I see on Wikipedia that the latest dev beta is "11.0.1 developer beta", and not "11.0 developer beta 11". Apple we love you !.

 

 

@Jief_Machak 9to5mac says: "Apple has released the first developer beta of macOS Big Sur 11.0.1, even though macOS 11 Big Sur has not yet even been released to the public. This comes as rumors about a potential Apple event circulate for sometime in November." It seems that the correct version number would be 11.0, 11.0.1, 11.0.2 and so on. Wait and see for the 11.0 release in November or Apple surprise :)

Edited by Matgen84

@Jief_Machak I have successfully tested the 9e7b4311c commit on my Z390 config (Beta 10).

Then I was able to update to Big Sur 11.0.1 Beta, but when restarting on macOS Installer, first the Clover timer did not work, no mouse and keyboard. So I shut down and restart the computer: after choosing macOSInstaller via Preboot (oddly) the sequence remains blocked on: EB LOG: EXITBS: START

Note: it's weird (where I am wrong): macOSInstaller via Preboot?

Debug.log in MP :)

On 10/28/2020 at 9:43 AM, Jief_Machak said:

Next version, I guess...

Documentation is a big problem we haven't started to address.

Answer is no, just post scattered everywhere.

I would love something like that https://opencore.slowgeek.com/  for clover.

 

If you have a working OC configuration. It should be quite easy. Just create a Quirks section. People from this forum will help, I'm sure.

 

18 hours ago, jlrycm said:

@Denisuu, there is a config.plist validation tool very similar to the OC Sanity Check which was recently developed and shared in this thread by @Jief_Machak. Not sure if the attached file is the latest one, but you can check in previous posts.

CloverConfigPlistValidator0.6

 

15 hours ago, Jief_Machak said:

This is the latest. But a quirk has moved. So you might get a false warning about console GOP.

 

Wow, thanks guys for the quick responses! How do I use the CloverConfigPlistValidator though? I tried dragging it into terminal but that doesn't work haha.

 

Just copying the Quirks section from the sample config.plist into my old config.plist doesn't work (system never boots).

 

Possibly there's a lot of unnecessary things in my EFI and config.plist, I followed Rehabmans guides years ago. Some things are probably outdated/unnecessary.

OC sanity checker for example says "FakePCIID.kext there are better ways to fake device ids".

 

I'm also not sure if I need all of these drivers? for OC I only need 4 drivers for everything to work.

Clover Drivers: ApfsDriverLoader.efi, DataHubDxe.efi, FirmwareVolume-64.efi, AptioMemoryFix-64.efi, FSInject.efi, HFSPlus.efi, AptioMemoryFix.efi, Fat-64.efi, PartitionDxe-64.efi, AudioDxe.efi

OC Drivers: AudioDxe.efi, HFSPlus.efi, OpenCanopy.efi, OpenRuntime.efi

 

I've attached my working 5122 EFI, everything works with this one.

Since moving back to clover I didn't install any kexts to L/E of S/L/E and everything works as intended, is there any benefit in installing the kexts?

N580VD-Clover_r5122_22OCT2020.7z

58 minutes ago, Matgen84 said:

 

@Jief_Machak I have successfully tested the 9e7b4311c commit on my Z390 config (Beta 10).

Then I was able to update to Big Sur 11.0.1 Beta, but when restarting on macOS Installer, first the Clover timer did not work, no mouse and keyboard. So I shut down and restart the computer: after choosing macOSInstaller via Preboot (oddly) the sequence remains blocked on: EB LOG: EXITBS: START

Note: it's weird (where I am wrong): macOSInstaller via Preboot?

Debug.log in MP :)


@Jief_Machak SOLVED: only for testing, I put also all the kexts in Other folder and in 11.0 folder. MacOS Installer can boot to finish update to macOS Big Sur 11.0.1 Beta 1

After last reboot, Big Sur Icons reappear beside Big Sur via Preboot icons in the Clover GUI. Finally, after select Big Sur via Preboot stuck on Automatic boot in 0 seconds (no mouse, no keyboard). If I add boot args: debug=0x100 keepsym=1, I can boot Big Sur 11.0.1

Edited by Matgen84
  • Like 2
1 minute ago, Matgen84 said:

 


@Jief_Machak SOLVED: only for testing, I put also all the kexts in Other folder and in 11.0 folder. MacOS Installer can boot to finish update to macOS Big Sur 11.0.1 Beta 1

After last reboot, Big Sur Icons reappear beside Big Sur via Preboot icons in the Clover GUI.

 

What was going on in my system. I left the kexts in folder 11, but when I selected "macOS Install" it restarted, I selected "macOS Install" again and pressed space, in the "OS X" section in the guid, the version of macOS type: 11.0 and the option of blocking kexts didn’t have, so it didn’t start because it didn’t identify the OS X version and the kexts in folder 11 wasn’t injected
Put in the folder "others" and now the folder 11 appeared in the lock section, and installed normal

  • Like 2
×
×
  • Create New...