rock.n.rollyn Posted October 19, 2017 Share Posted October 19, 2017 now ig-platform-id and device-id are same like old clover. your attempted clover version is too old. need to find way try another version except 4243 https://sourceforge.net/projects/cloverefiboot/files/Installer/ 4233 clover tested with same error. debug_preboot_4233.zip Sorry, just read your reply. I sent you a PM. Link to comment Share on other sites More sharing options...
apianti Posted October 19, 2017 Share Posted October 19, 2017 @fabiosun, Set Boot/Debug=true and you will get debug.log. Link to comment Share on other sites More sharing options...
Slice Posted October 19, 2017 Share Posted October 19, 2017 Thank you @Slice and @Badruzeus @Regi Yassin 's report, please try r4255 to see if this indeed solve wrong MatchOS injection on your computer. syscl Tested 4256 in QEMU. 10.7.3 injection works. 1 Link to comment Share on other sites More sharing options...
bergoulle Posted October 20, 2017 Share Posted October 20, 2017 Hello, Running High sierra every were smooth before applying the 4243 update. Since then, i can not go further than ++++++++ I m using an ASUS VI impact with an i5 4670k and a smbios of imac 14,2. Any help/Suggestion would be appreciated. Thx Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2017 Share Posted October 20, 2017 Hello, Running High sierra every were smooth before applying the 4243 update. Since then, i can not go further than ++++++++ I m using an ASUS VI impact with an i5 4670k and a smbios of imac 14,2. Any help/Suggestion would be appreciated. Thx known issue. Please update lastest clover from sf 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2017 Share Posted October 20, 2017 The error, same as before. IMG_20171019_200801.jpg preboot 0x01620005.log.zip Weird, second trial boot return me this: ioconsoleusers gioscreenlockstate okay i found something. why you not use lilu + intelgrahpicsfixup with latest clover? you used it with old clover r3763. i checked your ioreg. please upload files blow 1. r3763 clover bootlog. 2. r4257(there is in clover sf.net) preboot log file. before test, important remove ig-platform-id on config.plist. 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2017 Share Posted October 20, 2017 @Sherlocks could you take a look to this debug? it is the result config you did yesterday for me I was be able to have a debug.log inside config and debug.log Thank you looks good. how about performance compared before? patch is same like your old config. I just clarified the patch's comments and the unnecessary parts of the binary patch. you didn't use slide=128. i don't see slide=128 on your log. is there no problem about boot? Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2017 Share Posted October 20, 2017 Performance is the same Yes I don't use slide=128 and in first boot I have had allocation error after reboot I have entered clover options/ kernel and I have Unchecked two 10.12.6 active patches in this way system has booted I have refreshed my x99 deluxe 2 bios and deleted nvram.plist and rc script on volume I don't know if it could be relation to the fact now I can write debug.log yesterday no thank you again after reboot I have entered clover options/ kernel and I have Unchecked two 10.12.6 active patches - this point is strange. you used 10.13 HS. in config.plist, 10.12 kernel patches has MatchOS 10.12.6 or 10.12.x. can't work that mentioned Unchecked two 10.12.6 active patches as result, to avoid allocation error, you have to just enable two patch? how about enable other patch except you actived patches before? Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2017 Share Posted October 20, 2017 Sorry I have used only two patches related at system I am using (HighSierra) If I have enabled all 4 patches 10.12.x and 10.13.x I can boot only with slide=128 as you see from this log I hope thank you for your time strange. Unlike what you said, there is no difference from previous logs. before 25:659 0:007 Filtering KernelPatches: 25:661 0:002 - [00]: cpuid_set_info_rdmsr © vit9696 :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 25:666 0:004 - [01]: xcpm_idle_wrmsr © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 25:670 0:004 - [02]: xcpm_assert_rdmsr © Sherlocks :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 25:678 0:007 - [03]: xcpm_SMT_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 25:682 0:004 - [04]: cpuid_set_info - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 25:687 0:004 - [05]: xcpm_bootstrap - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12,x | MatchBuild: no] ==> disabled by user 25:692 0:004 - [06]: xcpm_bootstrap - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.6 | MatchBuild: no] ==> disabled by user 25:699 0:007 - [07]: xcpm_assert_perf_max © okrasit :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 25:704 0:004 - [08]: xcpm_assert_wrmsr © Sherlocks :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 25:709 0:004 - [09]: xcpm_core_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 25:713 0:004 - [10]: xcpm_program_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 25:721 0:007 - [11]: xcpm_pkg_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 25:725 0:004 - [12]: xcpm_SMT_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 25:730 0:004 - [13]: cpuid_set_info - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 25:735 0:004 - [14]: xcpm_bootstrap - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 25:742 0:007 - [15]: xcpm_assert_perf_max © okrasit :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 25:747 0:004 - [16]: xcpm_assert_wrmsr © Sherlocks :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 25:752 0:004 - [17]: xcpm_core_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 25:759 0:007 - [18]: xcpm_program_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 25:764 0:004 - [19]: xcpm_pkg_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 25:769 0:004 - [20]: xcpm_SMT_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user new 27:434 0:004 Filtering KernelPatches: 27:439 0:004 - [00]: cpuid_set_info_rdmsr © vit9696 :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 27:444 0:004 - [01]: xcpm_idle_wrmsr © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 27:449 0:004 - [02]: xcpm_assert_rdmsr © Sherlocks :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 27:453 0:004 - [03]: xcpm_SMT_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x,10.13.x | MatchBuild: no] ==> disabled by user 27:461 0:007 - [04]: cpuid_set_info - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 27:465 0:004 - [05]: xcpm_bootstrap - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12,x | MatchBuild: no] ==> disabled by user 27:470 0:004 - [06]: xcpm_bootstrap - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.6 | MatchBuild: no] ==> disabled by user 27:475 0:004 - [07]: xcpm_assert_perf_max © okrasit :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> not allowed by OS 27:482 0:007 - [08]: xcpm_assert_wrmsr © Sherlocks :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 27:487 0:004 - [09]: xcpm_core_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 27:492 0:004 - [10]: xcpm_program_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> not allowed by OS 27:499 0:007 - [11]: xcpm_pkg_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 27:504 0:004 - [12]: xcpm_SMT_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.12.x | MatchBuild: no] ==> disabled by user 27:509 0:004 - [13]: cpuid_set_info - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 27:513 0:004 - [14]: xcpm_bootstrap - Broadwell E © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 27:521 0:007 - [15]: xcpm_assert_perf_max © okrasit :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 27:526 0:004 - [16]: xcpm_assert_wrmsr © Sherlocks :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 27:530 0:004 - [17]: xcpm_core_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 27:535 0:004 - [18]: xcpm_program_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 27:542 0:007 - [19]: xcpm_pkg_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user 27:547 0:004 - [20]: xcpm_SMT_scope_msrs © Pike R. Alpha :: [OS: 10.13 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user Actual patch behavior is the same as before also i uploaded config files like pic. it has already actived 10.12.6 patches. i'm confused now Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2017 Share Posted October 20, 2017 in attachment you can see working config without adding slide=128 from log there is no evidence of this? or the first allocation error? i uploaded config.plist http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2518813 already enable 10.12 kernel patch but you used 10.13, its not working. i see your pic above. you disabled for 10.12 kernel patch compared i uploaded config above link. it makes confused. Even if you use osxaptiofixv2, you can face an allocation error. I am not a developer because I do not know the exact problem. I have often experienced these problems while testing several systems. So I use osxaptiofixv2-free2000(also use safe mode) on my system. It is not recommended to use free2000 but you have to find the most optimal setting. When I look at the logs anyway, I can see that your actions are recorded and the patches are determined to work accordingly. Clover has no problem at all. Now there is nothing I can help you with. thanks Link to comment Share on other sites More sharing options...
Sherlocks Posted October 20, 2017 Share Posted October 20, 2017 Grazie Sherlocks for your time , maybe is my english I am in MacOS High Sierra in your config.plist there are two active kernel patches that match 10.12.x and two active matching macOS 10.13.x if I am in HIGH Sierra I need of all 4 patches? If I understand well no. on 10.12.6 related in debug.log there is not allowed by OS instead in 10.13.x there is allow by os as I think is right By the way I am not saying it is a bug or not but it is a fact that in my system (x99 xeon and so on) I have allocation error if I am not using slide=128 also with log saying two patched are not allowed but maybe them occupy some memory space? thank you again I don't know that point.Your understand is right. I just actived two sierra patch for your oppertunity if you want to back sierra without considering kernel patch for sierra. There was Osxaptiofix or osxaptiofixv2 converstation before. I also reported it too. I don't know exact problem. Also i can't resolve this problem. I'm not a developer. So I just found best way for me. Clover features is no problem. I recommend you find best combination osxaptiofixv2 + slide value(like you mentioned 128) to avoid error. Sorry for my bad english. Thanks 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
bergoulle Posted October 20, 2017 Share Posted October 20, 2017 known issue. Please update lastest clover from sf 나의 LG-F800S 의 Tapatalk에서 보냄 All above fails. Had to revert back to 4012 (painful task without a rescue USB) Link to comment Share on other sites More sharing options...
Funky frank Posted October 20, 2017 Share Posted October 20, 2017 Please, for the dumb: I have a working 10.12.6 clover setup. Can I simply upgrade to last clover, then High Sierra, and it will work OOTB? Here is my config (Asus B85M-G): config.plist.zip And what specific FakeSMC version I have to use? Link to comment Share on other sites More sharing options...
rock.n.rollyn Posted October 20, 2017 Share Posted October 20, 2017 okay i found something. why you not use lilu + intelgrahpicsfixup with latest clover? you used it with old clover r3763. i checked your ioreg. please upload files blow 1. r3763 clover bootlog. 2. r4257(there is in clover sf.net) preboot log file. before test, important remove ig-platform-id on config.plist. debug_preboot_4257.zip Link to comment Share on other sites More sharing options...
Badruzeus Posted October 21, 2017 Share Posted October 21, 2017 Hello, using r4259 (legacy) from SF release; I sometime get this fluid UI on Kext Inject Management (but sometime it doesn't): Thanks Link to comment Share on other sites More sharing options...
arabesc Posted October 21, 2017 Share Posted October 21, 2017 I can't make Clover to boot from a last booted volume, I mean the DefaultVolume/LastBootedVolume option. It almost always selects the same volume. According to the guide it's necessary to remove the EmuVariableUefi-64.efi module, but I can't remove it because it's required for Nvidia Web Driver. The guide on Nvidia Web Driver mentions that module, and I can confirm that my system is unbootable without EmuVariableUefi-64.efi. Is there a solution to this issue? Here is the Boot section from my config: <key>Boot</key> <dict> <key>Arguments</key> <string>dart=0 darkwake=1 -shikigva -lilubeta</string> <key>CustomLogo</key> <string>Alternate</string> <key>Debug</key> <false/> <key>DefaultLoader</key> <string>boot.efi</string> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Legacy</key> <string>PBR</string> <key>Log</key> <false/> <key>Secure</key> <false/> <key>Timeout</key> <integer>-1</integer> <key>XMPDetection</key> <string>Yes</string> </dict> Link to comment Share on other sites More sharing options...
SavageAUS Posted October 21, 2017 Share Posted October 21, 2017 I can't make Clover to boot from a last booted volume, I mean the DefaultVolume/LastBootedVolume option. It almost always selects the same volume. According to the guide it's necessary to remove the EmuVariableUefi-64.efi module, but I can't remove it because it's required for Nvidia Web Driver. The guide on Nvidia Web Driver mentions that module, and I can confirm that my system is unbootable without EmuVariableUefi-64.efi. Is there a solution to this issue? Here is the Boot section from my config: <key>Boot</key> <dict> <key>Arguments</key> <string>dart=0 darkwake=1 -shikigva -lilubeta</string> <key>CustomLogo</key> <string>Alternate</string> <key>Debug</key> <false/> <key>DefaultLoader</key> <string>boot.efi</string> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Legacy</key> <string>PBR</string> <key>Log</key> <false/> <key>Secure</key> <false/> <key>Timeout</key> <integer>-1</integer> <key>XMPDetection</key> <string>Yes</string> </dict> Looks fine to me, Have you tried removing <string>boot.efi</string> O/T: You shouldn't need -lilubeta anymore if you have updated kexts. Also add system specs to signature. Link to comment Share on other sites More sharing options...
volc Posted October 21, 2017 Share Posted October 21, 2017 Hello, can someone help me? I use certain trick in windows (https://mspoweruser.com/enable-precision-touchpad-drivers-non-precision-pc/), it works fine when using default windows bootloader, but when using clover the trackpad doesn't work well and it only works a quarter part of it. Any work around for this? Thanks Edit: I forgot uploading my config. config.plist.zip Link to comment Share on other sites More sharing options...
arabesc Posted October 21, 2017 Share Posted October 21, 2017 Looks fine to me, Have you tried removing <string>boot.efi</string> It didn't help. I've removed that line and nothing has changed. I've tried to boot from the first volume and then after restart Clover selected the second volume as default. O/T: You shouldn't need -lilubeta anymore if you have updated kexts. Also add system specs to signature. Thanks. Done. Link to comment Share on other sites More sharing options...
Mike Ranger Posted October 21, 2017 Share Posted October 21, 2017 With the latest Clover Version, I am not able to boot anymore. Having updated from 4243, boot is hanging right at the start. How could I isolate the problem? It might be related with the Kernel patches I had all disabled. I have a X99 System with a 6900K CPU. Thanks, Mikel Link to comment Share on other sites More sharing options...
Regi Yassin Posted October 21, 2017 Share Posted October 21, 2017 With the latest Clover Version, I am not able to boot anymore. Having updated from 4243, boot is hanging right at the start. How could I isolate the problem? It might be related with the Kernel patches I had all disabled. I have a X99 System with a 6900K CPU. Thanks, Mikel have you tried to enable KernelXCPM in clover GUI? since r4250 "kernel XCPM patch for unsuppoted CPUs will be conditional" 1 Link to comment Share on other sites More sharing options...
telepati Posted October 21, 2017 Share Posted October 21, 2017 Guys I have a weird problem. I cant select anything on Clover Boot screen. Likes my mouse and keyboard locked. But when boot as an automatic everthings work. This is just happening on Clover Boot screen. I want to start recovery partition but keyboard space left/right arrow actually all keyboard unusable. What can I do? I attached my Clover Folder. CLOVER.zip Link to comment Share on other sites More sharing options...
Funky frank Posted October 21, 2017 Share Posted October 21, 2017 Oh {censored}, my Vaio F11 SSD has no EFI partition. How can I add it? Link to comment Share on other sites More sharing options...
Mike Ranger Posted October 21, 2017 Share Posted October 21, 2017 I enabled in the GUI the XCPM patches and now it is booting again.... many thanks to Regi Yassin. How do I define this in the config file? I think Clover Configurator does not yet support this flag, right? Regards, Mike Link to comment Share on other sites More sharing options...
apianti Posted October 21, 2017 Share Posted October 21, 2017 Oh {censored}, my Vaio F11 SSD has no EFI partition. How can I add it? The easy answer? Reformat the disk to pure GPT. The hard answer? Make sure it's GPT, then resize the first partition to be like 100MB smaller at the start, add the partition and make sure the GPT is sorted so the partitions appear in the correct order (the ESP first). Don't forget to reinstall everything. EDIT: Who edited my post? You could at least have said you edited it. Also, don't edit my posts again, don't care why. I don't need to be here and I have no problem leaving again... Guys I have a weird problem. I cant select anything on Clover Boot screen. Likes my mouse and keyboard locked. But when boot as an automatic everthings work. This is just happening on Clover Boot screen. I want to start recovery partition but keyboard space left/right arrow actually all keyboard unusable. What can I do? Did this start happening at some point or never worked? Have you tried using the keyboard and mouse drivers? Do you have some sort of legacy fixes turned on in your firmware? Also, a lot of the time, instead of using CsmVideo driver, disable CSM all together to get native resolutions. That only works if you have an EFI capable graphics though. 2 Link to comment Share on other sites More sharing options...
Recommended Posts