Jump to content
27,468 posts in this topic

Recommended Posts

4 hours ago, Slice said:

This bug is one year old! :(

I bisecting it. The first wrong commit was 22f9adcbc97e1291bc2361d69b66f96a29af0d05

between revision 5117 (good) and 5118 (bad). 

I have to revise the codes.

 

Resolved!

@Jief_Machak

Look commit a9cb692f6

+      MenuEntryOptions.Image.ImageNight.setEmpty();
       MenuEntryOptions.Image = ThemeX.GetIcon(BUILTIN_ICON_FUNC_OPTIONS);

Strange that setEmpty() is needed to close the bug. Assignment must be enough but no.

17 minutes ago, 5T33Z0 said:

INFO: I've added an english translation of the Clover Manual for all the available options, patches and fixes in the ACPI Section  of my Clover Update Guide. So, if you ever wondered what all these checkboses, fields and drop down menus do, this might be interesting to you.

 

Thanks for spending time translating :)

Posted (edited)

Hi @Slice

Using legacy boot (LegacyBIOSDefault) on my AMD 8350fx.

Clover is working until version 5130 but every newer version gives me the 'purple screen of death' --> purple error messages when normally Clover should give its boot options.

So I still see the version number flash on my screen, but then nothing.

 

I have a cleaned up Plist, so this should be OK.

Any idea what is causing this? Any changes to Legacy boot >5130 ?

On my Intel laptop latest Clover is working.

 

Thanks!

Edited by AntarcticP
9 hours ago, AntarcticP said:

Hi @Slice

Using legacy boot (LegacyBIOSDefault) on my AMD 8350fx.

Clover is working until version 5130 but every newer version gives me the 'purple screen of death' --> purple error messages when normally Clover should give its boot options.

So I still see the version number flash on my screen, but then nothing.

 

I have a cleaned up Plist, so this should be OK.

Any idea what is causing this? Any changes to Legacy boot >5130 ?

On my Intel laptop latest Clover is working.

 

Thanks!

Produce, please, debug.log with 5135.

	<key>Boot</key>
	<dict>
		<key>Debug</key>
		<true/>

After unsuccessful boot you can found ***.log file in the folder /EFI/CLOVER/misc

On 5/15/2021 at 5:57 PM, Slice said:

Resolved!

@Jief_Machak

Look commit a9cb692f6


+      MenuEntryOptions.Image.ImageNight.setEmpty();
       MenuEntryOptions.Image = ThemeX.GetIcon(BUILTIN_ICON_FUNC_OPTIONS);

Strange that setEmpty() is needed to close the bug. Assignment must be enough but no.

Yes, operator = should be enough. Operator = assign and therefore totally replace the old value, like operator = for integers does. But instead of working around by adding a setEmpty(), it's better to fix the operator = implementation in XIcon.cpp.

9 hours ago, Jief_Machak said:

Yes, operator = should be enough. Operator = assign and therefore totally replace the old value, like operator = for integers does. But instead of working around by adding a setEmpty(), it's better to fix the operator = implementation in XIcon.cpp.

Thanks, will do.

21 minutes ago, Slice said:

Thanks, will do.

Oups, no offense, I just did it...

 

I have another question : @MacKonsti pointed that FixHeaders exists in 2 places : ACPI and AXPI/DSDT/Fixes. Which is the more logical/obvious place ? Then, I'll put a warning in Validator asking to move it, and also a warning if both are defined.

1 hour ago, Jief_Machak said:

Oups, no offense, I just did it...

 

I have another question : @MacKonsti pointed that FixHeaders exists in 2 places : ACPI and AXPI/DSDT/Fixes. Which is the more logical/obvious place ? Then, I'll put a warning in Validator asking to move it, and also a warning if both are defined.

FixHeaders is more logical out of DSDT because it works with other ACPI tables.

On 5/15/2021 at 9:44 PM, chris1111 said:

New theme CloverLight  available in the repos Github Clover theme also in my signature Clover Themes

 

The theme are really nice :thumbsup_anim: 

Enjoy :wink_anim:

screenshot5.thumb.png.65a0988082b1919bc352c24c41266dc6.png

I have gone to use it. Is that it is very beautiful:lol:

21 hours ago, Slice said:

Produce, please, debug.log with 5135.


	<key>Boot</key>
	<dict>
		<key>Debug</key>
		<true/>

After unsuccessful boot you can found ***.log file in the folder /EFI/CLOVER/misc

Hi Slice

 

thanks, booted with the debug key. Hope you can find some clues in my log file on what is causing the crash.

 

2021-05-17_16-09_CLOVERX64.EFI.log

35 minutes ago, AntarcticP said:

Hi Slice

 

thanks, booted with the debug key. Hope you can find some clues in my log file on what is causing the crash.

 

2021-05-17_16-09_CLOVERX64.EFI.log 18.67 kB · 1 download

As I see boot process stops here

3:697  0:002  Searching volumes for latest nvram.plist ...
3:701  0:003   Modified = 2021-5-17 16:9:0 (3903955740000 ms)
3:704  0:003   - newer - will use this one

It is not normal. Consider to manually delete nvram.plist from all volumes.

×
×
  • Create New...