OpenCore General Discussion

[makk]

16 hours ago, MacNB said:

 

@Hervé

Yes I know SIP status is showing AppleInternal bit as disabled but clearly nvram command is clearly showing that bit is & was set.

Checking the OC log now shows that macOS (or boot.efi) is changing that bit (for whatever reason):

 

...

22:433 00:002 AAPL: [EB|#CSR:IN] 0x00000FFF
22:436 00:002 AAPL: [EB|#CSR:OUT] 0x00000FEF
...

That is the log output from Apple and proves that csr-active-config was properly set to 0x00000FFF but changed to 0x00000FEF.

So, "It's a plain binary matter and therefore an absolute impossibility if the csr-active-config parameter is properly applied" is not true as "something" is flipping that bit.

 

Thanks for checking your various systems.

I downgraded my OC back to 0.7.0 like yours just incase it's an issue in latest OC 0.7.3 Release but that's clearly that's not the case as I get the same result.

 

With emulated NVRAM, there's not reset NVRAM capability in OC from Bootpicker (though the feature function has been requested).

The only thing you can do is to delete the csr-active-config variable in macOS nvram via nvram command and delete the nvram.plist file before you reboot. Which I did but made no difference.

 

Not sure setting csr-active-config via Recovery OS would work for emulated nvram as it has no LogoutHook.command mechanism to save the nvram to the emulated nvram.plist.

 

So why is the AppleInternal bit being changed from 1 to 0 in some cases ?

Plot thickens.

 

I agreee with you here about SIP and OTA

 

 

Edited October 3, 2021 by makk

[makk]

Question Regarding (IOHIDFamily) Invalid digitizer transducer

Where is this fix located?

 

I had this with another unit and it did not work.

 

Is this a bug in OC or Apple?

 

In debug OC the first line is fix your kext

[1Revenger1]

1 hour ago, makk said:

Question Regarding (IOHIDFamily) Invalid digitizer transducer

 

Is this a bug in OC or Apple?

This is an Apple bug, I think it might happen with the Magic Trackpad 2 as well? Certainly happens with VoodooInput, though that still works just fine. Doesn't mean much.

1 hour ago, makk said:

In debug OC the first line is fix your kext

Seperate issue, should say what kext is causing the issue (likely some form of VoodooPS2) and what it replaced the dependency with.

[ghost8282]

@vit9696

Latest batch of commits about SB applied on Big Sur 11.6 (latest: OcMacInfoLib: Fix SB model case)

SecureBootModel: Default

SMBIOS: iMacPro1,1

 

produces a kernel panic, like if the seal is broken and the root volume is in r/w

 

kernel panic:

panic(cpu 0 caller 0xffffff8016c28fa2): "Rooting from the live fs of a sealed volume is not allowed on a RELEASE build\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/apfs/apfs-1677.141.2/kext/apfs_vfsops.c:2047
Backtrace (CPU 0), Frame : Return Address
0xffffffa08f502e40 : 0xffffff8013a8cfdd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa08f502e90 : 0xffffff8013bd3fd3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa08f502ed0 : 0xffffff8013bc45ca mach_kernel : _kernel_trap + 0x55a
0xffffffa08f502f20 : 0xffffff80178dc356 as.vit9696.VirtualSMC : __ZN18VirtualSMCProvider10kernelTrapI22x86_saved_state_1010_tEEvPT_Pm + 0x4b6
0xffffffa08f502fa0 : 0xffffff8013a31a2f mach_kernel : _return_from_trap + 0xff
0xffffffa08f502fc0 : 0xffffff8013a8c7fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa08f5030e0 : 0xffffff8013a8caf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa08f503150 : 0xffffff801429cdca mach_kernel : _panic + 0x54
0xffffffa08f5031c0 : 0xffffff8016c28fa2 com.apple.filesystems.apfs : _apfs_vfsop_mount + 0x3596
0xffffffa08f5039b0 : 0xffffff8016c32353 com.apple.filesystems.apfs : _apfs_vfsop_mountroot + 0x3d
0xffffffa08f5039e0 : 0xffffff8013d1870c mach_kernel : _vfs_mountroot + 0x13c
0xffffffa08f503b60 : 0xffffff8013fd4633 mach_kernel : _set_rootvnode + 0x2cd3
0xffffffa08f503e80 : 0xffffff8013abb507 mach_kernel : _max_valid_stack_address + 0xd77
0xffffffa08f503fa0 : 0xffffff8013a3113e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         as.vit9696.VirtualSMC(1.2.7)[31F93F0F-326D-33B6-874B-D66CEDE41846]@0xffffff80178cc000->0xffffff80178f3fff
            dependency: as.vit9696.Lilu(1.5.6)[CB1A03D7-259F-38B6-80CC-FF4D67CFC043]@0xffffff8017841000->0xffffff80178c8fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[59A305C2-E322-3EA6-B8DB-475512053CDE]@0xffffff8016044000->0xffffff8016045fff
         com.apple.filesystems.apfs(1677.141.2)[C27BB72B-DD05-3577-AF93-ECB5FBF79B46]@0xffffff8016bac000->0xffffff8016d1bfff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[4E1980E9-004D-36DF-A5D3-C536B34A9E7A]@0xffffff8014efe000->0xffffff8014f07fff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[5B734F34-DF9F-3478-8365-8314846DDD3C]@0xffffff8014f11000->0xffffff8014f16fff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[F9C68CEA-A200-3BF1-96B0-17B5D58B5E32]@0xffffff801536d000->0xffffff8015373fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[7C0E4949-640F-3D1D-97AF-030903A22663]@0xffffff801666f000->0xffffff8016680fff
            dependency: com.apple.kec.corecrypto(11.1)[E38D30E6-600F-30A0-8E38-E3EC38B9D929]@0xffffff8016d49000->0xffffff8016ddafff
            dependency: com.apple.security.AppleImage4(3.0.0)[94010577-1544-331F-97F2-28A99361745E]@0xffffff8014f7d000->0xffffff8014f8dfff

Process name corresponding to current thread: kernel_task
Boot args: vti=12 keepsyms=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64
Kernel UUID: C2591F4E-EE82-33CC-8C59-DB81D9AD80DD
KernelCache slide: 0x0000000013800000
KernelCache base:  0xffffff8013a00000
Kernel slide:      0x0000000013810000
Kernel text base:  0xffffff8013a10000
__HIB  text base: 0xffffff8013900000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 3242169432
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000000c13f9bd1
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000004670c823a7 0x0000000000000000
last started kext at 3171887010: @filesystems.apfs	1677.141.2 (addr 0xffffff8016bac000, size 1507328)
loaded kexts:
com.Ralink.driver.RT2870USBWirelessDriver	5.0.1
as.vit9696.VirtualSMC	1.2.7
as.vit9696.!AALC	1.6.5
as.vit9696.WhateverGreen	1.5.4
as.vit9696.Lilu	1.5.6
@filesystems.apfs	1677.141.2
>!AFileSystemDriver	3.0.1
@filesystems.tmpfs	1
@filesystems.hfs.kext	556.100.11
@BootCache	40
@!AFSCompression.!AFSCompressionTypeZlib	1.0.0
@!AFSCompression.!AFSCompressionTypeDataless	1.0.0d1
@private.KextAudit	1.0
>!AAHCIPort	346.100.2
>!AACPIButtons	6.1
>!ARTC	2.0
>!ASMBIOS	2.1
>!AAPIC	1.7
@!ASystemPolicy	2.0.0
@nke.applicationfirewall	311
|IOKitRegistryCompatibility	1
|EndpointSecurity	1
>!AXsanScheme	3
|IOAHCIBlock!S	332
>usb.IOUSBHostHIDDevice	1.2
>usb.!UHub	1.2
>usb.cdc	5.0.0
>usb.networking	5.0.0
>usb.!UHostCompositeDevice	1.2
>!UMergeNub	900.4.2
>!ABSDKextStarter	3
|IOSurface	290.8.1
|IOSkywalk!F	1
>mDNSOffloadUserClient	1.0.1b8
@filesystems.hfs.encodings.kext	1
>usb.!UXHCIPCI	1.2
>usb.!UXHCI	1.2
>usb.!UEHCIPCI	1.2
>!AEFINVRAM	2.1
>usb.!UUHCIPCI	1.2
>usb.!UUHCI	1.2
>usb.!UEHCI	1.2
>!AVirtIO	74.120.4
|IOSerial!F	11
|IOAHCI!F	294.100.1
>usb.!UHostPacketFilter	1.0
|IOUSB!F	900.4.2
>!AEFIRuntime	2.1
|IOHID!F	2.0.0
$!AImage4	3.0.0
|IOTimeSync!F	985.2
|IONetworking!F	3.4
>DiskImages	493.0.0
|IO!B!F	8.0.5d7
|IOReport!F	47
|IO!BPacketLogger	8.0.5d7
$quarantine	4
$sandbox	300.0
@kext.!AMatch	1.0.0d1
|CoreAnalytics!F	1
>!ASSE	1.0
>!AKeyStore	2
>!UTDM	511.141.1
|IOUSBMass!SDriver	184.140.2
|IOSCSIBlockCommandsDevice	436.140.1
|IO!S!F	2.1
|IOSCSIArchitectureModel!F	436.140.1
>!AMobileFileIntegrity	1.0.5
@kext.CoreTrust	1
>!AFDEKeyStore	28.30
>!AEffaceable!S	1.0
>!ACredentialManager	1.0
>KernelRelayHost	1
|IOUSBHost!F	1.2
>!UHostMergeProperties	1.2
>usb.!UCommon	1.0
>!ABusPower!C	1.0
>!ASEPManager	1.0.1
>IOSlaveProcessor	1
>!AACPIPlatform	6.1
>!ASMC	3.1.9
|IOPCI!F	2.9
|IOACPI!F	1.4
>watchdog	1
@kec.pthread	1
@kec.corecrypto	11.1
@kec.Libm	1

 

No kernel panic with SecureBootModel: x86legacy

 

Is it supposed to be expected? I suppose so, since the documentations recommends to use x86legacy for vms?

Edited October 3, 2021 by ghost8282

[makk]

10 hours ago, 1Revenger1 said:

This is an Apple bug, I think it might happen with the Magic Trackpad 2 as well? Certainly happens with VoodooInput, though that still works just fine. Doesn't mean much.

Seperate issue, should say what kext is causing the issue (likely some form of VoodooPS2) and what it replaced the dependency with.

Thank you 1Revenger1

 

This shows in the kernel log took care of time stamp.

From the Bootloader when in Debug version the first line says fix your kexts, I believe regarding the VoodooPS2Controller which is annoying to look at so I turned off Debug

 

Fallback to IOxxxSystem message,  

 

Debug 0x57d  0x583 kernel: (IOHIDFamily) IOHIDPointingEventDevice:0x100000290 open by IOHIDEventDriver 0x100000365 (0x0)

Error 0x57d  0x583 kernel: (IOHIDFamily) Invalid digitizer transducer

Default 0x57d  0x583 kernel: (IOHIDFamily) HID: Legacy shim 2

 

I recall a few years back when dealing with this issue Vit had link to go to to input into info.plist some new numbers

I can't find that page anymore

 

 

 

[1Revenger1]

1 minute ago, makk said:

Debug 0x57d  0x583 kernel: (IOHIDFamily) IOHIDPointingEventDevice:0x100000290 open by IOHIDEventDriver 0x100000365 (0x0)

Error 0x57d  0x583 kernel: (IOHIDFamily) Invalid digitizer transducer

Default 0x57d  0x583 kernel: (IOHIDFamily) HID: Legacy shim 2

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

1 minute ago, makk said:

I recall a few years back when dealing with this issue Vit had link to go to to input into info.plist some new numbers

I can't find that page anymore

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

[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 ?

 

 

[1Revenger1]

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

[1Revenger1]

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

 

 

[1Revenger1]

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?