Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,157 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted

I tried version 4200 too, but still the same.  :(

It is not a clover bug.

Clover installes DeviceProperties protocol and inform boot.efi about injected properties.

It works in current Clover else thousand users can't boot system.

EFI_GUID gDevicePropertiesGuid = {

  0x91BD12FE, 0xF6C3, 0x44FB, {0xA5, 0xB7, 0x51, 0x22, 0xAB, 0x30, 0x3A, 0xE0}
};
But device properties are absent in your report. Because of what? May be your osmosis prevent this? 
  • Like 1
Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted

Does Clover actually use the EFI_DEVICE_PATH_PROPERTY_DATABASE_PROTOCOL for injection? I thought it created a flattened property DB ("EFI string").

iirc it only implements the function that outputs the flat database. I think there is also some code to hassle with the flat database as one can inject an "EFI string" (how I hate this term...), though Clover sets own stuff nevertheless...

Link to comment
Share on other sites
MakAsus
MakAsus
Posted
Posted

 

It is not a clover bug.

Clover installes DeviceProperties protocol and inform boot.efi about injected properties.

It works in current Clover else thousand users can't boot system.

EFI_GUID gDevicePropertiesGuid = {

  0x91BD12FE, 0xF6C3, 0x44FB, {0xA5, 0xB7, 0x51, 0x22, 0xAB, 0x30, 0x3A, 0xE0}
};
But device properties are absent in your report. Because of what? May be your osmosis prevent this? 

 

 

I have two chips, one with an osmosis, and the other with a regular firmware. I changed the chip, But all without changes. It started around with the release of update 10.12.5. However, with osmosis, injection, still working fine.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

I have two chips, one with an osmosis, and the other with a regular firmware. I changed the chip, But all without changes. It started around with the release of update 10.12.5. However, with osmosis, injection, still working fine.

Thousands users installed 10.12.6 and 10.13 and have no problems with injection.

See anywhere DarwinDumper reports by different users and folder "Device properties".

  • Like 4
Link to comment
Share on other sites
Guest ricoc90
Guest ricoc90
Posted
Posted

The only problem I seem to have since r4202 is that nvidia injection does not work in both Sierra as High Sierra DP9 anymore (black screen, display not recognized).

It's not a big deal because I don't actually need graphics injection, other than proper memory report (2047MB without injection, 2048MB with injection thanks to Sherlocks)

27:625  0:000  read_nVidia_ROM
27:625  0:000  Using PRAMIN fixups
27:681  0:055  PROM
27:736  0:055  ERROR: Unable to locate nVidia Video BIOS
27:736  0:000   there are no ROM loaded and no VBIOS read from hardware
27:736  0:000  nVidia Gigabyte GeForce GT 710  -1MB NV1FF [10DE:128B] :: PcieRoot(0x0)\Pci(0x1,0x0)\Pci(0x0,0x0) => device #1
27:736  0:000  Nvidia: VideoPorts: undefined, default to: 2
27:736  0:000  default NVCAP: 04000000-00000300-0C000000-00000007-00000000

In r4205 nvidia injection is fine:

 

41:850  0:000  mem_detected 2048Mb
41:850  0:000  read_nVidia_ROM
41:850  0:000  Using PRAMIN fixups
41:947  0:096  PROM
42:150  0:202  version 80.28.A6.00.4B
42:150  0:000  nVidia Gigabyte GeForce GT 710  2048MB NV106 [10DE:128B] :: PcieRoot(0x0)\Pci(0x1,0x0)\Pci(0x0,0x0) => device #1
42:150  0:000  Nvidia: VideoPorts: undefined, default to: 2
42:150  0:000  default NVCAP: 04000000-00000200-3D000000-00000007-00000000
42:150  0:000   detected codec: 10EC:0269
42:150  0:000  stringlength = 3178
42:150  0:000  CurrentMode: Width=1920 Height=1080
Weird.

 

Ok, so:

 

My Optiplex 790 automatically POST to the PCIe card when plugged in. There's no BIOS setting to change the POST behaviour. It's either iGPU or PCIe card when plugged in. With a little workaround I can however POST to the HD3000 WITH PCIe card plugged in, but this also requires a monitor to be attached to the HD3000 to mark it as active and both the iGPU as well as the PCIe card will be active in macOS then. This apparently breaks nvidia injection since r4202.

 

(^ is the only way to make the HD3000 working to get AirPlay functioning without the need of taking the PCIe card out all the time)

Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

On clover 4200 my macOs partition boots fine. After updating to clover 4208, when I select to boot the macOs partition, I got a black screen and nothing happens, no disk activity, nothing. Something happened between these two revision. Can someone help me please ?

  • Like 1
Link to comment
Share on other sites
mitch_de
mitch_de
Posted
Posted

On clover 4200 my macOs partition boots fine. After updating to clover 4208, when I select to boot the macOs partition, I got a black screen and nothing happens, no disk activity, nothing. Something happened between these two revision. Can someone help me please ?

 

That can be a BUG in 4208 ( kext folders with OS X Version name not loaded!) for my unterstanding.

Seems to not happen if kext are in only one kext folder  other (no oS X version specific) folder .... so maybe an workaround to use only kext  folder  other

 

Discussion of that 4208 kext folder  load bug  here (bugs+dev Clover) :

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-125?do=findComment&comment=2495131

Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

That can be a BUG in 4208 ( kext folders with OS X Version name not loaded!) for my unterstanding.

Seems to not happen if kext are in only one kext folder  other (no oS X version specific) folder .... so maybe an workaround to use only kext  folder  other

 

Discussion of that 4208 kext folder  load bug  here (bugs+dev Clover) :

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-125?do=findComment&comment=2495131

Here is my debug.log if someone wants to look into it. I've also noticed that I can't go into clover options menu, it makes my computer freeze.

debug.log.zip

Link to comment
Share on other sites
syscl
syscl
Posted
Posted

Here is my debug.log if someone wants to look into it. I've also noticed that I can't go into clover options menu, it makes my computer freeze.

 

Thank you for the report, I know where's the 'issue' and will refine it now.

 

syscl

  • Like 2
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

Kext Inject work here in 4208

Works in 10.12 and 10.13

 

 

 

 

FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B49B1F18
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B49B1F18
7:757  0:026  Use origin smbios table type 1 guid.
7:759  0:002  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.12
7:768  0:008    Extra kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext
7:772  0:004    PlugIn kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
7:780  0:007    PlugIn kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
7:782  0:001    PlugIn kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
7:797  0:015    Extra kext: EFI\CLOVER\kexts\10.12\Lilu.kext
7:801  0:003    Extra kext: EFI\CLOVER\kexts\10.12\JMB38X.kext
7:810  0:009    Extra kext: EFI\CLOVER\kexts\10.12\IntelMausiEthernet.kext
7:814  0:004    Extra kext: EFI\CLOVER\kexts\10.12\HSSDBlockStorage.kext
7:822  0:007    Extra kext: EFI\CLOVER\kexts\10.12\FakeSMC.kext
7:829  0:007    PlugIn kext: EFI\CLOVER\kexts\10.12\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
7:835  0:006    PlugIn kext: EFI\CLOVER\kexts\10.12\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
7:844  0:008    Extra kext: EFI\CLOVER\kexts\10.12\BrcmPatchRAM2.kext
7:886  0:042    Extra kext: EFI\CLOVER\kexts\10.12\BrcmFirmwareData.kext
7:904  0:018    Extra kext: EFI\CLOVER\kexts\10.12\AppleALC.kext
7:915  0:010    PlugIn kext: EFI\CLOVER\kexts\10.12\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
8:048  0:133    Extra kext: EFI\CLOVER\kexts\10.12\ACPIBatteryManager.kext
8:064  0:015    Extra kext: EFI\CLOVER\kexts\10.12\ACPIBacklight.kext
8:120  0:056  Custom boot screen not used because entry has unset use graphics
 
 
sans_t90.png

 

 

Clover Boot Log.txt.zip

  • Like 1
Link to comment
Share on other sites
syscl
syscl
Posted
Posted

Kext Inject work here in 4208

Works in 10.12 and 10.13

 

 

 

 

FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B49B1F18
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B49B1F18
7:757  0:026  Use origin smbios table type 1 guid.
7:759  0:002  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.12
7:768  0:008    Extra kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext
7:772  0:004    PlugIn kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
7:780  0:007    PlugIn kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
7:782  0:001    PlugIn kext: EFI\CLOVER\kexts\10.12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
7:797  0:015    Extra kext: EFI\CLOVER\kexts\10.12\Lilu.kext
7:801  0:003    Extra kext: EFI\CLOVER\kexts\10.12\JMB38X.kext
7:810  0:009    Extra kext: EFI\CLOVER\kexts\10.12\IntelMausiEthernet.kext
7:814  0:004    Extra kext: EFI\CLOVER\kexts\10.12\HSSDBlockStorage.kext
7:822  0:007    Extra kext: EFI\CLOVER\kexts\10.12\FakeSMC.kext
7:829  0:007    PlugIn kext: EFI\CLOVER\kexts\10.12\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
7:835  0:006    PlugIn kext: EFI\CLOVER\kexts\10.12\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
7:844  0:008    Extra kext: EFI\CLOVER\kexts\10.12\BrcmPatchRAM2.kext
7:886  0:042    Extra kext: EFI\CLOVER\kexts\10.12\BrcmFirmwareData.kext
7:904  0:018    Extra kext: EFI\CLOVER\kexts\10.12\AppleALC.kext
7:915  0:010    PlugIn kext: EFI\CLOVER\kexts\10.12\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
8:048  0:133    Extra kext: EFI\CLOVER\kexts\10.12\ACPIBatteryManager.kext
8:064  0:015    Extra kext: EFI\CLOVER\kexts\10.12\ACPIBacklight.kext
8:120  0:056  Custom boot screen not used because entry has unset use graphics
 
 
sans_t90.png

 

 

Yeah Their 'issue' only occurs when they use Other folder as a general kext injection, and in previous version InjectKextList only be generated for unsupported newer macOS once(for speed). 

 

syscl

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...