Jump to content
ErmaC

Clover General discussion

19,135 posts in this topic

Recommended Posts

23 hours ago, Andres ZeroCross said:


Is this CLOVER or any SMC.kext/key problem??? Try with VirtualSMC.kext and FakeSMC.kext without success.

I use same configuration but working fine in Gigabyte B360 motherboard. This is MSI H310M PRO-M2 + i3 8100 + GTX1060. I use Clover r4813

I attach CLOVER folder for additional informations.

 

Neither, it is a problem with an ACPI table.

Share this post


Link to post
Share on other sites
Advertisement
10 hours ago, Badruzeus said:

I'll have similar problem if (for example) OS Badge and Volume icon are missing.

I removed "os_moja.icns, vol_internal_apfs.icns, vol_internal_hfs.icns" from "christmas" theme's \icons dir and here's what I get: (again, plz recheck your theme or simply test with another one). Happy New Year!

SS-christmas-VBox.png

Thanks man, happy new year to you too, and for the moment it stays as it is, because in the beginning of the new year I have a new build with an Asus Rog Strix H370-I mobo, Intel i5 8600K, 16 GB DDR4 2666 Crucial Ram, and M2 NVME Crucial 500 GB SSD.

Happy news year to all of you and thanks for all the help and tips gave to me...

Cheers   

Share this post


Link to post
Share on other sites

Since 18.10, GhostBSD is no longer using grub2 as defaut bootloader but what TrueOS has (FreeBSD hybrid Loader). It comes with rEFInd as bootloader #BTW; any idea how to make Clover detects this (also ZFS as rEFInd supports this FS) ? Thanks.

 

VirtualBox_Ghost-BSD-18.10_03_01_2019_13_01_10.png

Share this post


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

OK, "zfs_x64.efi" is installed on /EFI/CLOVER/drivers64UEFI/

I was actually, referring to this part but I found no BSD entry loader on it.

Adding this line is definitely possible, it detected by Clover and BSD System boot just fine (plus os_ghostbsd.icns for GUI):

{ L"\\EFI\\boot\\bootx64-trueos.efi", L"GhostBSD EFI boot menu", L"ghostbsd,linux", "GhostBSD" },

..though sorry for my script kiddie, it' s wrong bcoz BSD is not Linux for sure.

VirtualBox_Ghost BSD 18.10_04_01_2019_09_50_45.png

Share this post


Link to post
Share on other sites

That's a list of icons, you don't need to put linux there, lol. Just do ghostbsd,bsd and make both icons if you want. You can't have both ghostbsd and trueos installed then? That's stupid.

Share this post


Link to post
Share on other sites

Hi @Slice

 

Thanks for commit r4833: If I understand well Goldfish64's readme, it works only for Intel HD. My system use HDMI audio via my Nvidia graphic card. How can I have sound at startup on Clover GUI in this case. There is a solution.

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, apianti said:

That's a list of icons, you don't need to put linux there, lol. Just do ghostbsd,bsd and make both icons if you want. You can't have both ghostbsd and trueos installed then? That's stupid.

Oh I see, now much better with "os_unknown.icns" instead of wrong generic "os_linux.icns" for BSD System LoL (if there's no os_ghostbsd.icns provided with a theme used).

 

#EDIT: Nevermind, no longer using "os_unknown.icns" if there's "os_bsd.icns" on /icons dir (which previously was missing).

VirtualBox_Ghost BSD 18.10_04_01_2019_15_39_16.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
31 minutes ago, Matgen84 said:

Hi @Slice

 

Thanks for commit r4833: If I understand well Goldfish64's readme, it works only for Intel HD. My system use HDMI audio via my Nvidia graphic card. How can I have sound at startup on Clover GUI in this case. There is a solution.

VoodooHDA works with HDMI as well as with non-Intel chipsets so yes it's possible just requires a work.

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Matgen84 said:

Hi @Slice

 

Thanks for commit r4833: If I understand well Goldfish64's readme, it works only for Intel HD. My system use HDMI audio via my Nvidia graphic card. How can I have sound at startup on Clover GUI in this case. There is a solution.

I am unable to build r4833 until i downloaded AudioPkg-master.zip from https://github.com/Goldfish64/AudioPkg and extract it to my edk2 folder and rename it. Is this what you did also?

After using the guide from Slice i cannot get sound to work on my laptop even though while setting it up in clover shell i had audio. Is the issue my conversion?

 

Mac Startup.wav

Screen Shot 2019-01-04 at 8.10.25 pm.png

Edited by SavageAUS

Share this post


Link to post
Share on other sites
53 minutes ago, SavageAUS said:

 

check this file

and if you could, share your r4833 build please

sound.wav

Share this post


Link to post
Share on other sites
Posted (edited)

 

1 hour ago, MICKHAEL said:
check this file

 

and if you could, share your r4833 build please

sound.wav

Will do when I get a chance.

I converted my file as slice described and also tried 1 and 2 channel but neither work. Hopefully his test file will work.

 

Edit: test file works fine so it’s my conversion.

 

Edit2: All working now. Attached mac startup chime working with clover for anyone who wants it.

 

Clover_v2.4k_r4833.pkg

 

macstart.wav

Edited by SavageAUS

Share this post


Link to post
Share on other sites
3 hours ago, Badruzeus said:

@Slice Following your guide, it doesn't work on my mach till I also placed "BootChimeDxe.efi" on ../drivers64UEFI

But weird is, I hear StartUp sound after Clover GUI, not before it.. on the contrary as what you said.

Anyway, I built AudioPkg under Linux with GCC5 (debbuild.sh), how if using macOS? Thanks.

r4833_plus_AudioPkg.zip

Try the file attached in the theme folder your currently using.

macstart.wav

Share this post


Link to post
Share on other sites

Hi again @Slice

 

Could you add AudioPkg to Ext-Package: it will be more easy to build Clover than add AudioPkg manually method. Please. :)

Share this post


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

I propose to add AudioDxe into Clover instead of whole package.

For this moment you have to add ready-to-use-binaries.

 

Thanks for reply. I must use binaries. If I copy AudioPkg in src/UDK2018, I can't build Clover because I've this issue:

 

build.py...
/Users/mathieu/src/UDK2018/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	/Users/mathieu/src/UDK2018/AudioPkg/AudioPkg.dec

 

Share this post


Link to post
Share on other sites

You guys should definitely add a volume value for the chime... ;)

 

I just checked the stuff on my Skylake WoodenBox with an Headset and it almost blew my head off.... :D

Share this post


Link to post
Share on other sites
Posted (edited)
You guys should definitely add a volume value for the chime...

 

I just checked the stuff on my Skylake WoodenBox with an Headset and it almost blew my head off....

Clearly you didn’t follow instructions.

 

 

 

Tuning.Before first start you have to tune your sound system.Start Clover, goto Shell.Shell> fs0:fs0:> cd EFI\CLOVER\toolsfs0:EFI\CLOVER\tools>BootChimeCfg.efiYou will see all options-l -- list all devices. See and choose.Then you have to configure and hear.BootChimeCfg.efi -s 1 -v 60 -t Audio Output=1 and Sound Volume=60% will be stored in NVRAM and will be used by Clover after next restart.

   

 

 

Edited by SavageAUS

Share this post


Link to post
Share on other sites

You're right, I didn't saw that entry... :)

 

Thanks for the hint.

Share this post


Link to post
Share on other sites
Posted (edited)

Hi Guys

 

Despite of Slice's guide, I haven't any sound: AudioDxe isn't compatible with external HDMI. I use Nvidia HDMI audio output on my desktop. :cry::cry::cry:

 

From Goldfish64 Readme file:

AudioPkg is a set of drivers/applications for supporting audio (currently only Intel HD audio) under UEFI.

 

Edited by Matgen84

Share this post


Link to post
Share on other sites

Tried it on a H170N-Wifi, which only uses the HD530.

Since the Boards has two HDMI outlets I tested the following on both HDMI ports, but couldn't get a tone out of it.Clover4833-1.thumb.jpg.c896f1ba1190e16d5da2cf5f31458e50.jpg

 

Switching to "-s 2" I could hear the chime, while i had a headset plugged in at green rear.

Share this post


Link to post
Share on other sites

I was off for some days. Maybe this has been explained already somewhere else. Anyway, my problem is that when building the current clover revision with Build Clover command, I get the following error:

 

Processing meta-data .

build.py...
~/src/edk2/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	~/src/edk2/AudioPkg/AudioPkg.de

How to solve this issue? 

Share this post


Link to post
Share on other sites
6 minutes ago, KGP-iMacPro said:

I was off for some days. Maybe this has been explained already somewhere else. Anyway, my problem is that when building the current clover revision with Build Clover command, I get the following error:

 


Processing meta-data .

build.py...
~/src/edk2/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	~/src/edk2/AudioPkg/AudioPkg.de

How to solve this issue? 

 

I think Build_Clover.command will be update. You can post this issue to the Build_Clover topic. 

Share this post


Link to post
Share on other sites
5 hours ago, KGP-iMacPro said:

I was off for some days. Maybe this has been explained already somewhere else. Anyway, my problem is that when building the current clover revision with Build Clover command, I get the following error:

 


Processing meta-data .

build.py...
~/src/edk2/Clover/Library/WaveLib/WaveLib.inf(35): error 000E: File/directory not found in workspace
	~/src/edk2/AudioPkg/AudioPkg.de

How to solve this issue? 

Rev 4834.

Just wonder how can I compile before.

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

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By AppleBytes
      OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
      As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
      Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
      Thank you for all your time, and consideration.
       
      --Chris
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
×