Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,869 posts in this topic

Recommended Posts

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

 

Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted
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

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
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.

  • Thanks 2
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted
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.

Link to comment
Share on other sites
pkdesign
pkdesign
Posted
Posted (edited)
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
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted (edited)

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
  • Confused 1
Link to comment
Share on other sites
pkdesign
pkdesign
Posted
Posted (edited)
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
Link to comment
Share on other sites
Tobiko
Tobiko
Posted
Posted

 

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?

 

 

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
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:

 

Link to comment
Share on other sites
Tobiko
Tobiko
Posted
Posted (edited)

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
  • Like 1
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted
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

Link to comment
Share on other sites
apianti
apianti
Posted
Posted
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.........*

 

  • Thanks 1
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted

Error building 4848 with GCC  

/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:36:15: error: type of 'EmbeddedSound' does not match original declaration [-Werror=lto-type-mismatch]
 extern UINT8 *EmbeddedSound;
               ^
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/sound.c:1:7: note: 'EmbeddedSound' was previously declared here
 UINT8 EmbeddedSound[] = {
       ^
lto1: all warnings being treated as errors
lto-wrapper: fatal error: /Users/stlvnub/src/opt/local/cross/bin/x86_64-clover-linux-gnu-gcc returned 1 exit status
compilation terminated.
/Users/stlvnub/src/opt/local/cross/lib/gcc/x86_64-clover-linux-gnu/8.1.0/../../../../x86_64-clover-linux-gnu/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/DEBUG/CLOVER.dll] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

- Failed -
Build end time: 16:58:25, Jan.18 2019
Build total time: 00:00:43


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

  • Sad 1
Link to comment
Share on other sites
Dr. Hurt
Dr. Hurt
Posted
Posted
On 1/16/2019 at 2:53 AM, 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.

 

The boot chime works perfectly using AudioDXE.efi and BootChimeDXE.efi in the drivers64 folder. Those (and only those) two drivers are enough to get the chime going when the macOS boot entry is selected in Clover.

 

The only annoyance for me is that Clover takes 3 extra seconds to start. Hopefully that will be slightly optimized in the future.

 

PS. My laptop does have UEFI but its disabled. I'm using legacy boot.

 

  • Like 1
Link to comment
Share on other sites
WanderingAi
WanderingAi
Posted
Posted

I'm having a hard time setting my DefaultVolume in my config.plist, could someone please help me take a look at this bootlog and tell me what to put in the DefaultVolume field? I have tried reversing the endianness as someone suggested on another post ("C4B2367B74CD456F9E87FE3696F379E0"), as well as "Macintosh HD" and "7B36B2C4CD746F459E87FE3696F379E0" but it doesn't seem to work. Specifically, I am trying to set volume 09 as the boot default. I am able to set another drive without issue, so I don't think it's my config that is wrong...

  

1:784  0:002  - [08]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,AB2E508E48943E47B77B4294154D845B)
1:784  0:000          hiding this volume
1:784  0:000  - [09]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,7B36B2C4CD746F459E87FE3696F379E0)
1:784  0:000  - [10]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,085E15BDE052F446BB30B7D3714422FC)
1:784  0:000          hiding this volume
1:784  0:000  - [11]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,749023097C268C4D88A57ED372FE4D36)

--- SNIP ---

2:076  0:043  - [08]: 'Preboot', hidden
2:076  0:000  - [09]: 'Macintosh HD'
2:223  0:147          AddLoaderEntry for Volume Name=Macintosh HD
2:257  0:033      Check if volume Is Hibernated:
2:257  0:000      Check sleep image 'by signature':
2:297  0:040      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
2:297  0:000      using default sleep image name = \private\var\vm\sleepimage
2:329  0:031      sleepimage not found -> Not Found
2:329  0:000      hibernated: no - sign
2:333  0:004          [!] Icon 18 (icons\vol_internal_apfs.icns) not found (path: EFI\CLOVER\themes\Minimalism)
2:447  0:113  - [10]: 'Recovery', hidden
2:447  0:000  - [11]: 'VM'

 

Thanks!

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...