Jump to content
30960 posts in this topic

Recommended Posts

Thanks, working fine with r4842 even with latest AudioPkg (AudioDxe, BootChimeCfg), except... after power loss..

 

 

Seems, not related to Clover but NVRAM on my buggie firmware. It always broken after power outage (my laptop has faulty battery, sorry). On this case I need to boot into Windows (UEFI) via "Boot Manager" (not Clover) to get a working NVRAM again. Using this method however, "Windows Boot Manager" would be set as 1st Boot upon System Reboot and it overrides Clover (that I previously set as 1st through BIOS). Sounds silly, right? And sometimes "nvram -c / Clover's F11" not help at all for unknown reason. No problem on another laptop with (also) AMI Aptio.
 

 

Edited by Badruzeus
  • Like 1
7 minutes ago, Slice said:

Because  my Shell is better. It allows to edit config.plist which OpenCoreShell is not able.

OK, thanks.. not a proposition, just my thought if it' s possible looks like..

1. There's an Option on Clover package [ ] Tools: Shell (3rd party)

2. If user check it, provided Shell by Clover will be overrided by that one.

Nevermind, I'm still able to run ebuild.sh then replace *.efi before ./makepkg (for my personal use).

16 minutes ago, Slice said:

Are you able exchange/move files by mouse or you need installer do the work?

tools/ folder is not selectable because these tools not influence on work. They just occupy several kilobytes.

(Sorry, I don't really get what your 1st line means actually)

Yes, I'm able to manually replace Clover's EFI Shell with OpenCore's one as \tools\Shell64U.efi (before ./makepkg or after *.pkg installed). Would be better (I think for some with similar issue) if Installer do the work (user defined).

Edited by Badruzeus
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
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
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.

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.

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

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

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
×
×
  • Create New...