Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

 

1 hour ago, MICKHAEL said:
check this file

 

and if you could, share your r4833 build please

sound.wav

Will do when I get a chance.

I converted my file as slice described and also tried 1 and 2 channel but neither work. Hopefully his test file will work.

 

Edit: test file works fine so it’s my conversion.

 

Edit2: All working now. Attached mac startup chime working with clover for anyone who wants it.

 

Clover_v2.4k_r4833.pkg

 

macstart.wav

Edited by SavageAUS
Link to comment
Share on other sites

3 hours ago, Badruzeus said:

@Slice Following your guide, it doesn't work on my mach till I also placed "BootChimeDxe.efi" on ../drivers64UEFI

But weird is, I hear StartUp sound after Clover GUI, not before it.. on the contrary as what you said.

Anyway, I built AudioPkg under Linux with GCC5 (debbuild.sh), how if using macOS? Thanks.

r4833_plus_AudioPkg.zip

Try the file attached in the theme folder your currently using.

macstart.wav

Link to comment
Share on other sites

7 minutes ago, Slice said:

I propose to add AudioDxe into Clover instead of whole package.

For this moment you have to add ready-to-use-binaries.

 

Thanks for reply. I must use binaries. If I copy AudioPkg in src/UDK2018, I can't build Clover because I've this issue:

 

build.py...
/Users/mathieu/src/UDK2018/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	/Users/mathieu/src/UDK2018/AudioPkg/AudioPkg.dec

 

Link to comment
Share on other sites

You guys should definitely add a volume value for the chime...

 

I just checked the stuff on my Skylake WoodenBox with an Headset and it almost blew my head off....

Clearly you didn’t follow instructions.

 

 

 

Tuning.Before first start you have to tune your sound system.Start Clover, goto Shell.Shell> fs0:fs0:> cd EFI\CLOVER\toolsfs0:EFI\CLOVER\tools>BootChimeCfg.efiYou will see all options-l -- list all devices. See and choose.Then you have to configure and hear.BootChimeCfg.efi -s 1 -v 60 -t Audio Output=1 and Sound Volume=60% will be stored in NVRAM and will be used by Clover after next restart.

   

 

 

Edited by SavageAUS
Link to comment
Share on other sites

Hi Guys

 

Despite of Slice's guide, I haven't any sound: AudioDxe isn't compatible with external HDMI. I use Nvidia HDMI audio output on my desktop. :cry::cry::cry:

 

From Goldfish64 Readme file:

AudioPkg is a set of drivers/applications for supporting audio (currently only Intel HD audio) under UEFI.

 

Edited by Matgen84
Link to comment
Share on other sites

Tried it on a H170N-Wifi, which only uses the HD530.

Since the Boards has two HDMI outlets I tested the following on both HDMI ports, but couldn't get a tone out of it.Clover4833-1.thumb.jpg.c896f1ba1190e16d5da2cf5f31458e50.jpg

 

Switching to "-s 2" I could hear the chime, while i had a headset plugged in at green rear.

Link to comment
Share on other sites

I was off for some days. Maybe this has been explained already somewhere else. Anyway, my problem is that when building the current clover revision with Build Clover command, I get the following error:

 

Processing meta-data .

build.py...
~/src/edk2/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	~/src/edk2/AudioPkg/AudioPkg.de

How to solve this issue? 

  • Sad 1
Link to comment
Share on other sites

6 minutes ago, KGP-iMacPro said:

I was off for some days. Maybe this has been explained already somewhere else. Anyway, my problem is that when building the current clover revision with Build Clover command, I get the following error:

 


Processing meta-data .

build.py...
~/src/edk2/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	~/src/edk2/AudioPkg/AudioPkg.de

How to solve this issue? 

 

I think Build_Clover.command will be update. You can post this issue to the Build_Clover topic. 

  • Like 1
Link to comment
Share on other sites

5 hours ago, KGP-iMacPro said:

I was off for some days. Maybe this has been explained already somewhere else. Anyway, my problem is that when building the current clover revision with Build Clover command, I get the following error:

 


Processing meta-data .

build.py...
~/src/edk2/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	~/src/edk2/AudioPkg/AudioPkg.de

How to solve this issue? 

Rev 4834.

Just wonder how can I compile before.

  • Like 1
Link to comment
Share on other sites

16 hours ago, Matgen84 said:

Hi @Slice

 

Thanks for commit r4833: If I understand well Goldfish64's readme, it works only for Intel HD. My system use HDMI audio via my Nvidia graphic card. How can I have sound at startup on Clover GUI in this case. There is a solution.

 

No, it just doesn't work for HDMI or digital outputs, there are both intel and nvidia controllers and many audio codecs supported.

 

16 hours ago, Slice said:

VoodooHDA works with HDMI as well as with non-Intel chipsets so yes it's possible just requires a work.

 

Yes, just need to add digital support, but there is intel and nvidia chipsets support already, the only other one would be amd, that I know of. Don't confuse the controller chipset with the codec chipset.

https://en.wikipedia.org/wiki/Intel_High_Definition_Audio#Host_controller

https://en.wikipedia.org/wiki/Sound_card#Integrated_sound_hardware_on_PC_motherboards

Link to comment
Share on other sites

@Slice thank you for boot sound.

i have a question. how can i reset BootChimeCfg.efi(return original)?

also current gui screen -> play boot sound -> scan drive -> clover gui screen.

when play boot sound, hold 3sec(follow wav sound length), can we play boot sound with clover gui at the same time?

Edited by Sherlocks
Link to comment
Share on other sites

40 minutes ago, Sherlocks said:

@Slice thank you for boot sound.

i have a question. how can i reset BootChimeCfg.efi(return original)?

also current gui screen -> play boot sound -> scan drive -> clover gui screen.

when play boot sound, hold 3sec(follow wav sound length), can we play boot sound with clover gui at the same time?

Снимок экрана 2019-01-05 в 10.09.20.png

 I think -x will be answer to your question.

 

There is StartPlaybackAsync but it is still not full developed.

  • Like 2
Link to comment
Share on other sites

56 minutes ago, Sherlocks said:

@Slice thank you for boot sound.

i have a question. how can i reset BootChimeCfg.efi(return original)?

 

There are three variables in NVRAM if you want to trace it

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 3C                                               *<*
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 = 0xA2
  00000000: 50 00 63 00 69 00 52 00-6F 00 6F 00 74 00 28 00  *P.c.i.R.o.o.t.(.*
  00000010: 30 00 78 00 30 00 29 00-2F 00 50 00 63 00 69 00  *0.x.0.)./.P.c.i.*
  00000020: 28 00 30 00 78 00 31 00-42 00 2C 00 30 00 78 00  *(.0.x.1.B.,.0.x.*
  00000030: 30 00 29 00 2F 00 56 00-65 00 6E 00 4D 00 73 00  *0.)./.V.e.n.M.s.*
  00000040: 67 00 28 00 41 00 39 00-30 00 30 00 33 00 46 00  *g.(.A.9.0.0.3.F.*
  00000050: 45 00 42 00 2D 00 44 00-38 00 30 00 36 00 2D 00  *E.B.-.D.8.0.6.-.*
  00000060: 34 00 31 00 44 00 42 00-2D 00 41 00 34 00 39 00  *4.1.D.B.-.A.4.9.*
  00000070: 31 00 2D 00 35 00 34 00-30 00 35 00 46 00 45 00  *1.-.5.4.0.5.F.E.*
  00000080: 45 00 46 00 34 00 36 00-43 00 33 00 2C 00 30 00  *E.F.4.6.C.3.,.0.*
  00000090: 30 00 30 00 30 00 30 00-30 00 30 00 30 00 29 00  *0.0.0.0.0.0.0.).*
  000000A0: 00 00                                            *..*

 

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

Well, my friend's old Pentium laptop has no UEFI support (also non Hackintosh compatible), but he wants Windows UEFI on it so.. I converted whole Disk to GPT, manually created 200MB EFI using gParted under Ubuntu Live and set is as=boot,esp. I restored my prev. Windows 10 64-bit backup using G4L (Ghost for Linux) to a new NTFS partition (/dev/sda2), restoring EFI\Microsoft\ to ESP (/dev/sda1), repairing BCD with Windows PE (bootrec /RebuildBcd bla bla bla) and it's booting just fine using USB FlashDisk with Clover on it (following @fusion71au guide actually, thanks to him).

 

I then, manually installing Clover using Ubuntu Live into Internal EFI Partition (should be Legacy-GPT, but Windows is UEFI emulated, right?) Bootloader files used: boot (boot6) | boot0 (boot0af) | boot1 (boot1f32) \\Oh ya, I manually copying "BOOT && CLOVER" dir using FileManager, so not included on screenshot below LoL

 

Seems no problem with bootloader installation on Legacy as usual (I think, CMIIW), Windows is also booting fine.

The only issue is, everytime I powering on laptop it always goes to Firmware screen first (not laptop's BIOS) so I need to always pressing "Continue" to get Clover boot after it.

My questions are:

1. What's causing this issue? I've tried boot6 && boot7 with a same result #btw

2. How to set "Timeout" with only single boot volume (so I don't need to press KB key twice but just boot to Windows directly)? I realized it doesn't work here.

 

Thanks.

 

Screenshot from 2019-01-05 07-35-23.png

Edited by Badruzeus
Link to comment
Share on other sites

6 hours ago, Badruzeus said:

Well, my friend's old Pentium laptop has no UEFI support (also non Hackintosh compatible), but he wants Windows UEFI on it so.. I converted whole Disk to GPT, manually created 200MB EFI using gParted under Ubuntu Live and set is as=boot,esp. I restored my prev. Windows 10 64-bit backup using G4L (Ghost for Linux) to a new NTFS partition (/dev/sda2), restoring EFI\Microsoft\ to ESP (/dev/sda1), repairing BCD with Windows PE (bootrec /RebuildBcd bla bla bla) and it's booting just fine using USB FlashDisk with Clover on it (following @fusion71au guide actually, thanks to him).

 

I then, manually installing Clover using Ubuntu Live into Internal EFI Partition (should be Legacy-GPT, but Windows is UEFI emulated, right?) Bootloader files used: boot (boot6) | boot0 (boot0af) | boot1 (boot1f32) \\Oh ya, I manually copying "BOOT && CLOVER" dir using FileManager, so not included on screenshot below LoL

 

Seems no problem with bootloader installation on Legacy as usual (I think, CMIIW), Windows is also booting fine.

The only issue is, everytime I powering on laptop it always goes to Firmware screen first (not laptop's BIOS) so I need to always pressing "Continue" to get Clover boot after it.

My questions are:

1. What's causing this issue? I've tried boot6 && boot7 with a same result #btw

2. How to set "Timeout" with only single boot volume (so I don't need to press KB key twice but just boot to Windows directly)? I realized it doesn't work here.

 

Thanks.

 

You have a problem with NVRAM as nothing will ever be saved, you should replace the EmuVar module with the FSVariable module from DUET for some partial support. You can skip clover GUI entirely by just putting microsoft bootmgfw.efi as bootx64.efi.

 

EDIT: You may want to just use DUET actually.

EDIT2: Oh, actually I think the legacy firmware loads CLOVERX64.efi by default not BOOTX64.efi.

Edited by apianti
  • Thanks 1
Link to comment
Share on other sites

41 minutes ago, apianti said:

 

You have a problem with NVRAM as nothing will ever be saved, you should replace the EmuVar module with the FSVariable module from DUET for some partial support.

Hmmb that's why how many times I "Change Boot Order" on firmware it'll always reset to default after mach reboot, a same issue with VirtualBox even if configured as UEFI.. firmware configurations are not saved once app relaunched due to lack of NVRAM.

 

Funny thing here's (sorry, my bad); it boots directly into Clover w/o pressing "Continue" when I plugged Laptop's KeyBoard off (using USB ext-KB to replace it). I just realized that some Laptop's keys are broken (always keep pressed) after checking it using Keyboard Test software under Windows. I think they prevent (or suspend) Clover boot.

 

41 minutes ago, apianti said:

You can skip clover GUI entirely by just putting microsoft bootmgfw.efi as bootx64.efi.

Oh great, thank you. Much better idea with single Windows boot (though, I never tried this before.. honestly)

 

But my friend now (seems) feel happy using Clover bcoz he could place his gf's photo on it (I believe in his mind, Clover=Theme not a Boot Manager LoL).

 

Edited by Badruzeus
Link to comment
Share on other sites

4 hours ago, Badruzeus said:

Hmmb that's why how many times I "Change Boot Order" on firmware it'll always reset to default after mach reboot, a same issue with VirtualBox even if configured as UEFI.. firmware configurations are not saved once app relaunched due to lack of NVRAM.

 

Funny thing here's (sorry, my bad); it boots directly into Clover w/o pressing "Continue" when I plugged Laptop's KeyBoard off (using USB ext-KB to replace it). I just realized that some Laptop's keys are broken (always keep pressed) after checking it using Keyboard Test software under Windows. I think they prevent (or suspend) Clover boot.

 

Oh great, thank you. Much better idea with single Windows boot (though, I never tried this before.. honestly)

 

Yeah but it boots directly into clover with the usb right? So I doubt the keyboard is the issue, although maybe who knows... I know the NVRAM is for sure as there is no way to save the nvram.plist from windows to be loaded later. The FSVariable module from DUET saves the variable store when exiting boot services instead, so no runtime changes are saved but at least your would get semi working nvram. Either that or write an administrator app or kernel driver that dumps the uefi variables into a plist on the ESP. You might want to read my edit in the previous post about the default boot as I forgot it is different for clover legacy firmware, although if he wants to keep it whatever, lol. You can set DefaultVolume to the ESP (which you can get from log) and the DefaultLoader to \EFI\Microsoft\Boot\bootmgfw.efi, then set Timeout to whatever and it should automatically boot. As for the FSVariable module you can edit Clover.fdf and uncomment the line for it and comment out the other lines for NVRAM below or you can try using -DREAL_NVRAM to build and see if the real nvram can be used, however, I'm not sure how safe that is.

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...