lucke Posted July 21, 2020 Share Posted July 21, 2020 (edited) Hi at all, now with 5120 I able to boot to 10.15.6, but... with only KernelXCPM=true => XCPM not enabled, with new bootstrap entry in KerneltoPatch =>XCPM ok found new patch to replace in Kernel: Find: 8D43C43C 427722 Rep.: 8D43C13C 227722 On 5119 version, no problem of active XCPM using only KernelXCPM=true Thanks for your work! Edited July 21, 2020 by lucke 1 1 Link to comment Share on other sites More sharing options...
pkdesign Posted July 22, 2020 Share Posted July 22, 2020 (edited) On 7/21/2020 at 2:29 PM, Slice said: It looks like you didn't replace OcQuirks.efi to the version provided with Clover 5120. New version size is 43392 bytes. Okay, didn’t know I had to. So in the future, you can’t update to a new version unless it is bundled with the Clover installer? I am currently using v23 provided on the Reddest Dream GitHub. EDIT: I reinstalled Clover including the OcQuirks.efi from installer. I still cannot boot. This is my OcQuirk.plist: <dict> <key>AvoidRuntimeDefrag</key> <true/> <key>DevirtualiseMmio</key> <true/> <key>DisableSingleUser</key> <false/> <key>DisableVariableWrite</key> <false/> <key>DiscardHibernateMap</key> <false/> <key>EnableSafeModeSlide</key> <true/> <key>EnableWriteUnprotector</key> <true/> <key>ForceExitBootServices</key> <false/> <key>MmioWhitelist</key> <array/> <key>ProtectMemoryRegions</key> <false/> <key>ProtectSecureBoot</key> <false/> <key>ProtectUefiServices</key> <true/> <key>ProvideConsoleGopEnable</key> <true/> <key>ProvideCustomSlide</key> <true/> <key>ProvideMaxSlide</key> <integer>0</integer> <key>RebuildAppleMemoryMap</key> <true/> <key>SetupVirtualMap</key> <false/> <key>SignalAppleOS</key> <false/> <key>SyncRuntimePermissions</key> <true/> </dict> And this is Quirks section from Clover plist: <key>Quirks</key> <dict> <key>ProtectUefiServices</key> <true/> <key>RebuildAppleMemoryMap</key> <true/> <key>EnableSafeModeSlide</key> <true/> <key>ProvideMaxSlide</key> <integer>0</integer> <key>SyncRuntimePermissions</key> <true/> <key>DevirtualiseMmio</key> <true/> <key>ProvideCustomSlide</key> <true/> <key>AvoidRuntimeDefrag</key> <true/> <key>ProvideConsoleGopEnable</key> <true/> <key>EnableWriteUnprotector</key> <true/> </dict> Edited July 22, 2020 by pkdesign Link to comment Share on other sites More sharing options...
Slice Posted July 22, 2020 Share Posted July 22, 2020 I see no <key>SetupVirtualMap</key> <false/> In the clover config.plist. Default value is true which is not the same as you previously used. Link to comment Share on other sites More sharing options...
pkdesign Posted July 22, 2020 Share Posted July 22, 2020 No, that isn't in my current OcQuirks plist. I added it to the quirks section of Clover config and I still can not boot: <key>Quirks</key> <dict> <key>ProtectUefiServices</key> <true/> <key>RebuildAppleMemoryMap</key> <true/> <key>EnableSafeModeSlide</key> <true/> <key>ProvideMaxSlide</key> <integer>0</integer> <key>SetupVirtualMap</key> <true/> <key>SyncRuntimePermissions</key> <true/> <key>DevirtualiseMmio</key> <true/> <key>ProvideCustomSlide</key> <true/> <key>AvoidRuntimeDefrag</key> <true/> <key>ProvideConsoleGopEnable</key> <true/> <key>EnableWriteUnprotector</key> <true/> </dict> Link to comment Share on other sites More sharing options...
Slice Posted July 23, 2020 Share Posted July 23, 2020 In you OcQuirks.plist the value is false. With this value you can boot. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 23, 2020 Share Posted July 23, 2020 (edited) Hi @Slice I build and test latest r5120 commit f7c13f0b (Big Sur DP Beta 2): can't boot Installer Big Sur or Installed Big Sur HD: always stucks at IOUSBHostinterface, follow by crossed out circle. I made a mistake somewhere ! debug.log EDIT: I download Beta 3. This version is named now: 11.0.20A5323l macOS Big Sur Beta in Apple catalog instead of 10.16 Edited July 23, 2020 by Matgen84 Link to comment Share on other sites More sharing options...
Slice Posted July 23, 2020 Share Posted July 23, 2020 51 minutes ago, Matgen84 said: Hi @Slice I build and test latest r5120 commit f7c13f0b: can't boot Installer Big Sur or Installed Big Sur HD: always stucks at IOUSBHostinterface, follow by crossed out circle. I made a mistake somewhere ! debug.log I have no idea what to test. 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 23, 2020 Share Posted July 23, 2020 2 minutes ago, Slice said: I have no idea what to test. I am not english, I don't understand what you mean. Sorry. Link to comment Share on other sites More sharing options...
Slice Posted July 23, 2020 Share Posted July 23, 2020 37 minutes ago, Matgen84 said: I am not english, I don't understand what you mean. Sorry. I see you can't boot. My question is "What shall I do?". Link to comment Share on other sites More sharing options...
Matgen84 Posted July 23, 2020 Share Posted July 23, 2020 (edited) 1 hour ago, Slice said: I see you can't boot. My question is "What shall I do?". Ok, I understand now. If other users can boot Big Sur from a USB stick or hard drive, my Clover config has a problem, I guess. How to identify it! In fact, I don't know. If other users have succeeded which would allow me to compare. EDIT: I test latest commit with USB Installer Beta 3. I see several messages "couldn't alloc" for kexts as Lilu for example. Spoiler Edited July 23, 2020 by Matgen84 Link to comment Share on other sites More sharing options...
MICKHAEL Posted July 23, 2020 Share Posted July 23, 2020 (edited) 4 hours ago, Matgen84 said: Ok, I understand now. If other users can boot Big Sur from a USB stick or hard drive, my Clover config has a problem, I guess. How to identify it! In fact, I don't know. If other users have succeeded which would allow me to compare. EDIT: I test latest commit with USB Installer Beta 3. I see several messages "couldn't alloc" for kexts as Lilu for example. Hide contents you are not alone. Big Sur beta3 compiled latest Clover... with beta2 and Clover compiled from 2 days ago I was able to boot to install screen) Spoiler Edited July 23, 2020 by MICKHAEL 3 Link to comment Share on other sites More sharing options...
Dragster27 Posted July 23, 2020 Share Posted July 23, 2020 7 hours ago, Matgen84 said: Ok, I understand now. If other users can boot Big Sur from a USB stick or hard drive, my Clover config has a problem, I guess. How to identify it! In fact, I don't know. If other users have succeeded which would allow me to compare. EDIT: I test latest commit with USB Installer Beta 3. I see several messages "couldn't alloc" for kexts as Lilu for example. Hide contents Same issue here... I was able to boot with clover BS Beta 2.. 1 Link to comment Share on other sites More sharing options...
pkdesign Posted July 23, 2020 Share Posted July 23, 2020 17 hours ago, Slice said: In you OcQuirks.plist the value is false. With this value you can boot. I can not boot with or without this value. Do you need to add <false> values for Clover Quirks plist? If you look above, all I have are true values in the Clover Quirks plist. I'm hate to admit I used Clover Configurator and put check marks for values. It only generates true ones. Does it need to look like the OcQuirks plist with true and false values? 2 Link to comment Share on other sites More sharing options...
Slice Posted July 24, 2020 Share Posted July 24, 2020 TextEdit is your friend. Open config.plist and change <true/> to <false/>. Or use Clover.app to do the work but not Clover Configurator. 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 24, 2020 Share Posted July 24, 2020 7 hours ago, pkdesign said: I can not boot with or without this value. Do you need to add <false> values for Clover Quirks plist? If you look above, all I have are true values in the Clover Quirks plist. I'm hate to admit I used Clover Configurator and put check marks for values. It only generates true ones. Does it need to look like the OcQuirks plist with true and false values? I upload my working OcQuirks.plist for Z390 Aorus Master. If you want, you can add the settings to Quirks section in your config.plist. All keys must be present even the value is false or array/, of course OcQuirks.plist Link to comment Share on other sites More sharing options...
Matgen84 Posted July 24, 2020 Share Posted July 24, 2020 (edited) Hi @Slice I build latest commit c87aabd: it's better I think. Thanks. Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module I see "couldn't load" kexts and "couldn't alloc" EDIT: one more time, I double check all my Z390 config settings. After this test. Spoiler Edited July 24, 2020 by Matgen84 1 Link to comment Share on other sites More sharing options...
aryaone Posted July 24, 2020 Share Posted July 24, 2020 1 hour ago, Matgen84 said: Hi @Slice I build latest commit c87aabd: it's better I think. Thanks. Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module I see "couldn't load" kexts and "couldn't alloc" EDIT: one more time, I double check all my Z390 config settings. After this test. same with me, still not succeeded to boot Big Sur using latest clover, booting to Catalina is perfect 1 Link to comment Share on other sites More sharing options...
MICKHAEL Posted July 24, 2020 Share Posted July 24, 2020 8 minutes ago, aryaone said: same with me, still not succeeded to boot Big Sur using latest clover, booting to Catalina is perfect well, the funniest thing, beta 2 boots, but that's not happening with beta 3. also Catalina boots. Link to comment Share on other sites More sharing options...
iCanaro Posted July 24, 2020 Share Posted July 24, 2020 (edited) 13 minuti fa, aryaone ha detto: lo stesso con me, non sono ancora riuscito ad avviare Big Sur usando l'ultimo trifoglio, l'avvio su Catalina è perfetto Z370 idem Edited July 24, 2020 by iCanaro 1 Link to comment Share on other sites More sharing options...
MICKHAEL Posted July 24, 2020 Share Posted July 24, 2020 hello @Slice i will post it here, maybe its helpfulcommit c87aabd boot log for Big Sur Beta2 boot log for Big Sur Beta3 same EFI are booting Catalina without any other problem if you think I must post my EFI, just ask regards 2 Link to comment Share on other sites More sharing options...
Dragster27 Posted July 24, 2020 Share Posted July 24, 2020 4 hours ago, MICKHAEL said: well, the funniest thing, beta 2 boots, but that's not happening with beta 3. also Catalina boots. ditto 6 hours ago, Matgen84 said: Hi @Slice I build latest commit c87aabd: it's better I think. Thanks. Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module I see "couldn't load" kexts and "couldn't alloc" EDIT: one more time, I double check all my Z390 config settings. After this test. Reveal hidden contents I have the exact same issue here... 1 1 Link to comment Share on other sites More sharing options...
lesvink Posted July 24, 2020 Share Posted July 24, 2020 (edited) Hi, I tried to boot on Big Sur Beta 2 USB key (Clover 5120) with no hope...and I reached the installer ! I didn't continue because I had no hard drive ready for trying install but I'll test soon. Z77 DS3H rev 1.0 (socket 1155) Ivy Bridge (!) i3 3225 GTX 770 8 GB RAM Tried with SMBIOS iMacPro1,1 and latest Virtual SMC, Lilu and Whatevergreen (no other change on Clover 5120). Edited July 24, 2020 by lesvink 1 Link to comment Share on other sites More sharing options...
iCanaro Posted July 24, 2020 Share Posted July 24, 2020 Big Slice habemus ductus translations are now missing "only" 1 Link to comment Share on other sites More sharing options...
pkdesign Posted July 24, 2020 Share Posted July 24, 2020 14 hours ago, Matgen84 said: I upload my working OcQuirks.plist for Z390 Aorus Master. If you want, you can add the settings to Quirks section in your config.plist. All keys must be present even the value is false or array/, of course OcQuirks.plist Thanks Matgen but I have a fully working OcQuirks.plist. The issue I am having is the incorporation of these quirks into the Clover config.plist and not having them on their own in the drivers folder. I think Slice is misunderstanding me. What I was asking is, do I have to have both false and true statements for all the quirks. Currently I only have the true statements listed (see above) in the Clover config.plist. What I will do when I get a minute is literally copy ALL the quirks from my current OcQurks.plist (true AND false) and copy them into the Clover config.plist. 1 Link to comment Share on other sites More sharing options...
MICKHAEL Posted July 24, 2020 Share Posted July 24, 2020 38 minutes ago, pkdesign said: Thanks Matgen but I have a fully working OcQuirks.plist. The issue I am having is the incorporation of these quirks into the Clover config.plist and not having them on their own in the drivers folder. I think Slice is misunderstanding me. What I was asking is, do I have to have both false and true statements for all the quirks. Currently I only have the true statements listed (see above) in the Clover config.plist. What I will do when I get a minute is literally copy ALL the quirks from my current OcQurks.plist (true AND false) and copy them into the Clover config.plist. yes. positive. you must have all quirks entries in clovers config.plist, just like you have in OcQuirks.plist. and, don't forget, use OcQuirks.efi from Clover installer 1 Link to comment Share on other sites More sharing options...
Recommended Posts