OpenCore General Discussion

[texem]

1 hour ago, miliuco said:

@texem

Usually MP7,1 SMBIOS works better with iGPU disabled in BIOS since this model doesn't have iGPU. When iGPU disabled, of course removing DeviceProperties of Intel 630 in config.plist.

But if this settings are okay for you, go ahead.

MP7,1 can work with or without WhateverGreen, have you tried both?

 

WEG is not in use here and doesn't fix the issue ( tried with and w/o ).

Anyways, the UHD is not shown in system info as gfx card but only on PCI

 

 

[Matgen84]

Hi ALL

 

Despite of Opencanopy, Flavours theme installed, and settings, there is no GUI menu. Only BuildIn picker is showing up on my old Ivybridge.

Any ideas, please.

 

Edited October 21, 2024 by Matgen84

[chris1111]

@Matgen84 try this sintax

chris1111/Flavours-RoundSquare

 

[Matgen84]

9 hours ago, chris1111 said:

@Matgen84 try this sintax

chris1111/Flavours-RoundSquare

 

 

@chris1111 same issue: only builtin picker showing up. It's a first time for this problem.  Actually, I'm using OC Nightly 1.0.3 commit d4ddd29 to boot macOS Sequoia 15.0.1 on my old Ivybridge.

[miliuco]

@Matgen84

Good morning, this has to have an explanation that shouldn't be difficult to find.
You have to review:

• PickerVariant that @chris1111 has already told you, check that the path written in config.plist is the same as the theme folder
• OpenCanopy.efi has to be from the same package (version) as OpenCore.efi, make sure that both files are from the same OpenCore package
• set PickerVariant=Default if you have OC/Resources/Acidanthera/GoldenGate, give it a try
• check that the Flavours-RoundSquare folder theme has all the required icons with their right names.

[hardcorehenry]

Question about MCHC. If I rename device MC(present in my mobo) to MCHC, ioreg shows it right after IMEI, LPCB.

Spoiler

 

In real MacPro7,1(my smbios),there is no MCHC in ACPI/ioreg but there is DMI0, the same pciclass as MC and MCHC, checked with real MacPro7,1 dump. Now if I rename MC to DMI0, ioreg shows it right before HDEF device so this rename seems to matter. Any thoughts if it’s proper approach?

Spoiler

 

Edited October 22, 2024 by hardcorehenry

[Matgen84]

2 hours ago, miliuco said:

@Matgen84

Good morning, this has to have an explanation that shouldn't be difficult to find.
You have to review:

• PickerVariant that @chris1111 has already told you, check that the path written in config.plist is the same as the theme folder
• OpenCanopy.efi has to be from the same package (version) as OpenCore.efi, make sure that both files are from the same OpenCore package
• set PickerVariant=Default if you have OC/Resources/Acidanthera/GoldenGate, give it a try
• check that the Flavours-RoundSquare folder theme has all the required icons with their right names.

@miliuco
Good afternoon. I already review twice and more 3 steps.  I try to set PickerVariant=Default. 

 

SOLVED: The error occurred when I made a mistake with OCLP that overwritten the EFI folder. Fortunately, I had a backup. Thanks my friend.
 

Edited October 22, 2024 by Matgen84

[Slice]

On 10/22/2024 at 2:59 PM, hardcorehenry said:

Question about MCHC. If I rename device MC(present in my mobo) to MCHC, ioreg shows it right after IMEI, LPCB.

  Hide contents

 

In real MacPro7,1(my smbios),there is no MCHC in ACPI/ioreg but there is DMI0, the same pciclass as MC and MCHC, checked with real MacPro7,1 dump. Now if I rename MC to DMI0, ioreg shows it right before HDEF device so this rename seems to matter. Any thoughts if it’s proper approach?

  Hide contents

 

It looks like just alphabetic order.

[deeveedee]

Interesting Open Core 1.0.3 changelog

 

I have not personally experienced this OpenDuet hang at start, but this may be helpful to others with older hacks.

[Stefanalmare]

11 hours ago, deeveedee said:

Interesting Open Core 1.0.3 changelog

 

I have not personally experienced this OpenDuet hang at start, but this may be helpful to others with older hacks.

 

Me.

[FredWst]

Hi,

 

I'd like to expose an issue I get on my hack.

 

Everything works fine except that at each reboot I get a log that says

Date/Time:        2024-10-30 12:11:10.143 +0100
End time:         2024-10-30 12:11:11.144 +0100
OS Version:       macOS 15.1 (Build 24B83)
Architecture:     x86_64h
Report Version:   53

Data Source:      Stackshots
Shared Cache:     2DE8C81C-EE54-3099-8E26-F112966509C2 slid base address 0x7ff8102b4000, slide 0x102b4000 (System Primary)
Shared Cache:     B9AE3589-92C8-3F79-8A4F-9021B8A32EB9 slid base address 0x7ff819188000, slide 0x19188000 (DriverKit)

Event:            shutdown stall
Duration:         1.00s (sampling started after 2 seconds)
Steps:            101 (10ms sampling interval)

Hardware model:   iMac19,1
Active cpus:      12
HW page size:     4096
VM page size:     4096

Time Since Boot:  15877s
Time Awake Since Boot: 7897s
Time Since Wake:  639s

Total CPU Time:   0.288s (789.3M cycles, 1042.4M instructions, 0.76c/i)
Vnodes Available: 26.29% (69188/263168)

Preferred User Language: en-001
Country Code:     001
OS Cryptex File Extents: 1

------------------------------------------------------------
Heavy format: stacks are sorted by count
Use -i and -timeline to re-report with chronological sorting
------------------------------------------------------------



Process:          CloudTelemetryService [1386]
UUID:             33811ED3-F5E1-3D53-8A47-51773FE36002
Path:             /System/Library/PrivateFrameworks/CloudTelemetry.framework/Versions/A/XPCServices/CloudTelemetryService.xpc/Contents/MacOS/CloudTelemetryService
Identifier:       com.apple.CloudTelemetryService.xpc
Version:          ??? (2200.144)
Build Version:    5773
Project Name:     CloudTelemetry
Source Version:   2200144000000000
Shared Cache:     2DE8C81C-EE54-3099-8E26-F112966509C2 slid base address 0x7ff8102b4000, slide 0x102b4000 (System Primary)
Architecture:     x86_64
Parent:           launchd [1]
Responsible:      privatecloudcomputed [1384]
UID:              501
Sudden Term:      Tracked (allows idle exit)
Footprint:        3812 KB
Time Since Fork:  181s
Num samples:      101 (1-101)
CPU Time:         <0.001s (240.5K cycles, 86.5K instructions, 2.78c/i)
Num threads:      3
Note:             2 idle work queue threads omitted

 

Here is full log.

spindump.txt.zip

 

Is there somebody how can help me to solve that ?

 

System in my signature.

 

Fred

 

EDIT:

After some research it seems it's a very old mistake.
On Apple forum, people say don't take care about.

 

Edited October 30, 2024 by FredWst

[texem]

On 10/16/2024 at 10:53 PM, texem said:

 

WEG is not in use here and doesn't fix the issue ( tried with and w/o ).

Anyways, the UHD is not shown in system info as gfx card but only on PCI

 

 

 

Quoting myself. There is a simple solution fixing 4K playback with 7,1 or 1,1 imac pro 

 

Fixing 4K Streaming

 

Forget abt. enabling the GPU in BIOS.

 

Cheers to you all

 

 

 

[deeveedee]

Updated CPU detection may be a reason for some to upgrade to Open Core 1.0.3 Beta before the final 1.0.3 is released.

 

Be sure to inspect Acidanthera kexts, since those using newer CPUs may need to update kexts (like Lilu.kext) in addition to OC 1.0.3.

 

EDIT:

 

Edited November 14, 2024 by deeveedee

[meg2014]

So, I'm running 1.0.3 and getting an error message that I can't figure out or find where the error is referencing.

Normally, I can locate where the error might be, but this OC error message doesn't give some indication of where you can find the error.  I've checked with the sample plist, etc, checked any new items, etc, but can't find it.

 

Anybody have any idea what section of the config.plist this error is referring to?  I don't need much help, just a pointer to where this error might be....

 

Thanks in advance.

 

 

 

 

Edited December 7, 2024 by meg2014

[meg2014]

2 hours ago, eSaF said:

Hi, it looks like you're running an old OC EFI folder and config.plist files within that needs updating.

The app OCAT will actually point to the exact error or section in the config.plist.

 

Try updating the OC files and kexts first and see if the error is still there.

Good luck.

 

PS - I just thought you maybe running what I call a hybrid config.plist that has this unofficial line 'Enable For All'

This is line not included in the official OC releases, so whenever you update OC, it will throw up that error.

 

 

However, all kexts are the very latest and OC (1.0.3) is the very latest release.  OCAT shows no "Enable for all" line anywhere, also OCAT shows the same error, but not any detail about which line is causing this error message.

 

Oh well, thanks for trying

 

 

[deeveedee]

3 hours ago, meg2014 said:

So, I'm running 1.0.3 and getting an error message that I can't figure out or find where the error is referencing.

Normally, I can locate where the error might be, but this OC error message doesn't give some indication of where you can find the error.  I've checked with the sample plist, etc, checked any new items, etc, but can't find it.

 

Anybody have any idea what section of the config.plist this error is referring to?  I don't need much help, just a pointer to where this error might be....

 

Thanks in advance.

 

 

 

 

 

Is that a message that you're seeing while booting?  If so, what does OC 1.0.3's ocvalidate tell you?

[Max.1974]

1 hour ago, meg2014 said:

 

 

However, all kexts are the very latest and OC (1.0.3) is the very latest release.  OCAT shows no "Enable for all" line anywhere, also OCAT shows the same error, but not any detail about which line is causing this error message.

 

Oh well, thanks for trying

 

 

Hi, "Enable for All" is OC "NO ACPI" in general used in Olarila.com EFI is good to get no conflicts with Windows. To fix that you can validate with OCAT or validate with OC Configurator. Just open one of them, in OCAT look for red mark message, click and when shows up windows message, just save. With OC Configurator ate same, except for red mark. Program automatic will shoe to you errors messages for fix validate last builds. 

 

Good Lucky  

 

 

 

 

However, exist another method you can use ocvalidate with your plist, need Google it to fix that. 

 

https://dortania.github.io/OpenCore-Post-Install/universal/update.html#_3-replace-the-opencore-files-with-the-ones-you-just-downloaded 

 

 

Edited December 7, 2024 by Max.1974

[miliuco]

@meg2014

 

Expanding on what @deeveedee suggests, to check config.plist with ocvalidate you have to:

• ocvalidate tool must be from the same OpenCore package that you are using (1.0.3 in your case)
• open Terminal and drag ocvalidate onto it
• drag config.plist onto Terminal
• the result must match the error you see when starting up.

Paste the result here so I can help you further.

You can upload here your config.plist too.

 

Edited December 7, 2024 by miliuco
Typo

[iaihc]

OpenCore Configurator

 

Every time this file is automatically generated and updated, it is not the corresponding version of the software. Even after I replace it, the old version is still automatically overwritten. Therefore, the second time I open this software to compile the file, it is a version verification error.
I provided feedback to the author, but my description was not accurate.

 

 

The path of the verification file cannot be replaced. After closing and reopening the software, the verification file will be replaced

 

/Users/xxx(user name)/Library/Caches/org.altervista.mackie100projects.OpenCore-Configurator/Validation/Release

 

 

 

[Max.1974]

OC Configurator is have been get error. But you can reuse OCAT to update "again" and them you will fix it. 

 

Because this that im use Clover hehehe 

[meg2014]

16 hours ago, deeveedee said:

 

Is that a message that you're seeing while booting?  If so, what does OC 1.0.3's ocvalidate tell you?

 

Yes, the message comes up before the menu system (the gui icons) show up. It's not a big annoyance, its just something I'd like to address.  It doesn't, for example, affect booting or the system operations (from what I can tell).  And, I didn't see this with 1.0.2.

 

I'm usually pretty good at locating these errors and solving them myself, but this error message has no real pointers that lead me to where I can find what is going on.  I wonder if this is a bug of some sort.....

13 hours ago, miliuco said:

@meg2014

 

Expanding on what @deeveedee suggests, to check config.plist with ocvalidate you have to:

• ocvalidate tool must be from the same OpenCore package that you are using (1.0.3 in your case)
• open Terminal and drag ocvalidate onto it
• drag config.plist onto Terminal
• the result must match the error you see when starting up.

Paste the result here so I can help you further.

You can upload here your config.plist too.

 

 

I'll give that a try.  Thanks!

[meg2014]

15 hours ago, eSaF said:

Hi, Just a thought here. Compare your config.plist with the sample config.plist.

I think you need to add a Comment or a String Value, it looks like that is what is missing from an Entry at 0 index (ACPI entries??? not certain), hence the reason you need to compare your config.plist with the Sample config.plist

to see exactly what is missing. At least that is what that the error looks like to me.

 

Doing that compare is standard operating procedure for me.  It was my very first troubleshooting step   I too thought it was in the ACPI area, but didn't find anything.  Maybe one of my .aml files is bogus or not quite correct?  That's possible too.....but as I noted in another reply, I did not see this error in 1.0.2......Hmm....

[STLVNUB]

I Have Mentioned This Several Times, BUT

 

You Guys Still Stuffing Around With Your EFI Folder On ESP?

Take The Easy Way, Make A Fat 32 Partition As The First One

Name It e.g Booter, Or Whatever

And The Rest As Your OS Partition

When You Want To Change EFI, Its Super Easy To Do

As All You Need To Do Is Open The Boot Partition

And Make Your Changes

[Anto65]

Since from ver. 1.0.2 to 1.0.3 there has been no change in the plist. I assume that a new " Item " was added inadvertently but left empty, precisely because of the notification.
Since we don't have at least the plist, we can guess endlessly 😁

[STLVNUB]

1 hour ago, verdazil said:

Yes, this is similar to what happens when creating a bootable flash drive via the BDU utility. But the disadvantage is that this FAT32 Partition is visible in other operating systems (Windows, Linux) and can cause confusion when working in them.

i think the advantages out weight the negatives, but each to there own, thanks for your input