Jump to content
ErmaC

Clover General discussion

20,627 posts in this topic

Recommended Posts

3 hours ago, PMheart said:

Hi,

 

Sorry, I was too hurried yesterday, better to polish logging as follows:


Index: rEFIt_UEFI/Platform/kernel_patcher.c
===================================================================
--- rEFIt_UEFI/Platform/kernel_patcher.c	(revision 4974)
+++ rEFIt_UEFI/Platform/kernel_patcher.c	(working copy)
@@ -1048,7 +1048,7 @@
 
   // check OS version suit for patches
   if (!IsXCPMOSVersionCompat(os_version)) {
-    DBG("Unsupported macOS.\n");
+    DBG("HaswellLowEndXCPM(): Unsupported macOS.\n");
     DBG("HaswellLowEndXCPM() <===FALSE\n");
     return FALSE;
   }
@@ -1121,7 +1121,7 @@
 
   // check whether Ivy Bridge
   if (gCPUStructure.Model != CPU_MODEL_IVY_BRIDGE) {
-    DBG("Unsupported platform.\nRequires Ivy Bridge, aborted\n");
+    DBG("KernelIvyBridgeXCPM(): Unsupported platform.\nRequires Ivy Bridge, aborted\n");
     DBG("KernelIvyBridgeXCPM() <===FALSE\n");
     return FALSE;
   }
@@ -1129,7 +1129,7 @@
   // check OS version suit for patches
   // PMheart: attempt to add 10.14 compatibility
   if (!IsXCPMOSVersionCompat(os_version)) {
-    DBG("Unsupported macOS.\n");
+    DBG("KernelIvyBridgeXCPM(): Unsupported macOS.\n");
     DBG("KernelIvyBridgeXCPM() <===FALSE\n");
     return FALSE;
   } else if (os_version >= AsciiOSVersionToUint64("10.8.5") && os_version < AsciiOSVersionToUint64("10.12")) {
@@ -1205,7 +1205,7 @@
   
   // check whether Ivy Bridge-E5
   if (gCPUStructure.Model != CPU_MODEL_IVY_BRIDGE_E5) {
-    DBG("Unsupported platform.\nRequires Ivy Bridge-E, aborted\n");
+    DBG("KernelIvyE5XCPM(): Unsupported platform.\nRequires Ivy Bridge-E, aborted\n");
     DBG("KernelIvyE5XCPM() <===FALSE\n");
     return FALSE;
   }
@@ -1213,7 +1213,7 @@
   // check OS version suit for patches
   // PMheart: attempt to add 10.15 compatibility
   if (!IsXCPMOSVersionCompat(os_version)) {
-    DBG("Unsupported macOS.\n");
+    DBG("KernelIvyE5XCPM(): Unsupported macOS.\n");
     DBG("KernelIvyE5XCPM() <===FALSE\n");
     return FALSE;
   }

Thanks a lot!

Not a big deal! Committed.

Share this post


Link to post
Share on other sites
Advertisement
16 hours ago, vector sigma said:

Tadan: Clover_v2.4k_r4974.pkg

 

after one year, as soon I understood that you wanted a dark background image and not the logo Lol, here is it:

aqua.png.6b2c36684c89538f56496fc1b1aae65c.pngdark.png.54c0e0c718818dd66b22436f3e0a1dbd.png

 

To all,

before committing changes I want to know if the package can work in old OSes, e.g. 10.10 or maybe 10.7? Please report!

 

Install also succeeds in Lion and boots it as well :)...

 

Spoiler

1379580078_VectorSigmar4974inLion.thumb.png.cf1638b805d4bbad16604f0e132dbb52.png

 

Share this post


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

Thanks a lot :) I look forward to the new commit. It's possible that Clover Logo keeps Green color (in Dark Mode) instead of Gray. I've a dream.

I made it dark with Photoshop Lol, but ok will be green ;)

6 hours ago, fusion71au said:

Install also succeeds in Lion and boots it as well :)...

Thanks you so much! I'll commit this as soon as possible.

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
16 minutes ago, vector sigma said:

I made it dark with Photoshop Lol, but ok will be green ;)

Thanks you so mutch! I'll commit this as soon as possible.

I think gray is also cool, so Clover logo is also transformed into another color when UI goes Dark lol B)

Share this post


Link to post
Share on other sites
21 minutes ago, vector sigma said:

Why not automatic if "Reboot On Panic" is turned off?

In this case it will be good.

On 6/25/2019 at 5:56 PM, cecekpawon said:

@Slice Please ignore if you already have similar results like imac dump below.

 

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/smbios.c#l1083

 

rom.thumb.png.61e59cf6d94a28757a415b2a30ccd0a8.png

 

 

My result with Clover

Снимок экрана 2019-06-26 в 20.42.24.png

 

Снимок экрана 2019-06-26 в 20.04.55.png

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, Badruzeus said:

I think gray is also cool, so Clover logo is also transformed into another color when UI goes Dark lol B)

Yes,  I've only followed a popular policy lately in Apple, but green is default for a clover lol, so I think it's ok for most.. 

Anway I need to test it to ensure this method isn't applied in dark mode, that usually require an image to be greyscaled... otherwise the result will be unpleasant.

 

EDIT

committed

Edited by vector sigma

Share this post


Link to post
Share on other sites

Quick question, do you still have to format the EFI partition as FAT32? I am about to update to Mojave and want o be sure I get it right,

 

I apologize if this has been asked before but I can’t find a definitive answer.

Share this post


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

In this case it will be good.

My result with Clover

Снимок экрана 2019-06-26 в 20.42.24.png

 

Снимок экрана 2019-06-26 в 20.04.55.png

 

can we turn off cosmetic of apple rom info in system profiler from config.plist?

 

also what is better name for disabled kernel panic logging?

 

can i determine name?

Share this post


Link to post
Share on other sites

Regarding "disabled kernel panic logging", should you mean something like this in OpenCore?

 

12 hours ago, Sherlocks said:

@Slice

the most of people uses disable kernel panic patch to get exact panic kext part.

https://github.com/RehabMan/OS-X-Clover-Laptop-Config/pull/60

 

like this. can we include this patch default like SIP and EXT? if we need, i will consider

By the way, this is not the best approach, a better one can be found at https://github.com/acidanthera/OcSupportPkg/blob/master/Library/OcAppleKernelLib/CommonPatches.c#L948-L958, where the bytes are kind of stabler.

 

As for the name itself, not so bad to copy/paste it from OC I guess. =)

Share this post


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

 

can we turn off cosmetic of apple rom info in system profiler from config.plist?

 

also what is better name for disabled kernel panic logging?

 

can i determine name?

Apple ROM Info depends on macModel or FeatureMask. I don't know exactly.

As well we set smbis version as 2.4 while in newest Mac it is 3.0. May be it also should be adustable.

Share this post


Link to post
Share on other sites

Hmmb, I just realized that "Boot ROM Version" and "EFI Version" give a same result. (256.0.0.0.0 on my case)

Can EFI version replaced with Clover revision, or.. BiosReleaseDate? Thanks.

Share this post


Link to post
Share on other sites
17 minutes ago, Badruzeus said:

Hmmb, I just realized that "Boot ROM Version" and "EFI Version" give a same result. (256.0.0.0.0 on my case)

Can EFI version replaced with Clover revision, or.. BiosReleaseDate? Thanks.

We may include different information. Discussable. Do you really want to see BiosReleaseDate? Is it influence on something?

Share this post


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

Do you really want to see BiosReleaseDate? Is it influence on something

It doesn't, but I usually bdmesg grep it to compare my custom PlatformData on SMBios with Clover provided to see whether BiosReleaseDate is current or not, or you could consider another one like Board-id maybe..

Edited by Badruzeus

Share this post


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

We may include different information. Discussable. Do you really want to see BiosReleaseDate? Is it influence on something?

 

i want to keep vanilla system profiler like realmac without cosmetic. so i ask you to turn off cosmetics option

Share this post


Link to post
Share on other sites
Posted (edited)

@Slice Or EFI Version could be unified with BiosReleaseDate in single line like screenshot below, probably..

plus Board-ID as addition.

Windows-OC.png

 

15 minutes ago, Sherlocks said:

i want to keep vanilla system profiler like realmac without cosmetic. so i ask you to turn off cosmetics option

Uhmmb, if there's such option on config.plist I think it'll be better for user to choose.

 

Edited by Badruzeus

Share this post


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

 

i want to keep vanilla system profiler like realmac without cosmetic. so i ask you to turn off cosmetics option

I just added SMBIOS table 11. It does present in real Macs.

There is a question why System Profiler not always shows the information. May be because of FeatureMask? Or because of MacModel? Or because of SMBIOS version?

Share this post


Link to post
Share on other sites

Hi Clover Team

 

I don't know if I'm Off-Topic

 

Under catalina Developer Beta 2, Clover stuck at prepare stage so I can't update

 

 

 

Capture d’écran 2019-06-28 à 08.29.09.png

Share this post


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

Hi Clover Team

 

I don't know if I'm Off-Topic

 

Under catalina Developer Beta 2, Clover stuck at prepare stage so I can't update

 

 

 

Capture d’écran 2019-06-28 à 08.29.09.png

 

Hi Matt,

 

Uhm...no such issues on my side.

1379918933_Screenshot2019-06-28at10_21_56.png.f2d9ad139e8e3d4ae5efbe6fb43dfed8.png

 

However, I'm still getting this weird warning. Maybe because Clover was built on Mojave...? No idea. Clicking Install Anyway does seem to install it properly though.

 

1955136247_Screenshot2019-06-28at10_20_45.png.7e05700f5163c952b76c2a71ea419dc0.png

 

How are you building Clover? Maybe you're selecting something else in Drivers....? I only chose the mandatory (automatically checked) drivers + OSXAptioFix3Drv. That's all.

 

Also, we were previously talking about the post install script, which should prevent user from getting AptioMemoryFix and OSxAptioFix drivers, both at the same time.

There seems to be a case where this does not happen.

 

Because this is what I'm getting after installing Clover, while previously I had AptioMemoryFix in drivers64UEFI.

 

1408977674_Screenshot2019-06-28at10_28_47.png.d24c23f15a8ad8ebc19eb5f04d88c1e5.png

 

My guess is that since the previous Clover installer did have AptioMemoryFix (and it was checked for installation) and this one doesn't (since I've switched to the default OsXAptioFix3Drv instead, and did not include AptioMemoryFix in the build anymore), the installer doesn't know AptioMemoryFix is already present, and it doesn't do anything based on that. Doesn't skip the installation of OsXAptioFix3Drv, and it doesn't remove AptioMemoryFix either to avoid conflicts.

 

I'm looking forward to your opinions though. In my opinion this could be a real life scenario. If one day we ship Clover with AptioMemoryFix, and the other day we don't or we use something else instead, I see this as a potential problem on the long run, if people will end up with two (or more) Aptio fixes. And I've actually seen people with all 3 OsXAptioFixes in their drivers folders. Probably added manually, not through the installer. In which case there's not much we can do. But if that was through the installer...maybe we should think of a better solution to this other than relying on the post-install script to fix everything in the background.

 

I think a bit more transparency wouldn't hurt anyone. Meaning let the user know in the UI that what they're trying to do is not ok. I don't know, it's just my opinion. If we just allow the user to choose whatever he wants and then "fix it" in the background, it will create confusion, they'll think it's a bug the fact that they didn't get their drivers installed as they selected, and they will never learn anything from that. They'll think it's Clover's fault for not installing everything they wanted, not their fault, for selecting (stupid) incompatible things in the installer UI.

Edited by arsradu

Share this post


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

 

Hi Matt,

 

Uhm...no such issues on my side.

1379918933_Screenshot2019-06-28at10_21_56.png.f2d9ad139e8e3d4ae5efbe6fb43dfed8.png

 

However, I'm still getting this weird warning. Maybe because Clover was built on Mojave...? No idea. Clicking Install Anyway does seem to install it properly though.

 

1955136247_Screenshot2019-06-28at10_20_45.png.7e05700f5163c952b76c2a71ea419dc0.png

 

How are you building Clover? Maybe you're selecting something else in Drivers....? I only chose the mandatory (automatically checked) drivers + OSXAptioFix3Drv. That's all.

 

Also, we were previously talking about the post install script, which should prevent user from getting both AptioMemoryFix and OSxAptioFix drivers both at the same time.

There seems to be a case where this does not happen.

 

Because this is what I'm getting after installing Clover, while previously I had AptioMemoryFix in drivers64UEFI.

 

1408977674_Screenshot2019-06-28at10_28_47.png.d24c23f15a8ad8ebc19eb5f04d88c1e5.png

 

My guess is that since the previous Clover installer did have AptioMemoryFix (and it was checked for installation) and this one doesn't (since I've switched to the default OsXAptioFix3Drv instead, and did not include AptioMemoryFix in the build anymore), the installer doesn't know AptioMemoryFix is already present, and it doesn't do anything based on that. Doesn't skip the installation of OsXAptioFix3Drv, and it doesn't remove AptioMemoryFix either to avoid conflicts.

 

I'm looking forward to your opinions though. In my opinion this could be a real life scenario. If one day we ship Clover with AptioMemoryFix, and the other day we don't or we use something else instead, I see this as a potential problem on the long run, if people will end up with two (or more) Aptio fixes. And I've actually seen people with all 3 OsXAptioFixes in their drivers folders. Probably added manually, not through the installer. In which case there's not much we can do. But if that was through the installer...maybe we should think of a better solution to this other than relying on the post-install script to fix everything in the background.

 

I think a bit more transparency wouldn't hurt anyone. Meaning let the user know in the UI that what they're trying to do is not ok. I don't know, it's just my opinion. If we just allow the user to choose whatever he wants and then "fix it" in the background, it will create confusion, they'll think it's a bug the fact that they didn't get their drivers installed as they selected, and they will never learn anything from that. They'll think it's Clover's fault for not installing everything they wanted, not their fault, for selecting (stupid) incompatible things in the installer UI.

 

This revision was build on Mojave. I use sharing between two hacks for copy/paste Clover on Desktop.

"Clicking Install Anyway does seem to install it properly though." I hope the code was modified in the future in Clover source.

 

I try again 

Share this post


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

 

This revision was build on Mojave. I use sharing between two hacks for copy/paste Clover on Desktop.

 "Clicking Install Anyway does seem to install it properly though." I hope the code was modified in the future in Clover source.

 

I try again 

 

Yeah, but I mean...which method of building Clover did you use? Did you use the official steps provided by Slice a while ago for UDK2018, did you use another script? This is what I meant. And also, which drivers are you choosing for installation? I have a feeling that's where it gets stuck. Of course, and as always, I could be wrong. :)

 

EDIT: also, attached you can find my own build, if you wanna give this one a try, for comparison. Keep in mind, though, that it's built without AptioMemoryFix.

Clover_v2.4k_r4977.zip

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By e97
      HackPro X99 System
      Until Apple blesses us with the MacPro7,1 – this is for those that require tools to do their work.
      An appropriate bicycle for the mind.
       
       

       

       

       
      Specs:
       
      CPU: Intel Xeon E5-2678 v3 (12 core, 2.5 GHz / 3.3 GHz Boost)
      Motherboard: SZMZ X99-8D3
      RAM: 16GB DDR3-14900R 1866Mhz ECC RDIMM modules
      GPU: Radeon RX Vega 64 8GB
      Storage: Phison E12 m.2 NVMe PCI-E 3.0 x4 SSD
      Water blocks: BARROW CPU + GPU
      Radiator: 360mm x 25mm slim
      Pump: DDC
       
      Case dimensions: 431 mm x 342 mm x 177 mm
       
       
       
      XCPM OFF
       

       
      XCPM ON
       

       
      OpenCL
       

       
       
       
      iMacPro1,1
       

       
       

       
      OpenCL
       

       
       
      NVMe
       

       
       
      Win 10 x64 v1809
       
      AIDA64 - Cache & Memory
       

       
       
      Download:  https://github.com/xe97/X99-8D3-Clover
       
       
       
       
       
      Anyone else I forgot
       
       
    • By digivish
      Hi All - quick thing - I have a NUC 8i7BEH with 32GB RAM and 2 x 1TB SSD drives. Each drive has its own OS - Windows 10 and Catalina 10.15.
       
      Clover works well - Catalina Boots, so does Windows.
      Catalina - has sound over HDMI (to my monitor's speakers)
      Windows - no audio device found - It does show Realtek and Intel Display Drivers - but the speaker has a red"x" and in Devices, there is no entry for Microphone Array under Audio Input/Output. It does, however, show Intel display over the HDMI - but actually no sound.
       
      I have tried reinstalling Realtek drivers - now here's the thing...when it installs, it first uninstalls existing Realtek drivers - at this stage (and it's important) the sound starts working - as if uninstalling did the trick. As part of the installing, I have to reboot and upon reboot, it actually reinstalls the Realtek drivers. After that, I'm back to square 1. Unsure if it's the config.plist or boot args in clover. But something with Clover for sure.
       
      I have tested this by removing the Mac Drive with clover and just booting directly to Windows 10 bootloader and everything works as it should, I have sound over HDMI and the audio device shows. Just not when I boot with Clover.
       
      has anyone experienced this and have thoughts or pointers.
       
      Thanks a ton!
    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/viewtopic.php?f=28&amp;t=10578
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      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, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By kylon
      ACPI and Clover config for Acer Aspire v5-571PG
       
      Tested on Catalina 10.15.1 and Clover EFI 5098 (Should work on MacOS 10.9.x - 10.15.x)
       
      Not Working:
      - sd card reader
      - Atheros AR9462 (use a compatible USB wireless adapter, see below)
      - Touchscreen (MacOS 10.15 only)
       
       
      Notes:
      Disable Secure Boot and enable Legacy Boot. Legacy Mode is recommended.  
      **To reset your BIOS, power on the pc and hold the power button for about 30-40 seconds or you can short G2101 (RAM SLOT 1)**
       
       
      About the Atheros card:
      You can install ATH9KFixup (you will also need additional patches on 10.14+ to restore Atheros support) to enable this card, however,
      it will break sleep on MacOS 10.14+, it can freeze your OS at any time and it can freeze your network settings.
      Because of its instability it is highly recommended to buy a USB wireless adapter.
       
      You can find a list of working adapters, and the drivers, here.
       
       
      Additional things you will need:
      Latest Clover config (AcerAspireV5-571pg - CCE Bank) from here CloverEFI (download) or OpenCore (download - Untested) WhateverGreen (download) VoodooPS2 (download) VirtualSMC + SMCBatteryManager (download) AppleALC (download) Lilu (download) Mieze Realtek RTL8111 (download)  
      CloverEFI drivers you will need:
      ApfsDriverLoader EmuVariableUefi FSInject DataHubDxe VBoxHfs (if you have hfs partitions)  
      Remember to install BIOS drivers if you enable Legaby Boot.
       
       
       
      Feel free to ask for help.
      Please send me a PM if you have fixes or improvements, thanks.
    • By oldman20
      Hi all, i just want to know how can use mouse & keyboard USB with USB port when Cloverbootloader startup? I installed Ps2MouseDxe.efi and UsbMouseDxe.efi but not work, while touchpad and keyboard integrated laptop working!!
      thanks all!
      and 2nd question is: i installed success Catalina with APFS format, in Disk Utility show 2 partition is Catalina SSD and Catalina Data?? what is it?

      more and last, sorry cause it's short question: which most right, in 2 ways create USB installer Catalina,
      sorry my bad english!

      sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled && echo Catalina Boot Drive Created

      sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ Catalina.app --nointeraction

      thanks and regards    
×