Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

in my case, for long time, there is no issue related in FV2 driver. but

since AppleKeyFeeder.efi was added as default in clover package, GUI lag started.

i have to remove this driver as manual

Edited by Sherlocks

Share this post


Link to post
Share on other sites
Advertisement

Can clover installer have a sub menu or a checkbox for FV driver options so at least we know the drivers in that selection are for filevault? the problem is that the clover project does not have proper documentation. so if the dev's do not explain there project or driver properly how are we as end users going to  know what they do. only recently did we get some info of the drivers with the last rewrite of the installer.

13 hours ago, vit9696 said:

— Doctor, doctor, it hurts when I do like this, please help me.

— Alright, do not do it like this, and it will not hurt :)

 

Really, if you have some hidden love in FV2 drivers, it could be understood, but the only thing you do is taking devs' time trying to understand wtf your issue is. Do not use the drivers until you really need FV2. End of the story.

i understand your frustration but you as a dev might know what is what. clover is also used by non devs. but how can we help useres in the community when sometimes the dev's do not even know whats going on. like the issue sherlocks is having and he is a contributing dev.

 this is not a bash on you in any way or on anyone. it is just the gorilla in the room that no one likes to bring up. (problem no one wants to address)

 

i am the guy that has to help the end user use your projects just in case you where wondering.

Edited by bronxteck

Share this post


Link to post
Share on other sites

This is open source software

Quote

 * This software is provided 'as-is', without any express or implied
 * warranty.  In no event will the authors be held liable for any damages
 * arising from the use of this software.
 *

 

Share this post


Link to post
Share on other sites
On 9/20/2018 at 12:26 AM, kylon said:

My keyboard is not working in clover 4674!
I can t boot any os.

Default drivers + emuVariable (efi drivers, no bios drivers)

Was working on 4658, i have an ami bios, laptop.

 

Replace

/EFI/boot

with the one from r4658 (source).

Share this post


Link to post
Share on other sites

So, 4674 is broken

I removed every fv2 driver and the keyboard is still not working
@k0nrad
Not working

I need to install clover 4658 on top to make my keyboard working again

Share this post


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

So, 4674 is broken

I removed every fv2 driver and the keyboard is still not working
@k0nrad
Not working

I need to install clover 4658 on top to make my keyboard working again

 

Hi

Can you give a list of the drivers you are using with Clover and the deleted FV2 drivers.

Share this post


Link to post
Share on other sites

You can build clover Package without mandatory FileVault Drivers

Take look here ➜  Build-FileVault-Clover

that's work for UDK2018 and UDK2

I hope some Dev integrate my change in the Clover repos

 

 

1730396448_Capturedcranle2018-09-2112_32_58.png.f85a76152bd632cb70dd1b03b77b2f8e.png

Edited by chris1111

Share this post


Link to post
Share on other sites
38 minutes ago, chris1111 said:

You can build clover Package without mandatory FileVault Drivers

Take look here ➜  Build-FileVault-Clover

that's work for UDK2018 and UDK2

I hope some Dev integrate my change in the Clover repos

 

 

1730396448_Capturedcranle2018-09-2112_32_58.png.f85a76152bd632cb70dd1b03b77b2f8e.png

 

Great Job :) These file modifications are very interesting. For beginners, I think it would be easier if FV2 files are not checked by default, in my opinion.

Share this post


Link to post
Share on other sites
51 minutes ago, chris1111 said:

You can build clover Package without mandatory FileVault Drivers

Take look here ➜  Build-FileVault-Clover

that's work for UDK2018 and UDK2

I hope some Dev integrate my change in the Clover repos

 

 

1730396448_Capturedcranle2018-09-2112_32_58.png.f85a76152bd632cb70dd1b03b77b2f8e.png

Thank you for being part of the solution chris. this is what most users where asking for. a clear separation of what what is what. at least now the end user knows that those drivers are different to the general ones. as for EULA we know it is open source slice. its just small contributions like this that make the project better. that is what open source is.

Share this post


Link to post
Share on other sites
 

Hi

Can you give a list of the drivers you are using with Clover and the deleted FV2 drivers.

My drivers now

 

DataHubdxe

Emuvariable

FsInject

Smchelper

VboxHfs

 

Clover 4658 (it works with fv2 drivers)

 

I don t remember, i disabled every driver that said "for filevault 2" in the installer

 

I don t think the issue is fv2 here

Share this post


Link to post
Share on other sites
11 hours ago, kylon said:

My drivers now

 

DataHubdxe

Emuvariable

FsInject

Smchelper

VboxHfs

 

Clover 4658 (it works with fv2 drivers)

 

I don t remember, i disabled every driver that said "for filevault 2" in the installer

 

I don t think the issue is fv2 here

 

You don't use any Aptiodriver such like OSXAptio or AptioMemoryFix...? On my system Asus mobo, I have aptionmemoryFix for UEFI. Clover commit r4673 works fine

Share this post


Link to post
Share on other sites
18 hours ago, bronxteck said:

Thank you for being part of the solution chris. this is what most users where asking for. a clear separation of what what is what. at least now the end user knows that those drivers are different to the general ones. as for EULA we know it is open source slice. its just small contributions like this that make the project better. that is what open source is.

Thank you 

I did this exactly to help the community 

18 hours ago, Matgen84 said:

 

Great Job :) These file modifications are very interesting. For beginners, I think it would be easier if FV2 files are not checked by default, in my opinion.

Thanks 

Share this post


Link to post
Share on other sites
2 hours ago, chris1111 said:

Thanks 

 

I try your modified files: works fine of course. Why two directory for FileVault drivers? It's the same for x64 and x64UEFI. Also I make only one folder  for my personal use.

Share this post


Link to post
Share on other sites
2 hours ago, Matgen84 said:

 

I try your modified files: works fine of course. Why two directory for FileVault drivers? It's the same for x64 and x64UEFI. Also I make only one folder  for my personal use.

I you select UEFI Only drivers FileVault2 for Legacy(x64) not appears on choice

Of course If you are deselect UEFI Only the Drivers x64 filevault2 is selectable

Edited by chris1111

Share this post


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

I you select UEFI Only drivers FileVault2 for Legacy(x64) not appears on choice

Of course If you are deselect UEFI Only the Drivers x64 filevault2 is selectable

Alright I understand :)

Share this post


Link to post
Share on other sites

4674 bricks my X58 system.I just get a cursor, tried verbose still nothing that I can see besides a cursor.I should note that I always delete the EFI/Boot folder and leave the EFI/Clover as outlined HERE.Back to 4658 and all is well.Bless

Share this post


Link to post
Share on other sites

Would it be possible to hide a Volume (Trying to hide the Preboot Entires) in the Config.plist and not have F3 show it in the Clover GUI, I thought there was a way but it doesn't seem to work for me?

Share this post


Link to post
Share on other sites

@Slice I believe boot.efi cause I replaced 4678 EFI/boot with the one from 4658 EFI/boot and it worked as normal.i did not mess with CloverX64.efi.

 

Share this post


Link to post
Share on other sites
[mention=112217]Slice[/mention] I believe boot.efi cause I replaced 4678 EFI/boot with the one from 4658 EFI/boot and it worked as normal.i did not mess with CloverX64.efi.
 
try to install 4678 and remove AppleKeyFeeder.efi in UEFI64 Folder on EFI

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
5 hours ago, D-an-W said:

Would it be possible to hide a Volume (Trying to hide the Preboot Entires) in the Config.plist and not have F3 show it in the Clover GUI, I thought there was a way but it doesn't seem to work for me?

only hide. Not completely disappear.

Share this post


Link to post
Share on other sites

Hi Clover Team @vit9696  @savvas and others users

 

I can't build Clover r4678  because AppleSupportPkg/Apfsdriverloader files problem. Take a look, please: build.py error 7000

 

I've same error when I use macbuild.tool from AppleSupportPkg-master folder

 

Sorry for my bad english

Building ... /Users/mathieu/src/EXT_PACKAGES/AppleSupportPkg/Platform/ApfsDriverLoader/ApfsDriverLoader.inf [X64]
[CC] AppleImageLoader
/Users/mathieu/src/EXT_PACKAGES/AppleSupportPkg/Platform/ApfsDriverLoader/ApfsDriverLoader.c:532:36: error: operand of type 'EFI_GUID' (aka 'GUID') where arithmetic or pointer type is required
        if (CompareMem((EFI_GUID *)(ApplePartitionInfo->PartitionType),
                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[CC] FirmwareVolumeInject
1 error generated.
make: *** [/Users/mathieu/src/UDK2018/Build/AppleSupportPkg/RELEASE_XCODE8/X64/AppleSupportPkg/Platform/ApfsDriverLoader/ApfsDriverLoader/OUTPUT/ApfsDriverLoader.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/mathieu/src/UDK2018/Build/AppleSupportPkg/RELEASE_XCODE8/X64/AppleSupportPkg/Platform/ApfsDriverLoader/ApfsDriverLoader]


build.py...
 : error F002: Failed to build module
	/Users/mathieu/src/EXT_PACKAGES/AppleSupportPkg/Platform/ApfsDriverLoader/ApfsDriverLoader.inf [X64, XCODE8, RELEASE]

- Failed -

 

 

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 gengstapo
      @Hervé
       
      Im having similar issue with my HS setup, dell latitute 3480, i5-7200U
      Once the hdmi plugged in, the laptop display went blank, only could see the external tv
      But, when i put my laptop to sleep & wake up again, both screen got display (hdmi still connected)
      Even the hdmi could be plugged off & in (after sleep), the laptop display is fine
       
      What could be the culprit?
      Dell’s MacBook Pro IORegistry.zip
      config.plist.zip
    • By TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
    • By MaLd0n
      ---TUTORIAL---
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Original Post--
      https://www.olarila.com/topic/6531-olarila-hackbeast-z390-designare-thunderbolt-full-dsdt-patches-clover-opencore/
       
      --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://www.olarila.com/topic/6364-mojave-catalina-on-mobos-series-100200300-with-opencore-bootloader/
      *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 dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
×