OpenCore General Discussion

[Stefanalmare]

6 hours ago, rajkhand said:

How it will help? my drive is formatted with BTRFS filesystem with ZSTD compression and NOT ext4.

I tried that also but it didn't show the entry.

 

Any Solution to boot from OC?

 

If you have windows installed, download EasyUEFI. Boot windows from OpenCore and make a new entry of your linux in EasyUEFI. I don't know how Garuda works, but I suppose it have a boot folder in EFI. If you do like that, next time you are in OpenCore picker, you will see the linux icon. 

[AslashA]

How to rename this particular device PEG0.PEGP to PEG0.SSD0 in opencore?

 

Edited June 19, 2023 by AslashA

[cankiulascmnfye]

@AslashA You can't. You need to do it via ACPI with something like this: https://github.com/5T33Z0/OC-Little-Translated/tree/main/11_Graphics/GPU/AMD_Navi

 

Adjust names and paths accordingly.

[cankiulascmnfye]

How can I check if the reported RAM speed in macOS is correct? System Profiler says 2400 MHZ, but Windows reports 2666 mHZ which is te correct value. So I am wondering: is it a reporting problem or does it run slower in macOS…

[Avery B]

On 6/19/2023 at 12:17 PM, AslashA said:

How to rename this particular device PEG0.PEGP to PEG0.SSD0 in opencore?

 

You could disable the PEGP device then create a new SSD0 device. I would not recommend using an ACPI patch to rename, considering how common the PEGP device name likely is.
Does the device really need to be renamed though? I'd avoid it if you can.

Edited June 22, 2023 by 1Revenger1

[rajkhand]

On 6/18/2023 at 5:58 PM, Stefanalmare said:

 

If you have windows installed, download EasyUEFI. Boot windows from OpenCore and make a new entry of your linux in EasyUEFI. I don't know how Garuda works, but I suppose it have a boot folder in EFI. If you do like that, next time you are in OpenCore picker, you will see the linux icon. 

I have no windows. On one nvme I have Hackintosh and another I have installed Garuda linux which is an ARCH base distribution. It has an EFI partion with BOOT and Garuda directories. BOOT contains BOOTx64.efi And Garuda has grubx64.efi.

If from opencore picker after pressing space bar I select uefishell. In this I can cd to either of these directories and start by either running BOOTx64.efi ot grubx64.efi.

How to add an entry in opencore so the picker shows it?

[SavageAUS]

Ok I have tried to troubleshoot this mostly on my own but now I need help.

My OpenCore version is not detected by any 3rd party apps (About This Hack, Hackintool, Etc)

I have reset my NVRAM, I have formatted my EFI partition. This has been going on for a long time with this machine.

This is only happening on my AMD rig, my Intel laptops are all fine.

I know this is only a trivial matter but it is bugging me that nothing can see which OpenCore version I am using.

Spoiler

 

EFI.zip

Edited June 23, 2023 by SavageAUS

[cankiulascmnfye]

1 hour ago, SavageAUS said:

Ok I have tried to troubleshoot this mostly on my own but now I need help.

My OpenCore version is not detected by any 3rd party apps (About This Hack, Hackintool, Etc)

I have reset my NVRAM, I have formatted my EFI partition. This has been going on for a long time with this machine.

This is only happening on my AMD rig, my Intel laptops are all fine.

I know this is only a trivial matter but it is bugging me that nothing can see which OpenCore version I am using.

  Reveal hidden contents

 

EFI.zip 6.91 MB · 0 downloads

 

Looks like a nightly build to me.  Happens to me with nightlies as well as you can see:

 

 

Same result when using Terminal

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version	UNK-000-0000-00-00

 

Edited June 23, 2023 by cankiulascmnfye

[Matgen84]

@SavageAUS @cankiulascmnfye

 

Check the ExposeSensitiveData setting in the config.plist. It can be set to 2. I believe.

 

According the OC Manual:

7. ExposeSensitiveData
Type: plist integer
Failsafe: 0x6
Description: Sensitive data exposure bitmask (sum) to operating system.
• 0x01 — Expose the printable booter path as an UEFI variable.
• 0x02 — Expose the OpenCore version as an UEFI variable.
• 0x04 — Expose the OpenCore version in the OpenCore picker menu title. 
• 0x08 — Expose OEM information as a set of UEFI variables.

Edited June 23, 2023 by Matgen84

[cankiulascmnfye]

@Matgen84 Oh, you are right! I forgot about that. Mine was set at 4 but it needs to be set to 6 in my case. Thanks!

Edited June 23, 2023 by cankiulascmnfye

[SavageAUS]

20 hours ago, Matgen84 said:

@SavageAUS @cankiulascmnfye

 

Check the ExposeSensitiveData setting in the config.plist. It can be set to 2. I believe.

 

According the OC Manual:

7. ExposeSensitiveData
Type: plist integer
Failsafe: 0x6
Description: Sensitive data exposure bitmask (sum) to operating system.
• 0x01 — Expose the printable booter path as an UEFI variable.
• 0x02 — Expose the OpenCore version as an UEFI variable.
• 0x04 — Expose the OpenCore version in the OpenCore picker menu title. 
• 0x08 — Expose OEM information as a set of UEFI variables.

Thank you very much.

All is good with my OCD now lol.

 

Such a simple setting, mine was set on 8, now is set to 6.

Spoiler

 

[cankiulascmnfye]

So, OC 0.9.4 now has what is called InstanceIdentifier to " target .contentVisibility to specific instances". This sounds like that you can use different instances? of OpenCore now (located in different folders?).

 

So I checked the Documentation:

 

"InstanceIdentifier: […]The current use of this value is to optionally target .contentVisibility files to specific instances of OpenCore, as explained in the Boot Algorithm section."

 

Okay, so let's look into .contentVisibility: "The .contentVisibility file, when present, may optionally target only specific instances of OpenCore. Its contents are [{Instance-List}:](Disabled|Auxiliary). If a colon (:) is present, the preceding Instance-List it is a comma separated list of InstanceIdentifier values (example: OCA,OCB:Disabled). When this list is present, the specified visibility is only applied if the InstanceIdentifier of the current instance of OpenCore is present in the list. When the list is not present, the specified visibility is applied for all instances of OpenCore.

 

Note 1 : For any instance of OpenCore with no InstanceIdentifier value, the specified visibility from a .contentVisibility file with an Instance-List will never be applied. "

 

ICould  somebody show an example of how this is actually implemented? The explanations sound confusing.

[deeveedee]

@cankiulascmnfye If it gets us closer to having multiple config.plists for OC, maybe OC is finally catching up to CLOVER 🤣Maybe it helps me with this?

Edited June 25, 2023 by deeveedee

[cankiulascmnfye]

@deeveedee More like multiple versions of complete "OC" folders, if I understand correctly.

[deeveedee]

@cankiulascmnfye I haven't used CLOVER for quite a while, but I remember CLOVER having folders for each macOS version.  I think I always used the "Other" folder which applied to all versions of macOS.  I'm probably forgetting a lot, but if what you say is true, it sounds like an old CLOVER capability that's being resurrected in OC.

[AlfredoM]

I have a problem with OC 0.9.3 on a Hackintosh with MSI B250 Mortal motherboard (is kabylake Intel CPU i5-7600).

 

All USB ports are proven to work, they are displayed as Connect in the Hackintosh Tool and in the system properties for USB.

 

However, I don't see any external icons for the USB drives on the desktop or in Disk Utility.

It is only the case in Sonoma Beta1 and Beta2.

 

OC 0.9.3 runs fine with Ventura and Monterey etc.

 

What is causing external drives not showing up in Sonoma macOS? is it because of the OC 0.9.3?

 

Thanks for help on this.

 

My problem has been solved.

 

I have read in other forums that it works with an Intel Blutooth Fix.kext (disable this) then the external drives are displayed.

 

I only installed the BCM94360CD WLAN+BT combo card. Ok WLAN doesn't work under Sonoma anymore anyway, so I deleted all the Brcm kextes.

 

Simply deactivating the BlueToolFixup.kext brought about the success that my 2nd NvME in a PCIe controller and also all USB drives

are visible as external drives in the desktop and disk utility and I also have read+write access to them.

 

I was now able to deactivate all Brcm kextes under OC 0.9.3 and still WLAN and BT still work perfectly under Ventura.

 

So it what is probably simplified a lot under OC 0.9.3 compared to OC 0.8.8.

Edited June 25, 2023 by AlfredoM

[cankiulascmnfye]

1 hour ago, deeveedee said:

@cankiulascmnfye I haven't used CLOVER for quite a while, but I remember CLOVER having folders for each macOS version.  I think I always used the "Other" folder which applied to all versions of macOS.  I'm probably forgetting a lot, but if what you say is true, it sounds like an old CLOVER capability that's being resurrected in OC.

 

These folders in Clover are only relevant for loading kexts based on the macOS version. OpenCore's Min/Max Kernel settings are a much better solution in this regard this since this method doesn't produce kext duplicates.

 

But Clover supports loading different configs from the boot menu. And since the latest commit it now also supports multiple SMBIOS (with an auto-switcher) for different versions of macOS (including FakeCPUID) which allows using the same EFI and config for different versions of macOS which require a different SMBIOS and FakeCPUID which is required when trying to run old OSes with latest hardware.

 

For OpenCore it seems you need a duplicate of the whole OC folder, rename it, configure it differently then do the .contentVisibility thing, I guess.

[Max.1974]

1 hour ago, AlfredoM said:

I have a problem with OC 0.9.3 on a Hackintosh with MSI B250 Mortal motherboard (is kabylake Intel CPU i5-7600).

 

All USB ports are proven to work, they are displayed as Connect in the Hackintosh Tool and in the system properties for USB.

 

However, I don't see any external icons for the USB drives on the desktop or in Disk Utility.

It is only the case in Sonoma Beta1 and Beta2.

 

OC 0.9.3 runs fine with Ventura and Monterey etc.

 

What is causing external drives not showing up in Sonoma macOS? is it because of the OC 0.9.3?

 

Thanks for help on this.

 

Hello my friend, maybe you need to check if you put the correct SATA or NVME properties using Hackintool for example, in the Mass Storage Device. In DeviceProperties. Or flash USB ports with SSDTTime, best extracting from Windows. For example, the SSDT-USBW. In my case I used the direct method on SSDT compiled through a very cool method made by GitHub user.

 

Existe another way to check too, if your Opencore was disable (false) or enable (true) XhciPortLimit, I think have changes about it. 

 

[miliuco]

@cankiulascmnfye  @deeveedee

 

I too am confused about how to implement this new feature.

In April dakanji opened a PR whose proposal seemed complicated. mikebeaton opened another PR 2 weeks ago with a slightly different implementation, adding the new InstanceIdentifier property

 

I suppose that I must write a short alphanumeric string into each InstanceIdentifier, e.g. OCA, OCB, OCC... to identify each OC folder, and set the different visibility of each OC folder into its .contentVisibility file, e.g "OCA,OCB:Disabled" in OCC .contentVisibility (to show only OCC when booting OCC) or "OCC,OCB:Auxiliary" in OCA .contentVisibility (to show only OCA but also OCB and OCC pressing space bar when booting OCC).

 

I hope to be understood, it is difficult for me to express myself well in English when writing about some topics.

 

Edited June 25, 2023 by miliuco

[AlfredoM]

2 hours ago, Max.1974 said:

 

Hello my friend, maybe you need to check if you put the correct SATA or NVME properties using Hackintool for example, in the Mass Storage Device. In DeviceProperties. Or flash USB ports with SSDTTime, best extracting from Windows. For example, the SSDT-USBW. In my case I used the direct method on SSDT compiled through a very cool method made by GitHub user.

 

Existe another way to check too, if your Opencore was disable (false) or enable (true) XhciPortLimit, I think have changes about it. 

 

Yes, Max, I've been working on that for days, but as you can see, it's not at all because of that.

 

And in the Hackintosh tool and in the system properties, every USB port was ALWAYS connected, JUST NOT visible!!!!

 

So it has nothing to do with USB limit or xhci or ssdt or anything else, you just break more by tinkering with it.

Especially when I see that the respective USB drives are always visible in the hackintosh tool and in system properties under USB,

errors in USBinject or xhci-Limit or even with SSDT can be ruled out.

 

The connected drives were ONLY !! not visible, it was nothing more.

[cankiulascmnfye]

14 hours ago, miliuco said:

@cankiulascmnfye  @deeveedee

 

I too am confused about how to implement this new feature.

In April dakanji opened a PR whose proposal seemed complicated. mikebeaton opened another PR 2 weeks ago with a slightly different implementation, adding the new InstanceIdentifier property

 

I suppose that I must write a short alphanumeric string into each InstanceIdentifier, e.g. OCA, OCB, OCC... to identify each OC folder, and set the different visibility of each OC folder into its .contentVisibility file, e.g "OCA,OCB:Disabled" in OCC .contentVisibility (to show only OCC when booting OCC) or "OCC,OCB:Auxiliary" in OCA .contentVisibility (to show only OCA but also OCB and OCC pressing space bar when booting OCC).

 

I hope to be understood, it is difficult for me to express myself well in English when writing about some topics.

 

 

Well, I tried this: Assigned "OCA" to InstanceIdentifier of the internal config, assigned OCB to InstanceIdentifier to the config on USB flash drive.

Then I rebooted from USB flash drive. I don't see an additional entry for a different OC folder, though. With no contentvisibility options defined at all , it should list both folders, right? It doesn't.

 

I also tried renaming 2 OC folders (OCA and OCB). This resulted the system not finding OpenCore at all, aka booting straight into BIOS. At this stage I don't see the purporse nor the use of this feature at all.

[miliuco]

@cankiulascmnfye

 

I've tried without success, as you. I don't know where is the issue. As far as I know, it seems that I follow the instructions. In the Configuration.pdf we can read:

 

"The .contentVisibility file, when present, may optionally target only specific instances of OpenCore. Its contents are [{Instance-List}:](Disabled|Auxiliary). If a colon (:) is present, the preceding Instance-List it is a comma separated list of InstanceIdentifier values (example: OCA,OCB:Disabled). When this list is present, the specified visibility is only applied if the InstanceIdentifier of the current instance of OpenCore is present in the list. When the list is not present, the specified visibility is applied for all instances of OpenCore."

 

I've plugged 3 disks, macOS13R (SATA), macOS14 (SATA) and macOS13 (USB).

 

macOS13R

InstanceIdentifier=macOS13R
.contentVisibility: macOS13,macOS14:Disabled (no whitespaces)

Result: I see the 3 disks plus 1 EFI (I should see only macOS13R).

Spoiler

 

macOS14

InstanceIdentifier=macOS14
.contentVisibility: macOS13,macOS13R:Auxiliary (no whitespaces)

Result: I see the 3 disks plus 2 EFI (I should see only macOS14 and the other 2 disks after pressing space bar).

Spoiler

 

macOS13

InstanceIdentifier=macOS13
.contentVisibility: macOS13R:Disabled (no whitespaces)

Result: I see the 3 disks plus 1 EFI (I should see only macOS13 and macOS14).

Spoiler

 

In summary, I haven't success and I don't know why.

 

Edited June 26, 2023 by miliuco

[cankiulascmnfye]

@miliuco Did you adjust PickerAttributes? I think you also need to add flag OC_ATTR_USE_FLAVOR_ICON to make it work.

[miliuco]

5 hours ago, cankiulascmnfye said:

@miliuco Did you adjust PickerAttributes? I think you also need to add flag OC_ATTR_USE_FLAVOR_ICON to make it work.

 

Yes, it is my usual setting.

Mikebeaton has answered to me In the bug tracker but, apart from confirming that this new feature is not useful for the vast majority of users, it does not clarify my question of why it does not work if we have apparently followed the instructions.

 

[cankiulascmnfye]

@miliuco I've read his response. I had to laugh hard at "we believe that a correctly tuned config.plist can successfully boot all versions of macOS". Reality Distortion Level 100. In conclusion: a pretty over-engineered, underwhelming niche feature nobody asked for and nobody needs.

Edited June 26, 2023 by cankiulascmnfye