OpenCore General Discussion

[Matgen84]

44 minutes ago, cankiulascmnfye said:

 

That's what the "OCLP-Model" NVRAM entry is for. But iit has to be present in NVRAM/Delete as well so that it can be written:

 

 

Thanks. Where I can find more documentation about these keys and values. Please.

[cankiulascmnfye]

4 hours ago, Matgen84 said:

 

Thanks. Where I can find more documentation about these keys and values. Please.

 

There is none. This is OCLP stuff. All I've figured out about it is covered on my repo: https://github.com/5T33Z0/OC-Little-Translated/tree/main/14_OCLP_Wintel

Edited August 19, 2023 by cankiulascmnfye

[ThriftLover]

Great! now that OC 0.9.5 supports MBR based Windows booting, can we create a custom entry for MBR based Windows and hide System Reserved Partition appearing as Windows(Legacy) entry in OC Picker?

[joevt]

My Mac Pro 2008 (Penryn era?) recently died so I moved all my disks containing all Intel macOS versions (Mac OS X 10.4.11 Tiger to macOS 13.4.1 Ventura) to my 2016 Skylake Hackintosh.

 

I made disk images of the partitions to use in VMs because the VMs don't support very well using actual disk partitions.
Mac OS X 10.5.8 Leopard and later boot in Parallels Desktop for Mac 19 on the Skylake Hackintosh.

Mac OS X 10.4.11 Tiger boots in VirtualBox 7.0.10 after modifying some CPUID information. https://github.com/ranma42/TigerOnVBox

 

I know there's been some work done in OpenCore to support early Mac OS X versions but I haven't read posts from users or developers about that.

For each processor, Skylake included, Dortania's OpenCore Install Guide has a section regarding configuration options for early Mac OS X versions including 10.4. Does that mean 10.4 can work on SkyLake?

 

If OpenCore can't modify CPUID like VirtualBox, then maybe it can patch the kernel sufficiently enough? Do the required patches exist already?

 

The OCLP project deals with running newer macOS versions on older Macs. I would like to go in the other direction and use older macOS versions on newer Macs/PCs.

 

[mrmacdi2]

Hi,

 

Can somebody explain how LegacySchema works? I've read Configuration.pdf, but it's purpose and way of work is unclear to me: there are only keys, without any values.

For example, I have NVRAM - ADD - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - bluetoothInternalControllerInfo key with data, at the same time I see in NVRAM - LegacySchema - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - 7 (key number) and value bluetoothInternalControllerInfo without any data.

[cankiulascmnfye]

1 hour ago, mrmacdi2 said:

Hi,

 

Can somebody explain how LegacySchema works? I've read Configuration.pdf, but it's purpose and way of work is unclear to me: there are only keys, without any values.

For example, I have NVRAM - ADD - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - bluetoothInternalControllerInfo key with data, at the same time I see in NVRAM - LegacySchema - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - 7 (key number) and value bluetoothInternalControllerInfo without any data.

 

I think this sections for systems without NVRAM which require emulated NVRAM. But I don't have any systems that old so I never worked with the LegacySchema

[miliuco]

@mrmacdi2

 

LegacySchema is a set of NVRAM variables and OpenCore compares these to the variables present in nvram.plist so it is not necessary when we have native NVRAM. It’s required only for emulated NVRAM. 
 

If we have LegacyEnable=False and LegacyOverwrite=False, LegacySchema is not used by OpenCore. And macOS boots perfectly without the LegacySchema keys. We can even delete the  LegacySchema whole part if we have native NVRAM.

 

What is always recommended is to have WriteFlash=True.

 

Edited October 25, 2023 by miliuco

[Stefanalmare]

5 hours ago, mrmacdi2 said:

Hi,

 

Can somebody explain how LegacySchema works? I've read Configuration.pdf, but it's purpose and way of work is unclear to me: there are only keys, without any values.

For example, I have NVRAM - ADD - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - bluetoothInternalControllerInfo key with data, at the same time I see in NVRAM - LegacySchema - 7C436110-AB2A-4BBB-A880-FE41995C9F82 - 7 (key number) and value bluetoothInternalControllerInfo without any data.

For Legacy (non UEFI):

1. Download OpenCore: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

2. Install LegacyBoot (first on USB installer, after on boot drive). .../OpenCore-0/Utilities/LegacyBoot

3. Install OS

4. Run LogoutHook for emulated NVRAM: ..../OpenCore-0/Utilities/LogoutHook

I use this type of OC config for legacy:

Like you see I use "*" for every UUID. And it is working like a dream.

You should insert normal values to NVRAM -> Add/Delete

 

If you have another question about legacy (and you'll have 😇), shot!

[mrmacdi2]

3 hours ago, miliuco said:

@mrmacdi2

 

LegacySchema is a set of NVRAM variables and OpenCore compares these to the variables present in nvram.plist so it is not necessary when we have native NVRAM. It’s required only for emulated NVRAM. 
 

If we have LegacyEnable=False and LegacyOverwrite=False, LegacySchema is not used by OpenCore. And macOS boots perfectly without the LegacySchema keys. We can even delete the  LegacySchema whole part if we have native NVRAM.

 

What is always recommended is to have WriteFlash=True.

 

Thanks, still unclear. I have legacy systems without hardware NVRAM and I’ve always used the regular way: put items in NVRAM - Add/Delete, without touching anything in LegacySchema.

[Stefanalmare]

9 minutes ago, mrmacdi2 said:

Thanks, still unclear. I have legacy systems without hardware NVRAM and I’ve always used the regular way: put items in NVRAM - Add/Delete, without touching anything in LegacySchema.

Now I'm sorry for my time.

[miliuco]

35 minutes ago, mrmacdi2 said:

I have legacy systems without hardware NVRAM and I’ve always used the regular way: put items in NVRAM - Add/Delete, without touching anything in LegacySchema.

But without native NVRAM, motherboard doesn’t save those values. Maybe you have a kind of partially emulated NVRAM. 

[mrmacdi2]

29 minutes ago, Stefanalmare said:

Now I'm sorry for my time.

I have emulated NVRAM, but I have never touched LegacySchema, not before I had have turned NVRAM emulation on, not after that.

3 minutes ago, miliuco said:

But without native NVRAM, motherboard doesn’t save those values. Maybe you have a kind of partially emulated NVRAM. 

But how then LegacySchema works if it has no values, but keys only?

[Stefanalmare]

2 hours ago, miliuco said:

But without native NVRAM, motherboard doesn’t save those values. Maybe you have a kind of partially emulated NVRAM. 

Config.plist from one of my legacy rigs. Core2, NVRAM emulated running latest Sonoma beta. This config is a backup, not the latest. I'm not at home.

config.plist

 

Like I said above, for having full emulated NVRAM you must install LogoutHook. This and the NVRAM config.plist make all working. Even when upgrade OS, the installer become the default boot. That good emulated NVRAM work!

Edited October 25, 2023 by Stefanalmare

[miliuco]

@mrmacdi2

I guess that the keys (and their values) in LegacySchema are saved to nvram.plist from NVRAM variables, to be available at next boot. 

[naiclub]

On 10/26/2023 at 1:18 AM, Stefanalmare said:

Config.plist from one of my legacy rigs. Core2, NVRAM emulated running latest Sonoma beta. This config is a backup, not the latest. I'm not at home.

config.plist 84.88 kB · 5 downloads

 

Like I said above, for having full emulated NVRAM you must install LogoutHook. This and the NVRAM config.plist make all working. Even when upgrade OS, the installer become the default boot. That good emulated NVRAM work!

Hello friend, can I have your EFI file please? I have a board model GA-H61M-D2-B3 (rev. 1.0) rev. 1.1 CPU i3 2100 RAM 4GB graphics card GT-640 2GB and would like to try installing it. This is a model that does not support UEFI mode.

[makk]

I imagine at some point, when Apple drops all past Intel and AMD rigs from their list in future MacOS's that we all end up using Legacy everything and have very slim pickings if we continue to use as close as possible all Apple.

 

The idea of running MacOS on a PC was to patch all the kexts and everything else where, it is possible to run.

 

However, over the years, the development as stated in the first sentence has led to being a Mac as close as possible.  Imitation.

 

The idea of running MacOS on PC is then really detracted a bit in my thought.

 

A hack is to hack and use what is there.   Taking advantage of what is in place, not becoming it.  If you follow my thought here.

If you want a Mac buy one.

 

If you want to hack it, that is different. 

 

Back in the day, when I started this, the 'hackers' of those days, hacked and made use.

 

Any one can make a kext if they know how and what specs are needed to make it work for their piece of hardware.  I used to write scripts in UNIX many many years ago.  oops tells my age..

 

However, a hacker knows already what they are looking to do and then dive in and with their skills and intelligence see how far they can go.

 

So as long as you want to have mac on your pc exactly like a mac, then, the idea of hackintosh is lost.  Follow my thought here?

 

patching is what hackers start out by doing to find the core where all is then taken in control.  Data control and having it do precisely what is intended.
All I hear is that is not possible Mac is this and that. Well tell that to the hacker who made it possible.

 

All data.  Language is one: 1 0 1 0 1 1 0.  This is how a true hacker gains control.  the hardware is then theirs for the taking.

 

the history of data begins with those creating it and they were able to make it happen thus we are living in their work progressed through time.

 

 

[MacNB]

On 12/7/2023 at 7:12 PM, makk said:

I imagine at some point, when Apple drops all past Intel and AMD rigs from their list in future MacOS's that we all end up using Legacy everything and have very slim pickings if we continue to use as close as possible all Apple.

 

The idea of running MacOS on a PC was to patch all the kexts and everything else where, it is possible to run.

 

However, over the years, the development as stated in the first sentence has led to being a Mac as close as possible.  Imitation.

 

The idea of running MacOS on PC is then really detracted a bit in my thought.

 

A hack is to hack and use what is there.   Taking advantage of what is in place, not becoming it.  If you follow my thought here.

If you want a Mac buy one.

 

If you want to hack it, that is different. 

 

Back in the day, when I started this, the 'hackers' of those days, hacked and made use.

 

Any one can make a kext if they know how and what specs are needed to make it work for their piece of hardware.  I used to write scripts in UNIX many many years ago.  oops tells my age..

 

However, a hacker knows already what they are looking to do and then dive in and with their skills and intelligence see how far they can go.

 

So as long as you want to have mac on your pc exactly like a mac, then, the idea of hackintosh is lost.  Follow my thought here?

 

patching is what hackers start out by doing to find the core where all is then taken in control.  Data control and having it do precisely what is intended.
All I hear is that is not possible Mac is this and that. Well tell that to the hacker who made it possible.

 

All data.  Language is one: 1 0 1 0 1 1 0.  This is how a true hacker gains control.  the hardware is then theirs for the taking.

 

the history of data begins with those creating it and they were able to make it happen thus we are living in their work progressed through time.

 

 

 

Long term, Apple will ditch ALL Intel binaries from macOS thus only ARM instruction set will be used in macOS (that's what they did moving from PowerPC to Intel in past).

Big Sur is already dead...even on Apple Silicon.

So there's no hacking required to run macOS on a PC....since there's nothing to hack.

One possibility is to emulate ARM instructions in X84 and try to hack those new ARM macOS's to run under an emulator....under a VM.

 

So long term if one wants to run the latest macOS, get an Apple Silicon Mac.

 

Edited December 22, 2023 by MacNB

[cankiulascmnfye]

Question: How can my Whiskey Lake Laptop boot macOS 14.2 without this setting enabled…

 

 

…If CFGLock is enabled:

 

 

???

 

Using commit https://github.com/acidanthera/OpenCorePkg/commit/a1a8bd6c90f269cd184b37dbacde886c6a82cd1e

 

Technically, this should be impossible. So either, the quirk is always on, or something changed in macOS.

 

Reminder:

Quote

AppleXcpmCfgLock

Description: Disables PKG_CST_CONFIG_CONTROL (0xE2) MSR modification in XNU kernel, commonly causing early kernel panic, when it is locked from writing (XCPM power management).

Source: OpenCore Documentation.pdf

 

 

 

Edited December 8, 2023 by cankiulascmnfye

[brousseau6933]

59 minutes ago, cankiulascmnfye said:

Question: How can my Whiskey Lake Laptop boot macOS 14.2 without this setting enabled…

 

 

…If CFGLock is enabled:

 

 

???

 

Using commit https://github.com/acidanthera/OpenCorePkg/commit/a1a8bd6c90f269cd184b37dbacde886c6a82cd1e

 

Technically, this should be impossible. So either, the quirk is always on, or something changed in macOS.

 

Reminder:

 

 

 

My Dell XPS 8930 declare MSR 0xE2 locked and there is no way I can unlock it via EFI shell and it still can boot with or without this quirk ticked. Strange but at least, you are not alone! Just for sake of being kosher, it’s ticked on my hack.

[Slice]

8 hours ago, cankiulascmnfye said:

Question: How can my Whiskey Lake Laptop boot macOS 14.2 without this setting enabled…

 

 

…If CFGLock is enabled:

 

 

???

 

Using commit https://github.com/acidanthera/OpenCorePkg/commit/a1a8bd6c90f269cd184b37dbacde886c6a82cd1e

 

Technically, this should be impossible. So either, the quirk is always on, or something changed in macOS.

 

Reminder:

 

 

 

I may propose that macOS doesn't use the register for your CPU. There are checks of CPUID inside XCPM module.

[dogansan]

On 1/17/2022 at 11:35 PM, Hoshi Yamazaki said:

Hey, I updated my Thinkpad X230 config, OpenCore.efi, drivers and kexts to 0.7.7 version, but it stopped booting, and I'm curious why.

This is error I get:


It's quite interesing because I also updated my r5 3600/rx5700 XT config, and, even if it's AMD, it works without problems. So I don't know what is an issue with my laptop...
I also tried to mess with Execution Prevention, VT-x and VT-d options in BIOS. I think GPU is not getting initialized, but I also tried to add SSDT-IMEI...
The laptop comes with Ivy Bridge CPU (i5-3320M) and HD4000 mobile iGPU. I also want to mention that I updated from 0.6.1, and it was working fine on previous "build".

Hi, it is a bit late to ask however let me see if you can help, I have moved from my Intel to AMD Ryzen 5 3600 which was my son's PC used for Windows gaming. I will be happy if you can share your config.plist file 

On 9/15/2020 at 7:12 AM, SavageAUS said:

My Ryzen 5 3600 boots and works fine with OC on Catalina and Big Sur.


Sent from my iPhone using Tapatalk

Hi. Did you upgrade your Ryzen 5 3600 to Ventura or Sonoma and if yes, could you please share your config.plist as it will be too much effort for me to prepare from scratch 

[deeveedee]

I have performed a few brief tests with Open Core 0.9.7 (upgraded from OC 0.9.6) on my Dell Latitude E6410 (SMBIOS MBP6,2) and am finding that I can only boot with OC 0.9.7 if  I use the LegacyBoot utility from OC 0.9.6.  Is anyone else finding this?  Here's how I tested:

 

Test 1:

• Upgrade OC 0.9.6 binaries to OC 0.9.7 (EFI/BOOT/BOOTx64.efi, EFI/OC/Drivers/*.* (all except HfsPlusLegacy.efi), EFI/OC/OpenCore.efi, EFI/OC/Tools/*.*)
• Install new LegacyBoot with Utility from OC 0.9.7
• After rebooting, boot halts because OC can't load HfsPlusLegacy.efi

Test 2:

• Start with OC 0.9.7 config from Test 1 and disable HfsPlusLegacy.efi in OC config.plist
• After rebooting, OC does not see any of my APFS volumes (only item in OC boot menu is ResetNVram)

Test 3:

• Start with OC 0.9.7 config from Test 1 and keep LegacyBoot installed by OC 0.9.6
• After rebooting, all appears normal and Hackintool reports that I am booting with OC 0.9.7

 

It appears to me that there is a problem with OC 0.9.7 LegacyBoot utility (or more likely, I am incorrectly using the OC 0.9.7 LegacyBoot utility)

Edited December 18, 2023 by deeveedee

[pitrysha]

43 minutes ago, deeveedee said:

I have performed a few brief tests with Open Core 0.9.7 (upgraded from OC 0.9.6) on my Dell Latitude E6410 (SMBIOS MBP6,2) and am finding that I can only boot with OC 0.9.7 if  I use the LegacyBoot utility from OC 0.9.6.  Is anyone else finding this?  Here's how I tested:

 

Test 1:

• Upgrade OC 0.9.6 binaries to OC 0.9.7 (EFI/BOOT/BOOTx64.efi, EFI/OC/Drivers/*.* (all except HfsPlusLegacy.efi), EFI/OC/OpenCore.efi, EFI/OC/Tools/*.*)
• Install new LegacyBoot with Utility from OC 0.9.7
• After rebooting, boot halts because OC can't load HfsPlusLegacy.efi

Test 2:

• Start with OC 0.9.7 config from Test 1 and disable HfsPlusLegacy.efi in OC config.plist
• After rebooting, OC does not see any of my APFS volumes (only item in OC boot menu is ResetNVram)

Test 3:

• Start with OC 0.9.7 config from Test 1 and keep LegacyBoot installed by OC 0.9.6
• After rebooting, all appears normal and Hackintool reports that I am booting with OC 0.9.7

 

It appears to me that there is a problem with OC 0.9.7 LegacyBoot utility (or more likely, I am incorrectly using the OC 0.9.7 LegacyBoot utility)

What is the "OC 0.9.7 LegacyBoot utility" and what does it have to do with Open Core?

[deeveedee]

@pitrysha LegacyBoot (in the OpenCore/Utilities folder when you download OpenCore) is necessary when using OpenCore on PCs with legacy BIOS (non-UEFI).  It is the LegacyBoot utility that allows OpenCore to support old PCs (like my Dell Latitude E6410 which was released in 2010).

 

EDIT: OpenCore's LegacyBoot utility installs Duet to "emulate" the UEFI interface in the absence of native UEFI support.

Edited December 18, 2023 by deeveedee

[droples]

14 hours ago, deeveedee said:

@pitrysha LegacyBoot (in the OpenCore/Utilities folder when you download OpenCore) is necessary when using OpenCore on PCs with legacy BIOS (non-UEFI).  It is the LegacyBoot utility that allows OpenCore to support old PCs (like my Dell Latitude E6410 which was released in 2010).

 

EDIT: OpenCore's LegacyBoot utility installs Duet to "emulate" the UEFI interface in the absence of native UEFI support.

I also have some problems with legacy loading. The last on which legacy loading works is 0.97 (commit -11a33b4).But... I can boot with the latest version of the OС if I use a legacy boot from version 0.97 (commit -11a33b4)