Jump to content

Clover General discussion


ErmaC
29,868 posts in this topic

Recommended Posts

7 minutes ago, chris1111 said:

 

OK, so Apple changed the rule. New development needed.

Is it working in OpenCore?

3 hours ago, mariosun said:

@Slice

Is it possible to define SecureBootModel (Enabled/Disabled I mean) in Clover bootloader?

Thank you

Yes, we defined "Disabled" as only meaningful in Sonoma. And early too.

Link to comment
Share on other sites

2 minutes ago, Slice said:

OK, so Apple changed the rule. New development needed.

Is it working in OpenCore?

yes with securebootmodel set to Disabled

Link to comment
Share on other sites

35 minutes ago, Slice said:

OK, so Apple changed the rule. New development needed.

Is it working in OpenCore?

Yes, we defined "Disabled" as only meaningful in Sonoma. And early too.

I have to try THIS GUIDE + DANGER :unsure: I dont really have time now to see if that work

Edited by chris1111
Change Url's
Link to comment
Share on other sites

@Slice

 

OK now works after some adujtement in config.plist

image.pngimage.png

 

 

Start UP Disk Works after placing OpenVariableRuntimeDxe.efi before OpenRuntime.efi

 

 

See OpenCore 0.9.8 Duet  booting directly Sonoma :D

 

image.png

 

 

 

Edited by chris1111
Works
Link to comment
Share on other sites

21 minutes ago, Slice said:

I am waiting script or instruction from you what to repair.

I have the latest version of the compiler. But the installation became 5155 as usual instead of 5157 Look at the info, it shows the correct value 5157. But the boot page shows 5155. What is the reason?

thank.

Link to comment
Share on other sites

4 hours ago, Slice said:

I am waiting script or instruction from you what to repair.

I will see whats wrong but my thinking is it work correctly from Catalina in APFS volume without issue; so 

maybe its config.plist Set Up ? For OpenCore you need

 

  • Booter -> Quirks:
    • DisableVariableWrite: set to NO
  • Misc -> Security:
    • ExposeSensitiveData: set to at least 0x1
  • NVRAM:
    • LegacyOverwrite set to YES
    • LegacySchema: NVRAM variables set (OpenCore compares these to the variables present in nvram.plist)
    • WriteFlash: set to YES
    • OpenVariableRuntimeDxe.efi is placed before OpenRuntime.efi then both have LoadEarly set to YES
Link to comment
Share on other sites

@Slice I resolved from My testing Package, it work

 

I need more deep testing tonight then I will create a Pull Request

The issue is to Start all things I need to figure the best way Maybe an App call LegacyNVRAM :wink_anim: I dont know but I will propose the change to you

 

image.png

 

EDIT****

After installing Clover RCScripts

NVRAM can be install in EFI by  sudo /Private/etc/rc.shutdown.d/80.save_nvram_plist.local

Nothings more so its easy this way, for the user

NOTE:  If clover is installed for the first time, User have to reboot before using the command

image.png

 

 

  • Like 1
Link to comment
Share on other sites

8 minutes ago, chris1111 said:

No :D

@Slice

Sometimes we imagine that it would take a trick with a lot of modification but sometimes it's surprising how it's so simple

Link to comment
Share on other sites

1 hour ago, Slice said:

WIll it be working on next restart or you have to launch the script every time you want to reboot?

Working in next restart, the file nvram.plist always stay in EFI then you have all Logs of Starting services /Library/Logs/CloverEFI

clover.daemon.log and rc.boot.log + boot.log , system.log

Link to comment
Share on other sites

How did you install RcScript? Iam using Clover Package ESP /boot0af/Clover EFI 64-bits-sata

Install RC scripts on target volume

I hope you are using a real mac not a virtual machine or Qemu

Spoiler

image.pngimage.png

 

 

Link to comment
Share on other sites

×
×
  • Create New...