Jump to content
30960 posts in this topic

Recommended Posts

47 minutes ago, MifJpn said:

@LAbyOneThank you.

I was just having trouble with @D-an-W, so I just searched for a verbose but kind way.
If the same thing is done twice, but it's in place in the first place, it's virtually non-functional.
So it's an aesthetic.
If you don't forgive me aesthetically, I think from the beginning you should have asked slice to make a commit when you fixed the wrong make order.
Can you forgive me for this?

buildme.zip 4.75 kB · 0 downloads

 

@LAbyOne @MifJpn

@Slica

Without redundancy, it's better indeed, I think.

@LAbyOne

Maybe there is a problem of typo at the end of Buildme script: 'BuildCVP' instead of 'BuildCCPV'

 

Spoiler

1979241532_Capturedcran2021-05-1511_41_05.png.0bdee073c5a6dc6f9b5a868d6be2091f.png

 

Edited by Matgen84
  • Like 2
2 minutes ago, Matgen84 said:

 

@LAbyOne @MifJpn

@Slica

Without redundancy, it's better indeed, I think.

 

  Reveal hidden contents

1979241532_Capturedcran2021-05-1511_41_05.png.0bdee073c5a6dc6f9b5a868d6be2091f.png

 

ofc it is

 

2 minutes ago, Matgen84 said:

@LAbyOne

Maybe there is a problem of typo at the end of Buildme script: 'BuildCVP' instead of 'BuildCCPV'

No problems at all they are 2 different versions

  • Thanks 2
On 5/7/2021 at 9:23 PM, Slice said:

Hi @Jief_Machak,

something wrong when I change one theme to another (cesium to metal)

Снимок экрана 2021-05-07 в 21.18.02.png

Blue buttons are not updated to metal. It is "night" in the Clover now, may be related.

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.

 

Will 5135 fix the black screen I was getting with 5134 on AMD or is it simply adding the new tools? 5133 boots and works fine.


Sent from my iPhone using Tapatalk

I’ll answer my own question and say that clover is once again working on my AMD rig. No more black screen after choosing disk. So what ever happened in 5134 seems fixed for me.


Sent from my iPhone using Tapatalk
  • Like 1
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.

Guest 5T33Z0

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.

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

  • Like 1

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.

3 hours ago, MifJpn said:

@LAbyOne

I'm an unforgivable demon, so tranquilizers don't work anymore.

I'm going to see my psychiatrist tomorrow.

Alpha999 will do the rest.

sorry.

 

 

Don't be mate,

take good care of yourself and be back soon.

 

  • Like 2
  • Thanks 1
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.

×
×
  • Create New...