Jump to content
About Just Joined group Read more... ×
ErmaC

Clover General discussion

24,284 posts in this topic

Recommended Posts

2 hours ago, apianti said:

Sorry forgot you need to specify -all or it doesn't dump anything but globals.


dmpstore -all > nvram.txt

 

Sorry,, i have something to do before in real lif. Here is the nvram.txt

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
Advertisement
[mention=749318]apianti[/mention] BootChimeCfg may caused another problems in the future if you guys not also importing it into Clover, just guessing, since AudioPkg has rapid development and could be hard to resync from time to time _/|\_
I hope we can use bootchimedxe.efi too. Sound before apple loading bar is funny for me (like real mac)

Sent from my Mi Note 2 using Tapatalk

2 hours ago, apianti said:

 

Yeah, that's why I wanted to see the variable value. I imagine he is still using the older version though, which could also have an issue with matching the string.

 

 

These are unrelated problems. For the sound.wav to sound_night.wav, yes that is problem for raster theme as I posted before. For your own sounds, see here:

 



It works now,, i use BootChimeCfg.efi and AudioDxe.efi from Slice Prebuilt. So what's wrong?? BootChimeCfg.efi (to generate variable value in nvram) or AudioDxe.efi??

Share this post


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

 

Yeah, I have 3 diff. AudioDxe & BootChimeCfg depend on their commits on github AudioPkg project.
OK so.. to not make thing complicated, I rolling back using @Slice prebuilt since now. (not sure what has he done to make it becomes "compatible with current Clover" LoL).

 

The previous version of AudioPkg used the device path string, which is not compatible across firmware as each does it differently. This is the one clover currently uses. The newest version uses the device path protocol, which is uniform across firmwares, and what clover should be changed to use. It really only takes reading the variable differently then converting it to a string in the way clover does for every device path protocol, then it will work again with newest. However, it might just be better to remove from clover and have external dependency on AudioPkg instead, since it is better to let Goldfish64 maintain the sound devices then add more to clover that will lag behind.

 

1 hour ago, Andres ZeroCross said:

Sorry,, i have something to do before in real lif.

 

No problem, me too. Yeah its same issue, it set device path protocol in nvram instead of string:

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 64                                               *d*
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: 03 1F 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.........*

 

50 minutes ago, Andres ZeroCross said:

I hope we can use bootchimedxe.efi too. Sound before apple loading bar is funny for me (like real mac)

It works now,, i use BootChimeCfg.efi and AudioDxe.efi from Slice Prebuilt. So what's wrong?? BootChimeCfg.efi (to generate variable value in nvram) or AudioDxe.efi??

 

Problem is with mismatching versions that do different things. The correct way is to set the device path protocol, so the newest AudioPkg is what should be done. Clover needs fixed to work with it as it uses older device path string method which is not reliable. Just make sure you use the binaries slice provided for now.

 

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

Edited by apianti

Share this post


Link to post
Share on other sites
7 minutes ago, apianti said:

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

If we use the newer version of Goldfish, should we use both of his AudioDxe & BootChimeDxe or only the BooChimeDxe?

Share this post


Link to post
Share on other sites
13 minutes ago, ellaosx said:

If we use the newer version of Goldfish, should we use both of his AudioDxe & BootChimeDxe or only the BooChimeDxe?

 

You need to use all three binaries from his newest in that case. Make sure clover does not have a sound(_night).wav present in your theme.

Share this post


Link to post
Share on other sites
24 minutes ago, apianti said:

 

The previous version of AudioPkg used the device path string, which is not compatible across firmware as each does it differently. This is the one clover currently uses. The newest version uses the device path protocol, which is uniform across firmwares, and what clover should be changed to use. It really only takes reading the variable differently then converting it to a string in the way clover does for every device path protocol, then it will work again with newest. However, it might just be better to remove from clover and have external dependency on AudioPkg instead, since it is better to let Goldfish64 maintain the sound devices then add more to clover that will lag behind.

 

 

No problem, me too. Yeah its same issue, it set device path protocol in nvram instead of string:


Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 64                                               *d*
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: 03 1F 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.........*

 

 

Problem is with mismatching versions that do different things. The correct way is to set the device path protocol, so the newest AudioPkg is what should be done. Clover needs fixed to work with it as it uses older device path string method which is not reliable. Just make sure you use the binaries slice provided for now.

 

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.


I don't understand about New and old. Can we say The prebuilt AudioDxe.efi and BootChimeCfg.efi from Slice are Older??? And AudioDxe.efi and BootChimeCfg.efi from GoldenFixh are New???

i try boot with AudioDxe.efi and BootChimeCfg.efi from Slice and use BootChimeDxe.efi from Golden fish, sound from Clover theme is loaded and good and chime sound from BootChimeDxe.efi is good too. But i can't enter desktop screen. There is no loading bar progress,,, i should delete bootchimedxe.efi to boot (i delete it from Shell)

 

Share this post


Link to post
Share on other sites
Just now, Andres ZeroCross said:


I don't understand about New and old. Can we say The prebuilt AudioDxe.efi and BootChimeCfg.efi from Slice are Older??? And AudioDxe.efi and BootChimeCfg.efi from GoldenFixh are New???

i try boot with AudioDxe.efi and BootChimeCfg.efi from Slice and use BootChimeDxe.efi from Golden fish, sound from Clover theme is loaded and good and chime sound from BootChimeDxe.efi is good too. But i can't enter desktop screen. There is no loading bar progress,,, i should delete bootchimedxe.efi to boot (i delete it from Shell)

 

 

They are both from Goldfish64, it's just there are changes in the source to change the behavior. You need to use the matching binaries from the same version. Read my previous comment.

Share this post


Link to post
Share on other sites
4 minutes ago, apianti said:

 

You need to use all three binaries from his newest in that case. Make sure clover does not have a sound(_night).wav present in your theme.


I Read this,, so i can use CLOVER r4840 without editing / commenting some line in Clover file first???? if yes, i can try it right now

Share this post


Link to post
Share on other sites
27 minutes ago, Andres ZeroCross said:


I Read this,, so i can use CLOVER r4840 without editing / commenting some line in Clover file first???? if yes, i can try it right now

in my experience, i needed to edit it regardless if youl use old or new 

Share this post


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

 

They are both from Goldfish64, it's just there are changes in the source to change the behavior. You need to use the matching binaries from the same version. Read my previous comment.

I used AudioDxe.efiBootChimeDxe.efi and BootChimeCfg.efi from GoldFish64. Just put sound.wav in Theme Folder
So
1. My time is 21.00 here, so it's night.. I reset NVRAM from clover. AFter that set Audio and volume from shell with BootChimeCfg.efi. And boot to desktop and reboot. And when i boot again, i only can hear sound from BootChimeDxe.efi, no sound from Theme Sound (Sound before CLOVER GUI). I generate Preboot.log before boot and i see log about "no sound found". I think this's because my time. so i set my time to 13.15 (day time). And reboot,

2. And i got No sound from Theme Sound (sound before CLOVER GUI),, boot into desktop and i only can hear Chime from BootChimeDXE.efi only. I pressed F2  and get preboot.log  before and i see "no AudioIo".

So, what's wrong??? What should i do to get sound from Theme and sound from BootChimeDxe.efi????

i use Clover r4840.

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites

It's a pity Goldfish64 changed definition for "device" variables without back compatibility.

See how apple does:

efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>33D4733F-CBAF-4B8E-A33E-6EB6244C5BF2</string></dict></dict></dict></array>
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%07%00%00%00%c0Y%c3%1e%00%00%00%00%a81l%06%00%00%00%00?s%d43%af%cb%8eK%a3>n%b6$L[%f2%02%02%7f%ff%04%00

Same but different representation.

 

I will propose to create own audio configurator as Clover already knows all audio devices. Just give user a choice for output number and volume.

Also I can think about digital sound and about Speaker/Headphone autoswitch absent in original driver by Goldfish64.

Just take a time.

Share this post


Link to post
Share on other sites
5 minutes ago, Slice said:

It's a pity Goldfish64 changed definition for "device" variables without back compatibility.

See how apple does:


efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>33D4733F-CBAF-4B8E-A33E-6EB6244C5BF2</string></dict></dict></dict></array>
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%07%00%00%00%c0Y%c3%1e%00%00%00%00%a81l%06%00%00%00%00?s%d43%af%cb%8eK%a3>n%b6$L[%f2%02%02%7f%ff%04%00

Same but different representation.

 

I will propose to create own audio configurator as Clover already knows all audio devices. Just give user a choice for output number and volume.

Also I can think about digital sound and about Speaker/Headphone autoswitch absent in original driver by Goldfish64.

Just take a time.


And i hope you can consider make BootChimeDxe.efi for boot chime before loading bar and sound theme of clover be friendly. It will perfect if we can hear sound befor / after GUI CLOVER. just my opinion

Share this post


Link to post
Share on other sites

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.

Edited by Dr. Hurt

Share this post


Link to post
Share on other sites

Just tried the last official clover release 4842 and got the following errors while trying to check and configure BootChimeCfg.efi on my H170N-Wifi and Prime Z390-A:

1084557407_Clover4842-BootChimeCfg-Error.thumb.jpg.2f40e28621bd940ff562811527013050.jpg

 

Did I miss something?

 

Share this post


Link to post
Share on other sites
12 minutes ago, al6042 said:

Just tried the last official clover release 4842 and got the following errors while trying to check and configure BootChimeCfg.efi on my H170N-Wifi and Prime Z390-A:

1084557407_Clover4842-BootChimeCfg-Error.thumb.jpg.2f40e28621bd940ff562811527013050.jpg

 

Did I miss something?

 


It's look you don't have AudioDxe.efi in drivers64UEFI

 

Share this post


Link to post
Share on other sites

That I noticed by myself in the meantime...

Question is:

Why is BootChimeCfg.efi in an official release, but not AudioDxe.efi?

 

Share this post


Link to post
Share on other sites
14 minutes ago, al6042 said:

That I noticed by myself in the meantime...

Question is:

Why is BootChimeCfg.efi in an official release, but not AudioDxe.efi?

 


Because AudioDxe.efi from GoldFish64 use different method to read nvram variable for Audio Device with old ones (Slice's prebuilt).

You can use Prebuilt AudioDxe.efi and BootChimeCfg.efi from here 

 

Share this post


Link to post
Share on other sites

The AudioDxe mentioned in 

is also from GoldFish64, but older than the version in "r4833_plus_AudioPkg".

Share this post


Link to post
Share on other sites
9 hours ago, apianti said:

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

 

So i reconfigure my system. Update my CLOVER to r4842 from here https://github.com/Dids/clover-builder/releases . I remove AudioDxe.efi, BootChimeDxe.efi, BootChimeCfg.efi. Then,

1. Boot into Clover GUI and Reset nvram. Press F11 in CLOVER GUI
2. Boot into mac desktop and add AudioDxe.efi to drivers64UEFi and BootChimeCfg.efi to tools and just use sound.wav into Theme folder (BGM_SVG) then reboot to CLOVER GUI (AudioDxe.efi and BootChimeCfg.efi is from here


3. Enter shell and set "bootchimecfg.efi -s 7 -v 100 -t". I use 7 because my lineout is 7
4. Boot into mac then reboot again,, i can hear sound before GUI CLOVER. then i boot to mac desktop.
5. I add BootChimeDxe.efi from GoldFish64 https://github.com/Goldfish64/AudioPkg to drivers64UEFI then i Reboot.

Finally i can hear sound from Theme Sound and sound before loading progress too.

Here the video, sorry for bad english. I attach nvram.txt and preboot.log.

Thanks before

 

Share this post


Link to post
Share on other sites
On 1/7/2019 at 9:02 PM, Slice said:

BootChimeDxe is out of discussion here. I didn't make it and didn't recommend it.

 

Didn't Slice request BootChimeDxe to be not discussed here?

Share this post


Link to post
Share on other sites
12 hours ago, al6042 said:

Just tried the last official clover release 4842 and got the following errors while trying to check and configure BootChimeCfg.efi on my H170N-Wifi and Prime Z390-A:

1084557407_Clover4842-BootChimeCfg-Error.thumb.jpg.2f40e28621bd940ff562811527013050.jpg

 

Did I miss something?

 

Did you figure it out?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Announcements

  • Similar Content

    • By MaLd0n
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
        1 -Create a USB bootable
       
      Create your usb installer, use this tool and download Catalina or Big Sur from Apple servers
       
      Catalina
      installScript_allfullapp.zip
       
      Big Sur
      installScript_1016fullapp.zip
       
      Credits: crazybirdy
       
      Copy Catalina / Big Sur installer to Applications folder, open terminal and run
       
      Catalina
       
       
      Big Sur
       
       
      If you want check one step by step, check here
       
      -Opencore Vanilla Tutorial
      https://tinyurl.com/ycvcnp8h
       
      2- EFI folder USB installation
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/yxsw7d3t
       
      3- EFI folder SSD
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD 
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD
      https://tinyurl.com/yxsw7d3t
       
      4- Start Fine Tune
       
      Run this app and post full dump here for full ACPI solution
       
      RunMe.app
      https://tinyurl.com/y9562hz7
       
       
      If you like a SSDT way, here we go
      SSDT-OLARILA.aml.zip
       
      5- USB Solution
      USB INTEL SERIE 400.zip
       
      Use these kexts, enable XHCI port limit patch and follow this tutorial for remap USB ports
       
       
       
      --DSDT PATCHES--
       
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM -REAL TIME CLOCK -SLPB -DARWIN / WINDOWS -XHCI -PLUGIN TYPE -HDEF -ARTC -IPIC -TIMR -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -kUSBCompanionIndex -io-device-location -IMEI -EC -PNLF -ARPT -GFX0 -NVME -ACPI-WAKE-GPE -DTGP -HDMI / HDAU  
      --SCREENSHOTS--































      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      Big Thanks to XLR and your Badass Motherboard, Ultrafast CPU, Coolest Heatsink, Huge Graphics Card, Tonnes of RAM,
      Gigantic Hard Drive, Lightspeed Disk Burner, Professional Sound Card, Massive LCD Display.
       
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
    • By BALDY_MAN
      Hi All.
      Im Happy to share my new EFI file that I put together  18/10/2020. which got me up and running 11.0  Beta(20A5395g) on my hack
      a thanks you to everyone who's work I have use to assemble this EFI File. and the help I have received from this site
      I have used openCore 0.6.3, sound work for me (HDMI) and onboard Ethernet. map the usb ports as you wish.
      the definition to iMac20,2
      hope it helps all who need it
      PS. Please leave a comment if the EFI File is helpful to you
      (No Kexts were Harmed in the making of this EFI)
                                                                                                                     regards
                                                                                                                                         Baldy_man
      GigabyteZ40Master.EFI.(20A539g) .zip
    • By le332313
      Can someone share the dell 5593/5493 EFI ? I try to fit the graphics driver, but it not working please help me thanks
       
    • By Nomade
      Hello All,
       
      It's been a while that I am trying to update my system to 10.15.16.
      The install seem to start, then at reboot time I only see the Normal boot and the Recovery option from the Clover boot menu.
      None of those 2 allow to complete the update.
       
      Is there any ways to force it to install and/or show the "Update" option on the Clover boot screen?
       
      PS: I'm using Z97-Gaming-3
    • By Damx
      The specs CPU: Intel® Core™ i3 Processor 8130U, 2.20 GHz (Kaby Lake Refresh) Chipset: Intel® 300 Series Graphics: Intel® UHD Graphics 620 Display: 21.5'' 1920x1200 RAM: DDR4 PC2400 4GB SSD1: M.2 PLEXTOR (with original Windows 10) SSD2: SATA SAMSUNG 850 EVO (for macOS) Sound: Realtek ALC269 WiFi / BT: Intel 3168 NGW Realtek Card-reader  
       
      Not working
      WiFi: Intel 3168 NGW Realtek Card-reader  
       
      Pre-Installation
       
      I will not go through the basics since it is explained in details here on this site. Briefly, the process is to:
      Get Clover Get Catalina macOS installer Create USB with 2 MBR partitions (FAT32 for Clover and HFS+J for the installer)  
       
      Required kexts
      AppleALC.kext Lilu.kext RealtekRTL8111.kext VirtualSMC.kext WhateverGreen.kext  
       
      Config.plist
      I used the one provided by RehabMan called config_HD615_620_630_640_650.plist. Download it from GitHub. It has almost everything you will need with only few edits for audio.
      Edits:
      [CPU] Make sure there is lilcpu=9 setting in boot arguments needed for Kaby Lake R CPU to be recognised correctly. [GPU] Make sure there is a patch GFX0 to IGPU under ACPI->DSDT [GPU] Under Devices->Properties->PciRoot(0)/Pci(0x02,0) make sure that the AAPL,ig-platform-id value is 00001B59, and the device-id value is 16590000 [AUDIO] Under Devices->Properties->PciRoot(0)/Pci(0x1f,3) set the layout-id to 40 and the device-id to 70A10000 [SMBIOS] Set Mac model ID is iMac19,2  

       

       
      Notes
      For some reason with latest version of Clover the install partition was not visible. If you run into the same issue you can downgrade Clover to r5103, which worked perfectly. WiFi / BT Intel 3168 NGW needs to be replaced if one needs WiFi. Someone mentioned that to get HDMI work properly you may need to change AAPL,ig-platform-id value to 00001659 for PciRoot(0)/Pci(0x02,0) - not my case but may be considered if you get this issue. Don't forget to generate your serial and other SMBUS values before signing in with iCloud services.  
       
×