Jump to content
ErmaC

Clover General discussion

20,630 posts in this topic

Recommended Posts

Posted (edited)
7 hours ago, fusion71au said:

 

@arsradu,

 

I noticed the makeiso script formats the iso with -eltorito-boot, to allow for legacy BIOS booting, and it also uses boot6 instead of boot7 (BiosBlockIO) which works on your system.  I'm guessing the presence of the legacy BIOS code is what makes the CD-DVD-ROM "invisible" to your firmware when it is set to boot to "UEFI only".

 

Try the following modified makeiso files (place in ~/src/edk2/Clover/CloverPackage) to generate the Clover ISO instead of the default one...

makeiso_boot7.zip ---> uses boot 7 instead of boot 6 for legacy boot

makeiso_uefi_only.zip ---> removed -eltorito-boot formatting so only UEFI booting possible

 

PS BiosBlockIO is still available in the latest Clover Pkg installer r4995.  If the boot7/BosBlockIO installed by r4995 doesn't work, then simply replace it with the boot7 "boot" file from Clover r3911 (keep the rest of the files from Clover r4995, including CLOVERX64.efi, BOOTX64.efi and the new drivers folder file structure)...

 

BiosBlockIO.png.b2405cfea903cbfcee7b388de9265433.png1770777261_Bootfile.png.a70ac1b6f2c7150185c4c4e99ea329a9.png

 

Good Luck!

Clover_v2.4k_r4995.pkg.zip

 

Hi there! :) 

 

So, let's see.

 

1. I'm guessing you're building Clover with a custom script or something, cause I couldn't get mine to add BiosBlockIO. :P Also, I see yours also has a few third party drivers and other wonders.

 

This is what I get with regular compiling.

743490089_Screenshot2019-07-13at08_37_37.thumb.png.6b7bcfb96c4a29f506f970492100c6ca.png

 

However, even with your 4995 pkg, I still can't boot. But the behaviour is a little different than before.

 

I get the cursor on the top-left corner, the "not found" thing, but no red screen anymore. It's just stuck at "not found".

 

Replacing boot from 3911 into the 4995 USB also doesn't do anything. Same exact behaviour as above (stuck at "not found").

 

2. makeiso_boot7 - same as above. Stuck at "not found".

 

I've got the exact same behavior when nothing was written on the CD and trying to boot from it (stupid mistake on my side, I erased the disk, but forgot to put something back on it). Still, it was interesting to me that I got the exact same behaviour. So, no difference with or without content, that's what I'm trying to say.

 

3. makeiso_UEFI_only - still not visible in boot menu.

 

Also, not sure that's intended (but I've got the same issue with the regular makeiso), but I've got no themes (at all) in the /themes folder on the iso...although the themes are present in CloverV2/themespkg. But they don't seem to make their way into the actual iso file.

 

I don't think my inability to boot has anything to do with the themes, since I have the same issue with your 4995 pkg, and I do have themes on the USB drive, so it can't be that. But I'm just mentioning it in case they should be there (which I'm guessing they should).

 

 

Edited by arsradu

Share this post


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

1. I'm guessing you're building Clover with a custom script or something, cause I couldn't get mine to add BiosBlockIO.

you forgot to add -mc to ebuild.sh?

./ebuild.sh -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8

 

Share this post


Link to post
Share on other sites
Posted (edited)
2 minutes ago, vector sigma said:

you forgot to add -mc to ebuild.sh?


./ebuild.sh -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8

 

Can't forget something I never knew I needed. :))) But yeah, that part was missing. Thank you!

Edited by arsradu

Share this post


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

Replacing boot from 3911 into the 4995 USB also doesn't do anything. Same exact behaviour as above (stuck at "not found").

 

There might be a bit of confusion here.  Legacy boot should work now that you proved it does with r3911 :P.

  1. Install latest Clover r4996 with pkg installer in legacy mode targeting your USB drive (custom option: install in EFI etc)
  2. Make sure all your needed efi drivers are in EFI/CLOVER/drivers/BIOS, normal kexts, config.plist present in their respective folders etc
  3. Delete the file named "boot" at the root folder, / , of your USB drive's EFI partition (this is actually boot6=CloverEFI 64 bits SATA, renamed as "boot")
  4. Replace with boot7 = CloverEFI 64 bits BiosBlockIO (which I extracted from official Clover r3911 ISO on Sourceforge) on the root of the USB drive, renamed as "boot"

 

Try legacy boot again to your USB...

 

46 minutes ago, arsradu said:

Can't forget something I never knew I needed. :))) But yeah, that part was missing. Thank you!

Make sure you put the working boot7 from Clover r3911 in ~/src/edk2/Clover/CloverPackage/CloverV2/Bootloaders/x64 before running makeiso_boot7 from your ~/src/edk2/Clover/CloverPackage folder.  Otherwise it also won't be present in your Clover ISO :lol:.

 

Also regarding the missing embedded theme in your ISO:  Did you copy the embedded theme folder from ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/themes to ~/src/edk2/Clover/CloverPackage/CloverV2/themespkg before running makeiso?

 

 

 

2 hours ago, XLNC said:

is aptiomemfix removed from clover ? 

 

Yes, this is an acidanthera project now. 

 

If you build Clover with Build_Clover.command and specify XCODE5 toolchain, you will still find it compiled in the ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 folder  ---> manually copy it to your ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix folder.  Then cd to ~/src/edk2/Clover/CloverPackage and run ./makepkg to create the Clover installer.

 

Edited by fusion71au

Share this post


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

I made this change because of what? 

It was initially VOID*, but it is not compatible with VS2013 (error C2036).

Well that explain why. C standard treat void as an incomplete type while the gnu one consider it to be size 1. 

Share this post


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

There might be a bit of confusion here.  Legacy boot should work now that you proved it does with r3911 :P.

 

  1. Install latest Clover r4996 with pkg installer in legacy mode targeting your USB drive (custom option: install in EFI etc)
  2. Make sure all your needed efi drivers are in EFI/CLOVER/drivers/BIOS, normal kexts, config.plist present in their respective folders etc
  3. Delete the file named "boot" at the root folder, / , of your USB drive's EFI partition (this is actually boot6=CloverEFI 64 bits SATA, renamed as "boot")
  4. Replace with boot7 = CloverEFI 64 bits BiosBlockIO (which I extracted from official Clover r3911 ISO on Sourceforge) on the root of the USB drive, renamed as "boot"

 

Try legacy boot again to your USB...

 

 

 

 

Yeah, I guess I mixed some drivers...cause now IT WORKS!

 

I already replaced that boot file, as you mentioned. But I guess the problem was somewhere else....?

 

So, right now, I managed to get 4997 to boot (all the way into the OS) in Legacy mode.

But here's how:

1. on my existing USB drive with 3991, I replaced BOOTX64.efi in /BOOT and CLOVERX64.efi in /CLOVER with the ones I compiled for myself (version 4997) from my SSD's EFI folder. Call it "manual upgrade"...? :))

2. I copy-pasted drivers from drivers64 to drivers/BIOS and from drivers64UEFI to drivers/UEFI. The new /drivers folder was already there from my previous installations of 49xx versions. So I just copy-pasted from the old folder structure to the new one.

 

So maybe the reason why I couldn't boot with BiosBlockIO (getting stuck at Not Found) was the driver, not the boot file itself. That...or I was doing something else wrong. But I think that was it.

 

Update: confirmed.

 

SATA doesn't work (red screen).

BiosBlockIO DOES work (including from 4997, which now I can compile on my own, thanks to Vector Sigma's feedback).
 

BUT

 

The drivers need to be rewritten. Otherwise I get stuck with BiosBlockIO. As I said, the behaviour is a little different. With BiosBlockIO and wrong drivers, I get stuck at "Not Found". No red screen in this case. Just stuck.

With BiosBlockIO and correct drivers, all fine, I can boot Mojave with no problems.

 

With the default drivers in 4997, I can't boot. I have to look more into it, but not right now

 

However, with drivers copy-pasted from drivers64 and drivers64UEFI (from 3911, with some additions) into the new folder structure, it does boot.


2064342132_Screenshot2019-07-13at11_30_07.thumb.png.a48243a0aaa7ec032162fea2049368b4.png

 

*ApfsDriverLoader has been added by me, the rest of the drivers are from original 3911 installation.

482672959_Screenshot2019-07-13at11_30_22.thumb.png.f43b53c1f77369596cee67d819063ad8.png

 

*ApfsDriverLoader adn OsXAptioFix3Drv have been added by me. The rest of them are from the original 3911 installation.

drivers.zip

Edited by arsradu

Share this post


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

If you build Clover with Build_Clover.command and specify XCODE5 toolchain, you will still find it compiled in the ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 folder  ---> manually copy it to your

Guys, isn't more easy to go at github/acidanthera/AptioMemoryFix/release and just download it?:whistle:

 

if you want it in the package, just copy it in

../CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix/

just before call 'make pkg'

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
29 minutes ago, vector sigma said:

Guys, isn't more easy to go at github/acidanthera/AptioMemoryFix/release and just download it?:whistle:

 

if you want it in the package, just copy it in


../CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix/

just before call 'make pkg'

 

At the moment, the Build_Clover.command script has not been updated to take into account the new /Drivers folder structure that you introduced.  Before, AptioMemoryFix was automatically compiled and included in the final installer.pkg presented to the end user.

 

btw, I found another typo in the makeiso.script...for latest r5000, boot? should be boot6 I assume...attached fixed makeiso.fixed typo.zip OK, it copies both boot6 and boot7 :P

 

1879256035_typobootinmakeiso.png.15cde83f1d95db2955e07c99bd5fd5c4.png

 

Edited by fusion71au

Share this post


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

 

At the moment, the Build_Clover.command script has not been updated to take into account the new /Drivers folder structure that you introduced.  Before, AptioMemoryFix was automatically compiled and included in the final installer.pkg presented to the end user.

 

btw, I found another typo in the makeiso.script...for latest r5000, boot? should be boot6 I assume...attached fixed makeiso.fixed typo.zip

 

1879256035_typobootinmakeiso.png.15cde83f1d95db2955e07c99bd5fd5c4.png

 

Isn't a typo, it's correct. It just copy both boot6 and boot7 or whatever starts with boot

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
44 minutes ago, vector sigma said:

@arsradu can you kindly try the attached iso if works in pure UEFI?

Clover-v2.4k-5000-X64.iso.zip

 

Sadly...nope... BIOS is set to see both Legacy and UEFI drives. For all my other UEFI drives (such as my HDD and SSD), it does show something like "UEFI OS:". For the DVD ROM. It doesn't. Which makes me think it's not UEFI (yet).

 

Also, selecting that DVD ROM (the legacy mode entry), I get this message (old, classical "nope, that's not it" kind of message).

 

The message is most likely intended. But...yeah, no UEFI yet.

 

IMG_0008.thumb.jpeg.2c7d159a24ebc772ed5f3444cc79f533.jpeg

Edited by arsradu

Share this post


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

 

Sadly...nope... BIOS is set to see both Legacy and UEFI drives. For all my other UEFI drives (such as my HDD and SSD), it does show something like "UEFI OS:". For the DVD ROM. It doesn't. Which makes me think it's not UEFI (yet).

 

Also, selecting that DVD ROM (the legacy mode entry), I get this message (old, classical "nope, that's not it" kind of message).

 

The message is most likely intended. But...yeah, no UEFI yet.

 

Thanks anyway. I need a rw cd, or a UEFI virtual machine to do some tests..

Share this post


Link to post
Share on other sites
1 minute ago, vector sigma said:

Thanks anyway. I need a rw cd, or a UEFI virtual machine to do some tests..

Sure, no worries. Fusion71au seems to have made some progress with VM (if I got this right).

 

If you need any more tests on "real hardware", meaning a real CD, I can help you with that. :) 

Share this post


Link to post
Share on other sites
Posted (edited)

Hi @fusion71au did you also install 10.15 in HFS+..? On my case am no longer able to proceed Clover installation since r4999. It just got stuck at osascript read-write or whatever it's name. I believe HFS+ has no r/o limitation under Catalina. And it does nothing with $ sudo mount -uw / either. Thanks.

Edited by Badruzeus

Share this post


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

osascript read-write or whatever it's name. I believe HFS+ has no r/o limitation under Catalina. Thanks.

I'll fix it, but is this a hack or it's normally allowed?

Share this post


Link to post
Share on other sites
1 minute ago, vector sigma said:

I'll fix it, but is this a hack or it's normally allowed?

absolutely a hack, Apple has given warning back in Sierra time that HFS was being replaced with APFS. It's just some want to stay with old methods.

Share this post


Link to post
Share on other sites
6 hours ago, fusion71au said:

 

There might be a bit of confusion here.  Legacy boot should work now that you proved it does with r3911 :P.

  1. Install latest Clover r4996 with pkg installer in legacy mode targeting your USB drive (custom option: install in EFI etc)
  2. Make sure all your needed efi drivers are in EFI/CLOVER/drivers/BIOS, normal kexts, config.plist present in their respective folders etc
  3. Delete the file named "boot" at the root folder, / , of your USB drive's EFI partition (this is actually boot6=CloverEFI 64 bits SATA, renamed as "boot")
  4. Replace with boot7 = CloverEFI 64 bits BiosBlockIO (which I extracted from official Clover r3911 ISO on Sourceforge) on the root of the USB drive, renamed as "boot"

 

Try legacy boot again to your USB...

 

Can't forget something I never knew I needed. :))) But yeah, that part was missing. Thank you!

Make sure you put the working boot7 from Clover r3911 in ~/src/edk2/Clover/CloverPackage/CloverV2/Bootloaders/x64 before running makeiso_boot7 from your ~/src/edk2/Clover/CloverPackage folder.  Otherwise it also won't be present in your Clover ISO :lol:.

 

Also regarding the missing embedded theme in your ISO:  Did you copy the embedded theme folder from ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/themes to ~/src/edk2/Clover/CloverPackage/CloverV2/themespkg before running makeiso?

 

 

 

 

Yes, this is an acidanthera project now. 

 

If you build Clover with Build_Clover.command and specify XCODE5 toolchain, you will still find it compiled in the ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 folder  ---> manually copy it to your ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix folder.  Then cd to ~/src/edk2/Clover/CloverPackage and run ./makepkg to create the Clover installer.

 

And sorry for noob question: if I use the Acidanthera one, I must put it in the memory fix folder?

Share this post


Link to post
Share on other sites
34 minutes ago, brousseau6933 said:

And sorry for noob question: if I use the Acidanthera one, I must put it in the memory fix folder?

Found myself: just added it in Drivers/UEFI...

Share this post


Link to post
Share on other sites

Guys, please don't mad to me;

 

What are the differences between VBoxHfs and the HFSPlus? Both say "EFI filesystem driver for HFS+" is that so, what are the differences?

 

Share this post


Link to post
Share on other sites

 

7 minutes ago, telepati said:

What are the differences between VBoxHfs and the HFSPlus? Both say "EFI filesystem driver for HFS+" is that so, what are the differences?

VBoxHfs = open source driver that works really good, read only.

HFSPlus = extracted from Apple's firmware. Someone says you need it for RAID configurations. Otherwise VBoxHfs it's enough.

Share this post


Link to post
Share on other sites
Posted (edited)

@vector sigma or @fusion71au

 

Any idea which part of the makeiso script formats the resulting iso image as Apple Partition Map? I can't figure it out.

 

1370411295_Screenshot2019-07-13at20_40_33.thumb.png.fd8606b922be406b2da9d34bd1924114.png

 

Edit:

 

apparently this part:

hdiutil makehybrid...

 

Edited by arsradu

Share this post


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

Guys I think is better to commit all translatioons tomorrow and give times to any other is doing this. @Slice, why not opening a Topic for translations only?

OK, done!

All post about translations splitted into new topic Clover Localizations

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&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    
×