Jump to content
ErmaC

Clover General discussion

20,705 posts in this topic

Recommended Posts

Advertisement

Cool. The startup sound now plays on my laptop with 4855. Without using BootChimeCfg then clearing NVMRAM, I can set the volume and device output variable with Clover. The volume is saved but the device output isn't. So I still have to use BootChimeCfg in order to save all the parameters to NVRAM. 

 

You guys are mad geniuses. 

Edited by Tobiko
Had extra words

Share this post


Link to post
Share on other sites

I have a diff, but it based on revision 4853.  I never blame Slice, since he was always faster than me.

This patches contain some fixes for audio volume, port and also device to work with/from GUI and BootChimeCfg.

Please do check -or- take some -or- improve as usual and sync it with latest revision.

 

*update attachment

 

diff.diff.zip

Edited by cecekpawon

Share this post


Link to post
Share on other sites
[mention=112217]Slice[/mention] audio does not work on the bootloader and there is no option to change the volume to the clover GUI

234198530_Schermata2019-01-21alle09_45_42.thumb.png.056cfe49b046b032d14be6e6473dd51d.png

You mean the volume of the startup sound?

 

Does it work from Shell? Can you test the sound from there?

 

Cause there is an option in Clover’s GUI for that. You can see it in one of my screenshots above. But last time I tried it, it didn’t work very well (reset itself to 0000 when trying to change the volume). So I used BootChimeCfg.efi, accessed from Shell to adjust the volume. It’s a workaround.

 

You have to make sure you’re using the latest build. 4851 had some issues. But 4853 worked perfectly fine for me (aside from the GUI issues I mentioned above).

Share this post


Link to post
Share on other sites
12 minutes ago, Emanuele-1998 said:

@Slice audio does not work on the bootloader and there is no option to change the volume to the clover GUI

 

Can you give me preboot.log?

And wait for next Clover revision with some bugs corrected.

27 minutes ago, cecekpawon said:

Please take whatever it needs Slice _/|\_

Some notes.

1. I don't like ReallocatePool when we deal with 20*sizeof(HDA_OUTPUTS) bytes. May be 30 but not more.

2. F7 souldn't play sound file because it may absent. It's better to test hardware on a sound we sure to be playable.

3. About gSettings I am not decided finally. Keep only AudioVolume? What about other audio settings?

4. Currently we using gBootChimeVendorVariableGuid as Goldfish64 do. But it is not good for legacy Clover. May be remake to gAppleBootGuid? In this case we got saving audio parameters even with legacy Clover but we will loose original project compatibility.

 

PS. I need some ideas why PlayAsync is not working.

Share this post


Link to post
Share on other sites
22 minutes ago, Slice said:

Can you give me preboot.log?

And wait for next Clover revision with some bugs corrected.

Some notes.

1. I don't like ReallocatePool when we deal with 20*sizeof(HDA_OUTPUTS) bytes. May be 30 but not more.

2. F7 souldn't play sound file because it may absent. It's better to test hardware on a sound we sure to be playable.

3. About gSettings I am not decided finally. Keep only AudioVolume? What about other audio settings?

4. Currently we using gBootChimeVendorVariableGuid as Goldfish64 do. But it is not good for legacy Clover. May be remake to gAppleBootGuid? In this case we got saving audio parameters even with legacy Clover but we will loose original project compatibility.

 

@Slice I switched to 4855 and it works but the audio output does not remain fixed and when restarting it disappears remaining unchecked, then I can not boot via the HDMI because they are still in the process of being true?

 

I send you an example video, also as you can see the start of the clover gui is very slow even in the latest stable version, and pressing U that would be the button to shut down causes a bug.

1CE18938-4024-4443-8747-FCF1FC2883A7.jpeg

Edited by Emanuele-1998

Share this post


Link to post
Share on other sites

I switched to Clover r4855 without BootChimeCfg.efi and, as it turned out, Clover immediately writes the wrong value to NVRAM (got index=-1003609600, which cannot be changed without BootChimeCfg.efi). At the same time, it records the correct volume value (volume 90 received). It does not matter whether the audio output settings menu was used or not. In my configuration, hardware NVRAM is running. Therefore, I do not use EmuVariableUefi-64.efi and not nravam.plist :( If I boot from the flash drive which BootChimeCfg.efi and fix the output, then the value (got index = -1003609600) changes to the correct one, and the sound appears before loading Clover.

Edited by MakAsus

Share this post


Link to post
Share on other sites

@Slice

latest clover r4856, everything is good. thank you for update.

can we have chance to reset nvram(F11) lnclude BootChime GUID(initialized like factory)?

is BootChime GUID unique guid for only audiodxe.efi? not common?

 

also can we have chance for boot sound when showing apple log like BootChimeDxe.efi?

 

thanks in advance

 

EDIT1.

in r4856, sound.wav quality is bad. i listened original sound with electronic. i used sound.wav file from clovy theme folder

3:810  0:000  === [ InitTheme ] =========================================
3:810  0:000  use daylight theme
3:812  0:001  Using theme 'bootcamp' (EFI\CLOVER\themes\bootcamp)
3:812  0:000  Warning! Character width 9 should be even!
3:812  0:000    Channels: 2  Sample rate: 8000 Hz  Bits: 16
3:812  0:000  output to channel -780514048 with volume 80, len=75200
3:812  0:000   sound channels=2 bits=16 freq=8000
3:812  0:000  sound converted to 48kHz
6:448  2:635  Loading font from ThemeDir: Error
6:449  0:000  theme inited
6:449  0:000  Chosen theme bootcamp

Edited by Sherlocks

Share this post


Link to post
Share on other sites

Personally, I feel like having the startup sound before the UI is more realistic. But...an option to select to play it before or after, yeah, that would be interesting to have. I personally prefer it just the way it is now, meaning before the UI. I feel like it's closer to what real Macs do. But as I said, an option to choose which one you want, that would be interesting.

Edited by arsradu

Share this post


Link to post
Share on other sites
3 hours ago, arsradu said:

Personally, I feel like having the startup sound before the UI is more realistic. But...an option to select to play it before or after, yeah, that would be interesting to have. I personally prefer it just the way it is now, meaning before the UI. I feel like it's closer to what real Macs do. But as I said, an option to choose which one you want, that would be interesting.

Honestly, using AudioDxe, BootChimeDxe & BootChimeCfg from @Goldfish64 repo I can hear sound before - after Clover GUI since r4843 w/o issue, except my nvram is going crazy (sometimes).

Share this post


Link to post
Share on other sites

Hi

 

Sorry for questions for dummies:

  • I can't find internal speakers output in clover audio setting and rear output
  • Clover GUI seems to be slower at startup
  • I can't keep settings after reboot (I only use AptioMemoryFix): I must use emuvariable, Right.

Thanks

screenshot1.thumb.png.65f151987db067259d254065a903f400.png

Share this post


Link to post
Share on other sites
19 hours ago, Slice said:

3. About gSettings I am not decided finally. Keep only AudioVolume? What about other audio settings?

4. Currently we using gBootChimeVendorVariableGuid as Goldfish64 do. But it is not good for legacy Clover. May be remake to gAppleBootGuid? In this case we got saving audio parameters even with legacy Clover but we will loose original project compatibility.

 

3. It would be nice if Clover have own config (plist) including audio device, portindex, and also volumelevel. You may take this as example. User can grab device & port_index values from log and store it to config plist (I have log those values on my prev diff).

4. For nvram values, Clover can read values from gBootChimeVendorVariableGuid (if any) as 1st attempt, read from gAppleBootGuid as 2nd attempt, and fallback to user config plist values as last attempt, then save it to from gBootChimeVendorVariableGuid (+ gAppleBootGuid, meh!).

 

19 hours ago, Slice said:

PS. I need some ideas why PlayAsync is not working.

 

Have not tried it with Clover yet, will do. (already discussed with dev days ago about async playback here).

 

18 hours ago, MakAsus said:

value (got index = -1003609600)

 

17 hours ago, Sherlocks said:

output to channel -780514048

 

@MakAsus @Sherlocks seems you have bad values stored to nvram.

 

17 hours ago, Sherlocks said:

also can we have chance for boot sound when showing apple log like BootChimeDxe.efi?

 

Having those option in Clover is also great. But why you dont just install BootChimeDxe.efi for that purpose?

* AudioDxe will should much more useful to enhanced the GUI like this instead of just greeting sound

 

 

* link removed

Edited by cecekpawon

Share this post


Link to post
Share on other sites
39 minutes ago, Matgen84 said:

Hi

 

Sorry for questions for dummies:

  • I can't find internal speakers output in clover audio setting and rear output
  • Clover GUI seems to be slower at startup
  • I can't keep settings after reboot (I only use AptioMemoryFix): I must use emuvariable, Right.

Thanks

screenshot1.thumb.png.65f151987db067259d254065a903f400.png

 

1. Well, I think your Realtek ALC892_Headphones should also be your "internal speakers". They're usually paired in switch mode. 

Rear output should probably be Realtek ALC892_LineOut (the first one). Actually, they're most likely all Rear Outs... Just...different ports for different speakers. But the first one is probably mapped as the Green one. So that's why I said the first one.

 

2. Yeah, it's been reported before. It might be intended though... Not sure.

 

3. Mmm...which system are you trying this on? Isn't your system using native NVRAM? If not, I think AptioMemoryFix should be enough. But I'm not sure Clover is working in cooperation with it...yet. If your other NVRAM related settings are saved, I'd say this is probably a Clover issue and it doesn't work with AptioMemoryFix quite yet. I don't know. I might be talking stupid. So don't take my word for it.

 

Thing is, depending on your system, you might or might not need AptioMemoryFix for NVRAM. I do not think you need EmuVariable. And especially you shouldn't be using both at the same time.

Edited by arsradu

Share this post


Link to post
Share on other sites
10 minutes ago, arsradu said:

 

1. Well, I think your Realtek ALC892_Headphones should also be your "internal speakers". They're usually paired in switch mode. 

Rear output should probably be Realtek ALC892_LineOut (the first one). Actually, they're most likely all Rear Outs... Just...different ports for different speakers. But the first one is probably mapped as the Green one. So that's why I said the first one.

 

2. Yeah, it's been reported before. It might be intended though... Not sure.

 

3. Mmm...which system are you trying this on? Isn't your system using native NVRAM? If not, I think AptioMemoryFix should be enough. But I'm not sure Clover is working in cooperation with it...yet. If your other NVRAM related settings are saved, I'd say this is probably a Clover issue and it doesn't work with AptioMemoryFix quite yet. I don't know. I might be talking stupid. So don't take my word for it.

 

Thing is, depending on your system, you might or might not need AptioMemoryFix for NVRAM. I do not think you need EmuVariable. And especially you shouldn't be using both at the same time.

 

Thanks for reply :)

 

  1. I don't think Realtek ALC892_Headphones is Internal speakers and Rear output is not Realtek ALC892_LineOut (the first one). Both don't work in Clover options. Bootchimecfg.efi show Internal speakers in list output, mapped with rear green one.
  2. OK
  3. I don't know if my mobo 'Asus p8z77-v Pro' support native NVRAM. My other settings are saved.

Wait and see others commits :yes:

Share this post


Link to post
Share on other sites
2 minutes ago, Matgen84 said:

 

Thanks for reply :)

 

  1. I don't think Realtek ALC892_Headphones is Internal speakers and Rear output is not Realtek ALC892_LineOut (the first one). Both don't work in Clover options. Bootchimecfg.efi show Internal speakers in list output, mapped with rear green one.
  2. OK
  3. I don't know if my mobo 'Asus p8z77-v Pro' support native NVRAM. My other settings are saved.

Wait and see others commits :yes:

 

None of them will work in Clover options. :) That's a bug. If you wanna test them and set your boot chime, you need to use BootChimeCfg from Shell for now. As for your motherboard, I think all motherboards until Skylake (series 100) should have native NVRAM. So the issue might be somewhere else in your case.

Share this post


Link to post
Share on other sites
46 minutes ago, Matgen84 said:

 

Thanks for reply :)

 

  1. I don't think Realtek ALC892_Headphones is Internal speakers and Rear output is not Realtek ALC892_LineOut (the first one). Both don't work in Clover options. Bootchimecfg.efi show Internal speakers in list output, mapped with rear green one.
  2. OK
  3. I don't know if my mobo 'Asus p8z77-v Pro' support native NVRAM. My other settings are saved.

Wait and see others commits :yes:

Show me, please, voodoohda dump. I want to see if a problem with output configuration can be resolved by some patch like voodoohda do.

Share this post


Link to post
Share on other sites

Cod work. It seems that it began to work correctly. The startup sound now plays on my computer with rev. 4857. Without using BootChimeCfg then clearing NVMRAM, I can set the volume and device output variable with Clover. The volume and device output are saved to NVRAM. Respect! :)


7:841  0:000  found 3 handles with audio

7:841  0:000  got index=2

7:841  0:000  got volume 90

——————————————————————————————————

8:451  0:000  Using vector theme 'Clovy' (EFI\CLOVER\themes\Clovy)

8:468  0:017    Channels: 2  Sample rate: 44100 Hz  Bits: 16

8:468  0:000  output to channel 2 with volume 90, len=451584

8:468  0:000   sound channels=2 bits=16 freq=44100

11:364  2:895  theme inited

Share this post


Link to post
Share on other sites
13 hours ago, MakAsus said:

Cod work. It seems that it began to work correctly. The startup sound now plays on my computer with rev. 4857. Without using BootChimeCfg then clearing NVMRAM, I can set the volume and device output variable with Clover. The volume and device output are saved to NVRAM. Respect! :)

 


7:841  0:000  found 3 handles with audio

7:841  0:000  got index=2

7:841  0:000  got volume 90

——————————————————————————————————

8:451  0:000  Using vector theme 'Clovy' (EFI\CLOVER\themes\Clovy)

8:468  0:017    Channels: 2  Sample rate: 44100 Hz  Bits: 16

8:468  0:000  output to channel 2 with volume 90, len=451584

8:468  0:000   sound channels=2 bits=16 freq=44100

11:364  2:895  theme inited

 

I was just finishing compiling Clover when I saw your message. :)) Yeah, Clover 4857's UI seems to work a little better now. I was able to change the volume, without resetting itself, and select different outputs.

 

Things left to fix, for what I could see:

 

1. update the UI according to the previously saved configuration, when entering that menu.

 

Meaning: even though the settings are correctly saved, and the output you select is the one which will be used on the next reboot, it's still not correctly read when coming back to that menu. For example, although I'm using Device Output #8 in that list, when I enter that menu, it still displays the first one in the list as selected.

 

It looks like it's writing correctly to NVRAM, but it's not reading correctly from it. At least when it comes to the selected device output. It does display the volume correctly though. But not the device.

 

2. F7 still doesn't work yet. I understand it might be trickier to fix than it seems. :)

 

So...if you already know which device to choose from that list, yes, you can set it up from that UI and be done with it in a second. But if you don't...you might have to set each one of them individually and see which one works and also, which one suits your needs the best. Similar to what you would currently do using BootChimeCfg actually.

 

Other than that, just like you said: respect! Nice job!

 

Update:

 

Ok, it looks like it's more complicated than it seems in regards to bug nr 1. It DOES display them correctly when coming back to that menu, but for some reason, not all of them... Also, selecting some of them will freeze the UI. More details below.

 

So, these the options I've got. I selected option #8 just because that's what I'm using, not because that's what it was displaying when I opened this menu.

 

Now, all AMD options (options 1-6 in the list) are selectable, though no sound is coming out for this case. I understand this is a limitation of BootChime's implementation..? I could be wrong. Or at least it's not implemented yet. Point is, I'm not gonna say anything about it being functional or not if I'm not sure it should be.

 

Anwyay, selecting any of them will be actually saved and displayed correctly when coming back here. These are the only ones that are displayed. Anything else you select from the list below will be applied (correctly set), but not correctly displayed. Meaning they won't be displayed as selected when coming back to this menu.

 

Option 7 (Intel Haswell HDMI_HDMI) is not correctly displayed. I haven't tested the sound itself, since I'm not using the HDMI port on my motherboard. So it might work, but it probably doesn't, since it's still HDMI and it's not supported yet.

 

Now begins the interesting part:

 

Options 8 and 10 (Realtek ALC892_LineOut) work fine in terms of actual sound, but they're not displayed as selected.

Options 9, 11 and 12 (Realtek ALC892_LineOut and Realtek ALC892_Headphones) will freeze the UI if selected.

 

Screenshot2.thumb.png.656384b663a24974a704a1d05d3e946a.png

Edited by arsradu

Share this post


Link to post
Share on other sites
1 hour ago, MakAsus said:

Cod work. It seems that it began to work correctly. The startup sound now plays on my computer with rev. 4857. Without using BootChimeCfg then clearing NVMRAM, I can set the volume and device output variable with Clover. The volume and device output are saved to NVRAM. Respect! :)

 

Same. 

 

Awesome!

 

Is there a way to get rid of the metallic sound of the wav? It played clearly testing with BootChimeCfg but when hitting F7 in the Clover options and when it plays automatically it is buzzy.  My desktop it plays fine. Stupid laptop. 

Edited by Tobiko

Share this post


Link to post
Share on other sites
Hi [mention=112217]Slice[/mention]
Regarding the timezone feature, mine is +8. Should i write +8 or only 8?

Just 8 should be fine. I’m +9.5 and I do just 9 or 10 I can’t remember which.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ajmcello
      The following files exist on the github:
       
      a) Clover.app-v1.11-5100.zip
      b) Clover_v2.5k_r5100.pkg
      c) CloverISO-5100.tar.lzma
      d) CloverV2-5100.zip
      e) CLOVERX64.efi.zip
       
       
      Is (a) for installing as an app on OSX? What is it for?
       
      What is (b) for, the .pkg? Not exactly familiar with .pkg. I've seen it used in UNIX, but I believe it's also a PKG format for installing packages on OSX. So, what is the difference between this (b), and (a)? (a) is labeled v1.11-5100, while (b) is labeled v2.5k_r5100.
      (c) contains only this file, Clover-v2.5k-5100-X64.iso, which I assume is a pre-bootloader.
      (d) looks like the NON ISO version, to build an ISO?
      (e) Contains CLOVERX64.efi, which is the same CloverX64.efi for Clover.app-v1.11-5100 and CloverV2-5100.zip
       
      Thanks for any explanations. 
       

       
       
       
       
    • By Dolamarv
      Hi all, I have been using an x240 thinkpad for more than 2 months as hackintosh and it is very stable. As of now I am in Catalina 10.15.1 and it’s running great until I updated it to the new clover build r5100. My laptop won’t automatically sleep when I close the lid down now. I reverted back to 5099 and close-lid automatic sleep works. I don’t know what caused the problem but I think 5100 fixed a dsdt patching of some sort that that conflicted with my config plist? Thanks in advance!
    • By Aldaro
      Gigabyte, in their infinite wisdom, decided to remove the option to disable serial ports, and not being able to do so has been causing me some problems. I know that I have to either use a patch in clover, or create a custom SSDT to disable super I/O, but I honestly do not know how to go about doing this. One of the weirder problems I'm experiencing is the inability to connect to Apple Music (error 11556) unless I go into my network settings, and delete my serial connection. If anyone could help me out with this, that'd be greatly appreciated; anyway, thank you for taking the time to read this.
       
      SPECS:
      Mobo GIGABYTE Z390 M GAMING (UEFI F8)
      CPU: i5 9600k
      RAM: 32GB DDR4 @ 2666 Mhz
      GPU: AMD Radeon RX 580 w/ 8GB of VRAM (MSI armor oc edition)
      Storage Samsung 970 evo 500GB
    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
×