Jump to content
ErmaC

Clover General discussion

19,137 posts in this topic

Recommended Posts

Advertisement

No issues booting here. All kexts are in Other. 

 

EDIT: moved kexts to 10.13, also boots fine. 

 

EDIT2: moved kexts to 10.13, FakeSMC.kext to Other: doesn't boot. Kext Inject Management shows Other folder as being empty.

Share this post


Link to post
Share on other sites

I understand, it works if 10.13 or in Other but not both.

Will be corrected soon.

Thanks for correction @Slice, however using Legacy r4236 with these folders on my EFI:

 

#First Test (they should to have installed kexts by default)

~ 10.11 becomes 'Other' => with empty kext (I didn't use 'Other' folder, removed. But it suddenly appears on Kext Inject Mgmnt with no kext)

~ 10.13 leaves as it folder name => Also with no kext.

 

#Secondly:

~ 10.11 leaves as it's name => Became empty kext

~ 10.13 renamed to Other => My installed kexts detected here and loaded.

 

So for now, I could only use one folder with "Other" as the name to boot between 10.11. or 10.13.

preboot.log.zip

Share this post


Link to post
Share on other sites

Thanks for correction @Slice, however using Legacy r4236 with these folders on my EFI:

 

#First Test (they should to have installed kexts by default)

~ 10.11 becomes 'Other' => with empty kext (I didn't use 'Other' folder, removed. But it suddenly appears on Kext Inject Mgmnt with no kext)

~ 10.13 leaves as it folder name => Also with no kext.

 

#Secondly:

~ 10.11 leaves as it's name => Became empty kext

~ 10.13 renamed to Other => My installed kexts detected here and loaded.

 

So for now, I could only use one folder with "Other" as the name to boot between 10.11. or 10.13.

Test, please, with commenting out/removing 1 line 4917 in menu.c

AddMenuEntry(&OptionMenu, SubMenuKextInjectMgmt(LastChosenOS));

Share this post


Link to post
Share on other sites

Test, please, with commenting out/removing 1 line 4917 in menu.c

AddMenuEntry(&OptionMenu, SubMenuKextInjectMgmt(LastChosenOS));

On pregress, would give report asap.

Share this post


Link to post
Share on other sites

Test, please, with commenting out/removing 1 line 4917 in menu.c

AddMenuEntry(&OptionMenu, SubMenuKextInjectMgmt(LastChosenOS));

Situation:

FakeSMC in 10.13, other kexts in Other.

Kext Injection Management menu shows it correctly,

Booting in Debug shows that only the kexts from Other are being injected.

 

post-1502423-0-74515800-1507031826_thumb.jpg

 

Share this post


Link to post
Share on other sites

Similar to @ricoc90 results, but on my test using r4236 (edited menu.c) I lost the whole "Kext Inject Management" feature from Boot Options Menu.

 

#EDIT: I didn't use 'Other' folder, but only /10.11 & /10.13, seems not to be injected so both OSes never reach the Desktop.

preboot.log.zip

Share this post


Link to post
Share on other sites

I lost that menu in the boot options too, but it's still there under the selected OS boot options (spacebar)

 

post-1502423-0-56793200-1507032918_thumb.pngpost-1502423-0-21430700-1507032924_thumb.png

Share this post


Link to post
Share on other sites

I lost that menu in the boot options too, but it's still there under the selected OS boot options (spacebar)

U mean, Menu Entry details with Space Bar..?

Share this post


Link to post
Share on other sites

U mean, Menu Entry details with Space Bar..?

 

Yes  :P

Share this post


Link to post
Share on other sites

@slice / @syscl - any more thoughts on reverting the haswell-e changes in 4145/4146?  I'm pretty certain the new code doesn't work for a decent % of systems (I've actually tried it on 3 at this point) whereas the old code does.  Happy to provide the necessary changes against the latest clover rev!

Share this post


Link to post
Share on other sites

@slice / @syscl - any more thoughts on reverting the haswell-e changes in 4145/4146?  I'm pretty certain the new code doesn't work for a decent % of systems (I've actually tried it on 3 at this point) whereas the old code does.  Happy to provide the necessary changes against the latest clover rev!

i dont have any problem with my haswell e 5820k

without any xcpm patches, clover does it automatically.

as far as i know, i cant disable those patches with DisableExtCpuXCPM, or is there bootargs that can disable it?

Share this post


Link to post
Share on other sites

i dont have any problem with my haswell e 5820k

without any xcpm patches, clover does it automatically.

as far as i know, i cant disable those patches with DisableExtCpuXCPM, or is there bootargs that can disable it?

OK, I will consider to add it if it is necessary. But till now I will try to figure out suit patches for him.

 

syscl

Share this post


Link to post
Share on other sites

Rev 4237 looks good. Test, please!

3:431  0:010  chosen os 10.7.3
3:433  0:002  getList: sysver=10.7, Short=10.7
3:435  0:001  Added mKext=ATI7000Controller.kext, MatchOS=10.7
3:437  0:002  Added mKext=ATILead.kext, MatchOS=10.7
3:438  0:001  Added mKext=ATITVOut.kext, MatchOS=10.7
3:440  0:002  getList: sysver=Other, Short=10.7
3:443  0:002  Added mKext=FakeSMC.kext, MatchOS=Other
3:444  0:001  ---| added plugin=RadeonMonitor.kext, MatchOS=Other
3:445  0:001  ---| added plugin=ACPISensors.kext, MatchOS=Other
3:446  0:001  Added mKext=HWInfo.kext, MatchOS=Other
....
26:742  0:002  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
26:743  0:001  current kext name HWInfo.kext Match Other, while sysver: 10.7
26:746  0:002  Extra kext: EFI\CLOVER\kexts\Other\HWInfo.kext
26:754  0:008  current kext name FakeSMC.kext Match Other, while sysver: 10.7
26:755  0:001  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
26:766  0:010    |-- PlugIn kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
26:772  0:006    |-- Disabled plug-in kext: EFI\CLOVER\kexts\Other\FakeSMC.kext\Contents\PlugIns\RadeonMonitor.kext
26:774  0:001  current kext name ATITVOut.kext Match 10.7, while sysver: 10.7
26:776  0:001  current kext name ATILead.kext Match 10.7, while sysver: 10.7
26:777  0:000  current kext name ATI7000Controller.kext Match 10.7, while sysver: 10.7
26:778  0:001  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.7
26:779  0:001  current kext name HWInfo.kext Match Other, while sysver: 10.7
26:780  0:000  current kext name FakeSMC.kext Match Other, while sysver: 10.7
26:781  0:001  current kext name ATITVOut.kext Match 10.7, while sysver: 10.7
26:783  0:001  Extra kext: EFI\CLOVER\kexts\10.7\ATITVOut.kext
26:789  0:005  current kext name ATILead.kext Match 10.7, while sysver: 10.7
26:790  0:000  Disabled kext: EFI\CLOVER\kexts\10.7\ATILead.kext
26:791  0:000  current kext name ATI7000Controller.kext Match 10.7, while sysver: 10.7
26:792  0:001  Extra kext: EFI\CLOVER\kexts\10.7\ATI7000Controller.kext

In repo the debug messages switched off

Share this post


Link to post
Share on other sites

@Slice,

 

r4237 works great!

 

 

post-846696-0-81461600-1507097213_thumb.png

post-846696-0-56310400-1507097237_thumb.png

post-846696-0-74921100-1507097254_thumb.png

post-846696-0-32348600-1507097267_thumb.png

post-846696-0-68730400-1507097291_thumb.png

 

 

Bootlog1.txt with kexts injected from /Other & /10.12.

Bootlog2.txt with kexts injected from /Other, Disabled injection from /10.12 through Kext Management Submenu on chosen volume (Kext Management no longer in Clover Options Main Menu).  

 

IMHO, it makes more sense this way.  If you decide to boot 10.12, you don't need to see kexts in 10.11 folder or 10.13 folder to disable.

 

Edit

Spoke a bit too soon.

 

On selecting the 10.13 volume, 10.13 kext folder appears to be empty in Kext Management Submenu (but it isn't) ---> no kexts injected from 10.13 folder, only from /Other - Bootlog3.txt

 

 

post-846696-0-94775600-1507107017_thumb.png

post-846696-0-94499000-1507107045_thumb.png

 

 

Thanks Slice...

Bootlogs r4237.zip

Bootlog3.txt.zip

Share this post


Link to post
Share on other sites

Using r4237 with these folders on /EFI/CLOVER/kexts/ however:

~ 10.11 => OK, also appears on Kexts Inject Mgmt with it's contents.

~ 10.13 => missing folder

~ Other => OK, but I don't use it for installing any kext.

Thanks.

 

 

aSqMIfN.jpg

 

bootlog.log_r4237.txt.zip

Share this post


Link to post
Share on other sites

Using r4237 with these folders on /EFI/CLOVER/kexts/ however:

~ 10.11 => OK, also appears on Kexts Inject Mgmt with it's contents.

~ 10.13 => missing folder

~ Other => OK, but I don't use it for installing any kext.

Thanks.

 

 

aSqMIfN.jpg

 

10.13 missing because you chosen 10.11 system

Share this post


Link to post
Share on other sites

10.13 missing because you chosen 10.11 system

My bad. OK, thanks for correcting. With 10.13 macHDD selected, under Kexts Inject Mgmt it shows 10.13 folder, but with no installed kext (empty).

 

 

Ofun6GL.jpg

 

2:745  0:000  Starting Clover revision: 4237 on CLOVER EFI
2:745  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]

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 ?

Share this post


Link to post
Share on other sites

4237 works here  10.12

Not work 10.13 /10.7 /10.6

 

4222 works all the way

 

EDIT 1**

4237 works in Other for 10.13 /10.12

Not for 10.7 /10.6 FakeSMC  no good

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