Clover General discussion

[ccphuc2016]

Non-official

https://yadi.sk/d/6CR7yEk33PmRzW

thank you

 

My PC Main Gigabyte H110m_S2PV + CPU Core i3 Skylake 6100 3.7Ghz + DDRAM 4 Kington 4gb bus 2133 + VGA onboard HD 530 + VGA PCI ASUS Geforce 210 1Gb + LAN Realtek RLT8111 + Sound ACL887

imac 17,1-  HDD install : Win 10 GPT + Capitian 10.11.5 + Sierra 10.12.6 + High Sierra 10.13  + High Sierra 10.13.1 use Clover Bootyloader r4330

 

Use this Clover_v2.4k_r4303.pkg working OK VGA Geforce 210 boot to macOS 10.13 + 10.13.1 verry fast  and main board Gigabyte H110M-S2PV  update bios F21 OK

[Sherlocks]

Thanks. I will try after work. Strange?) You tell me))) yeah, it's strange how it works. And yes, it's Clover from yours zip

 

try this

 

EDIT1.

try fixup3.zip. i optimized and cleanup source.

fixup3.zip

[MICKHAEL]

try this

 

EDIT1.

try fixup3.zip. i optimized and cleanup source.

Sorry, but no go. The same error. Checked with and without plist that you uploaded (with plist error on PCI)

[Sherlocks]

Sorry, but no go. The same error. Checked with and without plist that you uploaded (with plist error on PCI)

config.plist-sherlocks.zip

Upload prebootlog

 

And i will send PM. We have to research this issue and find point.

 

나의 LG-F800S 의 Tapatalk에서 보냄

[MICKHAEL]

Upload prebootlog

 

And i will send PM. We have to research this issue and find point.

 

나의 LG-F800S 의 Tapatalk에서 보냄

yes sir

[chris1111]

yes sir

Please send here your complete EFI and I try to figure out whats wrong

[MICKHAEL]

Please send here your complete EFI and I try to figure out whats wrong

Sherlocks

EFI with preboot

[mitch_de]

Hi, 

i looked  in your EFI.

1. seems you let Clover generate P + C States (successfully), but ALSO use an SSDT.aml for P/Cstates ( i think thats generated from pike script.

I would only use one of them!

 

2. In your Clover / kext / other is an SLE.zip file, maybe Clover "oversees" that but i would remove that .zip from there

 

 

 

You use High Sierra? Does same happen also if you boot Sierra (same Clover, after removing SSDT.aml)? Perhaps its HS related (some patches wrong,...) and not Clover related?

[MICKHAEL]

Hi,

i looked in your EFI.

1. seems you let Clover generate P + C States (successfully), but ALSO use an SSDT.aml for P/Cstates ( i think thats generated from pike script.

I would only use one of them!

2. In your Clover / kext / other is an SLE.zip file, maybe Clover "oversees" that but i would remove that .zip from there

 

You use High Sierra? Does same happen also if you boot Sierra (same Clover, after removing SSDT.aml)? Perhaps its HS related (some patches wrong,...) and not Clover related?

Thanks. It's Clover related. With Clover 4233 all good and ok, and this is with that SSDT and zip. So? Conclusion? With Clover 4297 not working anymore

[mitch_de]

Yep, but you really should use only ONE!!! way of making CPU P & C states - by Clover generate OR by SSDT.aml (pike alpha script made) , not use both. 

This is in depended from the boot problem with newest beta Clover.

I think the clover devs will tell you same    ( I am an intermediate Clover knower )

 

EDIT: Interesting!!!! In the prelog clover tells it generates P/C states BUT in your config.plist is no setup/ no keys  for generate P/C states (that config.plist section is missed). So Clover (new) enables  generate P/Cstates  by default - if nothing set about that in config.plist? 

 

Can it be that your older Clover works, because it uses other default settings if some functions - like generate P/C states or not set in the config.plist? Could be that newer clover sets some other defaults for missing functions /keys in the config.plist-

I think such  things - older work newer not - may come up more often if users update Clover but not also check / update config.plist...

Is best way (for major Clover changes) to use always the config.plist which comes with the clover install and update settinsg from saved older config by hand?

 

Q: To clover devs  What happens in his case using both generate Clover p/C states and also SSDt.aml C/P States? 

EDIT: In the boot loog first is SSDT.aml inserted/used then later comes generate P/C States by clover in the log. So Clover overwrites the SSDT.aml inserted complete or only some part and result is an mixed up SSDT in case of P/C States?

[MICKHAEL]

Yep, but you really should use only ONE!!! way of making CPU P & C states - by Clover generate OR by SSDT.aml (pike alpha script made) , not use both.

This is in depended from the boot problem with newest beta Clover.

I think the clover devs will tell you same ( I am an intermediate Clover knower )

 

EDIT: Interesting!!!! In the prelog clover tells it generates P/C states BUT in your config.plist is no setup/ no keys for generate P/C states (that config.plist section is missed). So Clover (new) enables generate P/Cstates by default - if nothing set about that in config.plist?

 

Can it be that your older Clover works, because it uses other default settings if some functions - like generate P/C states or not set in the config.plist? Could be that newer clover sets some other defaults for missing functions /keys in the config.plist-

I think such things - older work newer not - may come up more often if users update Clover but not also check / update config.plist...

Is best way (for major Clover changes) to use always the config.plist which comes with the clover install and update settinsg from saved older config by hand?

 

Q: To clover devs What happens in his case using both generate Clover p/C states and also SSDt.aml C/P States?

EDIT: In the boot loog first is SSDT.aml inserted/used then later comes generate P/C States by clover in the log. So Clover overwrites the SSDT.aml inserted complete or only some part and result is an mixed up SSDT in case of P/C States?

And where it's that P C state selected in plist? A? Tell me. And you say it's not a Clover issue

[Sherlocks]

Yep, but you really should use only ONE!!! way of making CPU P & C states - by Clover generate OR by SSDT.aml (pike alpha script made) , not use both. 

This is in depended from the boot problem with newest beta Clover.

I think the clover devs will tell you same    ( I am an intermediate Clover knower )

 

EDIT: Interesting!!!! In the prelog clover tells it generates P/C states BUT in your config.plist is no setup/ no keys  for generate P/C states (that config.plist section is missed). So Clover (new) enables  generate P/Cstates  by default - if nothing set about that in config.plist? 

 

Can it be that your older Clover works, because it uses other default settings if some functions - like generate P/C states or not set in the config.plist? Could be that newer clover sets some other defaults for missing functions /keys in the config.plist-

I think such  things - older work newer not - may come up more often if users update Clover but not also check / update config.plist...

Is best way (for major Clover changes) to use always the config.plist which comes with the clover install and update settinsg from saved older config by hand?

 

Q: To clover devs  What happens in his case using both generate Clover p/C states and also SSDt.aml C/P States? 

EDIT: In the boot loog first is SSDT.aml inserted/used then later comes generate P/C States by clover in the log. So Clover overwrites the SSDT.aml inserted complete or only some part and result is an mixed up SSDT in case of P/C States?

 

like you said, i checked P/C states part on clover and think various case. i made clover. but he reported fail boot on both cases. very strange.

also his preboot is not good. i don't understand. already i gave file(turned off P/C) to him. still no luck.

And where it's that P C state selected in plist? A? Tell me. And you say it's not a Clover issueCaptură de ecran din 2017.11.18 la 16.20.22.png

 

please report on clover r4268

[MICKHAEL]

like you said, i checked P/C states part on clover and think various case. i made clover. but he reported fail boot on both cases. very strange.

also his preboot is not good. i don't understand. already i gave file(turned off P/C) to him. still no luck.

 

please report on clover r4268

i will try first Clover_v2.4k_r4243

[Sherlocks]

i will try first Clover_v2.4k_r4243

I want to test r4268. I'm suspecting some part. And if you can boot or not, upload bootlog or prebootlog.

 

나의 LG-F800S 의 Tapatalk에서 보냄

[MICKHAEL]

i will try first Clover_v2.4k_r4243

No and no

No and no

And from '68 the SAME picture)

Soon logs

No and no

And from '68 the SAME picture)

Soon logs

Logs

[Sherlocks]

No and no

And from '68 the SAME picture)

Soon logs

Logsdebug preboot.zip

 

try to remove all *.aml in ACPI/patches folder.

[Slice]

No and no

And from '68 the SAME picture)

Soon logs

Logsdebug preboot.zip

getSMCprovider error on your screen is clearly said you that FakeSMC is not loaded.

That's all.

 

Your debug.log

44:047  0:016  Use origin smbios table type 1 guid.
44:061  0:014  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
44:075  0:013  Custom boot screen not used because entry has unset use graphics
44:086  0:011  Closing log

Where is any FakeSMC?

[nvflash]

Quick question @Slice, is Clover Legacy EDK I or II?

[smolderas]

I have kext injecting and kext patching problem after some point r4302, probably with introducing new EDK version (r4305).

I'm on legacy.

[MICKHAEL]

try to remove all *.aml in ACPI/patches folder.

hell no. for what i will do that?

getSMCprovider error on your screen is clearly said you that FakeSMC is not loaded.

That's all.

 

Your debug.log

44:047  0:016  Use origin smbios table type 1 guid.
44:061  0:014  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
44:075  0:013  Custom boot screen not used because entry has unset use graphics
44:086  0:011  Closing log

Where is any FakeSMC?

where is his place. i could give this question to clover developers

PS: I'll remind once again, old 4233 clover works just ok.

thanks

[mhaeuser]

Quick question @Slice, is Clover Legacy EDK I or II?

I'm not Slice, but it's all EDK2

[Slice]

Quick question @Slice, is Clover Legacy EDK I or II?

"Clover legacy" doesn't mean "ancient Clover". It means modern Clover to boot ancient computers. 

 

 

hell no. for what i will do that?

where is his place. i could give this question to clover developers

PS: I'll remind once again, old 4233 clover works just ok.

thanks

Some changes for kexts injection did occur but I don't know what is bad in your configuration for new Clover compared to 4233.

Place FakeSMC into /EFI/CLOVER/kexts/Other/ and try again.

[MICKHAEL]

"Clover legacy" doesn't mean "ancient Clover". It means modern Clover to boot ancient computers. 

 

 

Some changes for kexts injection did occur but I don't know what is bad in your configuration for new Clover compared to 4233.

Place FakeSMC into /EFI/CLOVER/kexts/Other/ and try again.

some posts above i uploaded my efi. all ok in my config

EFI with preboot

Attached Files

•   EFI.zip   2.21MB   10 downloads
•  

[chris1111]

 

some posts above i uploaded my efi. all ok in my config

EFI with preboot

Attached Files

•   EFI.zip   2.21MB   10 downloads
•  

 

Please try this config

let me know? ?

config-sample.plist.zip

[MICKHAEL]

Please try this config

let me know? ?

thanks. how i will be at computer