OpenCore General Discussion

[Alpha22]

4 minutes ago, eSaF said:

I don't know man I followed @miliuco Guide and mine is correct.

I will post a couple of pics to show how it is on my rig.

 

followed this guide: 

 

[Alpha22]

Re-checked everything, but still the same problem

Edited April 17, 2023 by Alpha22

[miliuco]

@Alpha22

No more ideas.

Maybe you have to post this issue as a separate thread, here it's hidden and probably you'll get more help as standalone post.

[MakAsrock]

Came to Israel, my old hardware build and I installed macOS 12.6.5 (21G531). Installed in this way: Using OpenCore Legacy Patcher v.0.6.4 - download the OS and create an installation flash drive, then follow the instructions

edit Sample.plis, rename it to Config.plist, downloaded the necessary drivers and the latest kexts for my hardware. I put it all of them on EFI partition to the suitable in OC folders on the flash drive.

Everything was successfully installed (including after installation patches) and loaded into the desktop, but here's the oddity: It loads - not every time. That is, if you turn on the power button and do not press anything else, then the boot is usually normal, but if you select another partition (I have two different macOS on various volumes), then a black screen appears for a few seconds and then appears again the OS selection menu and so on in a circle. I don’t know where to dig, since logs are not created in this case. If you use the built-in Picker instead of OpenCanopy, then everything is OK. Can you see where I messed up? I am new to OpenCore. Iron earned everything except sleep.

opencore-2023-04-17-223314.txt EFI.zip

[Stefanalmare]

1 hour ago, MakAsus said:

Came to Israel, my old hardware build and I installed macOS 12.6.5 (21G531). Installed in this way: Using OpenCore Legacy Patcher v.0.6.4 - download the OS and create an installation flash drive, then follow the instructions

edit Sample.plis, rename it to Config.plist, downloaded the necessary drivers and the latest kexts for my hardware. I put it all of them on EFI partition to the suitable in OC folders on the flash drive.

Everything was successfully installed (including after installation patches) and loaded into the desktop, but here's the oddity: It loads - not every time. That is, if you turn on the power button and do not press anything else, then the boot is usually normal, but if you select another partition (I have two different macOS on various volumes), then a black screen appears for a few seconds and then appears again the OS selection menu and so on in a circle. I don’t know where to dig, since logs are not created in this case. If you use the built-in Picker instead of OpenCanopy, then everything is OK. Can you see where I messed up? I am new to OpenCore. Iron earned everything except sleep.

opencore-2023-04-17-223314.txt 256 kB · 3 downloads EFI.zip 9.19 MB · 6 downloads

OCLP it is JUST for real MAC's. For sure we can use it to see the patches and adapt them to our needs and hardware, but not to use the EFI generated by OCLP. The only thing that can be done directly in non Macintosh machine by OCLP is post install root patch (thanks to OCLP devs), to fix graphics an occasionally other things (USB1,1).

To build an opencore EFI for hackintosh use this:

https://dortania.github.io/OpenCore-Install-Guide/

After, if you want Monterey or Ventura and the processor is unsupported, OCLP become source of inspiration.

Edited April 19, 2023 by Stefanalmare

[MakAsrock]

7 hours ago, Stefanalmare said:

OCLP it is JUST for real MAC's. For sure we can use it to see the patches and adapt them to our needs and hardware, but not to use the EFI generated by OCLP. The only thing that can be done directly in non Macintosh machine by OCLP is post install root patch (thanks to OCLP devs), to fix graphics an occasionally other things (USB1,1).

To build an opencore EFI for hackintosh use this:

https://dortania.github.io/OpenCore-Install-Guide/

After, if you want Monterey or Ventura and the processor is unsupported, OCLP become source of inspiration.

I did everything just like that, only with the help of OCLP I made a USB flash drive, because it turned out to be convenient for them to download and prepare a usb media. And I set up OpenCore with my hands according to the manual. The question is: Why does everything load normally with the built-in picker, but not every time with OpenCanopy? There is no critical errors in the logs. 🤔

[miliuco]

@MakAsus

Not sure why you don't get the graphical picker, related items are ok in your EFI.

But this EFI is made by OCLP, as you say, and maybe it has some kind of incompatibility. I think (as @Stefanalmare) that you must build your EFI from OpenCore (not OCLP) following Dortania guide, adding to config.plist all the required patches copied from OCLP config.plist, and doing root patch from OCLP app if necessary. It's not recommended to create the EFI with OCLP in a hackintosh.

[MakAsrock]

56 minutes ago, MakAsus said:

I did everything just like that, only with the help of OCLP I made a USB flash drive, because it turned out to be convenient for them to download and prepare a usb media. And I set up OpenCore with my hands according to the manual. The question is: Why does everything load normally with the built-in picker, but not every time with OpenCanopy? There is no critical errors in the logs. 🤔
This is failed boot.

And this Successible boot. 

 

[MakAsrock]

21 minutes ago, miliuco said:

@MakAsus

Not sure why you don't get the graphical picker, related items are ok in your EFI.

But this EFI is made by OCLP, as you say, and maybe it has some kind of incompatibility. I think (as @Stefanalmare) that you must build your EFI from OpenCore (not OCLP) following Dortania guide, adding to config.plist all the required patches copied from OCLP config.plist, and doing root patch from OCLP app if necessary. It's not recommended to create the EFI with OCLP in a hackintosh.

I did not create EFI with Open Core Patcher, but only created a 16 GB USB drive for installation. Everything else was done by hand. And Reading Dortania did not bring me closer to unraveling this opus. 😉 Otherwise I wouldn't be asking here. 😎

[miliuco]

@MakAsus

The config.plist file into your EFI is the same as the file made by OCLP app, it's not as the config.plist made by OpenCore, this is the reason why I commented it in my previos post.

[MakAsrock]

1 hour ago, miliuco said:

@MakAsus

The config.plist file into your EFI is the same as the file made by OCLP app, it's not as the config.plist made by OpenCore, this is the reason why I commented it in my previos post.

I just added from  OCLP boot args darkwake=0 alcid=3 keepsyms=1 debug=0x100 ipc_control_port_options=0 -nokcmismatchpanic amfi=0x80 -v, csr-active-config=03080000 and a few kernel patches. It didn't load at all without them. The rest of the parameters has been moved to the Sample.plist from the working Clover. I added drivers and Kekstas based on my hardware. I checked the quirks with a validator (https://opencore.slowgeek.com).
Added right now. I replaced the clean config without patches one and the behavior did not change. Out of 3 boot, 2 are successful. If it fails, it just won't load. There is no panic and no freezes, but just nothing happens, as in the video.

 

Edited April 19, 2023 by MakAsus

[pkdesign]

On 4/17/2023 at 5:50 AM, eSaF said:

You cannot just use that value on it's own as you've found out with the error.

That value is used in conjunction with Misc/Entries in the config.plist when dual booting with i.e Windows but you need to find the correct path of the windows disk on your machine like my example. If the correct path is not correct, you will still get the error with that value. If you're not dual booting, then the '0' value is fine.

@miliuco - Has a great tutorial/walk through on 'How  to Custom Entry in Opencore to boot Windows'  to find the path of the disk and what you need to do.

 

PS Don't use the example in the Sample Config.plist as it is Generic and only there as an illustration or guide, you need to find your own on your machine.

  Hide contents

 

Hmm, I dual boot and have never had to add anything to Misc/Entries. Scan policy is set to 0. At boot I see Windows 11 and macOS.

[MakAsrock]

3 hours ago, MakAsus said:

I just added from  OCLP boot args darkwake=0 alcid=3 keepsyms=1 debug=0x100 ipc_control_port_options=0 -nokcmismatchpanic amfi=0x80 -v, csr-active-config=03080000 and a few kernel patches. It didn't load at all without them. The rest of the parameters has been moved to the Sample.plist from the working Clover. I added drivers and Kekstas based on my hardware. I checked the quirks with a validator (https://opencore.slowgeek.com).
Added right now. I replaced the clean config without patches one and the behavior did not change. Out of 3 boot, 2 are successful. If it fails, it just won't load. There is no panic and no freezes, but just nothing happens, as in the video.

 

Found where to dig. Enabled PointerSupport=Yes, and it started loading almost always, if you don't touch the keyboard. Apparently, something with the input section. So, it was not a matter of keys transferred from OCLP. I forgot to write that I have a 2.4 GHz radio, Logitech keyboard and mouse. 😎

[pkdesign]

1 hour ago, eSaF said:

Actually you are not wrong on that score but the object of the exercise (Misc/Entries) is to make OS X the first Booting System Icon in the Boot Menu.

See my attached pics then compare it with yours and you'll see what I mean, I bet the Windows Icon is the first one before any OS X on your System even though you may have the OS X Drive as the first drive to boot from in the BIOS.

  Reveal hidden contents

 

Ah yes it is. But macOS is set as default. Buuuut, if I mess with NVRAM or something with the Windows drive, it does default to Windows again. May be something to look into.

 

[miliuco]

@pkdesign @eSaF

 

It's annoying that clearing NVRAM may also clear the boot order in BIOS and the Windows disk may be set in the first place. To avoid this:

• LauncherOption set to Full or Short in config.plist
• ResetNVRAM driver >> "to obtain reset NVRAM functionality which does not remove other boot options, it is possible to use the --preserve-boot option specified in the Arguments section for this driver: If enabled, BIOS boot entries are not cleared during NVRAM reset" (from OpenCore Configuration.pdf, 11.7.1  ResetNvramEntry part) .

Edited April 19, 2023 by miliuco

[Ellybz]

@eSaF

 

 

 

 

 

Edited April 20, 2023 by Ellybz

[miliuco]

@eSaF

@Ellybz knows the way 😂

--preserve-boot

as text in Arguments. 

Edited April 20, 2023 by miliuco

[ANTIKO]

Please tell me how you change the order of loading? The fact is that Windows is always my first, it's a little inconvenient.

[miliuco]

@ANTIKO

 

The order of the boot entries in OpenCore is largely determined by the arrangement of the drives attached to the motherboard.
If a Windows system exists, OpenCore automatically detects it and places it as the first menu entry. This is like this due to design.

There are 2 methods to avoid this, which many users don't like (I include myself).

 

Method 1

Two settings are combined to obtain the desired result: create a custom entry for the Windows system (this entry is displayed behind macOS systems) and remove the automatic detection of Windows systems (NTFS + EFI) in ScanPolicy.

[HOW TO] Custom entry in OpenCore to boot Windows

[HOW TO] Windows entry after macOS in OpenCore menu

 

Method 2

 

In OpenCore 0.8.8 a new feature was added: .contentVisibility. You can read about it here.

In summary:

• put a file named .contentVisibility in the Windows EFI >> Boot folder next to bootx64.efi
• open the text file (pico, nano, bbedit, textedit, etc.) and write a single word in it
• if the word is Disabled >> this entry will not appear in the OpenCore menu no way
• if the word is Auxiliary >> this entry will not appear in the OpenCore menu until you press the space bar (this requires HideAuxiliary to be True in config.plist).

This is useful for the topic and is that, indirectly, we can prevent Windows from always being the first system in the OpenCore menu. Simply write Auxiliary to .contentVisibility so that at boot we see only macOS systems, and when we press space bar we see Windows and tools as well. Only when we want to go to Windows, we show auxiliary. All other boots, we don't even see the Windows icon.
 

[Ellybz]

2 minutes ago, miliuco said:

@ANTIKO

 

The order of the boot entries in OpenCore is largely determined by the arrangement of the drives attached to the motherboard.
If a Windows system exists, OpenCore automatically detects it and places it as the first menu entry. This is like this due to design.

There are 2 methods to avoid this, which many users don't like (I include myself).

 

Method 1

Two settings are combined to obtain the desired result: create a custom entry for the Windows system (this entry is displayed behind macOS systems) and remove the automatic detection of Windows systems (NTFS + EFI) in ScanPolicy.

[HOW TO] Custom entry in OpenCore to boot Windows

[HOW TO] Windows entry after macOS in OpenCore menu

 

Method 2

 

In OpenCore 0.8.8 a new feature was added: .contentVisibility. You can read about it here.

In summary:

• put a file named .contentVisibility in the Windows EFI >> Boot folder next to bootx64.efi
• open the text file (pico, nano, bbedit, textedit, etc.) and write a single word in it
• if the word is Disabled >> this entry will not appear in the OpenCore menu no way
• if the word is Auxiliary >> this entry will not appear in the OpenCore menu until you press the space bar (this requires HideAuxiliary to be True in config.plist).

This is useful for the topic and is that, indirectly, we can prevent Windows from always being the first system in the OpenCore menu. Simply write Auxiliary to .contentVisibility so that at boot we see only macOS systems, and when we press space bar we see Windows and tools as well. Only when we want to go to Windows, we show auxiliary. All other boots, we don't even see the Windows icon.
 

 

I’ve been using method 1 but I have to say that I still miss a great feature from the previous  NDK version: 

.- The order of entries in the boot menu is correlative to the order of  the custom entries listing. ( By also adding OSX as custom entries ).

This method was very effective.
 

[miliuco]

@Ellybz

Yes, this is one feature missing from the old NDK. Custom entries order was possible.

[Alpha22]

solved booting, as first macOS Ventura and Windows 11 

 

Spoiler

 

settings in config.plist - Misc - Entries and ScanPolicy 2951939

 

in the Log I see this error 

 

Spoiler

04:655 00:002 OCB: Invalid file system policy (400/290303) for 3250CA18
04:658 00:002 OCB: Adding fs 3250CA18 (E:0|L:1|P:Security Violation) - PciRoot(0x0)/Pci(0x6,0x0)/Pci(0x0,0x0)/NVMe(0x1,14-CD-)
04:661 00:003 OCB: Invalid file system policy (400/290303) for 31FFDF98
04:663 00:002 OCB: Adding fs 31FFDF98 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1A,0x0)/Pci(0x0,0x0)/NVMe(0x1,79-03-)
04:666 00:002 OCB: Invalid file system policy (800/290303) for 31FEEC98
04:669 00:002 OCB: Adding fs 31FEEC98 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1A,0x0)/Pci(0x0,0x0)/NVMe(0x1,79-03-)
04:671 00:002 OCB: Invalid file system policy (0/290303) for 31FEE918
04:674 00:002 OCB: Adding fs 31FEE918 (E:0|L:0|P:Security Violation)

 

if I set ScanPolicy 0 no error

 

advice

[MakAsrock]

On 4/19/2023 at 8:10 PM, MakAsus said:

And this Successible boot. 

 

Tat's all, I figured it out. You just had to wait until the cursor blinks twice before clicking anything. It's just that the keyboard and mouse receiver is slowly initializing. If you plug in a wired keyboard and mouse, then there is no glitch (By this method, I found out the kind of the glitch).
The EFI folder cleared of all unnecessary is in the attachment.

EFI.zip

Edited April 21, 2023 by MakAsus
Add files

[ANTIKO]

22 hours ago, eSaF said:

Перейдите по этой ссылке —  https://medium.com/macoclock/guide-multiboot-dualboot-opencore-with-windows-macos-linux-kextcache-131e96784c3f  — прокрутите вниз до  раздела «После установки» для просмотра .

 

20 hours ago, miliuco said:

@АНТИКО

 

Порядок загрузочных записей в OpenCore во многом определяется расположением дисков, подключенных к материнской плате.
Если система Windows существует, OpenCore автоматически обнаружит ее и поместит в качестве первого пункта меню. Это так из-за дизайна.

Есть 2 способа избежать этого, что не нравится многим пользователям (в том числе и мне).

 

Способ 1

Две настройки объединяются для получения желаемого результата: создание пользовательской записи для системы Windows (эта запись отображается за системами macOS) и удаление автоматического определения систем Windows (NTFS + EFI) в ScanPolicy.

[КАК] Пользовательская запись в OpenCore для загрузки Windows

[КАК] Запись Windows после macOS в меню OpenCore

 

Способ 2

 

В OpenCore 0.8.8 была добавлена новая функция: .contentVisibility. Вы можете прочитать об этом  здесь .

В итоге:

• поместите файл с именем .contentVisibility в папку Windows EFI >> Boot рядом с bootx64.efi
• откройте текстовый файл (pico, nano, bbedit, textedit и т. д.) и напишите в нем одно слово
• если слово Disabled >> эта запись не появится в меню OpenCore никоим образом
• если слово Auxiliary >>, эта запись не появится в меню OpenCore, пока вы не нажмете пробел (для этого требуется, чтобы HideAuxiliary было True в config.plist).

Это полезно для данной темы и заключается в том, что косвенно мы можем запретить Windows всегда быть первой системой в меню OpenCore. Просто пропишите Auxiliary в .contentVisibility, чтобы при загрузке мы видели только системы macOS, а когда нажимаем пробел, то видели и Windows и инструменты. Только когда мы хотим перейти в Windows, мы показываем вспомогательные. При всех других загрузках мы даже не видим значка Windows.
 

 

20 hours ago, Ellybz said:

 

Я использовал метод 1, но должен сказать, что мне все еще не хватает замечательной функции из предыдущей версии NDK: 

.- Порядок записей в меню загрузки соответствует порядку в списке пользовательских записей. (Также добавляя OSX в качестве пользовательских записей).

Этот метод оказался очень эффективным.
 

Thanks a lot to everyone who answered, everything worked out.

[SavageAUS]

Can anyone tell me why third party apps are not detecting my OpenCore version? I have done it the same as my intel systems and they work just fine as far as detection goes but on my AMD system the version doesn’t get detected. I have tried deleting all files from the EFI and copy and pasting them back with no luck. I have done an nvram reset as well. The EFI is on the same disk as macOS.


Sent from my iPhone using Tapatalk