Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

Advertisement

Hi, about GUI too. If there's any dev could manage "volume_external_recovery.icns" to show correctly on boot screen. Specially useful for theme with OS badge.

 

Thanks  :) 

Share this post


Link to post
Share on other sites

the last clover 4313 as well as several revision before

do not see the apple icons after an install startosinstall method on the boot, he see an HD

Share this post


Link to post
Share on other sites

I understand nothing.

with the startosinstall method normally you have this icon in first boot 

os_mac10.png

and for some reason the last clover 4313 as well as several revision before

Clover do not see the apple icons  only this icons

vol_in10.png

Share this post


Link to post
Share on other sites

with the startosinstall method normally you have this icon in first boot 

os_mac10.png

and for some reason the last clover 4313 as well as several revision before

Clover do not see the apple icons  only this icons

vol_in10.png

Is it APFS? Or new OS revision has new boot.efi location? This icon is working but wrong picture?

Why it should be apple icon what the icon means?

Share this post


Link to post
Share on other sites

Is it APFS? Or new OS revision has new boot.efi location? This icon is working but wrong picture?

Why it should be apple icon what the icon means?

yes APFS  HS 10.13.1

IT must be an apple when he boot on macOS Install Data 

startosinstall method

 

captu109.png

Share this post


Link to post
Share on other sites

Too far from here  :(

I do not know which revision more recent than 4222 is correct?

Sorry  :blush:

edit***

Anyway its not really important, just remember that to it's an HD and not an apple

Share this post


Link to post
Share on other sites

I do not know which revision more recent than 4222 is correct?

Sorry  :blush:

edit***

Anyway its not really important, just remember that to it's an HD and not an apple

But what this icon should launch?


// OS X installer paths
STATIC CHAR16 *OSXInstallerPaths[] = {
  L"\\Mac OS X Install Data\\boot.efi",
  L"\\macOS Install Data\\boot.efi",
  L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",
  L"\\OS X Install Data\\boot.efi",
  L"\\.IABootFiles\\boot.efi"
};

Or something else?

Share this post


Link to post
Share on other sites

But what this icon should launch?


// OS X installer paths
STATIC CHAR16 *OSXInstallerPaths[] = {
  L"\\Mac OS X Install Data\\boot.efi",
  L"\\macOS Install Data\\boot.efi",
  L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",
  L"\\OS X Install Data\\boot.efi",
  L"\\.IABootFiles\\boot.efi"
};

Or something else?

Not sure but I think its this one

L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",

 

 

post-951341-0-94355800-1511382383_thumb.png

post-951341-0-06067500-1511382391_thumb.png

Share this post


Link to post
Share on other sites

 

the last clover 4313 as well as several revision before

do not see the apple icons after an install startosinstall method on the boot, he see an HD

 

 

Clover uses the generic Apple logo only when it doesn't know the OS version it is booting eg when a new OS X comes out or if a custom entry is used in config.plist without specifying a custom image file to use ...

 

post-846696-0-66505300-1511383783_thumb.png

post-846696-0-82443000-1511383884_thumb.png

 

Since Clover r4293, Clover correctly recognizes the OS version in the "macOS Install Data" folder by reading the SystemVersion.plist ---> fixed kext injection failing from /CLOVER/kexts/10.13 due to OS ver not being recognised.  This had the side-effect of now showing the correct OS ver icon/badge instead of the generic Apple logo before...

 

post-846696-0-78695700-1511384512_thumb.png

 

I think what you are wanting is actually a new feature request - a supplementary icon/badge beside the main icon when the loader entry type is OSXInstaller eg like the plus sign for OSXRecovery...

Share this post


Link to post
Share on other sites

Clover uses the generic Apple logo only when it doesn't know the OS version it is booting eg when a new OS X comes out or if a custom entry is used in config.plist without specifying a custom image file to use ...

 

 

 

Since Clover r4293, Clover correctly recognizes the OS version in the "macOS Install Data" folder by reading the SystemVersion.plist ---> fixed kext injection failing from /CLOVER/kexts/10.13 due to OS ver not being recognised.  This had the side-effect of now showing the correct OS ver icon/badge instead of the generic Apple logo before...

 

 

I think what you are wanting is actually a new feature request - a supplementary icon/badge beside the main icon when the loader entry type is OSXInstaller eg like the plus sign for OSXRecovery...

I do not want new future I just wanted the apple as before in High Sierra  :D

Since the first day High Sierra the apple was there for startosinstall method and its disappear :(

If you say that it was disappear because of the version stystem fix ; I did not know that now is the HS icons os_mac11.pngos_mac12.png

I was going to do without  :lol: I thought the apple was really connected to startosinstall method

Edit ****

@fusion71au thanks for the explanations and sorry @Slice for disturbing you with this.

I was blinding through the apple and I did not see that the version was well HS

Share this post


Link to post
Share on other sites

Any way to make Clover boot into macOS installer when update? When I click update & restart on App Store, Clover should boot into "macOS installer volume name" if Clover found it, if not Clover should continue boot into "macOS system volume name". That way make Clover Bootloader look like a real mac and more easier to set update

Share this post


Link to post
Share on other sites

I tried to install Clover on my desktop, to use its UEFI emulator to be able to boot Windows 10 on a GPT partitioned disk on a legacy BIOS motherboard (P6T Deluxe V2), but I am unable to get it to boot into Clover. I plan to dual boot Windows 10 and NixOS (a Linux distribution). Normally I use NixOS on my desktop, so I first created a disk image with Clover on it, by using the following script: https://github.com/m13253/clover-linux-installer

 

I ran this disk image via Grub2 and memdisk (from Syslinux) on my laptop (Asus UL30A), which worked fine. It took a while because my USB stick is very slow, but it did boot into Clover without any issue. I then installed Clover on my new desktop disk using the same script. Unfortunately all I got was an underscore in the top left of the screen. When I try to boot Clover from the same USB stick as I used for the laptop, it eventually just reboots. I then tried to boot the Arch Linux iso on my desktop with the same USB stick, Grub2 and memdisk, and that did work, so it probably has to do with the hardware configuration of my desktop compared to my laptop. I changed quite a lot in my BIOS settings of my desktop, so I tried resetting it to the defaults, but that had no effect, still no Clover.

 

Any ideas what I could do to make Clover work on my desktop? Are the others with similar hardware that ran into issues? Should I maybe use an older version of Clover?

 

For now I will go with my plan B, to format the disk with MBR, install Windows 10, reformat the partition table to GPT and boot into Windows via a memdisk loaded MBR drive image that contains Windows 10's boot files. This allows me to boot into Windows 10 on a GPT partition disk, but I'd rather use Clover instead of this workaround.

 

Some more info about my desktop's hardware configuration:

CPU: i7 920 2.67Ghz (normally overclocked to 3.6Ghz)

MB: Asus P6T Deluxe v2

Share this post


Link to post
Share on other sites

Any way to make Clover boot into macOS installer when update? When I click update & restart on App Store, Clover should boot into "macOS installer volume name" if Clover found it, if not Clover should continue boot into "macOS system volume name". That way make Clover Bootloader look like a real mac and more easier to set update

Already done.

What Clover version you mean?

@grayen

 

I had an experience to boot macOS and Windows 7 Pro 64bit UEFI on GPT formatted disk on legacy-BIOS computer with Core2Duo CPU by Clover. It is possible as you said. I don't know if Windows 10 required something more.

Share this post


Link to post
Share on other sites

@Slice It is not that I have trouble booting Windows 10 with Clover, it is that I am unable to get Clover to show in the first place. I figure that I have to enable or disable some BIOS setting on my desktop, since the same setup works on my laptop.

Share this post


Link to post
Share on other sites

@Slice It is not that I have trouble booting Windows 10 with Clover, it is that I am unable to get Clover to show in the first place. I figure that I have to enable or disable some BIOS setting on my desktop, since the same setup works on my laptop.

Sounds like the boot order needs changing. If clover is installed properly you should be able to set that drive as first option in bios.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

@SavageAUS I did change the boot order after installing clover and used the "select boot device" popup at startup to boot into my USB stick, so I do not see how that could be the issue, but it was a good suggestion. I have searched quite a bit before posting here, but I have not found anything worthwhile to help me fix it, hence me posting here. I did found two people with the same hardware configuration with regards to the CPU and MB, so it should work in theory:

 

http://www.insanelymac.com/forum/topic/301376-complete-yosemite-on-x-powergtx480i7-920267/

http://www.insanelymac.com/forum/topic/329066-cant-boot-ubuntu-when-selecting-from-clover-on-legacy-triple-boot/

 

I am now going to try a preconfigured boot USB stick, to see if clover boots from there on my desktop:

https://www.aioboot.com/en/features/

Share this post


Link to post
Share on other sites

I tried AIO Boot, but when I run Clover from it, I get the same as before. I did however now notice a 7 showing up after about 2 seconds, which I assume is Clover telling me that it is using boot7 (Clover 64-bit with BiosBlockIO driver that works with any controller supported by the BIOS). However it just shows me the underscore in the top, no forced reboot, but I rebooted it myself after waiting a few minutes. I also tried pressing 6 at this two seconds pause, because it is stated that it will then boot in a different 64-bit boot loader, but I can press 6 however many times I want, it will still show me the 7 at the end of the 2 second interval.

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 
       
       
×