Clover General discussion

corint1 · January 13, 2019

25 minutes ago, Badruzeus said:
Use this option on your config.plist:
	<key>GUI</key>
	<dict>
		...
		<key>Scan</key>
		<true/>
		...
	</dict>
thank you ... can you post an EFI folder with all files needed for activate sound ? I do not manage or did not understand what to do ...

Badruzeus · January 13, 2019

@corint1 well explained here, AudioDxe-64.efi is already included into Clover package (installer) since r4843.

Thanks.

STLVNUB · January 13, 2019

10 minutes ago, Badruzeus said:

@corint1 well explained here, AudioDxe-64.efi is already included into Clover package (installer) since r4843.

Thanks.

Pity all the OTHER bits aren't included as well as this by itself is useless!

Badruzeus · January 13, 2019

16 minutes ago, STLVNUB said:

Pity all the OTHER bits aren't included as well as this by itself is useless!

Did you mean BootChimeCfg.efi? You could include it into package manually, right? Hah haa

But *.wav files? Oh sh*t.. it makes the *.pkg "Not Sexy", can't imagine sound.wav && sound_night.wav from \themes will increase some MegaBytes in size, not a big deal since users are still able to customize by their selves (I think).

Edited January 13, 2019 by Badruzeus

SavageAUS · January 13, 2019

Did you mean BootChimeCfg.efi? You could include it into package manually, right? Hah haa
But *.wav files? Oh sh*t.. it makes the *.pkg "Not Sexy", can't imagine sound.wav && sound_night.wav from \themes will increase some MegaBytes in size, not a big deal since users are still able to customize by their selves (I think).

Please how to include BootChimeCfg.efi into clover package?

Sent from my iPhone using Tapatalk

Did you mean BootChimeCfg.efi? You could include it into package manually, right? Hah haa
But *.wav files? Oh sh*t.. it makes the *.pkg "Not Sexy", can't imagine sound.wav && sound_night.wav from \themes will increase some MegaBytes in size, not a big deal since users are still able to customize by their selves (I think).

Please how to include BootChimeCfg.efi into clover package?

Sent from my iPhone using Tapatalk

Badruzeus · January 13, 2019

12 minutes ago, SavageAUS said:

Please how to include BootChimeCfg.efi into clover package?

I believe there's better way than this:

(Clover build root on my case is ~/udk, not ~/src)

Spoiler


// Update Clover
cd ~/udk/UDK2018/
svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover
cd Clover
./ebuild.sh --ext-co -fr

// Manually adding *.efi files (I have prebuilt AudioPkg binaries) 
cp ~/udk/EXT_PACKAGES/AudioPkg/UDK/Build/AudioPkg/RELEASE_XCODE5/X64/BootChimeCfg.efi ~/udk/UDK2018/Clover/CloverPackage/CloverV2/EFI/CLOVER/tools

// Make PKG (Sorry, 3rd party themes are excluded on my case)
cd ~/udk/UDK2018/Clover/CloverPackage/
./makepkg --nothemes

corint1 · January 13, 2019

It's working .... seems to be artificial and forced, but it works ...

Slice · January 13, 2019

12 hours ago, SavageAUS said:

Please how to include BootChimeCfg.efi into clover package?

Just place the file into this folder before creating the package.

LockDown · January 14, 2019

On 1/11/2019 at 2:29 PM, ellaosx said:

i got voodohda dump now.

voodoohda_dump.txt

Note: i am using applealc because voodoohda is only showing headphone & digital out.

On 1/11/2019 at 8:05 PM, Slice said:

OK, this is very problematic codec. I think BootChime can output to headphone. You have to choose this output in cfg and attach a headphone to hear something.

VoodooHDA can be tuned to use internal speaker. It was not happened because headphone has higher priority.

Change

nid20 config 0x90172110

nid30 config 0x02211020

I also think nid18 should be Microphone. I don't remember what is required config because I am not at home.

And nid19 is internal mic.

what will be my codec #?

<key>NodesToPatch</key>
<array>
<dict>
	<key>Codec</key>
	<integer>???</integer>
	<key>Config</key>
	<string>0x90172110</string>
	<key>Node</key>
	<integer>20</integer>
</dict>
</array>

Badruzeus · January 14, 2019

On 1/12/2019 at 1:59 PM, Slice said:

Clover package contains a shell that will work if launch it from clover.

OK, definitely it's possible with:

FS0:
cd EFI\CLOVER\tools
rm Shell64U.efi
cp Shell64.efi Shell64U.efi

I can run Legacy Shell version via UEFI > edit EFI\CLOVER\config.plist && save it as well but..

OFC "bcfg" is missing.. honestly, I don't really need bcfg since my AMI Bios comes with "Boot Entry" Options.

(Ah worse, nv vars are not saved using this.. #LoL)

From my test results with some of EFI Shell's, only v2.0 & v2.2 are running under UEFI.

Could be, limitation on my laptop with old AMI Aptio v2.01 firmware right?

No idea where these commits have gone (or replaced later with a better one), was from more than 5 years ago, I think #LoL

Spoiler


+  // dmazar: AMI Aptio 2.0 returns 0 as MaxVarSize - fix it
+  if (MaxVarSize <= 0) MaxVarSize = 16384;

_Shell2.zip

Slice · January 14, 2019

3 hours ago, ellaosx said:

what will be my codec #?


<key>NodesToPatch</key>
<array>
<dict>
	<key>Codec</key>
	<integer>???</integer>
	<key>Config</key>
	<string>0x90172110</string>
	<key>Node</key>
	<integer>20</integer>
</dict>
</array>

From your dump I see

Probing codec #0...
 HDA Codec #0: Realtek (Unknown)
 HDA Codec ID: 0x10ec0256

Your codec # is zero.

39 minutes ago, Badruzeus said:
OK, definitely it's possible with:
FS0:
cd EFI\CLOVER\tools
rm Shell64U.efi
cp Shell64.efi Shell64U.efi
I can run Legacy Shell version via UEFI > edit EFI\CLOVER\config.plist && save it as well but..

OFC "bcfg" is missing.. honestly, I don't really need bcfg since my AMI Bios comes with "Boot Entry" Options.

(Ah worse, nv vars are not saved using this.. #LoL)

From my test results with some of EFI Shell's, only v2.0 & v2.2 are running under UEFI.

Could be, limitation on my laptop with old AMI Aptio v2.01 firmware right?

No idea where these commits have gone (or replaced later with a better one), was from more than 5 years ago, I think #LoL
Reveal hidden contents
+  // dmazar: AMI Aptio 2.0 returns 0 as MaxVarSize - fix it
+  if (MaxVarSize <= 0) MaxVarSize = 16384;
_Shell2.zip

Because UEFI 2.0 has no UnicodeCollation protocol.

Badruzeus · January 14, 2019

2 minutes ago, Slice said:

Because UEFI 2.0 has no UnicodeCollation protocol.

Ah, OK.. no worry then; I can still use old version of your Shell via Clover UEFI.

Also thanks for "> edit config.plist" ability, it's useful feature which is better than I've to boot into Linux for fixing wrong config.

LockDown · January 15, 2019

Hi @Slice

Goldfish64's set the driver defaults to internal speakers or line out if not configured in shell. is it possible to do the same on your build?

pkdesign · January 16, 2019

On 1/8/2019 at 12:28 PM, Dr. Hurt said:

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.

I'm guessing us users with BIOS (non UEFI) motherboards are out of luck? I get sound when in Clover Shell but not during boot.

Edited January 16, 2019 by pkdesign

LockDown · January 16, 2019

1 hour ago, pkdesign said:

I'm guessing us users with BIOS (non UEFI) motherboards are out of luck? I get sound when in Clover Shell but not during boot.

I get both if i combine slice & Goldfish64

Badruzeus · January 16, 2019

Are these 2 NVRAM vars created by BootChimeCfg (red rectangles)?

Correct me if I'm wrong; can we run eg. this command via Terminal w/o Shell > fs0:\efi\clover\tools\bootchimecfg then?

sudo nvram specialbootdevice blah blah blah

Thanks.

[/spoler]

#EDIT: ..and I have this on my preboot logs with r4847:

nvram_dmpstore_all_a43sj.txt.zip

Edited January 16, 2019 by Badruzeus

pkdesign · January 16, 2019

14 hours ago, ellaosx said:

I get both if i combine slice & Goldfish64

What do you mean both? Could you tell me exactly what you did?

EDIT:
I added BootChimeDxe and got startup sound but immediately got red screen of death.

Edited January 16, 2019 by pkdesign

Tobiko · January 17, 2019

I am able to get the test sound from BootChime.Cfg.efi in shell but it doesn't play at boot and it doesn't play under the Startup sound options in Clover. My system is UEFI based.

I am using

AudioDxe-64.efi from v2.4k_r4848 in drivers64UEFI

and

BootChime.Cfg.efi and BootChimeDxe.efi from Goldfish64 AudioPKG in tools.

How to further trouble-shoot?

Matgen84 · January 17, 2019

6 minutes ago, Tobiko said:

I am able to get the test sound from BootChime.Cfg.efi in shell but it doesn't play at boot and it doesn't play under the Startup sound options in Clover. My system is UEFI based.

I am using

AudioDxe-64.efi from v2.4k_r4848 in drivers64UEFI

and

BootChime.Cfg.efi and BootChimeDxe.efi from Goldfish64 AudioPKG in tools.

How to further trouble-shoot?

Do you put sound file in your theme folder? I think you do not use BootChimeDxe.efi (it's a driver not a tool). Some others members can help you better than me.

Take a look for parameters:

Tobiko · January 17, 2019

Hi,

Thanks. I saw that thread. I used this as a guide but using the different file versions I mentioned. I use the Clovy theme which has a sound.wav in it. I also tried adding the sound.wav Slice provided to /EFI.

I tried it on my desktop and it worked fine using BootChime.Cfg.efi from GoldFish64, the AudioDXE-64 from Clover and the Clovy theme which has a sound.wav.

So on my laptop which is where this all started, I removed BootChimeDxe.efi rebooted, ran BootChime.Cfg.efi again it still worked from there. Cleared the NVRAM, ran BootChime.Cfg.efi and set up the device and volume again, rebooted a couple of times but still no luck. I even wiped clover and started fresh even recompiling the AudioPKG still not working on the Laptop. Just from the shell.

Edited January 17, 2019 by Tobiko
tried additional steps

Slice · January 17, 2019

Wait please...

Tobiko · January 17, 2019

1 hour ago, Slice said:

Wait please...

Ok.

Sherlocks · January 17, 2019

@vit9696

thank you for r4846 commit.

this is very great fix. i had problem unknown panic on sandy bridge laptop until this commit.

there is no more instant reboot issue

thanks

Badruzeus · January 17, 2019

58 minutes ago, Sherlocks said:

@vit9696

thank you for r4846 commit.

this is very great fix. i had problem unknown panic on sandy bridge laptop until this commit.

there is no more instant reboot issue

thanks

@Sherlocks Wait, Sandy? Seems no problem here.. but, my Mojave is using HFS+ since 10.14 till 10.14.3 #btw

Or could bcoz something else (we have diff. specs but CPU #LoL )

Oh hai, you didn't response my proposition yet since last year?

Spoiler


--- /Users/badruzeus/udk/UDK2018/Clover/rEFIt_UEFI/entry_scan/loader.c	2018-12-21 20:51:48.000000000 +0700
+++ /Users/badruzeus/src/edk2/Clover/rEFIt_UEFI/entry_scan/loader.c	2019-01-17 22:37:40.000000000 +0700
@@ -102,6 +102,9 @@
   { L"\\EFI\\goofiboot\\goofibootx64.efi", L"Solus EFI boot menu", L"solus,linux", "Solus" },
   { L"\\EFI\\centos\\grubx64.efi", L"CentOS EFI boot menu", L"centos,linux", "CentOS" },
   { L"\\EFI\\pclinuxos\\grubx64.efi", L"PCLinuxOS EFI boot menu", L"pclinux,linux", "PCLinux" },
+  { L"\\EFI\\neon\\grubx64.efi", L"KDE Neon EFI boot menu", L"neon,linux", "KDE Neon" },
+  { L"\\EFI\\MX18\\grubx64.efi", L"MX Linux EFI boot menu", L"mx,linux", "MX Linux" },
+  { L"\\EFI\\parrot\\grubx64.efi", L"Parrot OS EFI boot menu", L"parrot,linux", "Parrot OS" },
 #else
   { L"\\EFI\\grub\\grub.efi", L"Grub EFI boot menu", L"grub,linux" },
   { L"\\EFI\\Gentoo\\grub.efi", L"Gentoo EFI boot menu", L"gentoo,linux", "Gentoo" },
@@ -127,6 +130,9 @@
   { L"\\EFI\\goofiboot\\goofiboot.efi", L"Solus EFI boot menu", L"solus,linux", "Solus" },
   { L"\\EFI\\centos\\grub.efi", L"CentOS EFI boot menu", L"centos,linux", "CentOS" },
   { L"\\EFI\\pclinuxos\\grub.efi", L"PCLinuxOS EFI boot menu", L"pclinux,linux", "PCLinux" },
+  { L"\\EFI\\neon\\grub.efi", L"KDE Neon EFI boot menu", L"neon,linux", "KDE Neon" },
+  { L"\\EFI\\MX18\\grub.efi", L"MX Linux EFI boot menu", L"mx,linux", "MX Linux" },
+  { L"\\EFI\\parrot\\grub.efi", L"Parrot OS EFI boot menu", L"parrot,linux", "Parrot OS" },
 #endif
   { L"\\EFI\\SuSe\\elilo.efi", L"OpenSuse EFI boot menu", L"suse,linux" },
 };

Thank you before.. (y)

loader.c.patch.zip

apianti · January 17, 2019

On 1/16/2019 at 4:58 AM, Badruzeus said:
Are these 2 NVRAM vars created by BootChimeCfg (red rectangles)?

Correct me if I'm wrong; can we run eg. this command via Terminal w/o Shell > fs0:\efi\clover\tools\bootchimecfg then?
sudo nvram specialbootdevice blah blah blah
Thanks.

No, those are the macOS variables. These are the variables:

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 = 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.........*

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites