Jump to content

OpenCore General Discussion


dgsga
8,887 posts in this topic

Recommended Posts

@SavageAUS I think you have nailed it...not only did I remove all BootChime references but also the AudioDxe.efi and BootChimeCfg.efi which thinking about it were not OC built but from the Goldfish64 Github so might have been the issue all along as I can now boot without ApfsDriverLoader.efi or any reference to it.

 

THANK YOU!

 

I have also got sound working using the OC files but can't figure out how to turn it down a bit...any tips (It's way louder than when booted)?

 

Audio working but too loud!

Spoiler

728338883_Screenshot2020-08-27at15_20_31.png.3cc2053ab6d299dd5a42671731f1d509.png

 

Folder Structure now...

Spoiler

601954063_Screenshot2020-08-27at15_19_51.png.526ac59b3291f9dc06bba809b438a177.png

 

  • Like 1
Link to comment
Share on other sites

13 minutes ago, D-an-W said:

@SavageAUS I think you have nailed it...not only did I remove all BootChime references but also the AudioDxe.efi and BootChimeCfg.efi which thinking about it were not OC built but from the Goldfish64 Github so might have been the issue all along as I can now boot without ApfsDriverLoader.efi or any reference to it.

 

THANK YOU!

 

I have also got sound working using the OC files but can't figure out how to turn it down a bit...any tips (It's way louder than when booted)?

 

Audio working but too loud!

  Reveal hidden contents

728338883_Screenshot2020-08-27at15_20_31.png.3cc2053ab6d299dd5a42671731f1d509.png

 

Folder Structure now...

  Reveal hidden contents

601954063_Screenshot2020-08-27at15_19_51.png.526ac59b3291f9dc06bba809b438a177.png

 

 

Well done @D-an-W  to decrease the sound level at start-up, page 64 and 65 of the Configurations manual

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

[mention=1083558]SavageAUS[/mention] I think you have nailed it...not only did I remove all BootChime references but also the AudioDxe.efi and BootChimeCfg.efi which thinking about it were not OC built but from the Goldfish64 Github so might have been the issue all along as I can now boot without ApfsDriverLoader.efi or any reference to it.

 

THANK YOU!

 

I have also got sound working using the OC files but can't figure out how to turn it down a bit...any tips (It's way louder than when booted)?

 

Audio working but too loud!

Spoiler 728338883_Screenshot2020-08-27at15_20_31.png.3cc2053ab6d299dd5a42671731f1d509.png

 

Folder Structure now...

Spoiler 601954063_Screenshot2020-08-27at15_19_51.png.526ac59b3291f9dc06bba809b438a177.png

 

Your welcome.

As for volumes levels you can adjust that in your config.plist. On my desktop I have amplification set to 0 and audio set to default 40 I think it is.

 

 

Sent from my iPhone using Tapatalk

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

On 5/1/2019 at 6:39 AM, obus said:

Hello all.

 

How to change boot priority in bootpick? I want my macOS Mojave partition  ( #3 iMacPro) as primary boot. 

Is the asterisk showing automatic boot partition or?

Now I have:

 

* 1. BOOTCAMP Windows  (not booting with OC BOOTx64.efi. Why?)

   2. EFI  (Which EFI Partition?  (I have 2 nvme m.2 disk in my rig) Can I hide this partition?

   3. BACKUP (my backup-partition on my second nvme m.2 disk) Can I hide this partition?

   3. iMacPro (the partition I want to boot automatically to)

   4. Recovery 10.14.4 (dmg) 

 

Any ideas?

 

 

Its possible choose a boot partition. 

 

Works to me when im boot with OpenCore, select boot partition and press ctrl + I and then press ctrl + enter.

 

In the next boot will boot on partition that you choose and run this commands, included Windows...(im not used to install Windows, but im tested once).

 

Just don't forget use Timeout different from zero on Root>Misc>Boot>Timeout on config.plist 

 

1094019059_CapturadeTela2020-08-27s22_50_22.thumb.png.1dd00b500e678c9d1e9f2bd7472923b4.png

Edited by Max.1974
Link to comment
Share on other sites

On 8/21/2020 at 9:07 AM, MacNB said:

...and have you checked the Binaries folder to see what has been produced.

Yes. It is empty.

On 8/21/2020 at 9:07 AM, MacNB said:

..where's the terminal output ?

It's here. It did compile BaseTools, but that was it, so my statement still stands.

On 8/21/2020 at 9:07 AM, MacNB said:

...and where have you read/found that there's such a build flag as ENABLE_SECURE_BOOT ???

Clover has it for emulating UEFI secure boot. I'm under the impression that OpenCore is based on Clover, so I figured it would have this feature, too.

On 8/21/2020 at 9:07 AM, MacNB said:

To enable secure boot with OC, it is not a matter of compiling it.

There's more to it. You need security keys.

 

Read the manual where you will find:
Note 1: While it may appear obvious, but you have to use an external method to verify OpenCore.efi and BOOTx64.efi for secure boot path. For this you are recommended to at least enable UEFI SecureBoot with a custom certificate, and sign OpenCore.efi and BOOTx64.efi with your custom key. More details on customising secure boot on modern firmwares can be found in Taming UEFI SecureBoot paper (in Russian).

 

it's work-in-progress. Read here.

Forget about that for a second. Is there a way to enable/disable build flags at all with OpenCore as with something like ./configure -D MACRO_NAME?

Link to comment
Share on other sites

On 8/28/2020 at 11:59 PM, MacWill said:

 

How can I delete this entry from my menu. It is just a trace of some previous installation and it no longer works. Not even the nvram reset can eliminate it.

 

Menu.jpg

 

Moved my answer here from the Big Sur discussion since it is more relevant to troubleshooting OC entries than Big Sur per se.

 

1.  Enable OC Debug logging eg logging to Datahub enabled with config.plist/Misc/Debug/Target=5.  Note: for more complete logging, run DEBUG version of OC instead of RELEASE version eg download OpenCore-0.6.1-DEBUG

2.  Generate OC boot log with the following Terminal command ---> save to text file

ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p
Spoiler

1622245792_OCBootlogtoDatahub.thumb.png.e339745221e780d644f33c1f97f0b50d.png

 

3.  Search for loader path of each entry found by OC - look for “Registering entry” in the boot log
Eg

00:942 00:000 OCB: Trying to get label from \5B6874DE-4C06-3F4F-842E-5280E98B0BBC\System\Library\CoreServices\.contentDetails
00:942 00:000 OCB: Trying to get label from \5B6874DE-4C06-3F4F-842E-5280E98B0BBC\System\Library\CoreServices\.disk_label.contentDetails
00:944 00:002 OCB: Registering entry Macintosh SSD (T:2|F:0|G:0|E:0) - PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(5,GPT,FAFE3054-A960-4E0A-8141-80EB9D0F56AB,0xF0E4800,0x71A67C0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,B3FBCD0FC2332845867A57E138ABEFFD)/\5B6874DE-4C06-3F4F-842E-5280E98B0BBC\System\Library\CoreServices\boot.efi

Notice also that OC parses the text in file .contentDetails or  .disk_label.contentDetails to label the Menu Entry

For an installer entry, you might see

OCB: Registering entry macOS Installer (T:2|F:0|G:0|E:0) - PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(5,GPT,FAFE3054-A960-4E0A-8141-80EB9D0F56AB,0xF0E4800,0x71A67C0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,B3FBCD0FC2332845867A57E138ABEFFD)/\5B6874DE-4C06-3F4F-842E-5280E98B0BBC\com.apple.installer\boot.efi

4.  Determine disk UUIDs and volume names with diskutil output from terminal:

diskutil list
/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +61.0 GB    disk3
                                 Physical Store disk0s5
   1:                APFS Volume ⁨Macintosh SSD - Data⁩    9.2 GB     disk3s1
   2:                APFS Volume ⁨Preboot⁩                 279.1 MB   disk3s2
   3:                APFS Volume ⁨Recovery⁩                749.0 MB   disk3s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk3s4
   5:                APFS Volume ⁨Macintosh SSD⁩           15.1 GB    disk3s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.1 GB    disk3s5s1


diskutil apfs list
|   +-> Volume disk3s1 5B6874DE-4C06-3F4F-842E-5280E98B0BBC
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk3s1 (Data)
|   |   Name:                      Macintosh SSD - Data (Case-insensitive)
|   |   Mount Point:               /System/Volumes/Data
|   |   Capacity Consumed:         9215066112 B (9.2 GB)
|   |   Sealed:                    No
|   |   FileVault:                 No
|   |
|   +-> Volume disk3s2 0FCDFBB3-33C2-4528-867A-57E138ABEFFD
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk3s2 (Preboot)
|   |   Name:                      Preboot (Case-insensitive)
|   |   Mount Point:               /System/Volumes/Preboot
|   |   Capacity Consumed:         279105536 B (279.1 MB)
|   |   Sealed:                    No
|   |   FileVault:                 No

 

Note 0FCDFBB3-33C2-4528-867A-57E138ABEFFD is the UUID of the Preboot volume (Big Endian format), equivalent to B3FBCD0F-C233-2845-867A-57E138ABEFFD/\5B6874DE-4C06-3F4F-842E-5280E98B0BBC\com.apple.installer\boot.efi from the OC log.

 

5.  Mount the specific volume for the problematic entry (in this case, Preboot on disk3s2) , then delete the boot.efi loader
 

sudo mount disk3s2

sudo rm /System/Volumes/Preboot/UUID/com.apple.installer/boot.efi
Spoiler

1206046014_InstallerRemnant.thumb.png.792d32556cc7603ccd1809606047421c.png

 

UUID in the above example was 5B6874DE-4C06-3F4F-842E-5280E98B0BBC (which is actually the UUID of the macOS "- Data" volume associated with Preboot)

 

Hints

  • Press <Cmd><Shift><.> to show hidden files in Finder
  • Can drag and drop boot.efi from Finder to Terminal window to save typing the entire path

 

Edited by fusion71au
Added download link for DEBUG version of OC 0.6.1 for more complete boot logging
  • Like 3
  • Thanks 1
Link to comment
Share on other sites

@fusion71au Much more in-depth explanation to a fix than my feeble attempt which I wasn't sure would solve the problem on BS as mine was based on previous OS X versions which didn't have a Sealed volumed so it would probably have been hit and miss, so thanks for this, will come in handy for sure.

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

On 8/26/2020 at 3:23 PM, oli.mathieu said:

Can you elaborate
how did you manage to boot 9820X with open core ?
Thanks in advance

 

I have a different CPU now, but dropping the stock APIC and injecting the fixed APIC should be all you need that is specific to the i9-9820X.

 

Depending on BIOS version you might need to deal with AWAC and the CFG-Lock, but that holds true for Clover and OC alike. 

Link to comment
Share on other sites

I have tried many things and cannot get Big Sur Public Beta 2 to install.  I had no problem with Public Beta 1.  Now I get [EB|#LOG:EXITBS:START] kernel panic.  I am running all the latest kexts and drivers. OC 0.6.1. 

I have reset cmos and setup bios again, no change.  I believe my SIP is disabled properly with the new Big Sur code in csr-active-config = 0x00000FFF

 

This is the last error in boot log:

 

0:941 00:004 AAPL: [EB|`LD:OFS] Err(0xE) @ OPEN (usr\\standalone\\OS.dmg.root_hash)
00:946 00:004 AAPL: [EB|`RH:LRH] Err(0xE) @ LF (P)
00:951 00:004 AAPL: [EB|`BST:FBS] Err(0xE) @ PBARVRH
00:958 00:007 AAPL: [EB|`B:WFDW] Err(0xE), 0 @ LocHB 71B4903C-14EC-42C4-BDC6-CE1449930E49
00:963 00:005 AAPL: [EB|#LOG:DT] 2020-08-29T02:18:27
00:968 00:005 AAPL: [EB|#LOG:EXITBS:START] 2020-08-29T02:18:27

 

any assistance would be appreciated

opencore-2020-08-29-021817.txt

Config.plist

  • Confused 1
Link to comment
Share on other sites

On 8/27/2020 at 5:40 PM, Matgen84 said:

 

Well done @D-an-W  to decrease the sound level at start-up, page 64 and 65 of the Configurations manual

For some reason I tried your suggestions but for me is still the same. APFS drives or macOS update aren't shown. macOS update with APFSDriverLoader sometimes they do show but not always.

 

I have attached my EFI folder. Maybe there is something wrong in the config file.

https://drive.google.com/file/d/1zf6M0oYh16MAiLc8hUHf2soCGC1fT0cD/view?usp=sharing

Link to comment
Share on other sites

17 minutes ago, maxb2000 said:

For some reason I tried your suggestions but for me is still the same. APFS drives or macOS update aren't shown. macOS update with APFSDriverLoader sometimes they do show but not always.

 

I have attached my EFI folder. Maybe there is something wrong in the config file.

https://drive.google.com/file/d/1zf6M0oYh16MAiLc8hUHf2soCGC1fT0cD/view?usp=sharing

 

Sorry, I don't have a laptop or HP laptop. 
Have a look to Dortania guide for Intel Laptop Broadwell Check your OC folders, BIOS settings and config.plist.

Link to comment
Share on other sites

6 hours ago, eSaF said:

@bbritton This is what you need it has everything to get you up and running, whether Clover or Opencore. Read Guide provided and follow carefully. Good luck.

thanks very much I got it working now.  Quite a few changes from what I had.

  • Like 2
Link to comment
Share on other sites

1 hour ago, bbritton said:

thanks very much I got it working now.  Quite a few changes from what I had.

You're most welcomed, yea the thread is catered specially for the gigabyte z390 so any queries you have will be answered.

  • Like 1
Link to comment
Share on other sites

12 minutes ago, Jerone said:

@ markl18У меня точно такая же проблема - OpenCore застрял на логотипе Apple (Kernel Panic). В подробном режиме ниже отображается ошибка. BIOS настроен согласно руководствам. Пытаюсь установить Catalina или Big Sur. Прикрепил EFI. Пожалуйста, любой совет, спасибо!

Моя установка:

Intel i5-10600
XFX RX580
ASUS Prime Z490M-PLUS

Изображение WhatsApp 29.08.2020 в 19.07.30.jpeg

AMD GPU + IGPU (iMac19,1) .zip

Try

EFI_ASUS .zip

Link to comment
Share on other sites

Here's an interesting issue with macOS Catalina 10.15.6 that's appeared with the last couple Git commits today. Right now using and building the latest Git commits results in the prohibitory symbol (macOS Catalina boot fail). In verbose mode it shows...

 

IMG_20200829_161145.thumb.jpg.a4bf3cd9208810893fc19de6c8836b05.jpg

 

If I build the commits from 15 hours ago, it boots just fine. I'm guessing this might have something to do with the preview UEFI secure boot stuff that was added today? Is there anything I need to add/change/remove to get it working, or is it a bug or something? Just letting you guys know. :)

  • Like 1
  • Sad 1
Link to comment
Share on other sites

10 hours ago, Awesome Donkey said:

Here's an interesting issue with macOS Catalina 10.15.6 that's appeared with the last couple Git commits today. Right now using and building the latest Git commits results in the prohibitory symbol (macOS Catalina boot fail). In verbose mode it shows...

 

IMG_20200829_161145.thumb.jpg.a4bf3cd9208810893fc19de6c8836b05.jpg

 

If I build the commits from 15 hours ago, it boots just fine. I'm guessing this might have something to do with the preview UEFI secure boot stuff that was added today? Is there anything I need to add/change/remove to get it working, or is it a bug or something? Just letting you guys know. :)

Have You found any Solution? I am Having same issue on latest. 

 

@williambj1 williambj1 released this 8 hours ago

Changes

OpenCorePkg

  • Docs: provide legacy operating system documentation
  • OcMacInfoLib: Fix matching MBP for 64-bit kernel type
Link to comment
Share on other sites

18 minutes ago, iamprabhuantony said:

Have You found any Solution? I am Having same issue on latest. 

 

@williambj1 williambj1 released this 8 hours ago

Changes

OpenCorePkg

  • Docs: provide legacy operating system documentation
  • OcMacInfoLib: Fix matching MBP for 64-bit kernel type

 

I think, It seems fixed now: see OpenCore repo for some new commits. I can't try now 

Link to comment
Share on other sites

Could this be a OC issue?

 

Restart after wake = KP

 

sudo pmset -g log | grep -i failure
2020-08-30 02:53:33 -0700 Failure             Failure during sleep: 0x1010000001F : EFI/Bootrom Failure after last point of entry to sleep

Laptop goes fine into sleep, but restarts after wake.

USB is fine, battery is showing %

 

Laptop:

HP 15-ay506ng 15,6" Full-HD Display, Intel Core i3-5005U, 8GB, Grafik Intel HD5500

 

Thanks

URBANsUNITED

Link to comment
Share on other sites

On 8/19/2020 at 10:05 AM, nmano said:

Opencore new update 0.6.1

AppleEthernetAquantiaAqtion.kext-not loading

 

Asus 10gb ethernet card not work in 10.15.6

 

If anyone has same issue please update.

Thanks.

 

I have the same issue. Worked (OOB) previously. (Sorry a bit late...)

Edited by jonpm
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...