Jump to content
30960 posts in this topic

Recommended Posts

1 hour ago, rramon said:

So I do have to disable all other drives except the one I want to install Windows onto in BIOS?

All you have said is correct. After the installation is complete, then come to activate again.

  • Like 1
  • Thanks 1
5 hours ago, iCanaro said:

removed the initial underscores in proceedings
count = 0 changed to count = 1
count = 1 changed to count = 2

I try to start big sur, but it's not going; if you need here's the log and kerneltopatch tried

 

2021-07-01_20-50_CLOVERX64-5137-d2e652bd4.efi.logCLOVER_patches_17H19H_Monterey_beta1 3.plist

Good news !

After add Monterey specific patches to my original working config.plist it can boot both Big Sur and Monterey now to desktop smoothly.

But my Ryzen hackintosh had the issues of VoodooTSCSyncAMD-8-Core.kext and SmallTreeIntel82576.kext at Monterey only.

[Edit]

I found that Clover boots Monterey (system partition) while OpenCore boots Monterey (Data partition) by their respective names in Preboot.

config-Monterey beta1-jslai.plist

Edited by jsl2000
  • Like 3
  • Thanks 1
Good news !
After add Monterey specific patches to my original working config.plist it can boot both Big Sur and Monterey now to desktop smoothly.
But my Ryzen hackintosh had the issues of VoodooTSCSyncAMD-8-Core.kext and SmallTreeIntel82576.kext at Monterey only.
[Edit]
I found that Clover boots Monterey (system partition) while OpenCore boots Monterey (Data partition) by their respective names in Preboot.
config-Monterey beta1-jslai.plist

I’ll give your patches a crack when I get a chance on my AMD rig.


Sent from my iPhone using Tapatalk
9 hours ago, jsl2000 said:

Good news !

After add Monterey specific patches to my original working config.plist it can boot both Big Sur and Monterey now to desktop smoothly.

But my Ryzen hackintosh had the issues of VoodooTSCSyncAMD-8-Core.kext and SmallTreeIntel82576.kext at Monterey only.

[Edit]

I found that Clover boots Monterey (system partition) while OpenCore boots Monterey (Data partition) by their respective names in Preboot.

config-Monterey beta1-jslai.plist 23.65 kB · 6 downloads

 

unfortunately it doesn't work for me, it doesn't start any macOS.... I can't understand why the complete translation of the OC patches (which from me work on mojave, catalina and big sur, I have not yet installed monterey on AMD) with Clover instead does not work and does not start anything.
I did an experiment, in my patches I added yours, all you need to monterey and in mactOS I put 12 12.x and big sur starts, I just have to install monterey betya 1 and see what happens
if you try them too and tell me if they go to you

 

 

 

Edited by iCanaro
  • Like 1
4 hours ago, iCanaro said:

your i don't think

It's from fabiosun:

https://www.macos86.it/topic/4913-amd-clover-bootloader-monterey-beta-1-installation-patches/?tab=comments#comment-115745

I have modified his config.plist plus my original one.

Did your hackintosh stop after completetion of kernel patching (+++++++++++++++ appears) ?

After update Clover to 5137 version mine can boot to desktop, but whole system was not so stable.

Quite frequent frozen at desktop.

Edited by jsl2000
 
unfortunately it doesn't work for me, it doesn't start any macOS.... I can't understand why the complete translation of the OC patches (which from me work on mojave, catalina and big sur, I have not yet installed monterey on AMD) with Clover instead does not work and does not start anything.
I did an experiment, in my patches I added yours, all you need to monterey and in mactOS I put 12 12.x and big sur starts, I just have to install monterey betya 1 and see what happens
if you try them too and tell me if they go to you
 
 
CLOVER_17H_19H_TEST-iCan.plist

Have you managed to install Monterey yet?


Sent from my iPhone using Tapatalk
4 minutes ago, SavageAUS said:


Have you managed to install Monterey yet?


Sent from my iPhone using Tapatalk

 not yet

18 minutes ago, jsl2000 said:

Did your hackintosh stop after completetion of kernel patching (******************************* appears) ?

exact

if you've taken those patches, they're tailor-made on its TRX40, so I don't think they work best on ryzen

if someone with AMD ryzen and already monterey wants to try these kernelToPatch, finally from me starts macOS but I have not yet installed monterey.
I created the config in a way I didn't want to do, but given the current inability to translate the OC kernel patches in full, this could be an effective temporary solution for everyone.
Basically I took mine in use kerneltopatch for mojave, catalina and big sur, then of those of OC I translated and named 12.x 12 only those that serve for monterey

 

 

CLOVER_17H_19H_MJ_CT_BS+MRbeta1_iCan.plist

  • Like 2
if someone with AMD ryzen and already monterey wants to try these kernelToPatch, finally from me starts macOS but I have not yet installed monterey.
I created the config in a way I didn't want to do, but given the current inability to translate the OC kernel patches in full, this could be an effective temporary solution for everyone.
Basically I took mine in use kerneltopatch for mojave, catalina and big sur, then of those of OC I translated and named 12.x 12 only those that serve for monterey
 
 
CLOVER_17H_19H_MJ_CT_BS+MRbeta1_iCan.plist

What do you mean by temporary solution?


Sent from my iPhone using Tapatalk
10 minutes ago, SavageAUS said:


What do you mean by temporary solution?


Sent from my iPhone using Tapatalk

in the sense that I would like to find a way to make functional the simple translation of OC patches for Clover and not my solution for mojace, catalina, big sur + the only patches apart from monterey 

  • Like 1
19 hours ago, Slice said:

Why Count=0?

I have also propose to use more human name for procedures:

instead of "_i386_switch_lbrs" you'd better write "i386_switch_lbrs".

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

16 hours ago, iCanaro said:

if someone with AMD ryzen and already monterey wants to try these kernelToPatch, finally from me starts macOS but I have not yet installed monterey.
I created the config in a way I didn't want to do, but given the current inability to translate the OC kernel patches in full, this could be an effective temporary solution for everyone.
Basically I took mine in use kerneltopatch for mojave, catalina and big sur, then of those of OC I translated and named 12.x 12 only those that serve for monterey

 

 

CLOVER_17H_19H_MJ_CT_BS+MRbeta1_iCan.plist 41.26 kB · 5 downloads

Hi, Could you Please Share your Efi Folder without your Serial. I am on Ryzen 3600 + MSI x570 A Pro. I have Installed Monterey beta 1 using Opencore. I am new to Clover Bootloader.  so please Share your Clover EFI. Thank You!

if someone with AMD ryzen and already monterey wants to try these kernelToPatch, finally from me starts macOS but I have not yet installed monterey.
I created the config in a way I didn't want to do, but given the current inability to translate the OC kernel patches in full, this could be an effective temporary solution for everyone.
Basically I took mine in use kerneltopatch for mojave, catalina and big sur, then of those of OC I translated and named 12.x 12 only those that serve for monterey
 
 
CLOVER_17H_19H_MJ_CT_BS+MRbeta1_iCan.plist

I couldn’t boot my already installed (with OC) with these patches.


Sent from my iPhone using Tapatalk
2 hours ago, SavageAUS said:

Is there any reason Clover cannot adopt OC’s KerneltoPatch? For us AMD users it would be a blessing.


Sent from my iPhone using Tapatalk

I have successfully translated OC kerneltopatches for Clover several times and made available to everyone.
I'm not a programmer, a developer but a simple enthusiast, so I don't always have answers to questions, but from my point of view the issue now with this latest version of the patches, or there's a bug in Clover where it doesn't apply something properly in kerneltopatches, or some developers should tell us any mistakes we make in translating patches from OC to Clover

11 hours ago, iamprabhuantony said:

Hi, Could you Please Share your Efi Folder without your Serial. I am on Ryzen 3600 + MSI x570 A Pro. I have Installed Monterey beta 1 using Opencore. I am new to Clover Bootloader.  so please Share your Clover EFI. Thank You!

I ran out of space to uplod files, click in signature and find the EFI I put 

  • Like 1
I ran out of space to uplod files, click in signature and find the EFI I put 

And you do a fantastic job my friend, my post was just a question to the Clover devs to see if Clover can use the same kerneltopatch as oc. Then no translation would be needed.


Sent from my iPhone using Tapatalk
On 6/1/2021 at 6:43 PM, Slice said:

Second compilation resolved the problem:

CLOVERX64.efi.zip 698.16 kB · 16 downloads

 

Hello everyone, hello @Slice I have been using this "corrected" r5136 version for some time, without issues except Custom Entries.

For the love of me, I have been doing many tests and either no icons ever appear on the boot screen or the one that appears fails to boot Big Sur.

Finally after checking some shared config.plist files in earlier pages, I managed to show an icon for PreBoot container:

	<key>GUI</key>
	<dict>
		[...]
		<key>Custom</key>
		<dict>
			<key>Entries</key>
			<array>
				   <dict>
					<key>CustomLogo</key>
					<false/>
					<key>Disabled</key>
					<false/>
					<key>FullTitle</key>
					<string>Finally PreBoot</string>
					<key>Hidden</key>
					<false/>
					<key>InjectKexts</key>
					<true/>
					<key>NoCaches</key>
					<false/>
					<key>Title</key>
					<string>Just PreBoot</string>
					<key>Type</key>
					<string>OSX</string>
					<key>Volume</key>
					<string>95052FAF-1CDA-4FE0-A720-98F1EA09D664</string>
					<key>VolumeType</key>
					<string>Internal</string>
				</dict>
			</array>
		</dict>
	[...]

So the icon appears but when I boot (verbose) I get after a couple of verbose pages something about not being able to mount root or similar.

The Volume data/ID was retrieved from the boot log of Clover:

0:748  0:000  - [00]: 'Big Sur'
0:748  0:000      Checking volume "EFI" (PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0x0,0x0)\HD(1,GPT,FBE1ACEF-BC5C-494E-9793-46EE27B47E99,0x800,0x32000)) ... skipped because volume does not match
0:748  0:000      Checking volume "EFI" (PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(1,GPT,71BF5FC3-4AD1-41E8-8AA1-A943E33A017E,0x28,0x64000)) ... skipped because volume does not match
0:748  0:000      Checking volume "Preboot" (PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,95052FAF-1CDA-4FE0-A720-98F1EA09D664,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,A393FCACDEAA034693B76232A5B6BCE8)) ... skipped because volume is hidden
0:748  0:000      Checking volume "Intel NVMe - Data" (PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,95052FAF-1CDA-4FE0-A720-98F1EA09D664,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,12AC4AEDA939D443B80728A6049F074D)) ...   - search volume 'ACFC93A3-AADE-4603-93B7-6232A5B6BCE8', but MediaPath 'ED4AAC12-39A9-43D4-B807-28A6049F074D'

I am not sure what is going on and why, since the same Volume is selected as the "Preboot" detected by Clover, I don't get to boot?

@Slice is the build r5136 that you fixed, possibly not booting custom entries correctly?

 

Please, can some kind soul post their config section with Custom Entries that work and confirm it's on the r5136?

In previous Clover releases, we had <key> for "Path" that worked fine for Catalina, e.g. \System\Library\CoreServices\boot.efi key.

Do we still need a "Path" for Big Sur and what would be the contents, with volume UUID or not?

 

Thank you again..!

10 hours ago, Slice said:

And why the Preboot volume is hidden? You must start Preboot volume.

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.

 

Edited by MacKonsti
×
×
  • Create New...