OpenCore General Discussion

[Slice]

Why do you seek to disable SIP? Hackintosh will work with the SIP enabled, csr-active-config=0

You want unrestricted DTRACE? You want NVRAM overflow? You want write bytes outside disk partition?

[Slice]

This is the picture

The problem is VoodooHDA is not working. I have to set csr=0x285 to make it working.

 

[MacNB]

5 hours ago, Slice said:

This is the picture

The problem is VoodooHDA is not working. I have to set csr=0x285 to make it working.

 

 

Also found reason to turn on parts of the SIP for Legacy systems with emulated NVRAM.

In OC, LogoutHook.Command runs nvramdump to dump the content of nvram to nvram.plist file.

But during restart or shutdown macOS complains the nvramdump is from an unidentified developer and doesn't run it IF SIP is enabled.

Edited October 3, 2021 by MacNB

[makk]

1 hour ago, Slice said:

Why do you seek to disable SIP? Hackintosh will work with the SIP enabled, csr-active-config=0

You want unrestricted DTRACE? You want NVRAM overflow? You want write bytes outside disk partition?

 

Slice,

 

Ah, no, I want to work normally, but since I'm not 100% on this fact, as in I don't want to take a risk that no boot and other cannot access

happen.  

 

I assumed from the previous versions of MacOS to keep it as is to be able to make the necessary addon's moves changes.  Common.

 

As I am reading more and more about the ability, I am unsure the steps in order

a preferred order of procession. That works as is now.  No restrictions to this Hacky.

 

Can you if possible describe, list the order I should take?

 

Thank you for taking the time to inform a kind gesture on your part.

2 hours ago, 1Revenger1 said:

Right, nothing to worry about. I get it on my systems as well.

Probably need to change the dependency from IOHIDSystem to IOHIDFamily. Comment about it here: https://github.com/acidanthera/OpenCorePkg/blob/d5693d1b73c21c308e2720771cf5d03c1d01bb3d/Library/OcAppleKernelLib/PrelinkedKext.c#L879-L884

THank you 1REVENGER1

 

This is rather a very long file.

 

Do I copy the entire behemoth of a file?

[makk]

2 hours ago, 1Revenger1 said:

Right, nothing to worry about. I get it on my systems as well.

Probably need to change the dependency from IOHIDSystem to IOHIDFamily. Comment about it here: https://github.com/acidanthera/OpenCorePkg/blob/d5693d1b73c21c308e2720771cf5d03c1d01bb3d/Library/OcAppleKernelLib/PrelinkedKext.c#L879-L884

 

1Revenger1

 

A separate question.  

 

Sanbox errors that have (deny) are these normal?  Because they are encrypted and protected? or either one? during boot the kernel log files

 

there are errors that make no sense.

 

Is there an error log checker like a dictionary reference coded ?

 

 

[Avery B]

3 minutes ago, makk said:

Sanbox errors that have (deny) are these normal?  Because they are encrypted and protected? or either one? during boot the kernel log files

Most errors are going to be some sort of red herring or not really important. I tend to ignore errors coming from macOS, unless something isn't working and I'm actively looking for logs related to that.

Also the link I sent in my last post was just pointing to the comment. The fix is to change IOHIDSystem to IOHIDFamily in the Info.plist for the kext. The comment explains why this is needed.

[makk]

20 minutes ago, 1Revenger1 said:

Most errors are going to be some sort of red herring or not really important. I tend to ignore errors coming from macOS, unless something isn't working and I'm actively looking for logs related to that.

Also the link I sent in my last post was just pointing to the comment. The fix is to change IOHIDSystem to IOHIDFamily in the Info.plist for the kext. The comment explains why this is needed.

1Revenger1 Thank you  

 

Something like this:

1 edit the info.plist VoodooPS2Mouse.kext edit file in EFI>Kexts?

2 all the VoodooPS2 plugins plus the Controller?

 

Second question where to address the Airportitlwm issues? which section in this forum?

 

Much appreciated 

Edited October 3, 2021 by makk

[Avery B]

1 minute ago, makk said:

1 edit the info.plist VoodooPS2Mouse.kext edit file in EFI>Kexts?

2 all the VoodooPS2 plugins plus the Controller?

Which VoodooPS2 are you using?
Acidanthera's should already be fixed. But all of the plugins probably need to be fixed if your using a different fork. VoodooPS2Controller itself should be fine.

1 minute ago, makk said:

Second question where to address the Airportitlwm issues? which section in this forum?

No clue tbh, might be better to ask on their gitter?

[makk]

1 minute ago, 1Revenger1 said:

Which VoodooPS2 are you using?
Acidanthera's should already be fixed. But all of the plugins probably need to be fixed if your using a different fork. VoodooPS2Controller itself should be fine.

No clue tbh, might be better to ask on their gitter?

 

I'm using latest VoodooPS2 from Acid, 2.2.6  

I'm getting the IOHIDFamily debug and error then resorts to Shim legacy 2

 kernel: (IOHIDFamily) HID: Legacy shim 2

 

there's an actual error happening about the digitizer which resorts to Shim Legacy 2. As it may not seem normal to me.

What is Shim Legacy 2?  USB 2?

 

Where do I submit concerns on gitter as I do not have an account there? where is the appropriate section at the resource?

 

Thank you

 

 

[Avery B]

2 minutes ago, makk said:

I'm getting the IOHIDFamily debug and error then resorts to Shim legacy 2

 kernel: (IOHIDFamily) HID: Legacy shim 2

This really isn't an error to worry about. I get the error too, but everything still works fine.

2 minutes ago, makk said:

Where do I submit concerns on gitter as I do not have an account there? where is the appropriate section at the resource?

Can use a github account, though beyond that I don't know really.

[makk]

10 minutes ago, 1Revenger1 said:

This really isn't an error to worry about. I get the error too, but everything still works fine.

Can use a github account, though beyond that I don't know really.

 

Thank you

 

I'll check out the site 

[nmano]

I try install Monterey with Opencore 0.7.4 System not show all the hard drives only show USB Drive.

How to fix please help?

Thanks for your support.

 

config.plist

[Matgen84]

11 minutes ago, nmano said:

I try install Monterey with Opencore 0.7.4 System not show all the hard drives only show USB Drive.

How to fix please help?

Thanks for your support.

 

 

config.plist 109.31 kB · 0 downloads

 

ocvalidate find 251 issues requiring attention. Use this tool and correct your config.plist 

[miliuco]

1 hour ago, nmano said:

I try install Monterey with Opencore 0.7.4 System not show all the hard drives only show USB Drive.

How to fix please help?...

 

First of all you must fix a big number of errors in config.plist. Ocvalidate tool (included in each OpenCore package) is your friend, please use it to check if the config.plist file is ok.

• ACPI >> Add >> entries 3-7-17-21 contains illegal character (spaces).
• All ACPI >> Patch entries are missing 2 properties: Base and BaseSkip.
• Kernel >> Add >> entry 17 >> BundlePath contains illegal character (space).
• Kernel >> Patch >> entry 13 >> Comment contains illegal character (© I guess).
• Kernel >> Patch >> entries number 15 and 18 are missing MaxKernel and MinKernel.

Please check always your config before asking for help.

 

EDIT: all disks not displayed are APFS?

 

EDIT 2: please complete your signature (user >> profile).

 

Edited October 4, 2021 by miliuco

[makk]

Go here to make sure you have all your configs done right follow carefully the instructions to configure 

use ProperTree --see attachment and unzip it place it Applications Folder >> drag and drop

 

https://dortania.github.io/OpenCore-Install-Guide/config.plist/skylake.html#starting-point

 

sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

 

Open Terminal

type sudo

Go to Applications Folder or wherever you put the installer file

right click on the file select Show Package Contents

open to Contents>Resources> 

select and drag and drop "createinstallmedia" file to the Terminal 

type --volume

Drag and drop the USB drive into Terminal

press enter 

then it will ask to erase and copy the file press Y for Yes and press enter

 

Good luck

 

ProperTree.zip

[Anto65]

OpenCore-0.7.4-RELEASE   is out !

 

https://github.com/acidanthera/OpenCorePkg/releases/tag/0.7.4

 

👍

Edited October 4, 2021 by antuneddu

[Allan]

1 hour ago, antuneddu said:

OpenCore-0.7.4-RELEASE   is out !

 

https://github.com/acidanthera/OpenCorePkg/releases/tag/0.7.4

 

👍

Already updated here 😄

 

All went fine 

[miliuco]

But Dortania site doesn't display yet October updates, including kexts and @vit9696 message.

[oldman20]

3 hours ago, miliuco said:

 

First of all you must fix a big number of errors in config.plist. Ocvalidate tool (included in each OpenCore package) is your friend, please use it to check if the config.plist file is ok.

• ACPI >> Add >> entries 3-7-17-21 contains illegal character (spaces).
• All ACPI >> Patch entries are missing 2 properties: Base and BaseSkip.
• Kernel >> Add >> entry 17 >> BundlePath contains illegal character (space).
• Kernel >> Patch >> entry 13 >> Comment contains illegal character (© I guess).
• Kernel >> Patch >> entries number 15 and 18 are missing MaxKernel and MinKernel.

Please check always your config before asking for help.

 

EDIT: all disks not displayed are APFS?

 

EDIT 2: please complete your signature (user >> profile).

 

i have issue opposed to him: My Stick USB Installer OC 0.7.4 only show Big Sur installed + big sur installer, not show Catalina. And lower OC version is showup full entries

 

2 hours ago, antuneddu said:

OpenCore-0.7.4-RELEASE   is out !

 

https://github.com/acidanthera/OpenCorePkg/releases/tag/0.7.4

👍

 

BUT current document guides isn't 😳, how can i config plist properly?

[miliuco]

@oldman

Tell me if you have 0 in UEFI >> APFS >> MinDate and MinVersion.

 

Changed in OpenCore0.7.2

 

UEFI> APFS: Increased the MinDate and MinVersion defaults in the APFS driver to match Big Sur in search of greater security. These values constitute the minimum date and version of the APFS driver whose loading will be allowed at startup. Examples:

• MinDate and MinVersion 0 is the default setting (currently Big Sur), leave this value if you use Big Sur or Monterey
• MinDate = 20210508 and MinVersion = 1677120009000000 for Big Sur 11.4 (20F71)
• MinDate = 20200306 and MinVersion = 1412101001000000 for Catalina 10.15.4 (19E287)
• MinDate = 20190820 and MinVersion = 945275007000000 for Mojave 10.14.6 (18G103)
• MinDate and MinVersion -1 disable this check (not recommended).

MinDate and MinVersion need to be tuned for macOS versions prior to Big Sur. You must type MinDate=20200306 and MinVersion=1412101001000000 for Catalina.

Edited October 4, 2021 by miliuco

[etorix]

17 minutes ago, oldman20 said:

BUT current document guides isn't 😳, how can i config plist properly?

Either stay on 0.7.2—but this is then the wrong thread—or use Configuration.pdf to understand the new options.

But wait a while: The latest releases of Lilu and VirtualSMC are not out yet.

[MacNB]

33 minutes ago, miliuco said:

@oldman

• MinDate and MinVersion -1 disable this check (not recommended).

 

Unfortunately, -1 is the only option if you are quadruple booting High Sierra, Mojave, Catalina & Big Sur on the same system.

[oldman20]

37 minutes ago, miliuco said:

@oldman

Tell me if you have 0 in UEFI >> APFS >> MinDate and MinVersion.

 

Changed in OpenCore0.7.2

 

UEFI> APFS: Increased the MinDate and MinVersion defaults in the APFS driver to match Big Sur in search of greater security. These values constitute the minimum date and version of the APFS driver whose loading will be allowed at startup. Examples:

• MinDate and MinVersion 0 is the default setting (currently Big Sur), leave this value if you use Big Sur or Monterey
• MinDate = 20210508 and MinVersion = 1677120009000000 for Big Sur 11.4 (20F71)
• MinDate = 20200306 and MinVersion = 1412101001000000 for Catalina 10.15.4 (19E287)
• MinDate = 20190820 and MinVersion = 945275007000000 for Mojave 10.14.6 (18G103)
• MinDate and MinVersion -1 disable this check (not recommended).

MinDate and MinVersion need to be tuned for macOS versions prior to Big Sur. You must type MinDate=20200306 and MinVersion=1412101001000000 for Catalina.

 

Yes, MinDate and MinVersion is =0. If i change to like you said, can i still able can boot Monterrey or Big Sur?

 

22 minutes ago, etorix said:

Either stay on 0.7.2—but this is then the wrong thread—or use Configuration.pdf to understand the new options.

But wait a while: The latest releases of Lilu and VirtualSMC are not out yet.

But 0.7.2 cant boot Montery, right?

[Anto65]

8 minutes ago, oldman20 said:

 

Yes, MinDate and MinVersion is =0. If i change to like you said, can i still able can boot Monterrey or Big Sur?

 

But 0.7.2 cant boot Montery, right?

Why shouldn't it boot ? I boot Mrey, BS, Catalina, Windows and Linux without problems with settings MinDate ..... in APFS ( OC-0.7.4 )

 

[oldman20]

15 minutes ago, MacNB said:

 

Unfortunately, -1 is the only option if you are quadruple booting High Sierra, Mojave, Catalina & Big Sur on the same system.

 

3 minutes ago, antuneddu said:

Why shouldn't it boot ? I boot Mrey, BS, Catalina, Windows and Linux without problems with settings MinDate ..... in APFS ( OC-0.7.4 )

 

Thank you. But why do you have Conflict of opinion?

COnfig plist guide now just at 0.7.2, so i think must start from it, than modify to 0.7.3, then 0.7.4 following changes in pdf file of they? Not jump from 0.6.9 to 0.7.4?