OpenCorePkg / Documentation / Configuration Template / Bugtracker
Discussion and installation should be done in a separate thread! This thread is for development only!
Current status as of April 2019:
Support for UEFI and DuetPkg (legacy) booting
APFS and HFS+ compatibility
ACPI patcher (adding, dropping, binary patching, relocation)
Apple-compatible bless implementation
DataHub and SMBIOS generation
Symbolic kext and kernel patcher
Direct kext injection/patching/blocking within prelinkedkernel
Installation/Recovery/FileVault 2 support
Configuration in config.plist with open documentation
Simple boot picker for quick launch
Direct boot from dmg images
Known defects (for 02.05.2019):
Custom memory configuration is unsupported, and provided as is.
Full secure boot compatibility is in progress.
Hibernation support is missing.
For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
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:
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
Slice is glad to present a new EFI bootloader. CLOVER Now version 2 rEFIt based.
It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision. I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources. http://cloverefiboot.sourceforge.net/
If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma! Continued by blackosx and STLVNUB.
How to do UEFI boot
How to use - common words
Calculator for Automatic DSDT fix
Instructions for GraphicsInjector
Any kexts patching with some Samples
Hiding unnecessary menu entries
Instruction for DSDT corrections to do DeviceInjection works
About kexts injection
Instructions for P- and C-states generator
Patching DSDT to get Sleep working
CPU settings and geekbench
ACPI tables loading
How to make orange icons to be metallic
How to make software RAID (by Magnifico)
How to modify InstallESD.dmg (by shiecldk)
Using extra kexts and skipping kernelcache
Choosing EFI drivers
Automatic config.plist creating
Custom DSDT patches
How to do sleep/wake working with UEFI BOOT
DeviceID substitution (FakeID)
Using Custom OS Icons
Error allocating pages while starting OS
I'm trying to boot MacOS on a Chromebook without UEFI.
I'm stuck at getting the bootloader (Chameleon/Clover) to work.
My setup / context:
I have an Acer Chromebook Spin 13.
2 x USB-C
1 x USB-A 3.0
No USB A 2.0 (I've read that Clover has problems with USB 3.0)
There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS.
Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related.
This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options.
If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.
What I've tried so far:
Only selected setting was "Install chameleon on the chosen path", rest was unselected.
1 - Install chameleon first without restoring the basesystem:
> boot0: GPT
> boot0: done
(hangs; pressing power button once shuts down
Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
2 - Install Chameleon after restoring the base system:
> boot0: GPT
> boot0: GPT
> boot0: doneboot1: /boot <- Exactly like that, no line break in between
(hangs; pressing power button once shuts down)
I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
I tried multiple settings and configurations, but all of them boiled down to either one of these.
1 - Doesn't do anything, just hangs at "Booting from usb..."
2 - Boots into the blue/grey mode as shown in the attached images.
According to MrChromebox, this could be an old Tianocore DUET
It doesn't detect anything (cpu frequency, ram, partitions or disks)
I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
A few questions that came up:
Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer?
What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET
Where does it come from? Clover? The mainboard itself?
Why does the blue/grey thing not detect my processor frequency or any partitions/drives?
Can I use some sort of DUET bootloader to chainload Clover?
If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!