Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted
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.

  • Like 1
  • Thanks 2
naiclub
naiclub
Posted
Posted
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:

  • Like 2
AntarcticP
AntarcticP
Posted
Posted
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

Slice
Slice
Posted
Posted
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.

AntarcticP
AntarcticP
Posted
Posted
1 hour ago, Slice said:

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.

Deleted my NVRAM.plist and now getting the following message in the log. Clover still crashes.

 

29:055  0:002  Searching volumes for latest nvram.plist ...
29:059  0:004   - [0] no nvram.plist - skipping!

Allan
Allan
Posted
Posted

Hey guys, I have a little doubt.

 

AFAIK for BS there's no more USB Port limit patch (last one is for Catalina and is DISABLED on my Hack install).

So after doing the USB mapping, we need to keep XhciPortLimit quirk enabled? :idea:

Slice
Slice
Posted
Posted
2 hours ago, Allan said:

Hey guys, I have a little doubt.

 

AFAIK for BS there's no more USB Port limit patch (last one is for Catalina and is DISABLED on my Hack install).

So after doing the USB mapping, we need to keep XhciPortLimit quirk enabled? :idea:

It is destructive quirk so it will be better to keep it disabled as in config-sample.plist

  • Like 1
  • Thanks 2
Slice
Slice
Posted
Posted
2 minutes ago, SavageAUS said:

On my AMD rig I get distortion / cut off sound using the boot chime with clovers AudioDxe.efi but if I use OpenCores AudioDxe.efi I have no issues.
 

It looks like new authors corrections in the driver. Should look.

  • Like 1
matxpa
matxpa
Posted
Posted

@Slice

 

The two screenshots come from my Laptop Asus.

"EFI\CLOVER" useful ? may be no more but ...

There's two distinct versions :

 

1) Only with the short SHA (7 chars) added

2) with BUILDTARGET + TOOLCHAIN + short SHA (7 chars) added

Jief_Machak
Jief_Machak
Posted
Posted
17 minutes ago, PG7 said:

@Jief_Machak @Slice Team

 

 

Hello team

 

I have a problem I don't know if there is anything direct to be done on Clover

I will explain and it will be a little long, I apologize already but when and when you have to explain everything has to be checked!

 

I have a Samsung NP350V5C-S06FR
intel i3-3110M
intel HD4000 + Radeon HD 7670M is disabled in DSDT
SSD
8go RAM ddr3 (1333MHz)
working in Big Sur but already well since previous systems


he always bothered me with the BootLoader directly on the disk where he sometimes only accepted Legacy and even after being able to activate in UEFI it is necessary to use a Microsoft paste in EFI so that he can create the boot entry in the BIOS because without this method he does
- I tested it by the commands in Shell to create a new entry in the bios for Clover but I always find a problem now since I updated to r5135
it used to work now I tested it until I revolted the old version and I can't get it in any way

he can boot the Clover because as in the print here he recognizes a warning from the touchpad that I put on purpose to see if he found the config.plist and that is the case
it presents the print error but does not leave this screen automatically, that is, I send it to boot and it stops there
- if I choose manually by the F10 key and the boot partition where the Clover path is located (\EFI\CLOVER\CLOVERX64.efi) it passes on this same warning screen and continues the normal boot

remember I used that same form in r5134 and earlier and it worked
I did a reinstall of Clover by .pkg as I always do and I never had this problem

I leave the Logo NO boot auto where it stands and does not continue
just like Boot F10 OK where it boots

I already tried a little of everything even Clean CMOS but it remains the same and even in legacy mode it does not automatically boot to this screen

I suspect the bios but how it gets the Boot both from the USB and the disk with the F10 key makes me more confused

 

thanks to everyone who can check the logs and be able to give me an indication

Thanks to all who spend time to be able to put all this possible, right now I'm a little absent here with you for personal reasons but always following the Clover team

 

Google translate 

  Hide contents

IMG_20210518_190817_BURST001_COVER.thumb.jpg.f15cd536ca02defac188b96b8261d702.jpg


 

no boot auto 2021-05-18_17-26_CLOVERX64.efi.log 6.43 kB · 0 downloads boot F10 OK 2021-05-18_17-27_CLOVERX64.efi.log 52.22 kB · 0 downloads

At least, start to delete the key DoubleClick in GUI/Mouse from your config.plist...

Jief_Machak
Jief_Machak
Posted
Posted
On 5/17/2021 at 9:59 PM, AntarcticP said:

Deleted my NVRAM.plist and now getting the following message in the log. Clover still crashes.

 

29:055  0:002  Searching volumes for latest nvram.plist ...
29:059  0:004   - [0] no nvram.plist - skipping!

Send a zip of your whole Clover folder. I'll try to reproduce...

Just now, PG7 said:

I put this key to have the warning on the screen and be able to see if it is booting Clover

as a rule I no longer use this key as I already pointed out in a previous message at the exit of r5135

this error rapporteur is just for that (being able to have information instead of having only the Samsung screen!)

Oh, sorry. But your translated message is not understandable...

Try in French ?

Jief_Machak
Jief_Machak
Posted
Posted
1 hour ago, Slice said:

It is good for large screen but bothers on small screen like laptops.

Is the information "\EFI\CLOVER" useful somehow?

I have more than one Clover folder and switch a lot between them. So yes, I think it's useful. Now, it can be only when Boot/Debug in true, for example... Or just in my own builds if no one likes it.

41 minutes ago, PG7 said:

@Jief_Machak @Slice Team

 

 

Hello team

 

I have a problem I don't know if there is anything direct to be done on Clover

I will explain and it will be a little long, I apologize already but when and when you have to explain everything has to be checked!

 

I have a Samsung NP350V5C-S06FR
intel i3-3110M
intel HD4000 + Radeon HD 7670M is disabled in DSDT
SSD
8go RAM ddr3 (1333MHz)
working in Big Sur but already well since previous systems


he always bothered me with the BootLoader directly on the disk where he sometimes only accepted Legacy and even after being able to activate in UEFI it is necessary to use a Microsoft paste in EFI so that he can create the boot entry in the BIOS because without this method he does
- I tested it by the commands in Shell to create a new entry in the bios for Clover but I always find a problem now since I updated to r5135
it used to work now I tested it until I revolted the old version and I can't get it in any way

he can boot the Clover because as in the print here he recognizes a warning from the touchpad that I put on purpose to see if he found the config.plist and that is the case
it presents the print error but does not leave this screen automatically, that is, I send it to boot and it stops there
- if I choose manually by the F10 key and the boot partition where the Clover path is located (\EFI\CLOVER\CLOVERX64.efi) it passes on this same warning screen and continues the normal boot

remember I used that same form in r5134 and earlier and it worked
I did a reinstall of Clover by .pkg as I always do and I never had this problem

I leave the Logo NO boot auto where it stands and does not continue
just like Boot F10 OK where it boots

I already tried a little of everything even Clean CMOS but it remains the same and even in legacy mode it does not automatically boot to this screen

I suspect the bios but how it gets the Boot both from the USB and the disk with the F10 key makes me more confused

 

thanks to everyone who can check the logs and be able to give me an indication

Thanks to all who spend time to be able to put all this possible, right now I'm a little absent here with you for personal reasons but always following the Clover team

 

Google translate 

  Reveal hidden contents

IMG_20210518_190817_BURST001_COVER.thumb.jpg.f15cd536ca02defac188b96b8261d702.jpg


 

no boot auto 2021-05-18_17-26_CLOVERX64.efi.log 6.43 kB · 0 downloads boot F10 OK 2021-05-18_17-27_CLOVERX64.efi.log 52.22 kB · 0 downloads

C'est ce message là qui est difficilement compréhensible.

je n'ai pas compris quel est le problème.

Jief_Machak
Jief_Machak
Posted
Posted
47 minutes ago, PG7 said:

@Jief_Machak @Slice Team

 

 

Hello team

 

I have a problem I don't know if there is anything direct to be done on Clover

I will explain and it will be a little long, I apologize already but when and when you have to explain everything has to be checked!

 

I have a Samsung NP350V5C-S06FR
intel i3-3110M
intel HD4000 + Radeon HD 7670M is disabled in DSDT
SSD
8go RAM ddr3 (1333MHz)
working in Big Sur but already well since previous systems


he always bothered me with the BootLoader directly on the disk where he sometimes only accepted Legacy and even after being able to activate in UEFI it is necessary to use a Microsoft paste in EFI so that he can create the boot entry in the BIOS because without this method he does
- I tested it by the commands in Shell to create a new entry in the bios for Clover but I always find a problem now since I updated to r5135
it used to work now I tested it until I revolted the old version and I can't get it in any way

he can boot the Clover because as in the print here he recognizes a warning from the touchpad that I put on purpose to see if he found the config.plist and that is the case
it presents the print error but does not leave this screen automatically, that is, I send it to boot and it stops there
- if I choose manually by the F10 key and the boot partition where the Clover path is located (\EFI\CLOVER\CLOVERX64.efi) it passes on this same warning screen and continues the normal boot

remember I used that same form in r5134 and earlier and it worked
I did a reinstall of Clover by .pkg as I always do and I never had this problem

I leave the Logo NO boot auto where it stands and does not continue
just like Boot F10 OK where it boots

I already tried a little of everything even Clean CMOS but it remains the same and even in legacy mode it does not automatically boot to this screen

I suspect the bios but how it gets the Boot both from the USB and the disk with the F10 key makes me more confused

 

thanks to everyone who can check the logs and be able to give me an indication

Thanks to all who spend time to be able to put all this possible, right now I'm a little absent here with you for personal reasons but always following the Clover team

 

Google translate 

  Reveal hidden contents

IMG_20210518_190817_BURST001_COVER.thumb.jpg.f15cd536ca02defac188b96b8261d702.jpg


 

no boot auto 2021-05-18_17-26_CLOVERX64.efi.log 6.43 kB · 0 downloads boot F10 OK 2021-05-18_17-27_CLOVERX64.efi.log 52.22 kB · 0 downloads

Dans le fichier "no boot auto 2021-05-18_17-26_CLOVERX64.efi.log", le log s'arrete dans le chargement des drivers. J'imagine un crash...

  • Like 1
Allan
Allan
Posted
Posted

OMG, Portuguese, French and English at the same time. Which one I can read?

 

So many options...:P

 

But guys, seriously, in English sections, just post in English. Post more than one language will not make the help that you want came quickly.

  • Like 1
SavageAUS
SavageAUS
Posted
Posted
It looks like new authors corrections in the driver. Should look.

It’s been like it for a while, I just used OC’s driver and it’s all good but if can update clovers it will save the hassle of replacing it.


Sent from my iPhone using Tapatalk
Jief_Machak
Jief_Machak
Posted
Posted

Cool cool with languages, guys. Skipping few messages that are not in English is not that big of a problem, right ?

We moved to private messages, so that's fine.

 

But in a general way, when a specific problem is identified, I think we should open issues on GitHub. It's easier to follow issues one by one instead of this big forum where more than on conversation are going on at the same time.

 

So, @AntarcticP and @PG7 : Could you open an issue on github. @PG7 You can open it in French, that's fine.

  • Like 5
  • Thanks 1
 Share
Go to topic listing
×
×
  • Create New...