Clover General discussion

[prcmelo]

I got it working when I press ENTER on the drive to boot, and for me it's ok this way.

 

But I can't get the "output volume" to work. No matter the value I put... it will always play at maximum volume, and it's a huge BAAAAAMMMMMM!!!! 

 

Anyone knows how to fix it? Using Clover r4862 and ALC1150.

 

EDIT: I forgot to mention that F7 sound preview is also not working for me.

Edited January 31, 2019 by prcmelo

[SavageAUS]

I got it working when I press ENTER on the drive to boot, and for me it's ok this way.

 

But I can't get the "output volume" to work. No matter the value I put... it will always play at maximum volume, and it's a huge BAAAAAMMMMMM!!!! 

 

Anyone knows how to fix it? Using Clover r4862 and ALC1150.

 

EDIT: I forgot to mention that F7 sound preview is also not working for me.

How have you tried to configure output volume? Clover GUI or UEFI shell with BootChimeCfg?

It may help to clean nvram variables for bootchime before setting new values.

ALC1150 works great on my board using BootChimeCfg to configure. Have yet to test clovers GUI to configure output.

 

 

Sent from my iPhone using Tapatalk

[prcmelo]

4 minutes ago, SavageAUS said:

How have you tried to configure output volume? Clover GUI or UEFI shell with BootChimeCfg?


Sent from my iPhone using Tapatalk

 

Hi, Savage!

 

In both ways, Clover GUI doesn't matter the value I pu there...

 

and with BootChimeCfg in UEFI Shell give me an error, something like "path not found", even with the file inside Clover Tools folder...

 

Shell> fs0:

fs0:> cd EFI\CLOVER\tools

fs0:EFI\CLOVER\tools>BootChimeCfg.efi (Here is where I can't go on, with an error)

 

I'm using this pattern:

 

if you want to one chime when pressing enter in macOS Partition then just use 
1. AudioDxe.efi
2. BootchimeDxe.efi
3. Don't put any sound wav file in theme folder

 

And using these files r4864_AudoDxe_Goldfish64.zip

 

 

[arsradu]

50 minutes ago, prcmelo said:

 

Hi, Savage!

 

In both ways, Clover GUI doesn't matter the value I pu there...

 

and with BootChimeCfg in UEFI Shell give me an error, something like "path not found", even with the file inside Clover Tools folder...

 

Shell> fs0:

fs0:> cd EFI\CLOVER\tools

fs0:EFI\CLOVER\tools>BootChimeCfg.efi (Here is where I can't go on, with an error)

 

I'm using this pattern:

 

if you want to one chime when pressing enter in macOS Partition then just use 
1. AudioDxe.efi
2. BootchimeDxe.efi
3. Don't put any sound wav file in theme folder

 

And using these files r4864_AudoDxe_Goldfish64.zip

 

You have to find your Clover partition first. Especially if you've got multiple drives. Then cd into it.

 

FS0 is only an example. In my case, the Clover on my SSD is on FS11. So, check your partitions and choose the correct one.

 

In order to make sure you're on the right one, or at least on a partition that also has Clover on it, you can use the TAB key to autocomplete the path. IF it autocompletes the path when you type for example "cd EFI/CL...." and it autocompletes to "CLOVER", then you know you're in the right place. Or at least you're on a partition with Clover on it. Which is a good start.

 

You can use Clover Configurator for that. There might be easier ways to do this... This is just the one I used.

 

You need to find your boot partition first. In my case, it's on disk0s1. Then take a note of the Disk UUID. Then, when in Shell, try to see which partition has that UUID associated to it. Then you can use fs[number] and then continue with the rest of the tutorial.

 

Edited January 31, 2019 by arsradu

[prcmelo]

4 minutes ago, arsradu said:

 

You have to find your Clover partition first. Especially if you've got multiple drives. Then cd into it.

 

FS0 is only an example. In my case, the Clover on my SSD is on FS11. So, check your partitions and choose the correct one.

 

In order to make sure you're on the right one, or at least on a partition that also has clover on it, you can use the TAB key to autocomplete the path. IF it autocompletes the path when you type for example "cd EFI/CL...." and it autocompletes to "CLOVER", then you know you're on the right place. Or at least you're on a partition with Clover on it. Which is a good start.

 

asradu...

 

Understood!!!! I'll check it later when in home and try to configure the output volume with BootChimeCfg.

 

Thanks a lot!!!! 

[Wackymac]

is there a way to have the boot chime play through a USB DAC?

[Slice]

4 hours ago, prcmelo said:

I got it working when I press ENTER on the drive to boot, and for me it's ok this way.

 

But I can't get the "output volume" to work. No matter the value I put... it will always play at maximum volume, and it's a huge BAAAAAMMMMMM!!!! 

 

Anyone knows how to fix it? Using Clover r4862 and ALC1150.

 

EDIT: I forgot to mention that F7 sound preview is also not working for me.

Current revision 4870 has a big difference in sound support compared to 4862.

[prcmelo]

44 minutes ago, Slice said:

Current revision 4870 has a big difference in sound support compared to 4862.

Thank you, Slice!!!!

 

Would you mind give me a link for r4870?

 

Thanks again!!!!

 

 

[iCanaro]

qui https://github.com/Dids/clover-builder/releases

[prcmelo]

Thank you, iCanaro!!!!

 

 

[arsradu]

24 minutes ago, prcmelo said:

Thank you, iCanaro!!!!

 

Looks like today you learned two things.  How to navigate in Shell, in order to find your Clover boot drive. And learned about the existence of a Clover builder github page. Pretty cool knowledge for one day.  

 

Personally, I prefer to build it myself. The Dids builds, while very useful, seem to use some weird parameters to uncheck some of the default drivers in the installer (not sure why), which I don't particularly like. But if you're careful during installation, and check those boxes back again, you should be good to go.

Edited January 31, 2019 by arsradu

[iCanaro]

always and only customized installations (ad hoc)  or just cloverx64.efi

[prcmelo]

Now it's working fine! 

 

I've managed to do it through Shell!

 

Thanks... SavageAUS, arsradu, Slice, iCanaro 

[pkdesign]

Just to throw my 2 cents into the chime discussion:

 

I put AudioDxe.efi and BootChimeDxe.efi from the AudioPkg-R1-RELEASE into both the drivers64 and drivers64UEFI folders, and have PlayASYNC=False in config and I get the classic Mac boot chime right when I see the Apple logo appears on screen. Exactly the behavior I want!

 

Not sure I actually need the PlayASYNC switch but it works so I won’t touch it. Maybe I will test it later.

 

If you look at my signature you will see I am on an old non-UEFI motherboard.

[prcmelo]

13 minutes ago, pkdesign said:

Just to throw my 2 cents into the chime discussion:

 

I put AudioDxe.efi and BootChimeDxe.efi from the AudioPkg-R1-RELEASE into both the drivers64 and drivers64UEFI folders, and have PlayASYNC=False in config and I get the classic Mac boot chime right when I see the Apple logo appears on screen. Exactly the behavior I want!

 

Not sure I actually need the PlayASYNC switch but it works so I won’t touch it. Maybe I will test it later.

 

If you look at my signature you will see I am on an old non-UEFI motherboard.

Almost the same as you...

 

- I have AudioDxe-64.efi (from clover r4870), and BootChimeDxe.efi from AudioPkg-R1-RELEASE only at Drivers64UEFI...

 

- BootChimeCfg.efi and  HDACodecDump.efi (I'm not sure if I need this last one) from AudioPkg-R1-RELEASE at Clover\Tools...

 

- And no PlayASYNC in config.

 

With that I have the Mac Boot Chime only when I see the Apple Logo on screen. So, I think you don't need PlayASYNC at config.

[arsradu]

45 minutes ago, prcmelo said:

Almost the same as you...

 

- I have AudioDxe-64.efi (from clover r4870), and BootChimeDxe.efi from AudioPkg-R1-RELEASE only at Drivers64UEFI...

 

- BootChimeCfg.efi and  HDACodecDump.efi (I'm not sure if I need this last one) from AudioPkg-R1-RELEASE at Clover\Tools...

 

- And no PlayASYNC in config.

 

With that I have the Mac Boot Chime only when I see the Apple Logo on screen. So, I think you don't need PlayASYNC at config.

1 hour ago, pkdesign said:

Just to throw my 2 cents into the chime discussion:

 

I put AudioDxe.efi and BootChimeDxe.efi from the AudioPkg-R1-RELEASE into both the drivers64 and drivers64UEFI folders, and have PlayASYNC=False in config and I get the classic Mac boot chime right when I see the Apple logo appears on screen. Exactly the behavior I want!

 

Not sure I actually need the PlayASYNC switch but it works so I won’t touch it. Maybe I will test it later.

 

If you look at my signature you will see I am on an old non-UEFI motherboard.

 

PlayAsync actually doesn't have anything to do with any of that.

 

Play Async only refers to the portion before the Apple logo and the loading animation (before Clover UI to be precise), and consists of two modes:

 

1. in Sync -> the sound is played before Clover GUI and the UI is displayed after the sound has finished playing -> PlayAsync=False

2. Async -> the sound is played before the Clover GUI and continues to play when the UI is ready. -> PlayAsync=True

 

This is with Clover's implementation. What you guys are using right now is GoldFish's implementation, which will play the sound (packed into the BootChimeDxe.efi file) when selecting a boot drive (so AFTER the Clover GUI is loaded). So, for this case, PlayAsync = True or False will actually make no difference whatsoever, since you're not using Clover's implementation.

 

To me, what Clover did is closer to what's happening on real Macs. And I personally prefer it this way. But if that doesn't work for you guys, or if you prefer it after the Clover GUI, when the Apple logo is displayed, that's definitely an option.

Edited February 1, 2019 by arsradu

[prcmelo]

asradu,

 

Thanks for the clarification 

I'm thinking about to try "Sync" to see the result! 

 

After using Mac Boot Chime I have noticed an increased time until reaching the Clover GUI, and also at the end of the boot, it seems that the progress bar, just below the Apple logo, is stopped for a longer time until it reaches the Desktop.

 

Don't know if it's normal or only with me.

[arsradu]

26 minutes ago, prcmelo said:

asradu,

 

Thanks for the clarification 

I'm thinking about to try "Sync" to see the result! 

 

After using Mac Boot Chime I have noticed an increased time until reaching the Clover GUI, and also at the end of the boot, it seems that the progress bar, just below the Apple logo, is stopped for a longer time until it reaches the Desktop.

 

Don't know if it's normal or only with me.

 

Now that you know your way around the GoldFish method, why not give Clover implementation a try?

 

For this, you don't need BootChimeCfg or BootChimeDxe. You only need AudioDxe, added by Clover during installation.

 

All you need is the sound.wav file, configured correctly, placed inside your selected theme folder. The attached file works perfectly fine for me. So you can use it if you want to. The volume can be adjusted from Clover GUI -> Options -> Startup Sound. For 60%, you should type 0060. Also here you should be able to select the output device (you should already know which one it is from configuring it from Shell). After that, select Return to go back to main screen, Restart, and...hopefully it should work.

 

Now, in case the device output selection didn't go so well for you, you can still configure it from Shell, using BootChimeCfg.efi. Just the way you did before. The difference is that, if you removed BootChimeDxe, you should only have one startup sound, the one from the theme, and it should be played before the UI is loaded. You can still keep BootChimeDxe if you want...but it will play both sounds. :)) Which...well, I don't know why would you want that.

 

By default, PlayAsync should be OFF, so it will be "in Sync", meaning the UI will wait for the sound to finish playing before getting display. Personally, I prefer PlayAsync=True for two reasons: it takes less time to boot (since the UI usually finishes loading faster than the sound finishes playing), and it's closer to real Macs experience, in my opinion. But nobody's stopping you from trying both, if you want. As I said, by default, it will be the one you want, meaning "in Sync"

 

sound.wav

Edited February 1, 2019 by arsradu

[ktwist]

Is something significant has changed since clover v 48xx? I can't update clover past version 479x and get mojave to boot properly.

[arsradu]

15 minutes ago, ktwist said:

Is something significant has changed since clover v 48xx? I can't update clover past version 479x and get mojave to boot properly.

 

Not that I know of. I mean, there shouldn't be any significant changes that would cause boot issues... But if you could provide more information on what happens exactly, that might help. Maybe a boot log. You could boot in verbose mode and see where does it get stuck. You might need to update your drivers, in case you haven't already. So...there could be multiple issues. But I personally haven't encountered such issues. So...maybe you can also upload your Clover folder for a deeper analysis? You can remove the serials from your config.plist/smbios.

 

Also, I think it might help a lot to know which hardware are you using. Could you, please, update your signature to include this information?

Edited February 1, 2019 by arsradu

[iCanaro]

50 minutes ago, ktwist said:

Is something significant has changed since clover v 48xx? I can't update clover past version 479x and get mojave to boot properly.

with mojave 10.14.4beta the kernel has been changed and to start it it is necessary to at least clover 2.4_4862 

[isleeptill12]

Been trying to get the boot chime using the goldfish method but can't get it to work.

 

In the clover gui under startup sound output, I only have options for HDMI out through my GPU.

My realtek codec is ALC891 and I'm using layout=13 in my config.plist

I also tried updating clover to v4870 but I get the same result.

[LockDown]

It has nothing to do with layout. Configure it using bootchimecfg in shell.

[prcmelo]

5 hours ago, arsradu said:

 

Now that you know your way around the GoldFish method, why not give Clover implementation a try?

 

 

Thanks, asradu!

 

I did the "Clover way", and I must confess, it's better! From now I'm leaving Mac Boot Chime before Clover GUI 

 

But my boot time is still taking a long time since the implementation of Boot Chime, takes age at something like "gtrace synchronization point" or something like that.

 

Thank you again!!!!

[isleeptill12]

53 minutes ago, ellaosx said:

It has nothing to do with layout. Configure it using bootchimecfg in shell.

 

I just tried to configure using bootchimecfg in shell, same result. Only shows HDMI outputs, no realtek outputs.