Jump to content
ErmaC

Clover General discussion

19,137 posts in this topic

Recommended Posts

Ok what version works for 10.12 AND 10.13 without lot of extra configuration (10.12.6 currently works nicely)?

 

PS Cannot find the recent nvidia web drivers thread, search is disabled :P  So I have a GT1050, should I install the 10.13 webdriver just before the update? Will it work with 1050 on High Sierra?

Share this post


Link to post
Share on other sites
Advertisement

@fusion71au, @Badruzeus, @chris1111 and others

Make please a preboot.log, if compile Clover 4237 with

#define KEXT_INJECT_DEBUG 2

in kext_inject.c, line 3

 

Do you have 10.13.1 or 10.13b?

Share this post


Link to post
Share on other sites

@fusion71au, @Badruzeus, @chris1111 and others

Make please a preboot.log, if compile Clover 4237 with

#define KEXT_INJECT_DEBUG 2

in kext_inject.c, line 3

 

Do you have 10.13.1 or 10.13b?

10.13 not working

10.12 works

here the log 4237 with define KEXT_INJECT_DEBUG 2

10.13 Finale release

 

EDIT1** 1

Dont know if that help attaching log 10.13 Final Release Boot 4222 Working All OS

Clover bdmesg Log.txt.zip

Clover bdmesg Log-4222.txt.zip

Share this post


Link to post
Share on other sites

systemcl - If it's any help the system's I've tested are two 5930ks and a 5960x, all with ASUS mobos.  I'm happy to help test any patches or provide debug information!

Share this post


Link to post
Share on other sites

@fusion71au, @Badruzeus, @chris1111 and others

Make please a preboot.log, if compile Clover 4237 with

#define KEXT_INJECT_DEBUG 2

in kext_inject.c, line 3

 

Do you have 10.13.1 or 10.13b?

1. Preboot attached using Legacy r4237 with #define KEXT_INJECT_DEBUG 2 in inject_kext.c | Line 3.

2. I have 10.13.1 Beta (17B25C). Thanks.

preboot_a43sj_r4237_debug.log.zip

Share this post


Link to post
Share on other sites

Is anyone else having issues with battery indicator in latest clover revisions? 423x > i can't remember which one it started acting up.

Upon booting it just wont show up again, was working 100% fine. I have to unplug and plug then it will show up but it doesnt automatically update either, like if i unplug charger, the indicator still says its charging.

@Sherlocks ?

If I still remember; I got it to works under 10.13 using r4223 with:

1. Kozlek's FakeSMC v6.26.1440 and Rehabman's ACPIBatteryManager v1.81.3 / or 1.81.4 (with patched DSDT for battery)

2. Slice's FakeSMC v3.5 and VoodooBattery.kext (w/o patched DSDT for battery)

"BUT.." for point 1; it just works for a moment after I disassembled my mach. It then disappeared again after I rebooted my mach, IDK why.

Point. 2, it shows the indicator but since my battery device was failed; it spamming me with "Battery 0 empty capacity.. (or similar message)" on verbose logs, and it makes my boot time became longer. Sorry, I should to gave report earlier but on that time; I got trouble accessing the forum. My bad, now I only has 10.13.1 Beta and not testing point 2 yet, but just with point 1 it doesn't work here. Thanks.

Share this post


Link to post
Share on other sites

1. Preboot attached using Legacy r4237 with #define KEXT_INJECT_DEBUG 2 in inject_kext.c | Line 3.

2. I have 10.13.1 Beta (17B25C). Thanks.

The log is good

56:983  0:457  GetOSVersion: 10.11.6 (15G17013)

Try to change #elsif to #elif

Thanks for notice!

10.13 not working

10.12 works

here the log 4237 with define KEXT_INJECT_DEBUG 2

10.13 Finale release

 

EDIT1** 1

Dont know if that help attaching log 10.13 Final Release Boot 4222 Working All OS

Chris, I want to see log containing an error. Not your logs with full success.

Anyone can reproduce the issue with 10.13 folder?

Share this post


Link to post
Share on other sites

The log is good

56:983  0:457  GetOSVersion: 10.11.6 (15G17013)

Yes, just bcoz I was unable to boot to 10.13.1 using installed kexts on 10.13 folder, but Other folder did.

Share this post


Link to post
Share on other sites

The log is good

56:983  0:457  GetOSVersion: 10.11.6 (15G17013)

Thanks for notice!

Chris, I want to see log containing an error. Not your logs with full success.

Anyone can reproduce the issue with 10.13 folder?

How can log file with no boot

Boot stop  Apple ACPICPU , MCHC

 

EDIT**

Ok Slice I have log

I boot  in the 10.13 and its stop at the same point

I shutdown PC 

Boot to Sierra 10.12  ok

go to my High Sierra SSD / Library / Log / CloverEFI

here the 10.13 High Sierra  4237 log attaching

boot-r4237-2017-Bad boot.log.zip

Share this post


Link to post
Share on other sites

Press F2 in CloverGUI.

Boot OS.

If crash then reboot and see /EFI/CLOVER/misc/preboot.log

Notice here from @chris1111

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

Kext does not add into InjectKextList for Other and 10.13.

 

Edited: what I guess is that you have 10.12 and 10.13, and you disable 10.12's kext but boot 10.13, so kext was not injected for 10.13 folder and Other.

Share this post


Link to post
Share on other sites

Notice here from @chris1111

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

Kext does not add into InjectKextList for Other and 10.13.

 

Edited: what I guess is that you have 10.12 and 10.13, and you disable 10.12's kext but boot 10.13, so kext was not injected for 10.13 folder and Other.

I have nothing to deactivate, I boot 10.13

 

I have kext in 10.13, 10.12. 10.7, 10.6
No kext in Other  :)
 
Boot 10.12 is ok, this is the only OS working
if I put my kext in Other its work for 10.12 and 10.13

Share this post


Link to post
Share on other sites

 

I have nothing to deactivate, I boot 10.13

 

I have kext in 10.13, 10.12. 10.7, 10.6
No kext in Other  :)
 
Boot 10.12 is ok, this is the only OS working
if I put my kext in Other its work for 10.12 and 10.13

 

Hi, what's your default OS when clover GUI start? 10.12 or 10.13?

 

Edited: I have an idea and will let you know once I finish.

Share this post


Link to post
Share on other sites

Hi, what's your default OS when clover GUI start? 10.12 or 10.13?

 

Edited: I have an idea and will let you know once I finish.

10.13  :lol:

Share this post


Link to post
Share on other sites

r4237 works for me.

10.13.1 beta as only OS (besides Windows 10 but that's irrelevant)

FakeSMC in 10.13, other kexts in Other.

10:562  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
10:562  0:000  Extra kext: EFI\CLOVER\kexts\Other\USB_Injector.kext
10:564  0:001  Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext
10:566  0:002  Extra kext: EFI\CLOVER\kexts\Other\IntelMausiEthernet.kext
10:567  0:001  Extra kext: EFI\CLOVER\kexts\Other\AppleALC.kext
10:571  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\Other\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
10:683  0:112  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
10:683  0:000  Extra kext: EFI\CLOVER\kexts\10.13\FakeSMC.kext
10:697  0:013  Custom boot screen not used because entry has unset use graphics
10:697  0:000  Closing log

Share this post


Link to post
Share on other sites

 

r4237 works for me.

10.13.1 beta as only OS (besides Windows 10 but that's irrelevant)

FakeSMC in 10.13, other kexts in Other.

10:562  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
10:562  0:000  Extra kext: EFI\CLOVER\kexts\Other\USB_Injector.kext
10:564  0:001  Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext
10:566  0:002  Extra kext: EFI\CLOVER\kexts\Other\IntelMausiEthernet.kext
10:567  0:001  Extra kext: EFI\CLOVER\kexts\Other\AppleALC.kext
10:571  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\Other\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
10:683  0:112  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
10:683  0:000  Extra kext: EFI\CLOVER\kexts\10.13\FakeSMC.kext
10:697  0:013  Custom boot screen not used because entry has unset use graphics
10:697  0:000  Closing log

 for UEFI or Legacy

 

Edit **

UEFI  works in my Lapy

Share this post


Link to post
Share on other sites

 for UEFI or Legacy

 

Legacy

Share this post


Link to post
Share on other sites

Legacy

 

I can not put a FakeSMC in Other because = no Boot 10.7/10.6

 

I need to have different FakeSMC in each folder 

in fact for folder 10.13, 10.7 and 10.6

Share this post


Link to post
Share on other sites

I can not put a FakeSMC in Other because = no Boot 10.7/10.6

 

Yeah I know. I placed mine there to test.

In r4235 and r4236 I'd get stuck on ACPICPU stall too, because then the kexts in either 10.13 or Other wouldn't be injected but that seems to be fixed for me in r4237

Share this post


Link to post
Share on other sites

@fusion71au, @Badruzeus, @chris1111 and others

Make please a preboot.log, if compile Clover 4237 with

#define KEXT_INJECT_DEBUG 2

in kext_inject.c, line 3

 

Do you have 10.13.1 or 10.13b?

 

Hi Slice.

 

Clover kext folders on FAT32 USB shown below, booting 10.7.5, 10.12.6 or 10.13 release.

 

post-846696-0-73135700-1507155372_thumb.png

 

 

Only kexts in /Other and /10.12 are visible in Kext Inject Management Submenu.  When select to boot into 10.13, Kext Inject Management only shows kexts in /Other, none in 10.13...

 

 

135:377  0:000  Loading boot.efi  status=Success
135:738  0:360  GetOSVersion: 10.13 (17A365)
135:785  0:000  Beginning FSInjection
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DCD83398
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DCD83398
135:785  0:000  Use origin smbios table type 1 guid.
135:786  0:000  OSVesion: 10.13, ShortOSVersion=10.13, uni-vers=10.13,
135:786  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
135:786  0:000  current kext name RealtekRTL8111.kext Match Other, while sysver: 10.13
135:786  0:000  Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext
135:855  0:069  current kext name FakeSMC.kext Match Other, while sysver: 10.13
135:855  0:000  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
135:933  0:078    |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext
135:961  0:028    |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\HWInfo.kext
135:962  0:000  current kext name VoodooHDA.kext Match 10.12, while sysver: 10.13
135:962  0:000  current kext name AppleHDADisabler.kext Match 10.12, while sysver: 10.13
135:962  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
135:962  0:000  current kext name RealtekRTL8111.kext Match Other, while sysver: 10.13
135:962  0:000  current kext name FakeSMC.kext Match Other, while sysver: 10.13
135:962  0:000  current kext name VoodooHDA.kext Match 10.12, while sysver: 10.13
135:962  0:000  current kext name AppleHDADisabler.kext Match 10.12, while sysver: 10.13 

post-846696-0-95222400-1507156324_thumb.png

post-846696-0-76305900-1507156343_thumb.png

post-846696-0-54243800-1507156362_thumb.png

post-846696-0-24323900-1507156380_thumb.png

post-846696-0-83007800-1507156397_thumb.png

post-846696-0-25247700-1507156547_thumb.png

 

 

 

 

 

Debug/preboot.log attached.

Bootlog_r4237_debug.txt.zip

preboot.log.zip

Share this post


Link to post
Share on other sites

If I still remember; I got it to works under 10.13 using r4223 with:

1. Kozlek's FakeSMC v6.26.1440 and Rehabman's ACPIBatteryManager v1.81.3 / or 1.81.4 (with patched DSDT for battery)

2. Slice's FakeSMC v3.5 and VoodooBattery.kext (w/o patched DSDT for battery)

"BUT.." for point 1; it just works for a moment after I disassembled my mach. It then disappeared again after I rebooted my mach, IDK why.

Point. 2, it shows the indicator but since my battery device was failed; it spamming me with "Battery 0 empty capacity.. (or similar message)" on verbose logs, and it makes my boot time became longer. Sorry, I should to gave report earlier but on that time; I got trouble accessing the forum. My bad, now I only has 10.13.1 Beta and not testing point 2 yet, but just with point 1 it doesn't work here. Thanks.

Now that I think about it maybe it started happening when I updated fakesmc to 3.5. I'll try older and report back.

Share this post


Link to post
Share on other sites

I had made a USB install of OS X 10.13 High Sierra. Installed latest cloverv2.4k_r4233. and added below to clover/kexts/other

-78938-NullCPUPowerManagement-1.0.0d2.kext

-FakeSMC v6.21-311-g2958f55.1723

-IntelMausiEthernet-v2.2.0 

Also added the apfs.efi to drivers64UEFI

 

I replaced the config with the one provided on fist page (as instructed). 

I have attached my EFI and screen sot of the error during boot "IOUSBHostdevice:: forcepowergated: kpowerstatesuspended"

 

My Machine pecs: 

Cpu Intel 6700k

Asus Z170i Gaming Pro

Samsung NVMe 960 evo M.2 SSD

Intel 530 onboard graphics

Anything I need to add or take away from the EFI? DSDT, SSDT, Config.plist? If someone with similar motherboard setup can help I would really appreciate it.

r4237 works for me.

10.13.1 beta as only OS (besides Windows 10 but that's irrelevant)

FakeSMC in 10.13, other kexts in Other.

 

10:562  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
10:562  0:000  Extra kext: EFI\CLOVER\kexts\Other\USB_Injector.kext
10:564  0:001  Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext
10:566  0:002  Extra kext: EFI\CLOVER\kexts\Other\IntelMausiEthernet.kext
10:567  0:001  Extra kext: EFI\CLOVER\kexts\Other\AppleALC.kext
10:571  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\Other\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
10:683  0:112  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
10:683  0:000  Extra kext: EFI\CLOVER\kexts\10.13\FakeSMC.kext
10:697  0:013  Custom boot screen not used because entry has unset use graphics
10:697  0:000  Closing log
Can i have the link to clover r4237 please

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   1 member

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