OpenCore General Discussion

[deeveedee]

@naiclub You're becoming my favorite grandchild. 😉

[naiclub]

On 8/9/2024 at 10:07 PM, deeveedee said:

@naiclub You're becoming my favorite grandchild. 😉

Hello Grandma, this is how it is.

config.plist.zip

[deeveedee]

@naiclub In order to fully diagnose your issue, I would need both your current config.plist (the config.plist that causes the Memory Misconfigured message) and your previous config.plist (which did not have the Memory Misconfigured message), but I'll try to diagnose with what you provided.

 

You are using SMBIOS MacPro7,1.  According to the RestrictEvents.kext documentation here, you may want to add revblock=pci and revpatch=pci.  

 

Also, you are redundantly specifying RestrictEvents args in "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" and "NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args."  Remove the redundant/unnecessary boot-args:

Spoiler

 

Attached is a revised config.plist that should give you some ideas.

config.plist.zip

[naiclub]

44 minutes ago, deeveedee said:

@naiclub In order to fully diagnose your issue, I would need both your current config.plist (the config.plist that causes the Memory Misconfigured message) and your previous config.plist (which did not have the Memory Misconfigured message), but I'll try to diagnose with what you provided.

 

You are using SMBIOS MacPro7,1.  According to the RestrictEvents.kext documentation here, you may want to add revblock=pci and revpatch=pci.  

 

Also, you are redundantly specifying RestrictEvents args in "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" and "NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args."  Remove the redundant/unnecessary boot-args:

  Reveal hidden contents

 

Attached is a revised config.plist that should give you some ideas.

config.plist.zip 5.85 kB · 2 downloads

It didn't go away. I took yours and put them in. It didn't fix anything.

Spoiler

 

[deeveedee]

@naiclub It is impossible to diagnose any of your issues without the info I requested.  ALWAYS post your EFI (at least your config.plist) when you report problems and ask for help.  You're still on my favorite grandchild list, but you're testing my patience.

 

EDIT: Let's start over again by re-reading this post.  Please provide both config.plists (not just one).

Edited August 13, 2024 by deeveedee

[naiclub]

15 ชั่วโมงที่แล้ว deeveedee กล่าวว่า:

@naiclub เป็นไปไม่ได้ที่จะวินิจฉัยปัญหาของคุณโดยไม่มีข้อมูลที่ฉันขอไว้ โพสต์ EFI ของคุณเสมอ (อย่างน้อยก็ config.plist) เมื่อคุณรายงานปัญหาและขอความช่วยเหลือ คุณยังคงอยู่ในรายชื่อหลานคนโปรดของฉัน แต่คุณกำลังทดสอบความอดทนของฉัน

 

แก้ไข: มาเริ่มใหม่อีกครั้งด้วยการอ่านโพสต์นี้ อีกครั้ง โปรดจัดเตรียมไฟล์ config.plists ทั้งสองไฟล์ (ไม่ใช่แค่ไฟล์เดียว)

ยังไงก็ขอบคุณคุณยาย
ตามนี้ค่ะ

 

Edited August 14, 2024 by naiclub

[deeveedee]

@naiclub Still not what I requested.  One thing I missed before is that you redundantly specify revcpu in "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" and "NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args."  Remove the instance of revcpu=1 in "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" (I've only tested with revcpu=1 in boot-args.

 

EDIT: Also, add revblock to "NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102"

 

EDiT2: One more thing - after you removed revcpu=1 from "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102," remove revcpu from "NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" - see attached config.plist.  Add revpatch to "NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102"

 

If you make changes to any "NVRAM > Add" properties that are not in "NVRAM > Delete," you MUST Reset NVRAM before each test.

config.plist.zip

Edited August 13, 2024 by deeveedee

[naiclub]

59 minutes ago, deeveedee said:

@naiclub Still not what I requested.  One thing I missed before is that you redundantly specify revcpu in "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" and "NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args."  Remove the instance of revcpu=1 in "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" (I've only tested with revcpu=1 in boot-args.

 

EDIT: Also, add revblock to "NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102"

 

EDiT2: One more thing - after you removed revcpu=1 from "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102," remove revcpu from "NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102" - see attached config.plist.  Add revpatch to "NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102"

 

If you make changes to any "NVRAM > Add" properties that are not in "NVRAM > Delete," you MUST Reset NVRAM before each test.

config.plist.zip 6.13 kB · 2 downloads

I've resigned myself to fate, Grandma. I'll remove the SSD and keep it for now. 😅

[obus]

Hi guys.

Have a problem with booting my rig on OC 10.0.1.

Developers has in this release disabled "XcpmExtraMsrs MSR_MISC_PWR_MGMT patch on macOS 12+ due to non-existence"

This patch is mandatory on my rig for booting. (Skylake Xenon W) The patch is still in the config file under kernel --> quirk and normally I have this quirk enabled but in this new version it dosen't work. I get the message "failed to patch writes to MSR_MISC_PWR_MGMT"

Any help is appreciated.

Edited September 1, 2024 by obus

[pkdesign]

I have had this issue before and it persists. I decided to do a clean install of Sonoma and add apps one by one (rather than migrate my (rock solid) Monterey OS. Mostly things work fine but I continually get this when I first boot:

 

 

Does anyone have any idea what may be happening? I go to Settings>Displays and pick another resolution and go back to the one I want (2560) which clears it up until next boot.

[miliuco]

@pkdesign

If you delete /Library/Preferences/com.apple.windowserver.plist, logout and loggin, does it fix the issue?

[pkdesign]

No, I've tried that and the issue comes back. I will try it again though.

[cankiulascmnfye]

On 8/25/2024 at 10:01 PM, obus said:

Hi guys.

Have a problem with booting my rig on OC 10.0.1.

Developers has in this release "Disabled XcpmExtraMsrs MSR_MISC_PWR_MGMT patch on macOS 12+ due to non-existence"

This patch is mandatory on my rig for booting. (Skylake Xenon W) The patch is still in the config file under kernel --> quirk and normally I have this quirk enabled but in this new version it dosen't work. I get the message "failed to patch writes to MSR_MISC_PWR_MGMT"

Any help is appreciated.

  Reveal hidden contents

 

 

 

Screenshot doesnt show…

 

Well, the patch is still in the config because it does something in macOS 11 and older. But since the code that is effected by the patch was removed from macOS 12 and newer, the patch is disabled in this case.

 

According to the OpenCore install guide this quirk is not required for booting Skylake W.

 

Just try OpenCore 1.0.0 and if the system boots, you probably should report that this quirk is still required for booting whatever OS you are using with Skylake W

Edited September 1, 2024 by cankiulascmnfye

[obus]

On 8/30/2024 at 12:11 AM, cankiulascmnfye said:

 

Screenshot doesnt show…

 

Well, the patch is still in the config because it does something in macOS 11 and older. But since the code that is effected by the patch was removed from macOS 12 and newer, the patch is disabled in this case.

 

According to the OpenCore install guide this quirk is not required for booting Skylake W.

 

Just try OpenCore 1.0.0 and if the system boots, well you probably should report that this quirs is still required for booting hatever OS you are using with Skylake W

My system is booting perfect on 1.0.0 up to latest version of Sonoma with this quirk enabled. Must be something with my Asus C422 Pro SE motherboard. I will report to developers.

[obus]

Still unable to boot macOS Ventura 13,7 with OpenCore 10.0.1. 

Anybody has any sugestions?

Debugfiles and EFI attached.

 

Archive.zip

Edited September 21, 2024 by obus

[cankiulascmnfye]

1 hour ago, obus said:

Still unable to boot macOS Ventura 13,7 with OpenCore 10.0.1. 

Anybody has any sugestions?

Debugfiles and EFI attached.

 

Archive.zip 16.53 MB · 0 downloads

 

Did you create an issue in the Acidanthera bug report section about the changes for the XcpmExtraMsrs quirk yet?

Edited September 21, 2024 by cankiulascmnfye

[Max.1974]

2 hours ago, obus said:

Still unable to boot macOS Ventura 13,7 with OpenCore 10.0.1. 

Anybody has any sugestions?

Debugfiles and EFI attached.

 

Archive.zip 16.53 MB · 0 downloads

 

Can I suggest you add Restrict Events boot args in your Nvram ? 

 

See my config.plist partial attachment 

 

Nvram OC.plist.zip

 

I'ts recommend use revpatches in 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 line. 

 

Note: If you will install Ventura, not need OCLP patches. You are using kexts that is used for OCLP. 

 

Kernel min version its not 100% that will not affect configurations. 

 

I think you missing some IRQ patches from ACPI menu. Need extract with SSDTTime from CorpNewT user and DMAR Table. 

 

 

Report said that not found Deleted patches 

 

 

 

 

Edited September 21, 2024 by Max.1974

[Max.1974]

See mine for example 

 

Spoiler

 

[obus]

18 hours ago, cankiulascmnfye said:

 

Did you create an issue in the Acidanthera bug report section about the changes for the XcpmExtraMsrs quirk yet?

Nope. I will do that after testing some other thing first. Thank's anyway for your support.

17 hours ago, Max.1974 said:

See mine for example 

 

  Reveal hidden contents

 

Will test your suggestions.

[obus]

On 9/21/2024 at 8:57 PM, cankiulascmnfye said:

 

Did you create an issue in the Acidanthera bug report section about the changes for the XcpmExtraMsrs quirk yet?

Problems solved with @PMheart. 😄

https://github.com/acidanthera/bugtracker/issues/2410

Edited September 24, 2024 by obus

[PMheart]

On 9/21/2024 at 8:57 PM, cankiulascmnfye said:

 

Did you create an issue in the Acidanthera bug report section about the changes for the XcpmExtraMsrs quirk yet?

Apologies for my fault in June. It is fixed now. Please wait for OpenCore 1.0.2 release in October 2024. Thanks.

[pkdesign]

I updated to Sequoia from Sonoma and in the process renamed my drive from "macOS Sonoma" to "macOS Sequoia? but the bootloader still shows "macOS Sonoma." I have cleared NVRAM but it still shows up with wrong name. Why isn’t this happening automatically and how do I change it?

 

Thanks!

[FirstCustomac]

22 minutes ago, pkdesign said:

I updated to Sequoia from Sonoma and in the process renamed my drive from "macOS Sonoma" to "macOS Sequoia? but the bootloader still shows "macOS Sonoma." I have cleared NVRAM but it still shows up with wrong name. Why isn’t this happening automatically and how do I change it?

 

Thanks!

 

You will have to edit this hidden file accordingly.

 

Preboot->UUID->System->Library->CoreServices->.disk_label.contentDetails

[miliuco]

@pkdesign

How to update macOS volume name in the OpenCore picker without Intel Power gadget

 

OpenCore uses .disk_label file if it exists, otherwise it tries .contentDetails and, if this doesn't exist, it tries .disk_label.contentDetails.

• config.plist: change csr-active-config to 6F020000 (having csr-active-config also in NVRAM >> Delete >> 7C436110-AB2A-4BBB-A880-FE41995C9F82) or pick the ToggleSIP tool to switch from Enabled to Disabled (having Misc >> Security >> AllowToggleSip as True)
• reboot
• mount Preboot volume from Terminal (I'm not sure if that this is required, I see Preboot volume mounted by default but other users have had to mount that volume)
• edit /System/Volumes/Preboot/UUID-number/System/Library/CoreServices/.contentDetails and /System/Volumes/Preboot/UUID-number/System/Library/CoreServices/.disk_label.contentDetails (they are hidden files)
• change the volume name to anything else (plain text, make it simple)
• reboot.

The new name is displayed in the OpenCore text and graphical picker.

 

Note: UUID-number is the UUID of the APFS volume group where Preboot volume is located, you can do "diskutil list" and "diskutil info diskx" where diskx is the APFS Container Scheme.

 

How to update macOS volume name in the OpenCore picker with Intel Power gadget

 

Easy method: install or reinstall Intel Power Gadget and reboot.

[Anto65]

It worked in the past...It doesn't work with Sip disabled or not...not editable, you can only duplicate it

 

Spoiler

 

Try it this way it works 100%
Type in terminal:

 

diskutil info / | grep "APFS Volume Group"

 

 

in my case : A8B51008-746E-4F15-82B6-251F5500E96C ( you need yours ) 

Type

cd /System/Volumes/Preboot/YOUR-UUID/System/Library/CoreServices/ 

 

 

Type 

sudo bless --folder . --label "macOS Sequoia"  

( and type passw ) 

 

note: "macOS Sequoia" or whatever name/label you want to give it

 

to finish type

printf "macOS Sequoia" | sudo tee .disk_label.contentDetails; echo

sudo chgrp wheel .disk*

 

Edited September 24, 2024 by Anto65