Jump to content
ErmaC

Clover General discussion

19,137 posts in this topic

Recommended Posts

Advertisement

any idea what this mean? it's in boot log. I am trying to figure out why NVRAM.plist is not generating

 

" UEFI with NVRAM?  no, Boot0082 not exists "

what happens if you run the script manually like this:

 

sudo /etc/rc.shutdown.d/80.save_nvram_plist.local

Share this post


Link to post
Share on other sites

Hey tluck I figured it out. the issue is clover installers RC script option to install on all bootable volumes does not seem to work on HighSierra APFS maybe not at all lol.

 I have Sierra as main, and HS as second os. when I install clover to Sierra volume so that it installs to EFI I selected RC option for all osx volumes.

it did not create the RC scripts in HS/etc. I had to install clover to second volume HighSierra then delete EFI directory on root of HS and then thats when I saw rc scripts where in HS etc folder.

any idea why selecting the option in clover installer did not work as it's supposed too?

Share this post


Link to post
Share on other sites

For Clover.

 

Your patch for Clover r4238 also works for me.  All kexts in folders /10.xx and /Other detected...

 

 

 

post-846696-0-98944700-1507257828_thumb.png

post-846696-0-26743700-1507258098_thumb.png

post-846696-0-76974100-1507257870_thumb.png

post-846696-0-36510100-1507257889_thumb.png

post-846696-0-65015300-1507257960_thumb.png

post-846696-0-95022100-1507257984_thumb.png

 

 

 

Thanks @cecekpawon!  :)

 

 

Edit

@Slice has made the necessary changes in the official repo.

 

Kext injection for Clover r4239 works as well from all folders /10.xx and /Other - preboot_r4239.log attached.

 

Thanks @Slice!

 

 

Can someone upload a zip of 4237 and help me install the files from windows?? TIA! [EDIT] or a patched 4238 and a lil help with installing the files from windows....

 

 

@og-phantom,

 

CLOVERX64.efi attached in r4238.zip file and How to Manually Install Clover in Windows  :).

preboot_r4238patched.log.zip

Clover_v2.4k_r4238_cecekpawon_patched.zip

preboot_r4239.log.zip

r4238.zip

Share this post


Link to post
Share on other sites

Well,

 

4238 hosed my install and now no folders are being injected.  Not even other.  Can someone upload a zip of 4237 and help me install the files from windows?? TIA! [EDIT] or a patched 4238 and a lil help with installing the files from windows....

Share this post


Link to post
Share on other sites

Well,

 

4238 hosed my install and now no folders are being injected.  Not even other.  Can someone upload a zip of 4237 and help me install the files from windows?? TIA! [EDIT] or a patched 4238 and a lil help with installing the files from windows....

.. using Windows U may need this? And plz note that r4237-4238 were only for testing purpose.

Share this post


Link to post
Share on other sites

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

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By AppleBytes
      OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
      As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
      Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
      Thank you for all your time, and consideration.
       
      --Chris
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
×