Jump to content
ErmaC

Clover General discussion

25,349 posts in this topic

Recommended Posts

Thanks @cecekpawon & @Slice for r4239; now it works under 10.13.1:

 

 

EOsemH9.jpg

 

Do you have any kext in Other folder?

57:140  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
57:140  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13

Share this post


Link to post
Share on other sites
Advertisement

Do you have any kext in Other folder?

57:140  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
57:140  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13

No, I don't. Only inside 10.11 & 10.13. Another folders begun from 10.6 I leave there, I mean w/o removing them my 10.11 kexts also well injected to boot El Capitan. Thanks.

Share this post


Link to post
Share on other sites

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

 

 

Boot Logs.zip

Share this post


Link to post
Share on other sites

^ Yup. r4239 and 10.13.1 results in AppleACPICPU time-out here. All 10.13 kexts in 10.13 folder. Bootlog coming right up.

 

Edit: I get the "Thinning failed" message on FakeSMC.kext, IntelmausiEthernet.kext, AppleALC.kext and Lilu.kext (so, all kexts except USB_Injector.kext)

30:533  0:000  Preparing kexts injection for arch= from EFI\CLOVER\kexts\Other
30:533  0:000  Preparing kexts injection for arch= from EFI\CLOVER\kexts\10.13
30:533  0:000  Extra kext: EFI\CLOVER\kexts\10.13\Lilu.kext
30:535  0:002  Thinning failed: EFI\CLOVER\kexts\10.13\Lilu.kext
30:535  0:000  Extra kext: EFI\CLOVER\kexts\10.13\AppleALC.kext
30:538  0:003  Thinning failed: EFI\CLOVER\kexts\10.13\AppleALC.kext
30:538  0:000    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
30:649  0:111  Extra kext: EFI\CLOVER\kexts\10.13\FakeSMC.kext
30:663  0:013  Thinning failed: EFI\CLOVER\kexts\10.13\FakeSMC.kext
30:663  0:000  Extra kext: EFI\CLOVER\kexts\10.13\USB_Injector.kext
30:668  0:005  Extra kext: EFI\CLOVER\kexts\10.13\IntelMausiEthernet.kext
30:675  0:006  Thinning failed: EFI\CLOVER\kexts\10.13\IntelMausiEthernet.kext
30:675  0:000  Custom boot screen not used because entry has unset use graphics
30:675  0:000  Closing log

preboot.log.zip

Share this post


Link to post
Share on other sites

Hi,

 

r4239 and 10.13 only results in AppleACPICPU boot stall here (Kext stall 240s, 3 times) and black screen: no injection in pre-bootlog.

 

r4239 and 10.13 + Other: only Other injection work and boot fine  :) 

preboot_Clover_r4239_10-13+Other.log.zip

preboot_Clovder_r4239_10-13_Only.log.zip

Share this post


Link to post
Share on other sites

....

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...

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).

Or did U mean the problems only occurred if they placed on "Other" folder to boot hSierra? Since I've placed them on "10.13" folder, using Legacy.. that maybe the main different here.

 

 

 

2:707  0:000  Now is 6.10.2017,  6:29:43 (GMT)
2:707  0:000  Starting Clover revision: 4239 on CLOVER EFI
2:707  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.11.6 | XCODE: 8.2]
...... .....  ...

56:644  0:000  === [ StartLoader ] =======================================
56:644  0:000  Finally: ExternalClock=24MHz BusSpeed=99773kHz CPUFreq=2195MHz PIS: hw.busfrequency=96000000Hz
56:644  0:000  Loading boot.efi  status=Success
57:085  0:441  GetOSVersion: 10.13.1 (17B25c)
...... .....  ...

57:119  0:000  Beginning FSInjection
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 1EC14E18
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 1EC14E18
57:140  0:020  Use origin smbios table type 1 guid.
57:140  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
57:140  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
57:140  0:000  Extra kext: EFI\CLOVER\kexts\10.13\RealtekRTL8111.kext
57:163  0:022  Extra kext: EFI\CLOVER\kexts\10.13\ACPIBatteryManager.kext
57:176  0:012  Extra kext: EFI\CLOVER\kexts\10.13\CalDigitFastIO.kext
57:190  0:013  Extra kext: EFI\CLOVER\kexts\10.13\ApplePS2SmartTouchPad.kext
57:225  0:035    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext
57:235  0:010    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext
57:240  0:004  Extra kext: EFI\CLOVER\kexts\10.13\Lilu.kext
57:259  0:018  Extra kext: EFI\CLOVER\kexts\10.13\AsusNBFnKeys.kext
57:271  0:011  Extra kext: EFI\CLOVER\kexts\10.13\AppleALC.kext
57:306  0:034    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
57:549  0:243  Extra kext: EFI\CLOVER\kexts\10.13\CalDigitUSBxHCI.kext
57:589  0:040  Extra kext: EFI\CLOVER\kexts\10.13\AsusACPIBackLightPanel.kext
57:603  0:013  Extra kext: EFI\CLOVER\kexts\10.13\FakeSMC.kext
57:632  0:029  SetStartupDiskVolume:
57:632  0:000    * Volume: 'macOS High Sierra'
...... .....  ...

 

 

 

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).

r4239_boot6.zip

Share this post


Link to post
Share on other sites

@Badruzeus: Strange. Yours is working. I guess something indeed messed up during compiling (XCODE9).
 
Note: When booting yours, Clover said something about the prelinked text (+- 4 lines). It went too fast to actually read what it said and the logs doesn't show anything related to it.

14:251  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
14:252  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
14:252  0:000  Extra kext: EFI\CLOVER\kexts\10.13\Lilu.kext
14:254  0:002  Extra kext: EFI\CLOVER\kexts\10.13\AppleALC.kext
14:258  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
14:368  0:110  Extra kext: EFI\CLOVER\kexts\10.13\FakeSMC.kext
14:382  0:013  Extra kext: EFI\CLOVER\kexts\10.13\USB_Injector.kext
14:388  0:006  Extra kext: EFI\CLOVER\kexts\10.13\IntelMausiEthernet.kext
14:397  0:008  Custom boot screen not used because entry has unset use graphics
14:397  0:000  Closing log

Edit:

 

Here it is:

KernelRelocBase = 0
Found PRELINK_TEXT, 64bit
at 600D00: vmaddr = 0xFFFFFF0001096000, vmsize = 0x53F9000
PrelinkTextLoadCmdAddr = 0x600D00, PrelinkTextAddr = 0x1096000. PrelinkTextSize = 0x53F9000
Found PRELINK_INFO, 64bit
vmaddr = 0x0648F000
vmsize = 0x00295000
__info found at 6010D8: addr = 0xFFFFFF000648F000, size = 0x2947D2
PrelinkInfoLoadCmdAddr = 0x6010D8, PrelinkInfoAddr = 0x648F000, PrelinkInfoSize = 0x2947D2

Share this post


Link to post
Share on other sites
34:185  0:049  GetOSVersion: 10.12

 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? 

Share this post


Link to post
Share on other sites

 

@Badruzeus: Strange. Yours is working. I guess something indeed messed up during compiling (XCODE9).

 

Note: When booting yours, Clover said something about the prelinked text (+- 4 lines). It went too fast to actually read what it said and the logs doesn't show anything related to it.

....

Oops, my bad... I forgot to rolled-back my previous change on /rEFIt_UEFI/Platform/kernel_patcher.c:

My compiled r4239 above was using..

#define KERNEL_DEBUG 2

instead of...

#define KERNEL_DEBUG 0

I think, that was the caused. Sorry, need to recompile it again (with XCode 8.2 under 10.11.6). Thanks..

Share this post


Link to post
Share on other sites

 

Maybe you get mixed up with my prev patches?

svn revert -R rEFIt_UEFI/
svn up

Yeah I thought the same. I thought tc would be okay, but apparently not  :P

I recompiled and it's working now. Thanks!

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

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

Share this post


Link to post
Share on other sites

Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error;

 

post-803029-0-52147000-1507334145_thumb.png

 

But when I remove the EmuVariableUefi-64.efi I can update without any problem. 

Share this post


Link to post
Share on other sites

Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error;

 

attachicon.giferror-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.

Share this post


Link to post
Share on other sites

  • Similar Content

    • By 5T33Z0
      Background: Since the Pre-Release of Clover v5123, OpenCore Momory Fixes have been integrated into Clover in the form of OpenRuntime.efi. It replaces previous AptioMemory Fixes. Since v5126 AptioMemoryFixes are obsolete and no longer supported, so an upgrade to v5126 is mandatory in order to be able to install and boot macOS BigSur with Clover.
       
      This guide is for everyone trying to update to the latest Clover version or having issues while updating from previous versions, so they can install and run BigSur on their Machines. While updating to the latest iteration of Clover, there are several obstacles one can come across along the way. This guide is here to assist users trying to make the switch from the "old" Clover version with AptioMemory Fixes to the new one with OpenRuntime and Quirks Settings in CloverConfigurator.
       
      Problem: If you update your existing Clover installation by either installing the clover.pkg file or manually updating it the way you used to this will most likely result in an inoperable bootlader due to missing boot parameters.
       
      Approach: In order to avoid the dilemma of your system not wanting to boot, you have to know that the following files are obsolete and are no longer necessary, so they should eiither be disbabled/deleted when updating Clover from a built prior to v 5123 or omitted altogether when setting up a new EFI Folder:
       
      AptioMemoryFixes: AptioMemoryFix.efi, OsxAptioFix3Drv.efi, OsxAptioFixDrv.efi and everyhing else containing "memoryfix". Unnecessary Drivers (for UEFI-based Systems): DataHubDxe.efi – enables DataHub Protocol Support if it is missing from the BIOS. Modern UEFI BIOSes support this. So it's probably only necessary for Legacy Systems. FSInject.efi – For Kext-Injecttion. But pretty much obsolete since it's fully integrated in Clover nowadays. Might be necessary for Legacy Systems, though. SMCHelper.efi – Necessary when using FakeSMC.kext and ONLY FakeSMC. If you use it in combination with VirtualSMC.efi, it leads to an instant Kernel Panics. So, in other words: when using VirtualSMC – which is higly recommended over FakeSMC – DON'T use SMCHelper, use it in conjunction with VirtulSMC.efi (although unnecessary in most cases). EmuVariableUefi.efi – necessary for emulating NVRAM, if NVRAM is either not available (legacy systems) or working incorrectly. OcQuirks.efi and OcQuirks.plist – delete if present. OcQuirks is a relict from earlier attempts to include OpenCore Booter Quirks into Clover up until version 5122. Incompatible Kexts – wherever possible, you should use the latest available kexts provided by acidanthera (one of the devs behind OpenCore). Because incompatible Kexts are a source for Kernel Panics. I had an issue with my Laptop where VoodooPS2Controller.kext would cause a kernel Panic when used alongside VoodooPS2Mouse.kext, VoodooPS2Trackpad.kext and VoodooPS2Controller.kext. At the time I updated clover from 5122 to 5123, I didn't know that these 3 kexts are now includes as plugins inside of VoodooPS2Controller, so having them twice would cause a panic.

      In general, having Kexts wich have depedencies to oher kexts can cause a KernelPanic if not loaded in the correct order. In OpenCore, you can and have to set up the correct loading order of kexts manually by yourself, but in Clover only a few essential kexts like Lilu and Fake/VirtualSMC are hard-coded in, so they are always loaded first. It took me a while to figure this out. So when you update Clover and you are using lot of Kexts (usually on Laptops), try to update all Kexts first using Kext-Updater which is incredibly useful tool to download all sorts of bootloader-related files, have a look inside of them so see if they include more kexts as plugins and make sure nothing is present twice – HID, Wifi and Bluetooth kexts come to mind here. If you get panics you can not isolate, just move all unnecessary kexts to the "off" folder to temporarily to work around the issue by starting with a minimal set up to get the system running. Then put the disabled kexts back one by one to find the culprit for the panic.  
      Updating your EFI
       
      Prepare an USB Stick. Format it to FAT32 (MBR). We'll use it for testing our updated EFI Folder first, before copying it to the ESP on the HDD. Download the latest Clover Release  as a .zip archive for a manual update (currently "CloverV2-5126.zip"): https://github.com/CloverHackyColor/CloverBootloader/releases Extract the .zip. We'll create our EFI based on the one insides of it. Have a look at the "EFI > Clover > drivers > off > UEFI" Folder – you find the following Files: Copy the following files over to EFI > Clover > drivers > UEFI: ApfsDriverLoader.efi, VBoxHfs.efi and OpenRuntime.efi Now we have a minimal set of Drivers which looks like shown below. The files tagged in gray are in the drivers Folder by defautl and are most likely unnecessary on UEFI-based systems. As mentioned earlier, SMCHelper MUST be deleted when using VirualSMC.kext! I would turn of each of the gray drivers one by one and chick if the system still boots without them.
      Next, copy over your kexts (updated to the latest available version, of course), your ACPI > patched folder and your config.plist form your existing EFI Folder Open CloverConfigurator and update it to the latest Version. It should now include a new section at the bottom called Quirks, as mentioned earlier Now open your config.plist you copied over from your working EFI and click on "Quirks". It should look like this (without the descriptions of course):
      Head over to the OpenCore Install Guide and pick the guide for your CPU Family and Platform. Jump to the "Booter" Section. It contains all required Booter Quirks tinted green in the screenshot. Make sure to unfold the "more in-depth info" box to see what they do. Find the options for your system and tick them away in Clover Configurator. Next, jump to the "Kernel" section of Dortania's guide and copy over the settings from "Quirks" and "Scheme". Again, make sure to unfold the "more in-depth" section to find all necessary settings. NOTE: some of the settings Located in "Kernel > Quirks" have different names and are located in the "Kernel and Kext Patches" section of Clover Configurator. These include:

      In most cases you have these set up correctly already, otherwise your system wouldn't have started before. But it's good to double check if you have settings enabled which may be unnecessary. Once you've ticked all the necessary quirks, save your configuration, copy the new EFI Folder to the root of your USB Flash Drive and try booting from it. If everything was set up correctly, the system should boot as expected. If it does boot, you can mount the ESP partition of your hard drive, backup your EFI Folder, delete it and put in the one from your USB Flash drive to make the changes permanent.  
      TROUBLESHOOTING: If you get Kernel Panics take a note of them and head over to the OpenCore Troubleshooting Guide and have a look at the "OpenCore Boot issues" and "Kernelspace Issues" sections to find your error message and possible fixes to resolve it. Another great resource to check if your Clover config is set-up correctly in general (excluding Quirks) is the Hackintosh Vanilla Desktop Guide For more info about how OpenCore differs from clover and see which settings, drivers and features are compatible, check out the Clover Conversion Guide.
       
      Good luck!
       
      PS: If you run into trouble after following this guide you can upload your config.plist and I can have a look at the quirks.
      PSS: When running BigSur, you need to remove the PreBoot Volume from the "Hide" Section of the GUI because if I understand correctly, BigSur requires booting from it.
      PSSS: if your system boots correctly you can upload a screenshot with your quirks with additional Info like your Board and CPU which might be helpful for other users.
       
    • By MaLd0n
      iMac20,1 Hackintosh 
      A good build for professional audio and video processing.
      We love silence and Cooler SCYTHE Ninja 5 is mandatory in this case!
      A very custom DSDT for best experience under macOS. Removed all unused devices, injected all Apple devices, essentials, cosmetics, real improvements.
       
       

       
       
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
       
      -Bios/UEFI Settings-
      CSM Support - Disabled
      Internal Graphics - Enable
      -Thunderbolt Configuration-
      Security Level - No Security
      GPIO3 Force Pwr - Enabled
       
      -Hardware-
      Mobo - Ga Z490 Vision D
      https://tinyurl.com/y4gajha4

      Processor - i7 or i9 10th Intel
      https://tinyurl.com/y6jlskwz

      GPU - RX 580, 590, VEGA 56, VEGA64, 5700XT or RADEON VII
      https://tinyurl.com/y4mxc7t6

      Cooler - SCYTHE Ninja 5 
      https://tinyurl.com/yyrbx5lf

      NVME - WD Black SN750 NVMe SSD
      https://tinyurl.com/vnq46yr
       
      -EFI folders- 
      Clover - https://tinyurl.com/yxzftuyr
      OpenCore - https://tinyurl.com/y3lt8t9l
      Just paste EFI folder into EFI partition, reboot and extract one SendMe. Post this dump here for full ACPI solution!
      Download RunMe.app dumper
       
      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      -DSDT- Complete Solution
      DSDT.Z490 VISION D MaLd0n.zip
       
      -SSDT- Not complete solution
      SSDT-OLARILA.aml.zip
       
      -DSDT Patches-
       
       
       
      -USB Solution-
      USB SOLUTION.zip
       
       
       
       
      -Boot Time with Clover or Opencore is same-
       
      -Screenshots-































       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thx to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
    • By VortexisTV
      So I've been trying to update to Big Sur from Catalina but I get stuck at the +++ message at the beginning. I made sure I have all my kexts and drivers updated. Updating to Clover revision 5126 would only get me kernel panics. Am I doing something wrong? Any response would be greatly appreciated. EFI
       
      ASUS Zenbook UX331FN
      Intel Core i5-8265U
      Intel UHD 620
      Clover 5120
       

    • By amadeusex
      Hey guys - how are you holding up?
      Because of a lot of free time and after abandoning the idea to get Catalina installed i tried to run Mojave on my beloved z820v2.
      Everything went fine except power management.
      I've used @WoodCabin's EFI folders to install and later on run Mojave (14.6).
      Here's a glimpse of what i get as soon as i put the patched (from 10.13 as suggested on stinga's X79 power management topic) AppleIntelCPUPowerManagement.kext into S/L/E
       

       
      I tried also @stinga11 s kext patches for Mojave but still either PM's not working or KP.
      Here's my my EFI folder

      @antonio.clb
    • By BALDY_MAN
      Z490 GigabyteMaster.Config plist Template
       
      Hi all I have put together a  config.plist template to help you get started. Setting up your z490 Motherboard
      It is a template for you to copy the settings to your OWN
      Config.plist
      Open it with a plist editor
      And copy the same settings to your OWN Plist
      You will need to add you own motherboard  serail numbers
      I Have  put it so in the template (P.Y.O) Meaning put your own)
      Z490Gigabyte.Master. Config.plistTemperate.zipOpenCore. SanityCheck Screen Shots
      Attached  OpenCore Sanity screen Shots
       
×