Slice Posted October 6, 2017 Share Posted October 6, 2017 Hi Slice, With Clover r4239, I get a boot stall when booting into 10.13.1beta (17B25c). In the boot log, "arch=" and there is an error relating to RealtekRTL8111.kext "Thinning failed" ---> hang is like when FakeSMC fails to load... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DCD84198 30:081 0:000 Use origin smbios table type 1 guid. 30:082 0:000 Preparing kexts injection for arch= from EFI\CLOVER\kexts\Other 30:082 0:000 Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext 30:165 0:082 Thinning failed: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext 30:165 0:000 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext 30:215 0:050 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext 30:244 0:028 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\HWInfo.kext 30:244 0:000 Preparing kexts injection for arch= from EFI\CLOVER\kexts\10.13 30:244 0:000 Extra kext: EFI\CLOVER\kexts\10.13\VoodooHDA.kext 30:371 0:127 Extra kext: EFI\CLOVER\kexts\10.13\AppleHDADisabler.kext No problem with r4239 and booting into 10.13 (17A405) FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DCD83198 37:575 0:000 Use origin smbios table type 1 guid. 37:576 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 37:576 0:000 Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext 37:645 0:069 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext 37:695 0:050 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext 37:724 0:028 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\HWInfo.kext 37:725 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13 37:725 0:000 Extra kext: EFI\CLOVER\kexts\10.13\VoodooHDA.kext 37:852 0:127 Extra kext: EFI\CLOVER\kexts\10.13\AppleHDADisabler.kext Also no problem with @cecekpawon's patched r4238 booting into 10.13 or 10.13.1beta 54:322 0:346 GetOSVersion: 10.13.1 (17B25c) - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DCD87198 54:355 0:000 Use origin smbios table type 1 guid. 54:356 0:000 OSVesion: 10.13.1, ShortOSVersion=10.13, uni-vers=10.13, 54:356 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 54:356 0:000 current kext name RealtekRTL8111.kext Match Other, while sysver: 10.13 54:356 0:000 Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext 54:425 0:069 current kext name FakeSMC.kext Match Other, while sysver: 10.13 54:425 0:000 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext 54:475 0:050 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext 54:504 0:028 |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\HWInfo.kext 54:504 0:000 current kext name VoodooHDA.kext Match 10.13, while sysver: 10.13 54:504 0:000 current kext name AppleHDADisabler.kext Match 10.13, while sysver: 10.13 54:504 0:000 current kext name VoodooHDA.kext Match 10.12, while sysver: 10.13 54:504 0:000 current kext name AppleHDADisabler.kext Match 10.12, while sysver: 10.13 54:504 0:000 current kext name VoodooHDA.kext Match 10.7, while sysver: 10.13 54:504 0:000 current kext name AppleHDADisabler.kext Match 10.7, while sysver: 10.13 54:504 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13 54:504 0:000 current kext name RealtekRTL8111.kext Match Other, while sysver: 10.13 54:504 0:000 current kext name FakeSMC.kext Match Other, while sysver: 10.13 54:504 0:000 current kext name VoodooHDA.kext Match 10.13, while sysver: 10.13 54:504 0:000 Disabled kext: EFI\CLOVER\kexts\10.13\VoodooHDA.kext 54:504 0:000 current kext name AppleHDADisabler.kext Match 10.13, while sysver: 10.13 54:504 0:000 Disabled kext: EFI\CLOVER\kexts\10.13\AppleHDADisabler.kext 54:504 0:000 current kext name VoodooHDA.kext Match 10.12, while sysver: 10.13 54:504 0:000 current kext name AppleHDADisabler.kext Match 10.12, while sysver: 10.13 54:504 0:000 current kext name VoodooHDA.kext Match 10.7, while sysver: 10.13 54:504 0:000 current kext name AppleHDADisabler.kext Match 10.7, while sysver: 10.13 It is impossible for unknown arch=. There is Clover sources MsgLog("Preparing kexts injection for arch=%s from %s\n", (archCpuType==CPU_TYPE_X86_64)?L"x86_64":(archCpuType==CPU_TYPE_I386)?L"i386":L"", SrcDir); I look all code and found that #if defined(MDE_CPU_X64) cpu_type_t archCpuType=CPU_TYPE_X86_64; #else cpu_type_t archCpuType=CPU_TYPE_I386; #endif I may propose that your compilation is buggy. What is your toolchain? 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 6, 2017 Share Posted October 6, 2017 Hi Slice, Another test: Clover r4241 on HDD macOS 10.13.1 with HDD Sierra connected. When I boot from macOS 10.13.1----->No injection (10.13 folder only). r4241. Kext management don't see empty folder (10.6, 10.7, etc) When I boot from macOS 10.13.1----->Ok (10.13 folder only), r4233. Kext management see all empty folder (10.6, 10.7, etc) preboot_Clover_r4241_10.13.1_Beta.log.zip Link to comment Share on other sites More sharing options...
syscl Posted October 6, 2017 Share Posted October 6, 2017 @syscl - any more thoughts on the Haswell-E issue? Please give me a PM... syscl 1 Link to comment Share on other sites More sharing options...
Slice Posted October 6, 2017 Share Posted October 6, 2017 Could be possible to add again support for this reboot fix patch in latest clover? It was working in 4184 release..in latest it is no more working: <dict> <key>Comment</key> <string>reboot fix</string> <key>Disabled</key> <false/> <key>Find</key> <data> vgsAAABd6QgAAAAPH4QAAAAAAFVIieVBVw== </data> <key>Replace</key> <data> vgsAAABd6QgAAAAPH4QAAAAAAMNIieVBVw== </data> </dict> find be0b0000 005de908 0000000f 1f84000000000055 4889e541 57 replace be0b0000 005de908 0000000f 1f840000000000c3 4889e541 57 Thank you Commit 4185 already reverted to the state of 4184. Check latest Clover and provide debug.log. Link to comment Share on other sites More sharing options...
Badruzeus Posted October 6, 2017 Share Posted October 6, 2017 Thanks @Slice, Legacy r4241 works well under 10.13.1 (17B25c). Already tested placing kexts on 10.13, or Other only.. both work and even got faster boot time (not sure what have U done, I mean for my mach). #EDIT: The log file below is with 10.6 upto 10.13 & Other folders available on /kexts (but as prev, I'm only using 10.11 & 10.13 for kext inject) bootlog.log_a43sj_r4241.txt.zip Link to comment Share on other sites More sharing options...
chris1111 Posted October 6, 2017 Share Posted October 6, 2017 Clover 4221 10.6/10.7/10.12/10.13 No issue kext inject 1 Link to comment Share on other sites More sharing options...
Slice Posted October 6, 2017 Share Posted October 6, 2017 Sorry for my bad english I forgot to say that my Sierra HDD was connected. After select USB by F8 for booting, I try r4239 with USB installer. I don't understand your answer. what is the correct procedure in this case for testing? I just see no issues in your observations. You started 10.12 and don't see 10.13. It is OK (All Correct). Hi Slice, Another test: Clover r4241 on HDD macOS 10.13.1 with HDD Sierra connected. When I boot from macOS 10.13.1----->No injection (10.13 folder only). r4241. Kext management don't see empty folder (10.6, 10.7, etc) When I boot from macOS 10.13.1----->Ok (10.13 folder only), r4233. Kext management see all empty folder (10.6, 10.7, etc) This is a difference between old and new Clover. You need no to see 10.6 folder if you boot 10.13.1. 1 Link to comment Share on other sites More sharing options...
syscl Posted October 6, 2017 Share Posted October 6, 2017 I just see no issues in your observations. You started 10.12 and don't see 10.13. It is OK (All Correct). This is a difference between old and new Clover. You need no to see 10.6 folder if you boot 10.13.1. Slice, why no init InjectKextList for all folder then list kext for current system, then it will never fail inject kext even if user see 10.6 then boot 10.13? syscl 1 Link to comment Share on other sites More sharing options...
fusion71au Posted October 6, 2017 Share Posted October 6, 2017 When I boot from macOS 10.13.1----->No injection (10.13 folder only). r4241. Kext management don't see empty folder (10.6, 10.7, etc) @Matgen84, From your boot log 90:535 0:026 GetOSVersion: 10.13.1 (17B25c) 90:842 0:000 Beginning FSInjection 90:842 0:000 skipping kext injection (not requested) Check your config.plist/SystemParameters/InjectKexts set to Yes or Detect? <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> </dict> Hmmb, sounds strange. I was also using r4239 under 10.13.1 (17B25C) but got no problem with Slice's FakeSMC (v3.5.0) & RealtekRTL8111 (v2.2.1). Is there any unresolved patch when U were compiling r4239 binary using buildclover script? (I don't think so, though) (I attached my compiled r4239 below, thanks). It is impossible for unknown arch=. I may propose that your compilation is buggy. What is your toolchain? I think I compiled r4239 (XCODE 8.3.3 in 10.13, toolchain setting XCODE8) forgetting to revert @cecekpawon's diff patch from r4238... 4:038 0:000 Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13 | XCODE: 8.3.3] After deleting & re-downloading Clover r4241 from svn, everything OK again. Clover r4241 boots successfully into 10.13.1beta and kexts detected in /10.xx & /Other. Compiled with XCODE 8.2.1 in 10.11.6, toolchain setting XCODE8 ---> boots fine into 10.13.1beta, 10.13, 10.12.6, 10.7 Compiled with XCODE 9.0 in 10.13.1beta, toolchain setting XCODE8 ---> boots fine into 10.13.1beta, 10.13, 10.12.6, 10.7 Thanks everyone for helping with troubleshooting . Boot logs.zip Clover_v2.4k_r4241.zip Link to comment Share on other sites More sharing options...
telepati Posted October 6, 2017 Share Posted October 6, 2017 Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error; But when I remove the EmuVariableUefi-64.efi I can update without any problem. Link to comment Share on other sites More sharing options...
SavageAUS Posted October 7, 2017 Share Posted October 7, 2017 Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error; error-install.png But when I remove the EmuVariableUefi-64.efi I can update without any problem. I dont even have EmuVariableUEFI on my laptop and im getting that error. Link to comment Share on other sites More sharing options...
cyrhex Posted October 7, 2017 Share Posted October 7, 2017 @slice can i have ur fakesmc 3.5 coz other user says using this version of fakesmc bypass the osinstall.mpkg damage error installing high sierra using clover uefi,,TIA Link to comment Share on other sites More sharing options...
bronxteck Posted October 7, 2017 Share Posted October 7, 2017 the link is in his signature HWsensors3 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 7, 2017 Share Posted October 7, 2017 @Matgen84, From your boot log 90:535 0:026 GetOSVersion: 10.13.1 (17B25c) 90:842 0:000 Beginning FSInjection 90:842 0:000 skipping kext injection (not requested) Check your config.plist/SystemParameters/InjectKexts set to Yes or Detect? I install r4241 in update mode. Config.plist work well if I downgrade to r4223 with EFI Backups, for example. I just see no issues in your observations. You started 10.12 and don't see 10.13. It is OK (All Correct). This is Test r4239 from USB pendrive with HDD Sierra connected: I started 10.13. GetOSversion detected 10.12. Only Other folder in pendrive, boot High Sierra. Sorry for my english. Link to comment Share on other sites More sharing options...
Slice Posted October 7, 2017 Share Posted October 7, 2017 Slice, why no init InjectKextList for all folder then list kext for current system, then it will never fail inject kext even if user see 10.6 then boot 10.13? syscl You should realise the process of menu creation and running. There are two different process. If we set Init InjectKextList into menu creation then it will be added with every menu entries that we already saw as double injection. I can set the init conditionally if not inited yet. Link to comment Share on other sites More sharing options...
Slice Posted October 7, 2017 Share Posted October 7, 2017 For those who have a problem with kext injection please test my version CLOVERX64.efi-4243.zip 2 Link to comment Share on other sites More sharing options...
azlvda Posted October 7, 2017 Share Posted October 7, 2017 since 4239 folder Other case-sentitive wont boot with lowercase o letter Link to comment Share on other sites More sharing options...
Badruzeus Posted October 7, 2017 Share Posted October 7, 2017 For those who have a problem with kext injection please test my version CLOVERX64.efi-4243.zip Ah, forgot to mention that my prev tests were using "InjectKexts=Yes", now with "...=Detect" ur r4243 boots 10.13.1 (17B25c) fine from "/kexts/10.13" folder, also same result with manually buildclover script for r4243. And how could we figure out that gotta "kext injection problem"..? Thanks. bootlog.log_r4243_slice.txt.zip bootlog.log_r4243_buildclover.txt.zip Link to comment Share on other sites More sharing options...
Matgen84 Posted October 7, 2017 Share Posted October 7, 2017 For those who have a problem with kext injection please test my version CLOVERX64.efi-4243.zip Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.12 when I boot from USB pen drive (10.13 only) and HDD Sierra connected: Kextd stall on AppleACPICPU and black screen Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.13.1 when I boot from HDD High Sierra (10.13 only) and HDD Sierra connected. Kextd stall on AppleACPICPU Commits r4243 HDD 10.13.1 alone (10.13 folder only): with or without CloverX64.efi-4243: No Injection -----> "Thinning failed" error. Here, new kext management don't work with 10.13 folder only I don't understand why these issues? preboot_Clover_r4243_USB.log.zip preboot_Cloverr4243_HDD_alone.log.zip Link to comment Share on other sites More sharing options...
artur_pt Posted October 7, 2017 Share Posted October 7, 2017 hello Slice for me is working good boot.log.zip thanks Link to comment Share on other sites More sharing options...
Slice Posted October 7, 2017 Share Posted October 7, 2017 Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.12 when I boot from USB pen drive (10.13 only) and HDD Sierra connected: Kextd stall on AppleACPICPU and black screen Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.13.1 when I boot from HDD High Sierra connected. Kextd stall on AppleACPICPU Commits r4243 HDD 10.13.1 alone (10.13 folder only): with CloverX64.efi-4243: No Injection -----> "Thinning failed" error. I don't test without CloverX64.efi-4243 I don't understand why these issues? Both logs with NOT MY clover. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 7, 2017 Share Posted October 7, 2017 Both logs with NOT MY clover. Forgot when I have edited my previous post. Can you look it. Please New attached files here with your cloverX64. preboot_Clover_r4243_HDD_newCloverX64.log.zip Link to comment Share on other sites More sharing options...
Slice Posted October 7, 2017 Share Posted October 7, 2017 Forgot when I have edited my previous post. Can you look it. Please New attached files here with your cloverX64. No, it is not my Clover. Link to comment Share on other sites More sharing options...
cecekpawon Posted October 7, 2017 Share Posted October 7, 2017 ___Matgen84___ mv CLOVERX64.efi to \EFI\BOOT\BOOTX64.efi ? Link to comment Share on other sites More sharing options...
phi777 Posted October 7, 2017 Share Posted October 7, 2017 I've got a dumb question, but could this be a clover problem? https://github.com/Piker-Alpha/HandyScripts/issues/7 EDIT: already fixed Link to comment Share on other sites More sharing options...
Recommended Posts