Jump to content
30960 posts in this topic

Recommended Posts

On 7/2/2021 at 7:56 PM, iCanaro said:

sorry if I insist, but in your opinion Counts how should it be set up to make it work best with Clover?

I think we can neglect those warning by CloverValidator because I can boot FX-6300 at Monterey beta1 now !

Screen Shot 2021-07-04 at 8.50.02 PM.png

config-Clover-M5A-Monterey.plist

Edited by jsl2000
  • Like 2
1 hour ago, MacKonsti said:

I hide everything in GUI -> Hidethat gets detected so I can place my own Custom Entries icons, is that not correct?

I use MacOS and Windows in 2 separate drives and want to add just 2 icons pointing to the correct disk/partition/container etc.

Otherwise I will get a "Preboot" entry shown in the main screen, like some other EFI and Windows icons...


	<key>GUI</key>
	<dict>
		<key>Hide</key>
		<array>
			<string>Legacy</string>
			<string>Preboot</string>
			<string>Recovery</string>
			<string>Windows</string>
		</array>
[...]

Thanks for any advice @Slice and everyone.

 

 

Hi @MacKonsti Clover boot Big Sur or Monterey via Preboot despite Big Sur or Monterey icons are showing up. So don't hide Preboot, if you want to start macOS :) @Slice already says that.

  • Like 2
  • Thanks 1

Hi @Matgen84 yes thank you, I did keep in mind what @Slice wrote, indeed.

I am of course not complaining, just seeking help if others made Custom Entries work well.

The idea is to hide all icons on Clover boot screen and use only custom entries -- but seems it doesn't work on Big Sur and newer. OK I accept that.

If anyone has experimented with Custom Entries, feel welcome to send me a PM so we don't flood the thread. Thanks again.

Does clover 5137 require a specific named icns file for Monterey in the boot GUI, or is this a theme issue? 

 

Created a custom icon for Monterey for BGM theme but have to name it os_mac.icns to display for Monterey.

 

Since this is the forum for clover, can someone tell me if clover 5137 can use different numbered folders under kexts directory in order to load different kexts for multiboot mac OS versions.

 

Example: folder named 10.15 for Catalina, folder named 11 for Big Sur and folder named 12 for Monterey.

 

If so, what is the exact folder nomenclature for these versions?

Edited by HenryV
Hi [mention=1110743]Matgen84[/mention] yes thank you, I did keep in mind what [mention=112217]Slice[/mention] wrote, indeed.
I am of course not complaining, just seeking help if others made Custom Entries work well.
The idea is to hide all icons on Clover boot screen and use only custom entries -- but seems it doesn't work on Big Sur and newer. OK I accept that.
If anyone has experimented with Custom Entries, feel welcome to send me a PM so we don't flood the thread. Thanks again.

I’ve inboxed you.


Sent from my iPhone using Tapatalk
I think we can neglect those warning by CloverValidator because I can boot FX-6300 at Monterey beta1 now !
163401003_ScreenShot2021-07-04at8_50_02PM.png.ba32035e2ecb10b411ec89e279e641ef.png

I can’t even boot Monterey with Clover on my Ryzen system yet, how did you get fx system to work?


Sent from my iPhone using Tapatalk
8 hours ago, HenryV said:

Does clover 5137 require a specific named icns file for Monterey in the boot GUI, or is this a theme issue? 

 

Created a custom icon for Monterey for BGM theme but have to name it os_mac.icns to display for Monterey.

 

Since this is the forum for clover, can someone tell me if clover 5137 can use different numbered folders under kexts directory in order to load different kexts for multiboot mac OS versions.

 

Example: folder named 10.15 for Catalina, folder named 11 for Big Sur and folder named 12 for Monterey.

 

If so, what is the exact folder nomenclature for these versions?

 

Hi @HenryV Since 25 days, there is a specific name for Monterey Badges: os_monterey

 

Spoiler

1655900920_Capturedcran2021-07-0507_09_00.png.c7c728325eaff2a35b3ef58d81c23ab4.png

 

  • Like 2

@SavageAUS if you want to try these kerneltopatches, they should be the exact translation of those of OC.
NB: anyone can check them if there are errors or forgetfulness

 

CLOVER_17H_19H_patches_All 3.plist

I double-checked the quirks in my AMD hack and they are identical between Clover and OC
With MONTEREY Boot OC, Clover doesn't start anything with the translation of the latest kerneltopatch

  • Like 2

This is why I put the question out there about using OC’s kerneltopatch in clover at least for AMD machines.
Maybe a simple if statement?
If cpu-type = Intel {
Run clover kerneltopatch patch
}
Else if cpu-type = amd {
Run OC kerneltopatch
}
I know it’s not that simple but hopefully a dev will see and have some input.


Sent from my iPhone using Tapatalk

  • Thanks 1

Hi @Jief_Machak @Slice

I build latest r5137 commit  a634a82. Using USB drive,  I test a new config.plist called config-wifi.plist. Strange behavior appears: what is ':4'

 

  • Clover detected an error from Clover GUI
Spoiler

screenshot0.thumb.png.0aae8cf0b201c0dbe86d0538797856ab.png

 

  • The same tool from local repo: no error
Spoiler

424154887_Capturedcran2021-07-0516_02_39.png.ef8289d85b4b8ff014dc75a8bd92e34a.png

 

 

Clover GUI shows up 'Boot macOS Big Sur via Preboot' instead of 'Boot macOS Monterey via Preboot'

 

Spoiler

screenshot0.thumb.png.a909acb1a19e692dcf83c4647db5fcd3.png

 

2021-07-05_14-15_BOOTX64.EFI.log

Edited by Matgen84

It says "Boot Mac OS BigSur via Preboot" because your drive's name is "BigSur"

 

The already defined tag means that it is added by the first config.plist, then the new one with new values are overwriting the defined value. It is a cosmetic bug.

53 minutes ago, kushwavez said:

It says "Boot Mac OS BigSur via Preboot" because your drive's name is "BigSur"

 

The already defined tag means that it is added by the first config.plist, then the new one with new values are overwriting the defined value. It is a cosmetic bug.

 

My drive is named 'Monterey' not BigSur. I have rename it since Beta 1  :) Strange indeed. Clover Keep the old name ! Right  Tag ':4' is a bug, but not cosmetic. I think there is a problem in configmanager, see commits on July, 1 @Jief_Machak or @Slice will find a solution.

 

Spoiler

988692793_Capturedcran2021-07-0516_48_39.png.aee4527fc46e4468c0908e012e057324.png

 

Edited by Matgen84
34 minutes ago, Matgen84 said:

 

My drive is named 'Monterey' not BigSur :) Strange indeed ! Right  Tag ':4' is a bug, but not cosmetic. I think there is a problem in configmanager, see commits on July, will find a solution.

 

  Reveal hidden contents

988692793_Capturedcran2021-07-0516_48_39.png.aee4527fc46e4468c0908e012e057324.png

 

No issue latest Compile Clover here

My drive is SSD Monterey 

screenshot6.thumb.png.786eb52ba99fa3351735dc253e6766db.png

 

  • Like 4
13 hours ago, chris1111 said:

No issue latest Compile Clover here

My drive is SSD Monterey 

 

 

 

Thanks :) After some investigations, I think the problem is occured when I rename my BigSur'HDD to Monterey via Disk Utility (Finder). Maybe System/Preference/Start Up disk keep the old name :cry: I don't know what is the correct way, to rename internal macOS drive, correctly o avoid this kind of issue. Now, my two USB key (Clover and Opencore) can't boot macOS Monterey :bye:

 

EDIT: I upgrade from Big Sur 11.5 Beta to Monterey Beta 2. Not a clean install

Edited by Matgen84
  • Sad 1

Hi @Slice @Jief_Machak

I've got few problem to boot macOS Monterey Beta via my USB stick (Z390 Config). Clover r5137 commit e12aefe81

Either the USB installation pen drive or the hard drive via the USB stick.

672:606  0:015  OCOS: OS set: <null> macOS 11.0
672:620  0:013  OCOS: OS set: Apple Inc. macOS 11.0

Let me know if there is a solution. Please

2021-07-06_08-57_BOOTX64.EFI.log

Edited by Matgen84
12 hours ago, 5T33Z0 said:

I have a question about csr-active config. For Monterey I use EF0F0000 in OpenCore. Would that be 0xFEF in Clover or what is the correct value to disable SIP?

I updated Monterey beta 1 to Monterey beta 2 with Clover 5137 having csr-active-config=0x285. Other bits are surplus.

 

2 hours ago, iCanaro said:

@Jief_Machak @Slice currently that version of opencore is in use in the clover engine?

If you carefully see changes in OpenCore then you may notice there are nothing essencial since 0.6.0 which is partially used in modern Clover.

We are tracing OpenCore changes to apply significant events.

Again, Clover uses 10% of OpenCore. 

  • Like 4
4 minutes ago, naiclub said:

I tried the latest OC version 0.7.1 but I'm not as happy as beta 0.7.1 before that, the latest version, booting into the icon selection page is very slow with slow.

Problems with OC has nothing to do with Clover right? Or am I wrong? 🤔

  • Like 1
Guest 5T33Z0
4 hours ago, Slice said:

If you carefully see changes in OpenCore then you may notice there are nothing essencial since 0.6.0 which is partially used in modern Clover.

We are tracing OpenCore changes to apply significant events.

Again, Clover uses 10% of OpenCore. 

 

"10 per cent" which provide all the memory fixes in the form of OpenRuntime.efi which make up 90 % of what makes Hackintoshes work. :D

On 7/5/2021 at 5:10 PM, iCanaro said:

@SavageAUS if you want to try these kerneltopatches, they should be the exact translation of those of OC.
NB: anyone can check them if there are errors or forgetfulness

 

CLOVER_17H_19H_patches_All 3.plist 26.9 kB · 6 downloads

I double-checked the quirks in my AMD hack and they are identical between Clover and OC
With MONTEREY Boot OC, Clover doesn't start anything with the translation of the latest kerneltopatch

Eventually my Ryzen 1700X can boot by Clover 5137 at Monterey beta1 now.

Please try my clover-config.plist

Screen Shot 2021-07-07 at 8.24.57 AM.png

 

Screen Shot 2021-07-07 at 8.38.09 AM.png

config.plist.zip

Edited by jsl2000
  • Like 1
  • Thanks 1
×
×
  • Create New...