Jump to content
ErmaC

Clover General discussion

19,118 posts in this topic

Recommended Posts

Advertisement

Put CsmVideoDxe.efi in your drivers64UEFI folder. Works only when you're on UEFI. However, this isn't really a good "fix" because when I do that, I have to go blind on the Clover GUI because the whole screen is scrambled. For others it seems to work fine.

 

CsmVideoDxe-64.efi is already there (need it for forcing the 1440p resolution with other bootloaders booted by Clover) and I'm using UEFI exclusively, and it still appears. Any other "fixes"?

Share this post


Link to post
Share on other sites

As a test I edited out the changes made in 4217 and compiled 4232, everything works ok so does anyone know how I modify my setup to work with the cancellation of ARPT renaming please?

 

I tried with CsmVideoDxe-64.efi but it made no difference, did you mean that file or the none -64 one?

It's the same file, just with a different name due to duplication

 

 

CsmVideoDxe-64.efi is already there (need it for forcing the 1440p resolution with other bootloaders booted by Clover) and I'm using UEFI exclusively, and it still appears. Any other "fixes"?

 

Nope, sorry. I know that there's a log free apfs.efi, but I don't know if it still works: http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2470184

Share this post


Link to post
Share on other sites

@Slice / @ Syscl - confirmed that reverting 4145 + 4146 then re-applying the rest of the revisions works.

 

Here's my code changes (based against r4220)

 

Anyone else with a Haswell-E PM me for my r4220 build - it should work!  (Can't upload as it's 12.5mb which is over the 10mb limit)

clover_deltas.zip

Share this post


Link to post
Share on other sites

@Slice: Kext injection of Clover/kexts/Other happens 3 times in r4233:

Can also confirm is happening (@syscl):

9:989  0:001  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
9:989  0:000  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID_Intel_HDMI_Audio.kext
9:990  0:001  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID.kext
9:992  0:002  Extra kext: EFI\CLOVER\kexts\Other\VerbStub.kext
9:994  0:001  Extra kext: EFI\CLOVER\kexts\Other\NvidiaGraphicsFixup.kext
9:996  0:001  Extra kext: EFI\CLOVER\kexts\Other\BT4LEContiunityFixup.kext
9:997  0:001  Extra kext: EFI\CLOVER\kexts\Other\AppleBacklightInjector.kext
9:998  0:000  Extra kext: EFI\CLOVER\kexts\Other\HibernationFixup.kext
10:000  0:002  Extra kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext
10:002  0:001    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
10:005  0:002    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
10:007  0:001    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
10:011  0:004  Extra kext: EFI\CLOVER\kexts\Other\ACPIBatteryManager.kext
10:013  0:002  Extra kext: EFI\CLOVER\kexts\Other\Shiki.kext
10:015  0:001  Extra kext: EFI\CLOVER\kexts\Other\IntelGraphicsFixup.kext
10:018  0:002  Extra kext: EFI\CLOVER\kexts\Other\AirportBrcmFixup.kext
10:020  0:002  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
10:023  0:003  Extra kext: EFI\CLOVER\kexts\Other\CoreDisplayFixup.kext
10:026  0:002  Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext
10:029  0:003  Extra kext: EFI\CLOVER\kexts\Other\AppleALC.kext
10:031  0:002    |-- PlugIn kext: EFI\CLOVER\kexts\Other\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
10:044  0:012  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID_Intel_HDMI_Audio.kext
10:047  0:003  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID.kext
10:049  0:002  Extra kext: EFI\CLOVER\kexts\Other\VerbStub.kext
10:052  0:002  Extra kext: EFI\CLOVER\kexts\Other\NvidiaGraphicsFixup.kext
10:055  0:002  Extra kext: EFI\CLOVER\kexts\Other\BT4LEContiunityFixup.kext
10:057  0:002  Extra kext: EFI\CLOVER\kexts\Other\AppleBacklightInjector.kext
10:059  0:001  Extra kext: EFI\CLOVER\kexts\Other\HibernationFixup.kext
10:062  0:003  Extra kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext
10:065  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
10:071  0:005    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
10:074  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext

Share this post


Link to post
Share on other sites

Time ago I have "extract" some image from embedded in the code...

attachicon.gifhex_png.zip

most of them are 64x64... what you mean with reduce? the pixel ex:32x32 or 16x16

or you mean a different/better compression ?

 

ErmaC

There is no interest to extract existing images which are probably problematic. I means quite other images. Other design. Minimum set of icons.

Compression is proposed the same - pngquant which is proved for Clover.

Share this post


Link to post
Share on other sites

Updated to Clover v4233. I noticed that NvidiaWeb under SystemParameters in config.plist no longer enables the Nvidia Web Drivers without adding nv_drv=1. Was this an intentional change? Before v4233, only having NvidiaWeb set to TRUE enabled the drivers without nv_drv=1 flag. 

Share this post


Link to post
Share on other sites

Put CsmVideoDxe.efi in your drivers64UEFI folder. Works only when you're on UEFI. However, this isn't really a good "fix" because when I do that, I have to go blind on the Clover GUI because the whole screen is scrambled. For others it seems to work fine.

Since Clover is responsible for loading the driver, is it possible for it to redirect console output to a null device during that time? Maybe a buffer that could be added to the debug log?

Share this post


Link to post
Share on other sites

I take a good example from StartLoader () and it work good. Cant make sure if this work with this Clover, because LoadDrivers () were called before InitScreen ()? Attached also an example how to use Cupertinos EFI_DEVICE_PATH_PROPERTY_DATABASE_PROTOCOL with Clover (based on Racermaster & Linux source).
** Is current SubMenuKextBlockInjection () potentially scan & load kexts in folder multiple times?

Share this post


Link to post
Share on other sites

Hi guys,

 

Looks like even with the latest apfs.efi (as in the one from the Release build),  the debug mode is still enabled.

 

The apfs file posted on the previous pages seems to be from Beta 4 and if I'm not mistaken, it was custom made by cecekpawon. :) Not sure if there's a "log free" version of the release apfs file. If there is, I would be interested to have it too. :D

Share this post


Link to post
Share on other sites

Hey, you can try those old patterns with current binary >>>

 

I would say that worked out beautifully. :)

 

Still have some debug log but it seems to be from FileVault drivers. About the log itself, I guess I should ask into the FV thread. :)

 

post-1303722-0-29499000-1506956397_thumb.png

 

Anyway, attached the patched apfs.efi from the release build, for anyone interested.

 

@cecekpawon, many thanks.

apfs.efi

Share this post


Link to post
Share on other sites

** Is current SubMenuKextBlockInjection () potentially scan & load kexts in folder multiple times?

You are right, the issue is here.

Share this post


Link to post
Share on other sites

 

Can also confirm is happening (@syscl):

9:989  0:001  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
9:989  0:000  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID_Intel_HDMI_Audio.kext
9:990  0:001  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID.kext
9:992  0:002  Extra kext: EFI\CLOVER\kexts\Other\VerbStub.kext
9:994  0:001  Extra kext: EFI\CLOVER\kexts\Other\NvidiaGraphicsFixup.kext
9:996  0:001  Extra kext: EFI\CLOVER\kexts\Other\BT4LEContiunityFixup.kext
9:997  0:001  Extra kext: EFI\CLOVER\kexts\Other\AppleBacklightInjector.kext
9:998  0:000  Extra kext: EFI\CLOVER\kexts\Other\HibernationFixup.kext
10:000  0:002  Extra kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext
10:002  0:001    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
10:005  0:002    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
10:007  0:001    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
10:011  0:004  Extra kext: EFI\CLOVER\kexts\Other\ACPIBatteryManager.kext
10:013  0:002  Extra kext: EFI\CLOVER\kexts\Other\Shiki.kext
10:015  0:001  Extra kext: EFI\CLOVER\kexts\Other\IntelGraphicsFixup.kext
10:018  0:002  Extra kext: EFI\CLOVER\kexts\Other\AirportBrcmFixup.kext
10:020  0:002  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
10:023  0:003  Extra kext: EFI\CLOVER\kexts\Other\CoreDisplayFixup.kext
10:026  0:002  Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext
10:029  0:003  Extra kext: EFI\CLOVER\kexts\Other\AppleALC.kext
10:031  0:002    |-- PlugIn kext: EFI\CLOVER\kexts\Other\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
10:044  0:012  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID_Intel_HDMI_Audio.kext
10:047  0:003  Extra kext: EFI\CLOVER\kexts\Other\FakePCIID.kext
10:049  0:002  Extra kext: EFI\CLOVER\kexts\Other\VerbStub.kext
10:052  0:002  Extra kext: EFI\CLOVER\kexts\Other\NvidiaGraphicsFixup.kext
10:055  0:002  Extra kext: EFI\CLOVER\kexts\Other\BT4LEContiunityFixup.kext
10:057  0:002  Extra kext: EFI\CLOVER\kexts\Other\AppleBacklightInjector.kext
10:059  0:001  Extra kext: EFI\CLOVER\kexts\Other\HibernationFixup.kext
10:062  0:003  Extra kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext
10:065  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
10:071  0:005    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
10:074  0:003    |-- PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext

Thank you for pointing out this issue. I am going to see what @Slice changed.

 

Edit: @Slice corrected it  ^_^

 

syscl

Share this post


Link to post
Share on other sites

I take a good example from StartLoader () and it work good. Cant make sure if this work with this Clover, because LoadDrivers () were called before InitScreen ()? Attached also an example how to use Cupertinos EFI_DEVICE_PATH_PROPERTY_DATABASE_PROTOCOL with Clover (based on Racermaster & Linux source).

 

I want this protocol to be implemented but carefully.

See

DeviceSetProperty (
  IN EFI_DEVICE_PATH_PROTOCOL   *DevicePath,
  IN CHAR16                     *Name,
  IN VOID                       *Value,
  IN UINTN                      Size
) {

should add property to a device.

        if (!Found) {
...
        }
      }
  #ifdef DEVPROP_OVERRIDE
    }
  #endif

  return Status;
}

So the properties will add once. Only one property.

Next case the device will be found.

Share this post


Link to post
Share on other sites

Same here  :(

 

img_1236.jpg

 

I use several kexts in several Folder because I have several OS X Diferant

If I put my kext in Other it works for 10.13 but not for my other OS
Sierra, Lion Snow
I do not use the folder Other, has all the times that work on this folder, the injection of the diferant folder is broken
should not delete the Other folder that is in fact useless because if people would use separate folder kexts as was before, they would not have this problem
 
4222 works for folder 10xx

Share this post


Link to post
Share on other sites

has any one booted 4235 and reached the OS I seem to get stuck at ACPICPU now

Guys, u mean only get it to boot 10.13 or ..?

Strange is, #r4235 on Clover boot Options - Kext Inject Management; I see no kext installed on my 10.13 folder, however I should to have more than 5 there. How if moving them to Other folder?

Share this post


Link to post
Share on other sites

It looks like kexts are not being detected in the 10.x folders by Clover r4235.  

 

If I go into "kext management" submenu from Clover's Main Menu, 10.13 appears empty when it has kext in it.  However, kext injection OK from /Other folder....

 

 

post-846696-0-20279200-1506986756_thumb.png

post-846696-0-04764000-1506986807_thumb.png

post-846696-0-28796600-1506986823_thumb.png

post-846696-0-08784400-1506986839_thumb.png

 

 

Bootlogs attached:

 

Bootlog1=Clover r4235 from FAT32 USB - EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts

Bootlog2=Clover r4235 from EFI System Partition - EFI\CLOVER\kexts

 

 

Bootlogs Clover r4335.zip

Share this post


Link to post
Share on other sites

It looks like kexts are not being detected in the 10.x folders by Clover r4235.

...

I have dualboot OSes with El Capitan, my installed kexts properly loaded from .../kexts/10.11; but not with ../kexts/10.13 to boot High Sierra   :)

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 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....
       
       
    • By kylon
      Cloud Clover Editor allows you to manage Clover EFI and Ozmosis configs everywhere!
       
       
      WEB
      Open Cloud Clover Editor
       
      APP (MacOS - Discontinued)
      Clover flying editor ( Micky1979 )
       
       
       
       
      Sources: https://bitbucket.org/kylon/cloud-clover-editor-cce/overview


      To run CCE at home you will need:
       
      An HTTP server (Apache, Nginx, ...) PHP 5.3.3+ (latest PHP version is always recommended for better performances/security) Sqlite3 PHP extension  
       
      Some Features:
       
      Edit text in tables:
      Editable fields are marked with a text cursor.
      Double click, or tap and hold, to open the inline editor.
      You can now press Enter or click outside to save your changes.
       
       
      Tri-state checkboxes:
      There are 3 possible states for a checkbox: Checked, indeterminate and unchecked.
       
      Checked: Value is true;
      Indeterminate: Value is false;
      Unchecked: Value is not set (ie, removed from plist)
       
      Working with multiple configs:
      The right sidebar is your multitasking menu.
      Use the add button to create a new config and add it to the list.
      You can safely switch between all your configs, no changes will be lost.
      You can mix Clover EFI and Ozmosis configs.


      Config Upgrade feature:
      In the case you are using old configuration options, CCE gives you the ability to automatically upgrade your config.
       
       
      Copy to:
      You can copy patches between your configs (you will love this when you need to copy kernel and kext patches ;D ).
      You will find a yellow copy icon if that field does support the copyTo feature.
       
       
      Ozmosis Mode:
      A new setting, Cloud Clover Editor Mode, is now added in Cloud Clover Editor -> CCE Settings.
      This will let you switch from Clover EFI to Ozmosis mode.
      Changes to your current file will be lost.
       
       
      CCE Bank 2.0:
      Thanks to @cecekpawon for the idea.
       
      CCE Bank is a database where you can save/load Clover EFI and Ozmosis configs.
      You can protect your config from unwanted modifications or make a publicly editable config.
       
      To save a config in CCE Bank you only need to check the "Save to CCE Bank" option.
       
      Tick the box generate a new CID, if you don t have one.
       
      A CID (CCE ID) acts like a container and it is your authentication key.
      You can group multiple configs under the same CID or generate as many CIDs as you like.
       
      Edit Modes:
      Public: Anyone can make modifications, only the owner can change its settings. Private: Only the owner can make modifications and change its settings. MyBank: Only the owner can see this config, make modifications or change its settings.  
      MyBank is your private area.
      Change the 'view mode' to switch between the public bank and your personal bank.
       
      To manage your currently loaded config, go to Cloud Clover Editor -> Open config -> click the settings button.
       
       
      Notes:
      Locked/Private configs are marked with a padlock MyBank configs are only visibile in your private area Only the owner of a locked config can save the modifications in CCE Bank, hower you are free to do whatever you want in CCE and download the modified config If you loose your CID you can just reply or pm me No account is required!  
       
      Main Features:
      Left sidebar does support touch swipe on touch devices.
      No changes will be lost on page reload.
       
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support Please let me know if i forgot you!
×