Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

Hi Slice, apianti, Download-Fritz, and everyone else who's still here :)

I've updated my system (after a long pause in the osx department), so now I put also High Sierra on it, and of course came here for a visit.

 

Yes, AptioFix2 works with High Sierra.

For my board I use a mixture of AptioFix2 with LowMemFix with KERNEL_TOP_ADDRESS=0x40000000.

I've seen 10.13 boot.efi allocate way up to 1GB on my system, and I have a clean memory map with the exception of 40 pages at 0x3289A000 that were causing occasional "couldn't allocate runtime area" and had to be freed.

 

Hi, Pene! How are you? Well, so, technically you are getting this same problem, and just freeing random memory.... Need better memory management... All allocations should be above 4GB barrier if possible, or as close to the top as possible, and freed when applicable, which would allow for bigger chunk of memory under 4GB, then there wouldn't (shouldn't) be an issue....

 

Yeah this OsxAptioFixv2 is horrible, about to boot once out of 30 reboots.

 

Have you tried safe mode, then rebuilding the cache? Or something like that? It's very super annoying, because when mine does boot there is kernel panic... GRRRR

Link to comment
Share on other sites

causing occasional "couldn't allocate runtime area" and had to be freed.

-i experienced this issue long time ago. I also reported it several months ago in bug/report thread. I'm a free for this issue by using free2000 files. But not work safe mode. To use safe mode, properly need slide value.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites

try to test this for boot. and report.

Thanks. Will test and report after work.

after: don't know in what direction is moving clover but it's a wrong way for me.

 

17:450  14:760  applied KernelXCPM ???

 

same - busy timeout (0), (60s): AppleACPICPU

Link to comment
Share on other sites

Thanks. Will test and report after work.

after: don't know in what direction is moving clover but it's a wrong way for me.

 

17:450  14:760  applied KernelXCPM ???

 

same - busy timeout (0), (60s): AppleACPICPU

 

why your system not load kext?
my test files is no problem. your system log strangely shown result that i can't understand.
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 58D5C218
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 58D5C218
33:520  0:004  Use origin smbios table type 1 guid.
33:523  0:002  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
33:525  0:002  Custom boot screen not used because entry has unset use graphics
33:525  0:000  Closing log
 
 
i see
33:469  0:004  === [ PatchAllSSDT ] ======================================
33:469  0:000  Patch table: SSDT  SataTabl len=0x36D
33:469  0:000  Patch table: SSDT  PmMgt len=0x15E50
33:469  0:000  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
33:469  0:000   Xsdt has tables count=19
33:469  0:000  CPUBase=0 and ApicCPUBase=0 ApicCPUNum=12
33:469  0:000  Unsupported CPU (0x6): P-States not generated !!!
33:469  0:000  GeneratePStates failed: Status=Not Found
33:469  0:000  SSDT with CPU C-States generated successfully
33:469  0:000  === [ RestSetup macOS ] ===================================
 
your log shown this. are you sure that your system boot on clover r4268?
 
my log shown
5:523  0:000  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
5:523  0:000   Xsdt has tables count=71
5:523  0:000  BUG! Too many XSDT entries 
5:523  0:000  CPUBase=0 and ApicCPUBase=1 ApicCPUNum=8
5:523  0:000  === [ RestSetup macOS ] ===================================
 
i first see this line. strange. i will test to back r4268 on my system.
 
if you can boot with r4268, upload your bootlog file
 
EDIT1. this is my log on r4268
2:017  0:000  CPUBase=0 and ApicCPUBase=1 ApicCPUNum=8
2:017  0:000  === [ RestSetup macOS ] ===================================

it's clean.

 

@Slice

user can boot on r4268.

between r4273 and 4279, seems something wrong, some user has boot hang about AICPUM

https://sourceforge.net/p/cloverefiboot/tickets/421/

 

also like my log, xdst part shown bugs message

 

EDIT2

try r4297 and this file.

config.plist-fix1.zip

Link to comment
Share on other sites

why your system not load kext?

my test files is no problem. your system log strangely shown result that i can't understand.

 

FSInjectionInstall ...

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 58D5C218

FSInjectionInstall ...

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 58D5C218

33:520 0:004 Use origin smbios table type 1 guid.

33:523 0:002 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other

33:525 0:002 Custom boot screen not used because entry has unset use graphics

33:525 0:000 Closing log

 

 

i see

 

33:469 0:004 === [ PatchAllSSDT ] ======================================

33:469 0:000 Patch table: SSDT SataTabl len=0x36D

33:469 0:000 Patch table: SSDT PmMgt len=0x15E50

33:469 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0

33:469 0:000 Xsdt has tables count=19

33:469 0:000 CPUBase=0 and ApicCPUBase=0 ApicCPUNum=12

33:469 0:000 Unsupported CPU (0x6): P-States not generated !!!

33:469 0:000 GeneratePStates failed: Status=Not Found

33:469 0:000 SSDT with CPU C-States generated successfully

33:469 0:000 === [ RestSetup macOS ] ===================================

 

your log shown this. are you sure that your system boot on clover r4268?

 

my log shown

 

5:523 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0

5:523 0:000 Xsdt has tables count=71

5:523 0:000 BUG! Too many XSDT entries

5:523 0:000 CPUBase=0 and ApicCPUBase=1 ApicCPUNum=8

5:523 0:000 === [ RestSetup macOS ] ===================================

 

i first see this line. strange. i will test to back r4268 on my system.

 

if you can boot with r4268, upload your bootlog file

 

EDIT1. this is my log on r4268

 

2:017 0:000 CPUBase=0 and ApicCPUBase=1 ApicCPUNum=8

2:017 0:000 === [ RestSetup macOS ] ===================================

it's clean.

 

@Slice

user can boot on r4268.

between r4273 and 4279, seems something wrong, some user has boot hang about AICPUM

https://sourceforge.net/p/cloverefiboot/tickets/421/

 

also like my log, xdst part shown bugs message

 

EDIT2

try r4297 and this file.

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
Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

post-110586-0-86594500-1511014185_thumb.jpg

 

 

 

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?

Link to comment
Share on other sites

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
Link to comment
Share on other sites

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 1
Link to comment
Share on other sites

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
Link to comment
Share on other sites

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 issueattachicon.gifCaptură de ecran din 2017.11.18 la 16.20.22.png

 

please report on clover r4268

Link to comment
Share on other sites

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

Link to comment
Share on other sites

No and no1da3f1fca9d4febc37578ac3a08399c3.jpg

And from '68 the SAME picture)

Soon logs

Logsattachicon.gifdebug 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?

Link to comment
Share on other sites

×
×
  • Create New...