Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

24 minutes ago, Slice said:

Why I will bother about OpenCore Shell.efi?

20 pages back on this topic, it's still no clear solution yet till date, honestly:

On another side, @apianti ever said; it could be issue with specific firmware.. or Shell version matching.

Using OpenCore Shell is a solution that I've found (on my case), beside using old version of your Shell.

Edited by Badruzeus
Link to comment
Share on other sites

16 hours ago, Badruzeus said:

20 pages back on this topic, it's still no clear solution yet till date, honestly:

On another side, @apianti ever said; it could be issue with specific firmware.. or Shell version matching.

Using OpenCore Shell is a solution that I've found (on my case), beside using old version of your Shell.

OpenCore Shell https://github.com/acidanthera/OpenCoreShell

is present as a series of patches to EDK2 and to Shell. I think I implemented all of them. If not correct me.

And yes, EnglishDxe.efi required for some UEFI BIOSes.

10 hours ago, ellaosx said:

No, its not. i have it loaded. The rest of my hacks works

May be you have unsupported Audio hardware. Show me dump from VoodooHDA or from DarwinDumper.

  • Thanks 1
Link to comment
Share on other sites

43 minutes ago, chris1111 said:

Why puting AudioDxe mandatory commit 4843 

my opinion it should by drivers-off 

Else you will not hear sound.

There is a big question who is mandatory.

 

@Badruzeus

Test, please, this version

Shell.efi-DEBUG.zip

You may start it from some other shell just to see messages on screen.

Link to comment
Share on other sites

5 hours ago, ellaosx said:

i got voodohda dump now.

 

voodoohda_dump.txt

 

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

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.

Link to comment
Share on other sites

16 hours ago, Slice said:

 

@Badruzeus

Test, please, this version

Shell.efi-DEBUG.zip

You may start it from some other shell just to see messages on screen.

 

(Late reply, sorry)

With EnglishDxe.efi is installed on ..\drivers64UEFI, using Shell.efi as..

 

\EFI\CLOVER\tools\Shell64U.efi (via Clover UEFI) = BestLanguage (

ESP Root\SHELLX64.EFI (Launch EFI Shell via AMI Aptio v2.0.1 BIOS) = Screenshot below:

Thanks. 

Launch_EFI_Shell_AMI_Aptio.png

Edited by Badruzeus
Link to comment
Share on other sites

5 hours ago, Badruzeus said:

 

(Late reply, sorry)

With EnglishDxe.efi is installed on ..\drivers64UEFI, using Shell.efi as..

 

\EFI\CLOVER\tools\Shell64U.efi (via Clover UEFI) = BestLanguage (

ESP Root\SHELLX64.EFI (Launch EFI Shell via AMI Aptio v2.0.1 BIOS) = Screenshot below:

Thanks. 

Launch_EFI_Shell_AMI_Aptio.png

This ASSERT will not be if EnglishDxe.efi is loaded because it installs UnicodeCollation protocol.

  • Like 1
Link to comment
Share on other sites

Yeah, those "Assertion" when I launched your EFI Shell Debug directly from BIOS (not Clover).

If versioning is important, these what I got from different Shell's (via Clover Bootloader):

Thanks.

// EFI Shell from EDK2 r28597 or UDK2018 (Legacy w/o EnglishDxe):
UEFI Interactive Shell v2.204
EDK II
UEFI v2.70 (CLOVER, 0x000112EC)
  
// EFI Shell from old Clover rev (UEFI + EnglishDxe, https://ptpb.pw/~Shell2.zip)
UEFI Interactive Shell v2.0
Copyright 2009-2011 Intel(r) Corporation.
UEFI v2.00 (American Megatrends, 0x0004027B)

// OpenCore Shell (UEFI + EnglishDxe, https://github.com/acidanthera/OpenCoreShell)
UEFI Interactive Shell v2.2
EDK II
UEFI v2.00 (American Megatrends, 0x0004027B)

 

Edited by Badruzeus
  • Like 1
Link to comment
Share on other sites

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

Link to comment
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

Link to comment
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
Link to comment
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 ...

 

Link to comment
Share on other sites

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!

  • Haha 1
Link to comment
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
Link to comment
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
Link to comment
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

 

 

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...