Jump to content
ErmaC

Clover General discussion

20,932 posts in this topic

Recommended Posts

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

Share this post


Link to post
Share on other sites
Advertisement
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.........*

 

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites
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.

 

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites
16 hours ago, ellaosx said:

install rc script with emuvariable, then LastBootedVolume

 

Oh true, I forgot I could do that. I still wonder what's wrong though, I'm not sure exactly what value should have gone in there to set the macOS volume to be default...

 

Edit: Actually, the last used volume option doesn't seem to stick booting to macOS if change the value to boot into Windows. Ideally I should be able to chose the disk by name or UUID or other value. Any other ideas?

 

Edit 2: It looks like I found the culprit. The boot entry that Clover installed in the NVRAM boot options was pointing to the wrong bootloader. Once I removed that entry, using the full copy-pasted value of HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60) worked for me.

Edited by WanderingAi

Share this post


Link to post
Share on other sites
On 1/8/2019 at 9:06 PM, 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?

 

 

I think BootChimeCfg.efi needs to be executable. Which, depending on where did you get it from, it might not be.

 

Personally I couldn't get my system to play the sound.wav file I placed in the theme folder. Not sure why. Still checking a few things.

Edited by arsradu

Share this post


Link to post
Share on other sites

Nope, 

BootChimeCfg.efi was working fine, that's why the last command in the screenshot worked.

The errors with the other options were gone, as soon as an AudioDxe.efi-file was placed in /EFI/CLOVER/driver64UEFI...

Either as manual copy or with clover 4844...

Share this post


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

Nope, 

BootChimeCfg.efi was working fine, that's why the last command in the screenshot worked.

The errors with the other options were gone, as soon as an AudioDxe.efi-file was placed in /EFI/CLOVER/driver64UEFI...

Either as manual copy or with clover 4844...

 

You're correct. After further investigation, it looks like I managed to reproduce the errors you were having. So yeah, it wasn't related to being executable or not. Actually, I think they're made executable anyway, when you drop them in the tools folder. Could be wrong thought. In my case, it was the "sound.wav" file missing from the theme's folder.

 

Still trying to get it to work... So far I managed to set it up... But still no sound on startup. I'm sure there's probably a mistake on my side somewhere.

 

EDIT: if you have more than one SSD/HDD with Clover on it, make sure you set the chime on the correct one.

 

EDIT 2: ok, so now I'm exactly where you are. Managed to set it up for boot (it was a total pain in the rear to find the correct boot EFI partition to load from Shell - for some reason, in my case it was FS11...) and tested it, working fine in Shell, but no sound on boot.

 

My guess is that maybe the sound output device is not selected correctly....? I don't know. What I do know, is that, Clover 4851 has an interface for testing and configuring the boot sound, but it always selects Device Output #1 for some reason...even after I selected Device #8, aaaand...pressing F7 to test that device will freeze the entire UI.

 

screenshot2.thumb.png.528c8b384dbd047e5e4b722f66d49c55.png

 

In my case, I set in the Shell the output device to be the one selected below (nr 8 in the list) but every time I enter here, it shows the first option. My guess is that the output device might haven't been saved. That's why it doesn't make any sound on boot.

 

Also, as I said, pressing F7 here will freeze the interface without making any sound.

 

screenshot3.thumb.png.c76faa99e3cb8460c679310c76e5f72a.png

 

Interestingly enough, it seems to have remembered the correct volume setting (60%). But not the output device.

Edited by arsradu

Share this post


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

Correct to


extern UINT8 EmbeddedSound[];

Thats the first thing I tried throws up another error 

/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c: In function 'StartupSoundPlay':
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:81:14: error: assignment to 'UINT8 *' {aka 'unsigned char *'} from 'UINT8' {aka 'unsigned char'} makes pointer from integer without a cast [-Werror=int-conversion]
     FileData = EmbeddedSound;
              ^
[CC] ntfscomp
cc1: all warnings being treated as errors
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/OUTPUT/Platform/StartupSound.obj] 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: 05:28:45, Jan.19 2019
Build total time: 00:00:41


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

 

Share this post


Link to post
Share on other sites
14 hours ago, Dr. Hurt said:

 

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.

 

That is exactly where I had those two files. As I said, I got chime to work in Clover Shell, but it wouldn’t play on regular boot.

 

I am also confused, where do I acquire those files? There seems to be some confusion about where to obtain those files.

Edited by pkdesign

Share this post


Link to post
Share on other sites

@cecekpawon

 I tried that, too. 

 

On startup, it says: "No device outputs were found. Ensure AudioDxe is loaded."

 

Well...boot log says AudioDxe is loaded...

 

0:152  0:000  Loading AudioDxe-64.efi  status=Success
0:153  0:001   - driver needs connecting

Any idea?

Edited by arsradu

Share this post


Link to post
Share on other sites
15 minutes ago, arsradu said:

@cecekpawon

 I tried that, too. 

 

On startup, it says: "No device outputs were found. Ensure AudioDxe is loaded."

 

Well...it is present in drivers64UEFI...not sure if it's loaded though.

Any idea?

Try to clear the previous settings. To do this, choose option x, then s and v :) it also makes sense to check if the latest AudioDxe-64.efi or AudioDxe.efi is present in the drivers64UEFI folder.

Share this post


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

Thats the first thing I tried throws up another error 


/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c: In function 'StartupSoundPlay':
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:81:14: error: assignment to 'UINT8 *' {aka 'unsigned char *'} from 'UINT8' {aka 'unsigned char'} makes pointer from integer without a cast [-Werror=int-conversion]
     FileData = EmbeddedSound;
              ^
[CC] ntfscomp
cc1: all warnings being treated as errors
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/OUTPUT/Platform/StartupSound.obj] 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: 05:28:45, Jan.19 2019
Build total time: 00:00:41


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

 

Same with XCODE

Works with XCODE *EmbeddedSound

 

Edited by STLVNUB

Share this post


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

@arsradu from your log it sure enough that driver were successfully loaded. If you are already start BootChimeCfg from GUI, I have nothing to says more. Not sure AudioDxe (Clover vs Official) version is really matter here _/|\_

 

Yeah, I am able to configure, test and set the wav sound I put in my selected theme (Minimalism). It respects the file name (sound.wav), the sample rate (44.1KHz) and the bits per sample (16bps). So... I would say the file is ok, the locations are ok (otherwise I think I wouldn't have been able to test and configure boot sound in the first place), still, upon startup, it says the output device is not found, and ensure AudioDxe is loaded... So...not sure what to say. :)) All seems to be working properly. Still, it doesn't. :))

 

And I'm using Clover 4851 (with the built-in AudioDxe) which in this exact commit it says: "update AudioDxe driver to sync with origin". So...I guess there shouldn't be a difference anymore, should it?

 

If you have another version of AudioDxe, I would love to give it a try.

 

Update: nevermind. IT WORKS! :)) It just works AFTER selecting the boot drive, not before, as it probably should, and as Clover's AudioDxe is probably trying to achieve.

 

I guess Clover's AudioDxe is not (yet) compatible with the prebuilt BootChimeCfg.efi? Ooor...there's something missing somewhere.

 

Bottom line, what did I do is: I got Goldfish's sources, compiled everything on my machine, used AudioDxe.efi, BootChimeDxe.efi in /drivers64UEFI and BootChimeCfg.efi and HdaCodecDump.efi in /tools and it works. :)

 

Also, one thing to note is that I had to shut down my computer, and then restart. Simple restart didn't do it for me. Don't know why. Also, there was no error anymore. So I guess they're not compatible yet. So the config file doesn't see the AudioDxe file from Clover. But if it's built with it...it does.

 

There are also other files, such as BootChimeDxe and HdaCodecDump which are missing from the Clover's instructions. They might not be needed. I just took everything as it was from the compiled sources. Just to have all the possible chances of this to work. And, what do you know? It does. :))

 

I'll test a few more things now and let you know if I find anything interesting.

Edited by arsradu

Share this post


Link to post
Share on other sites
18 minutes ago, arsradu said:

 

Yeah, I am able to configure, test and set the wav sound I put in my selected theme (Minimalism). It respects the file name (sound.wav), the bitrate (44.1KHz) and the bps (16bps). So... I would say the file is ok, the locations are ok (otherwise I think I wouldn't have been able to test and configure boot sound in the first place), still, upon startup, it says the output device is not found, and ensure AudioDxe is loaded... So...not sure what to say. :)) All seems to be working properly. Still, it doesn't. :))

 

And I'm using Clover 4851 (with the built-in AudioDxe) which in this exact commit it says: "update AudioDxe driver to sync with origin". So...I guess there shouldn't be a difference anymore, should it?

 

If you have another version of AudioDxe, I would love to give it a try.

 

I am using a driver (official Goldfish64 build). The built in clover 4851 doesn't work properly for me. In the driver folder, I have BootChimeDxe.efi, which contains the ta-da sound. When I try to use the built-in (AudioDxe-64.efi) driver, I have no sound, and if I try to configure its parameters from the Clover menu, everything hangs and the previous settings are erased from the nvram. I am attaching the complete package I have just build in the archive. I apologize for my bad english. I'm from Russia.

AudioPkg-R1-RELEASE.zip

Share this post


Link to post
Share on other sites
47 minutes ago, MakAsus said:

I am using a driver (official Goldfish64 build). The built in clover 4851 doesn't work properly for me. In the driver folder, I have BootChimeDxe.efi, which contains the ta-da sound. When I try to use the built-in (AudioDxe-64.efi) driver, I have no sound, and if I try to configure its parameters from the Clover menu, everything hangs and the previous settings are erased from the nvram. I am attaching the complete package I have just build in the archive. I apologize for my bad english. I'm from Russia.

AudioPkg-R1-RELEASE.zip

 

Thanks, man. :) Yeah, if you read the update on my previous post, you'll see I did the exact same thing. :)) And it does work. As I said, it works in a different way though. Meaning the sound is played back after selecting the boot drive, not before, as I saw in one of the earlier posts, and as I think Clover is trying to achieve with its AudioDxe driver (when loading the theme). But it does work, if you're using all the files from the same source and you have them correctly placed in their locations.

 

By the way, your English is quite good actually. :)) And I'm pretty sure very few people on this forum are actually native speakers. So don't worry about it. :) 

Edited by arsradu

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 kingoffright
      Dear all,
       
      I have a external harddisk about 500GB, I installed the clover into it and the harddisk is GPT format, below is the 3 partitions details:
      FS01: EFI - disk0s1 - fat32
      FS02: install mac  image - disk0s2 -  hfs+
      FS03: install windows 10 - disk0s3 - fat32
       
      I can use this external harddisk to install Mac without issue, I use below steps to install windows 10
      enter the FS03:
      cd to efi/boot/ and excuete bootx64.efi
      after pop up the windows install screen, i click next and it shows error 'A media driver your computer needs is missing...' and the installation can not go any further.
      Firstly I use ultraiso to write the windows 10 image to a flash disk and no issue to start install window 10 so the image is working fine. Since I dont know how to write
      a wiindow installation image into harddisk partition, I used winrar extra all the files into disk0s3, am I missing some steps or actually clover not support to install windows
      by partitions, apprecating any helps.
       
    • By kushwavez
      Acer Aspire V15 V5-591G - Catalina 10.15.1
      This post will no longer updated, go for the osxlatitude link for further updates
      Original and updated link:
      https://osxlatitude.com/forums/topic/11355-acer-aspire-v-15-v5-591g-catalina-windows-10/
      (Note: mine is 55TU version, but the bootpack will work fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)
      Specifications:
      - Motherboard: USOPP_SLS (Skylake-H PCH)
      - BIOS: Insyde Corp. v 1.15
      - CPU: Intel Core i5-6300HQ 2.3 GHz (Skylake)
      - GPU: NVIDIA GeForce GTX 950M 2 GB (Optimus) & Intel HD Graphics 530
      - RAM: SK hynix 4 GB DDR4 (Later I bought + KINGSTON 4 GB) 2133 MHz
      - WiFi + Bluetooth: Qualcomm Atheros QCNFA344A 5 GHz (Later -> Broadcom BRCM94352Z M.2 5 GHz WiFi + 4.0 Bluetooth)
      - Audio: Realtek HD Audio: ALC 255 
      - Ethernet: Realtek RTL8168/8111
      - Card Reader: Realtek USB 2.0 Card Reader (USB2.0-CRW)
      - Webcam: HD Webcam
      - HDD: TOSHIBA MQ01ACF032 320 GB HDD
      - SSD: SPCC M.2 230 GB SSD
      - Display: 1366x768 (15.6", Matte)
      - Battery: 6 cell 56Wh / 5040mAh
      - Connectors: 
      1x SD Card Reader 2x USB 3.0 (1x USB Charging), 1x USB 2.0 1x VGA 1x HDMI 1x 3.5mm microphone/audio combined jack connector 1x Ethernet (Rj-45) - Keyboard & Touchpad: Multi-Touch & Multi-gestures ELAN 501 Touchpad, Backlight Keyboard.
      Working:  
      - Wi-Fi (with BCM94352Z)
      - Bluetooth hand-off (With BCM94352Z)
      - Full Graphics enabled on HD 530: ig-platform-id: 0x191b0000 (HD 530 Mobile)
      - Display: if default colour profile is corrupted (blue is not actual blue but purplish) Use "Rec. ITU-R BT. 709-5" Color Profile (System Pref. -> Displays -> Color)
      - HDMI & VGA Outputs: AppleGraphicsDevicePolicy.kext Clover patch
      - Audio (ALC 255): (Internal Speakers, Internal Microphone, Headphone jack with AppleALC, ALCPlugFix -> layout-id=17)
      - Ethernet Realtek 8168/8111: RealtekRTL8111.kext
      - App Store, Messages, FaceTime, Siri, iCloud (native)
      - Integrated webcam (native)
      - 3.0 USB (native)
      - Touchpad and Keyboard (ELAN501): Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn-> To fix this try Karabiner (VoodoPS2Controller.kext), - for gestures try SmartTouchpad drivers
      - Battery info: Install ACPIBatteryManager.kext with Kext Utility or other installer.
      - Sleep Mode
      - SSD with TRIM enabled (to enable trim, open Terminal and write "sudo trimforce enable")
      Not working:
      - Original Wi-Fi (Qualcomm Atheros QCNFA344A):  unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle.
      - NVIDIA GeForce GTX 950M: Optimus not supported.
      - Card Reader: Unsupported -> Can't really fix because I don't have any SD Card at the moment, maybe can be fixed by adding Prod & Ven IDs to AppleStorageDevices.kext, I never used it anyway. name: "USB2.0-CRW" Prod ID: "0x0129" Ven ID: "0x0bda  (Realtek Semiconductor Corp.)"
      For Wi-Fi:
      - 1st method: You can choose an external USB wifi dongle (I used TP-Link Archer T1U (5GHz support), TP-Link has official macOS drivers, you just need to install it
      - 2nd and I think the best method: Replace your M.2 Qualcomm Card with a compatible BCM94352Z card (you will have hand-off Bluetooth too), just install the kexts (enabled with BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, they're all in my attached zip). You could buy this card from ebay, aliexpress, or amazon
       
      Issues:
      - None
      BIOS Settings:
      - BIOS version 1.15 (irrelevant)
      - Secure Boot: Disabled
      - Touchpad: Advanced
      - Boot mode: UEFI
      Getting ready for Installation:
      - Download the Catalina install zip (bootpack & postinstall): acer_aspire_V591G-55TU_cata.zip
      Installation:
      - Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager)
      - Copy my Clover folder to the USB's EFI folder
      - Boot with the Installer USB
      - If you stuck in boot, reboot and in the Clover bootloader select "config_debug.cfg" -> you'll have more informations about the freeze
       
      Please open the README.rtf in my install zip for more informations about the USB Installer & Post installation!
      On Catalina the System folder is read-only, so you need to remount in rw to modify System/Library. 
      If you have a single RAM and getting panic at boot, then you need to edit the "config.plist" with these (SMBIOS->after "Version 1.0"):
      ->Edit "Frequency" and "Size" to match your RAM values
      <key>Version</key> <string>1.0</string> <key>Memory</key> <dict> <key>Channels</key> <integer>1</integer> <key>SlotCount</key> <integer>1</integer> <key>Modules</key> <array> <dict> <key>Slot</key> <integer>0</integer> <key>Size</key> <integer>8192</integer> <key>Frequency</key> <integer>2133</integer> <key>Type</key> <string>DDR4</string> </dict> </array> </dict> </dict>  
      PowerManagement  fix:
      Set HWPEnable=YES in Clover (already set), CPUFloor to "700", Frequency to "2300" and "3200"(Normal and Turbo, if you have i7-6700HQ version then it should be "2600", "3500") and "FrequencyVectors" from "0x0d000000" to "0x07000000" in "S/L/E/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-A5C67F76ED83108C.plist", MSR _xcpm_idle Patch to KernelToPatch in Clover (If you have High Sierra, change "MatchOS" to 10.13):

      <key>KernelToPatch</key> <array> <dict> <key>Comment</key> <string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> ILniAAAADzA= </data> <key>MatchOS</key> <string>10.14</string> <key>Replace</key> <data> ILniAAAAkJA= </data> </dict> </array> Reboot, and it's 800MHz in idle state, same on Windows.
       

      Elan SmartTouchpad
      I only use scrolling, one-, double- & tripletap
      If you want to try other gestures go to this link for more informations, options (v4.6.5) ->  DETAILS ABOUT THE SMART TOUCHPAD DRIVER FEATURES
      Fn Brightness keys not working with this, tried several things without success. With VoodoPS2Controller it's working, but you'll have no gestures (neither scrolling).
       
       
      Before updating to a new version of Catalina please update kexts (and clover if necessary) to newer versions to avoid kernel panics.
      Generate a serial number with Clover Configurator.app (open up your config.plist with CC then -> SMBIOS -> Serial Number -> Generate New)
       
      Catalina & Windows 10 Dual-Boot:
      Dual-boot clean install (on one drive), UEFI Only:
       
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac),   Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart,  Boot into your Win installer, Format the partition you created for Win, install.   Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       5.  You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive), UEFI Only:
      If you already have Windows and you don't want to lose all your data there is a hope:
      I created a video from this restore method: [Hackintosh] Dual-Boot High Sierra & Windows - when Windows already installed - no data waste - UEFI
      You need bootable Mac Installer and a full system restore image (link is in my video's description).
      (You may see errors if your EFI partition is not 200 MB)
       Boot into your Windows, resize your partition or create one for Mac.  Boot into your Mac installer and in Disk Utility format the partition you created.  Restore from image: select your full system restore image.  When it's finished restoring you just need to restart, then boot to the system with your usb.  When you successfully booted to Mac desktop, mount your EFI partition (use terminal or an EFI mounter app), open EFI, you will see there is a Microsoft folder already (don't touch that!). Copy my CLOVER folder to the EFI folder then Restart.  Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       7.  You're done! You can select your old Windows and your new macOS!
      (Only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      - Make sure you have partitions in GPT
      - Windows using 100 MB EFI and will annoy the Mac restore. Don't worry, just ignore the errors.
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      - Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)
       
      IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found):
      - It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem)
      - You also could "mount" the EFI from Windows:
      1st method: open cmd in administrator mode and type:
      diskpart list vol (Now select the "System" volume,(FAT 32) For example I select 4) sel vol 4 list part (Select System type partition, for example 2) sel part 2 assign letter=b (This will "mount" your EFI partition) Open Explorer++ or TotalCommander in administrator mode to manage EFI remove letter=b (This will "unmount" your EFI) 2nd method: open cmd in administrator mode and type:
      mountvol b: /s (This will mount your EFI) Open Explorer++ or TotalCommander in administrator mode to manage EFI mountvol b: /d (This will unmount your EFI) Thanks to all OSXLatitude members for helping me out! (Jake Lo, Hervé, Bronxteck, black.dragon74)!
      Notes:
      2019.11.03: Enabled SIP caused a lots of issues so now it's disabled -> updated bootpack
      2019.11.02: Updated to 10.15.1 -> no problem when/after installing
      2019.10.09: Installed macOS Catalina 10.15 -> Updated Clover, kexts & config.plist -> no problem so far
      2019.08.18: Updated to 10.14.6 -> no problem when/after installing
      2019.06.01: Updated to 10.14.5 -> no problem when/after installing
      2019.04.25: Optimized touchpad scrolling -> updated install files
      2019.03.30: Fixed USB 3.0 ports, fixed Bluetooth crashes after sleep -> updated bootpack
      2019.03.28: Updated to 10.14.4. Unexpected crashes while updating to 10.14.4 -> fixed by updating Clover to the latest (v4910) version. Bluetooth crashes appeared -> fixed by downgraded Brcm*.kexts. Updated bootpack.
      2019.02.24: Bluetooth crashes after sleep -> fixed, updated bootpack. 
      2019.02.22: Updated to 10.14.3. Fixed HDMI Audio by installing "FakePCIID_Intel_HDMI_Audio.kext" -> fixed freezing during boot. Fixed brightness levels by installing "AppleBacklightFixup.kext". Also updated bootpack & postinstall zip down in attachments.
      2019.01.21: Removed FakeSMC.kext, SMCHelper-64.efi, replaced by VirtualSMC.kext, VirtualSMC.efi because I got random freezes when booting system (kextd stall[0], (120s): 'AppleACPICPU' -> CPU is at 100%, fans are spinning fast), also updated bootpack in the attachments "acer_aspire_v591g-55tu_clover.zip" -> Freeze continued, brought back FakeSMC, deleted VirtualSMC (caused BT crashes).
      2019.01.18: HDMI Audio is fixed, I didn't do anything HDMI Audio is not fixed, sometimes it worked but most likely not. (no idea why)
      2018.12.09: Updated to 10.14.2 -> did without any complication
      2018.11.28: Fixed combo-jack garbage sound output by installing ALCPlugFix and CodecCommander.kext
      2018.11.01: Updated to 10.14.1 -> HDMI & VGA ports are gone again. -> Fixed by "AppleIntelSKLGraphicsFramebuffer.kext" rollback from 10.14.
      2018.09.28: Updated to Mojave 10.14 -> Fixed HDMI & VGA Outputs by adding "AppleGraphicsDevicePolicy.kext" patches to config.plist, HDMI audio not working
    • By Cwtf
      I just made a clean install of High Sierra on a 1TB crucial ssd. Installed clover Clover_v2.5k_r5070 into the EFI of this ssd, but when I tried to make it my default boot drive, the clover screen wouldn't come up, and left a black screen.
      I tried using the Olarilia usb drive and clover did the same thing.  The only way I can currently boot is to use my old drive with clover v2.4k_4945 then select  my new drive from the clover menu.   
       
      Do I need to install v2.4k on my new drive or is there a way I can get v2.5k working?
       
      I have a GA-x79-ud5 motherboard, AMD  rx580 graphics card and use a Sony 4k tv as my monitor.
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage the configuration of various Hackintosh Bootloaders.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly and more...  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
×