Jump to content
ErmaC

Clover General discussion

19,695 posts in this topic

Recommended Posts

Advertisement
21 hours ago, Slice said:

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

Weird is, now I'm also having a same issue even running Clover's UEFI Shell through VM (VirtualBox)..

with or w/o drivers64UEFI/EnglishDxe-64.efi installed.

Screenshot 26.png

Share this post


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

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

how is working ? how activate or run or enter in shell mode ? what must be make for this efi shell ? tky

Share this post


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

how is working ? how activate or run or enter in shell mode ? what must be make for this efi shell ? tky

Use this option on your config.plist:

	<key>GUI</key>
	<dict>
		...
		<key>Scan</key>
		<true/>
		...
	</dict>



Screenshot 27.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
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 ...

 

Share this post


Link to post
Share on other sites
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).



Screenshot 28.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
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).




485626210_Screenshot28.png.b68bb56d4847f18c39b7ead94c74862b.png




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).




485626210_Screenshot28.png.b68bb56d4847f18c39b7ead94c74862b.png




Please how to include BootChimeCfg.efi into clover package?


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
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

 

 

Share this post


Link to post
Share on other sites
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>

 

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

 

_Shell2.zip

Because UEFI 2.0 has no UnicodeCollation protocol.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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 by pkdesign

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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.

 

 

 

nvram -p.png
[/spoler]

 

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

 

preboot.png

 

nvram_dmpstore_all_a43sj.txt.zip

Edited by Badruzeus

Share this post


Link to post
Share on other sites
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 by pkdesign

Share this post


Link to post
Share on other sites

 

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?

 

 

Share this post


Link to post
Share on other sites
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:

 

Share this post


Link to post
Share on other sites

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 by Tobiko
tried additional steps

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 Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
×