Slice Posted June 9, 2021 Share Posted June 9, 2021 I updated and compile Clover in the Monterey OS. 0:162 0:000 Now is 09.06.2021, 17:56:32 (GMT) 0:162 0:000 Starting Clover revision: 5136 (master, commit fd780172d) on American Megatrends EFI 0:162 0:000 Build id: unknown 0:162 0:000 Build with: [Args: --conf=/Users/sergey/src/CloverBootloader/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -DLESS_DEBUG -t GCC53 -n 5 | OS: 12] Xcode 11.2.1 is still compatible with OS 12.0 2 Link to comment Share on other sites More sharing options...
bronxteck Posted June 10, 2021 Share Posted June 10, 2021 slice can you also compile voodoohda in monteray it seems it does not load for some users. Link to comment Share on other sites More sharing options...
Slice Posted June 10, 2021 Share Posted June 10, 2021 9 hours ago, bronxteck said: slice can you also compile voodoohda in monteray it seems it does not load for some users. Today evening I will propose some compilations. Link to comment Share on other sites More sharing options...
JorgeMax Posted June 10, 2021 Share Posted June 10, 2021 Installation made on top of the beta version of Big Sur: Spoiler Spoiler Spoiler Spoiler Spoiler On the first reboot the bluetooth didn't work properly, because my mouse still worked with limitations, without scrolling pages. Then I turned it off and started and there was the Bluetooth working fully, I didn't understand 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 10, 2021 Share Posted June 10, 2021 7 minutes ago, JorgeMax said: Installation made on top of the beta version of Big Sur: On the first reboot the bluetooth didn't work properly, because my mouse still worked with limitations, without scrolling pages. Then I turned it off and started and there was the Bluetooth working fully, I didn't understand Great What Clover r5136 commit did you use. Link to comment Share on other sites More sharing options...
JorgeMax Posted June 10, 2021 Share Posted June 10, 2021 14 minutos atrás, Matgen84 disse: Ótimo Qual commit do Clover r5136 você usou. master, commit 8b2af7e28 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 10, 2021 Share Posted June 10, 2021 (edited) Hi @Slice The latest commit don't understand "os_monterey" icon name for my two theme: the Monterey's USB stick is showing "os_mac.icns" instead. I use real icns format for the icon. Very strange again Any ideas. Please. EDIT: I apologize maybe missing: "Install%20Install%20macOS%20Monterey", "Install%20Install%20macOS%2012" or I misunderstood something, sorry for my bad English. Spoiler Edited June 10, 2021 by Matgen84 Link to comment Share on other sites More sharing options...
Slice Posted June 10, 2021 Share Posted June 10, 2021 1 hour ago, Matgen84 said: Hi @Slice The latest commit don't understand "os_monterey" icon name for my two theme: the Monterey's USB stick is showing "os_mac.icns" instead. I use real icns format for the icon. Very strange again Any ideas. Please. EDIT: I apologize maybe missing: "Install%20Install%20macOS%20Monterey", "Install%20Install%20macOS%2012" or I misunderstood something, sorry for my bad English. Hide contents Did you know that the file named "Install macOS 12"? Link to comment Share on other sites More sharing options...
Matgen84 Posted June 11, 2021 Share Posted June 11, 2021 9 hours ago, Slice said: Did you know that the file named "Install macOS 12"? Hi @Slice I made a Monterey's USB Installer to clean install the Preview. The key is "Install macOS 12 Beta" Maybe, for others Beta, the usb stick will be named "Install%20Install%20macOS%20Monterey". Only Apple now. Spoiler 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted June 11, 2021 Share Posted June 11, 2021 I just build recent commits for clover and got a kernel panic in Monterey when booting. Doesn’t happen with 5136 release clover. I did also update kexts so it could be something else. I will test more and report. Sent from my iPhone using Tapatalk 1 Link to comment Share on other sites More sharing options...
iCanaro Posted June 15, 2021 Share Posted June 15, 2021 @Jief_Machak @Fetta i can't figure out how to fix this alert on my amd hack config-T-RyZo.plist you need help or some indication... I checked the kerneltopatch section several times, but i couldn't find a solution to the warning, thank you Link to comment Share on other sites More sharing options...
iCanaro Posted June 15, 2021 Share Posted June 15, 2021 strange situation... I checked that if I open the plist with clover configurator last release, then I use syncronize and save, then I no longer have any error reporting from the validator, but at the boot then it does not start, as it seems to upset something and the kernel patches are not loaded. If you leave the config with the error warning, the system (whether mojave, catalina, or big sur) then loads correctly. I think it's a really weird bug. Let's hope that with translators something comes up that you understand 1 1 Link to comment Share on other sites More sharing options...
jsl2000 Posted June 16, 2021 Share Posted June 16, 2021 2 hours ago, iCanaro said: @Jief_Machak @Fetta i can't figure out how to fix this alert on my amd hack config-T-RyZo.plist you need help or some indication... I checked the kerneltopatch section several times, but i couldn't find a solution to the warning, thank you I guess because 3 "Find" were found "#Find" in your config.plist. Try to fix it for re-testing. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 16, 2021 Share Posted June 16, 2021 (edited) 5 hours ago, iCanaro said: strange situation... I checked that if I open the plist with clover configurator last release, then I use syncronize and save, then I no longer have any error reporting from the validator, but at the boot then it does not start, as it seems to upset something and the kernel patches are not loaded. If you leave the config with the error warning, the system (whether mojave, catalina, or big sur) then loads correctly. I think it's a really weird bug. Let's hope that with translators something comes up that you understand Hi @iCanaro I notice that in your config.plist: algrey - Disable _i386_lbr_init have a Replace, but no Find (Line 2282) algrey - Disable _i386_switch_lbrs: Idem (Line 2255) algrey - Disable _i386_lbr_native_state_to_mach_thread_state: Idem (Line 2337) Maybe, it's an explanation for the warnings. I hope Edited June 16, 2021 by Matgen84 1 Link to comment Share on other sites More sharing options...
iCanaro Posted June 16, 2021 Share Posted June 16, 2021 2 hours ago, Matgen84 said: Hi @iCanaro I notice that in your config.plist: algrey - Disable _i386_lbr_init have a Replace, but no Find (Line 2282) algrey - Disable _i386_switch_lbrs: Idem (Line 2255) algrey - Disable _i386_lbr_native_state_to_mach_thread_state: Idem (Line 2337) Maybe, it's an explanation for the warnings. I hope kernel patches are exact translation for Clover of those of OC and the find has empty field there 6 hours ago, jsl2000 said: I guess because 3 "Find" were found "#Find" in your config.plist. Try to fix it for re-testing. I made some changes from what the config was like and it gave the same alerts even with Find without # in front 1 Link to comment Share on other sites More sharing options...
kushwavez Posted June 16, 2021 Share Posted June 16, 2021 (edited) But then how do you patch a thing if Find isn't defined? Just a Replace won't do anything, because the patcher doesn't know what to patch. That is why the warning there Edited June 16, 2021 by kushwavez 1 1 Link to comment Share on other sites More sharing options...
iCanaro Posted June 16, 2021 Share Posted June 16, 2021 I understand the arguments, but I did not make patches; I just converted them for Clover from OC https://github.com/AMD-OSX/AMD_Vanilla In addition, these alerts are related to the latest versions of Clover and the validater, until recently nothing was reported. I also fixed the warnings by opening the config with clover configurator --> text mode --> synchronize; but it has a serious side effect, the validater does not report anything, but the AMD hack no longer starts as it does not load the kernelpatch 1 Link to comment Share on other sites More sharing options...
naiclub Posted June 16, 2021 Share Posted June 16, 2021 That's why the developers disappeared because everyone was scolding him for making him disappear. Link to comment Share on other sites More sharing options...
kushwavez Posted June 16, 2021 Share Posted June 16, 2021 Oh I see. Unfortunately I don't use KernelPatcher so this is out of my understanding. Bet @Slice can help you Link to comment Share on other sites More sharing options...
Slice Posted June 16, 2021 Share Posted June 16, 2021 5 hours ago, iCanaro said: kernel patches are exact translation for Clover of those of OC and the find has empty field there I made some changes from what the config was like and it gave the same alerts even with Find without # in front "Find" should not be empty. It must contains array of bytes the same length as "Replace". If the contents of the array is not meaningful then set Find=00000 and MaskFind as 00000 with the same length. 1 3 Link to comment Share on other sites More sharing options...
iCanaro Posted June 19, 2021 Share Posted June 19, 2021 On 6/16/2021 at 2:18 PM, Slice said: "Find" should not be empty. It must contains array of bytes the same length as "Replace". If the contents of the array is not meaningful then set Find=00000 and MaskFind as 00000 with the same length. I did not reply immediately, because in these days I have done several tests, I have run the translation of the OC patchkernels for Clover from scratch, but I cannot find a solution. In patches 0, 1 and 3 (which relate only to big sur) if I leave the find and maskfind fields blank, I get the validator signal; if I fill them as recommended with 00000, then I have no signal at boot and from the validator, but the effect is that big sur does not start; catalina and mojave start regularly, but big sur not. At the moment I have not found a solution for not having warnings and being able to start big sur. 2 Link to comment Share on other sites More sharing options...
jsl2000 Posted June 19, 2021 Share Posted June 19, 2021 17 minutes ago, iCanaro said: I did not reply immediately, because in these days I have done several tests, I have run the translation of the OC patchkernels for Clover from scratch, but I cannot find a solution. In patches 0, 1 and 3 (which relate only to big sur) if I leave the find and maskfind fields blank, I get the validator signal; if I fill them as recommended with 00000, then I have no signal at boot and from the validator, but the effect is that big sur does not start; catalina and mojave start regularly, but big sur not. At the moment I have not found a solution for not having warnings and being able to start big sur. In my Hackintoshs there was a bug of Clover 513x if legacy boot of Big Sur which should be 11.x instead of 10.13.6. So I need patch Big Sur as 10.13.6 to boot properly including FX-6300, P6TSE, P5Q PRO, and GA-965P-DS4. No such an issue if legacy booted by OpenCore. So can you change your patch MatchOS from 11.x to 10.13.6 and reboot ? Link to comment Share on other sites More sharing options...
iCanaro Posted June 19, 2021 Share Posted June 19, 2021 i could boot regularly from high sierra to big sur; just yesterday due to the failure to support ad display port 1.2 and USB problems, I updated high sierra to big sur 11.4 stable, while big sur 11.5 beta I will update it in monterey when there will be patches to try Link to comment Share on other sites More sharing options...
iCanaro Posted June 19, 2021 Share Posted June 19, 2021 this is my latest OC kernelpatch translation job for Clover CLOVER_KernelToPatch_17H_19H.plist_iCan.zip 2 Link to comment Share on other sites More sharing options...
jsl2000 Posted June 19, 2021 Share Posted June 19, 2021 (edited) 1 hour ago, iCanaro said: this is my latest OC kernelpatch translation job for Clover CLOVER_KernelToPatch_17H_19H.plist_iCan.zip Please try my modification of your config.plist either one of which should boot Big Sur successfully. CLOVER_KernelToPatch_17H_19H-modified.plist CLOVER_KernelToPatch_17H_19H-Ryzen.plist Edited June 19, 2021 by jsl2000 2 1 Link to comment Share on other sites More sharing options...
Recommended Posts