Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Badruzeus
Badruzeus
Posted
Posted (edited)

Hmmb, and it seems.. still has stability issue (at least, on my mach). ¯\_(ツ)_/¯

Previously worked fine with a same r4840, also a same *.wav.. but now I hear nothing after mach powered off.

Both sound.wav & sound_night.wav are available on my loaded "Theme Name" dir, though.

Ah, my eyes are sick reading what's "dmpstore -all > nvram.txt" wanna tell?

nvram_dmpstore_all_a43sj.txt.zip

Edited by Badruzeus
apianti
apianti
Posted
Posted
29 minutes ago, Badruzeus said:

Hmmb, and it seems.. still has stability issue (at least, on my mach). ¯\_(ツ)_/¯

Previously worked fine with a same r4840, also a same *.wav.. but now I hear nothing after mach powered off.

Both sound.wav & sound_night.wav are available on my loaded "Theme Name" dir, though.

Ah, my eyes are sick reading what's "dmpstore -all > nvram.txt" wanna tell?

 

This is device path protocol, so you are using new version which won't produce the string in nvram so incompatible with current clover: 

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 50                                               *P*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 00 1B 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

  • Thanks 1
Badruzeus
Badruzeus
Posted
Posted (edited)
17 minutes ago, apianti said:

This is device path protocol, so you are using new version which won't produce the string in nvram so incompatible with current clover: 


Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 50                                               *P*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 00 1B 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

 

Yeah, I have 3 diff. AudioDxe & BootChimeCfg depend on their commits on github AudioPkg project.
OK so.. to not make thing complicated, I rolling back using @Slice prebuilt since now. (not sure what has he done to make it becomes "compatible with current Clover" LoL).

Edited by Badruzeus
Andres ZeroCross
Andres ZeroCross
Posted
Posted (edited)
2 hours ago, apianti said:

Sorry forgot you need to specify -all or it doesn't dump anything but globals. 


dmpstore -all > nvram.txt

 

Sorry,, i have something to do before in real lif. Here is the nvram.txt

Edited by Andres ZeroCross
Andres ZeroCross
Andres ZeroCross
Posted
Posted
[mention=749318]apianti[/mention] BootChimeCfg may caused another problems in the future if you guys not also importing it into Clover, just guessing, since AudioPkg has rapid development and could be hard to resync from time to time _/|\_
I hope we can use bootchimedxe.efi too. Sound before apple loading bar is funny for me (like real mac)

Sent from my Mi Note 2 using Tapatalk

2 hours ago, apianti said:

 

Yeah, that's why I wanted to see the variable value. I imagine he is still using the older version though, which could also have an issue with matching the string.

 

 

These are unrelated problems. For the sound.wav to sound_night.wav, yes that is problem for raster theme as I posted before. For your own sounds, see here:

 



It works now,, i use BootChimeCfg.efi and AudioDxe.efi from Slice Prebuilt. So what's wrong?? BootChimeCfg.efi (to generate variable value in nvram) or AudioDxe.efi??

apianti
apianti
Posted
Posted (edited)
1 hour ago, Badruzeus said:

 

Yeah, I have 3 diff. AudioDxe & BootChimeCfg depend on their commits on github AudioPkg project.
OK so.. to not make thing complicated, I rolling back using @Slice prebuilt since now. (not sure what has he done to make it becomes "compatible with current Clover" LoL).

 

The previous version of AudioPkg used the device path string, which is not compatible across firmware as each does it differently. This is the one clover currently uses. The newest version uses the device path protocol, which is uniform across firmwares, and what clover should be changed to use. It really only takes reading the variable differently then converting it to a string in the way clover does for every device path protocol, then it will work again with newest. However, it might just be better to remove from clover and have external dependency on AudioPkg instead, since it is better to let Goldfish64 maintain the sound devices then add more to clover that will lag behind.

 

1 hour ago, Andres ZeroCross said:

Sorry,, i have something to do before in real lif.

 

No problem, me too. Yeah its same issue, it set device path protocol in nvram instead of string: 

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 64                                               *d*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 03 1F 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

50 minutes ago, Andres ZeroCross said:

I hope we can use bootchimedxe.efi too. Sound before apple loading bar is funny for me (like real mac)

It works now,, i use BootChimeCfg.efi and AudioDxe.efi from Slice Prebuilt. So what's wrong?? BootChimeCfg.efi (to generate variable value in nvram) or AudioDxe.efi??

 

Problem is with mismatching versions that do different things. The correct way is to set the device path protocol, so the newest AudioPkg is what should be done. Clover needs fixed to work with it as it uses older device path string method which is not reliable. Just make sure you use the binaries slice provided for now.

 

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

Edited by apianti
  • Like 1
  • Thanks 1
LockDown
LockDown
Posted
Posted
7 minutes ago, apianti said:

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

If we use the newer version of Goldfish, should we use both of his AudioDxe & BootChimeDxe or only the BooChimeDxe?

apianti
apianti
Posted
Posted
13 minutes ago, ellaosx said:

If we use the newer version of Goldfish, should we use both of his AudioDxe & BootChimeDxe or only the BooChimeDxe?

 

You need to use all three binaries from his newest in that case. Make sure clover does not have a sound(_night).wav present in your theme.

  • Thanks 1
Andres ZeroCross
Andres ZeroCross
Posted
Posted
24 minutes ago, apianti said:

 

The previous version of AudioPkg used the device path string, which is not compatible across firmware as each does it differently. This is the one clover currently uses. The newest version uses the device path protocol, which is uniform across firmwares, and what clover should be changed to use. It really only takes reading the variable differently then converting it to a string in the way clover does for every device path protocol, then it will work again with newest. However, it might just be better to remove from clover and have external dependency on AudioPkg instead, since it is better to let Goldfish64 maintain the sound devices then add more to clover that will lag behind.

 

 

No problem, me too. Yeah its same issue, it set device path protocol in nvram instead of string: 


Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 64                                               *d*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 03 1F 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

 

Problem is with mismatching versions that do different things. The correct way is to set the device path protocol, so the newest AudioPkg is what should be done. Clover needs fixed to work with it as it uses older device path string method which is not reliable. Just make sure you use the binaries slice provided for now.

 

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.


I don't understand about New and old. Can we say The prebuilt AudioDxe.efi and BootChimeCfg.efi from Slice are Older??? And AudioDxe.efi and BootChimeCfg.efi from GoldenFixh are New???

i try boot with AudioDxe.efi and BootChimeCfg.efi from Slice and use BootChimeDxe.efi from Golden fish, sound from Clover theme is loaded and good and chime sound from BootChimeDxe.efi is good too. But i can't enter desktop screen. There is no loading bar progress,,, i should delete bootchimedxe.efi to boot (i delete it from Shell)

 

apianti
apianti
Posted
Posted
Just now, Andres ZeroCross said:


I don't understand about New and old. Can we say The prebuilt AudioDxe.efi and BootChimeCfg.efi from Slice are Older??? And AudioDxe.efi and BootChimeCfg.efi from GoldenFixh are New???

i try boot with AudioDxe.efi and BootChimeCfg.efi from Slice and use BootChimeDxe.efi from Golden fish, sound from Clover theme is loaded and good and chime sound from BootChimeDxe.efi is good too. But i can't enter desktop screen. There is no loading bar progress,,, i should delete bootchimedxe.efi to boot (i delete it from Shell)

 

 

They are both from Goldfish64, it's just there are changes in the source to change the behavior. You need to use the matching binaries from the same version. Read my previous comment.

Andres ZeroCross
Andres ZeroCross
Posted
Posted
4 minutes ago, apianti said:

 

You need to use all three binaries from his newest in that case. Make sure clover does not have a sound(_night).wav present in your theme.


I Read this,, so i can use CLOVER r4840 without editing / commenting some line in Clover file first???? if yes, i can try it right now

Andres ZeroCross
Andres ZeroCross
Posted
Posted (edited)
1 hour ago, apianti said:

 

They are both from Goldfish64, it's just there are changes in the source to change the behavior. You need to use the matching binaries from the same version. Read my previous comment.

I used AudioDxe.efi, BootChimeDxe.efi and BootChimeCfg.efi from GoldFish64. Just put sound.wav in Theme Folder
So
1. My time is 21.00 here, so it's night.. I reset NVRAM from clover. AFter that set Audio and volume from shell with BootChimeCfg.efi. And boot to desktop and reboot. And when i boot again, i only can hear sound from BootChimeDxe.efi, no sound from Theme Sound (Sound before CLOVER GUI). I generate Preboot.log before boot and i see log about "no sound found". I think this's because my time. so i set my time to 13.15 (day time). And reboot,

2. And i got No sound from Theme Sound (sound before CLOVER GUI),, boot into desktop and i only can hear Chime from BootChimeDXE.efi only. I pressed F2  and get preboot.log  before and i see "no AudioIo".

So, what's wrong??? What should i do to get sound from Theme and sound from BootChimeDxe.efi????

i use Clover r4840.

Edited by Andres ZeroCross
  • Sad 1
Slice
Slice
Posted
Posted

It's a pity Goldfish64 changed definition for "device" variables without back compatibility.

See how apple does: 

efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>33D4733F-CBAF-4B8E-A33E-6EB6244C5BF2</string></dict></dict></dict></array>
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%07%00%00%00%c0Y%c3%1e%00%00%00%00%a81l%06%00%00%00%00?s%d43%af%cb%8eK%a3>n%b6$L[%f2%02%02%7f%ff%04%00

Same but different representation.

 

I will propose to create own audio configurator as Clover already knows all audio devices. Just give user a choice for output number and volume.

Also I can think about digital sound and about Speaker/Headphone autoswitch absent in original driver by Goldfish64.

Just take a time.

  • Like 2
Andres ZeroCross
Andres ZeroCross
Posted
Posted
5 minutes ago, Slice said:

It's a pity Goldfish64 changed definition for "device" variables without back compatibility.

See how apple does: 


efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>33D4733F-CBAF-4B8E-A33E-6EB6244C5BF2</string></dict></dict></dict></array>
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%07%00%00%00%c0Y%c3%1e%00%00%00%00%a81l%06%00%00%00%00?s%d43%af%cb%8eK%a3>n%b6$L[%f2%02%02%7f%ff%04%00

Same but different representation.

 

I will propose to create own audio configurator as Clover already knows all audio devices. Just give user a choice for output number and volume.

Also I can think about digital sound and about Speaker/Headphone autoswitch absent in original driver by Goldfish64.

Just take a time.


And i hope you can consider make BootChimeDxe.efi for boot chime before loading bar and sound theme of clover be friendly. It will perfect if we can hear sound befor / after GUI CLOVER. just my opinion

Dr. Hurt
Dr. Hurt
Posted
Posted (edited)

Sorry if this has been asked before, but how do I get the boot chime with Clover legacy?

 

Which files do I need and where do I put them? Also, any changes needed in config? 

I'm using embedded theme.

 

Edit: Got it to work. A users' guide would still be useful though.

Edited by Dr. Hurt
  • Confused 1
Andres ZeroCross
Andres ZeroCross
Posted
Posted
12 minutes ago, al6042 said:

Just tried the last official clover release 4842 and got the following errors while trying to check and configure BootChimeCfg.efi on my H170N-Wifi and Prime Z390-A:

1084557407_Clover4842-BootChimeCfg-Error.thumb.jpg.2f40e28621bd940ff562811527013050.jpg

 

Did I miss something?

 


It's look you don't have AudioDxe.efi in drivers64UEFI

 

Andres ZeroCross
Andres ZeroCross
Posted
Posted
14 minutes ago, al6042 said:

That I noticed by myself in the meantime...

Question is:

Why is BootChimeCfg.efi in an official release, but not AudioDxe.efi?

 


Because AudioDxe.efi from GoldFish64 use different method to read nvram variable for Audio Device with old ones (Slice's prebuilt).

You can use Prebuilt AudioDxe.efi and BootChimeCfg.efi from here 

 

Andres ZeroCross
Andres ZeroCross
Posted
Posted
9 hours ago, apianti said:

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

 

So i reconfigure my system. Update my CLOVER to r4842 from here https://github.com/Dids/clover-builder/releases . I remove AudioDxe.efi, BootChimeDxe.efi, BootChimeCfg.efi. Then,

1. Boot into Clover GUI and Reset nvram. Press F11 in CLOVER GUI
2. Boot into mac desktop and add AudioDxe.efi to drivers64UEFi and BootChimeCfg.efi to tools and just use sound.wav into Theme folder (BGM_SVG) then reboot to CLOVER GUI (AudioDxe.efi and BootChimeCfg.efi is from here


3. Enter shell and set "bootchimecfg.efi -s 7 -v 100 -t". I use 7 because my lineout is 7
4. Boot into mac then reboot again,, i can hear sound before GUI CLOVER. then i boot to mac desktop.
5. I add BootChimeDxe.efi from GoldFish64 https://github.com/Goldfish64/AudioPkg to drivers64UEFI then i Reboot.

Finally i can hear sound from Theme Sound and sound before loading progress too.

Here the video, sorry for bad english. I attach nvram.txt and preboot.log.

Thanks before

 

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