Jump to content
30960 posts in this topic

Recommended Posts

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"?

Guest ricoc90

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

@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

  • Like 1

@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
  • Like 1

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.

  • Like 1

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. 

  • Like 1

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?

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?

  • Like 6

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

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

  • Like 2

 

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

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.

  • Like 2

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

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?

  • Like 3

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

  • Like 2

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

  • Like 1
×
×
  • Create New...