Jump to content

OpenCore General Discussion


dgsga
8,759 posts in this topic

Recommended Posts

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 by AlfredoM
  • Like 2
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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. 

 

  • Like 1
Link to comment
Share on other sites

@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 by miliuco
  • Like 1
Link to comment
Share on other sites

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.

  • Like 3
Link to comment
Share on other sites

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.

  • Like 1
  • Confused 1
  • Sad 1
Link to comment
Share on other sites

@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

macOS13R.thumb.png.60c1f01adb7bccb377a5d0e097d2da0f.png

 

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

macOS14.thumb.png.d75278b86819a4ec2ecca55b2a3005a1.png

 

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

macOS13.thumb.png.ba9c6fa61bbda296156fe2bba4b2d22f.png

 

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

 

Edited by miliuco
  • Like 2
Link to comment
Share on other sites

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.

 

  • Like 1
Link to comment
Share on other sites

@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 by cankiulascmnfye
  • Like 1
  • Haha 2
Link to comment
Share on other sites

Hopefully someone here can help me track down what is going on. There is a 47 second delay during boot which didn’t use to be there. I have indicated with an arrow the spots where there is a delay:

Timestamp                       (process)[PID]    
2023-06-14 10:41:18.335821-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_log_mount_unmount:1889: disk4s5 unmounting volume macOS, requested by: com.apple.MobileSoftwareUpdate. (pid 363); parent: launchd (pid 1)
2023-06-14 10:41:18.362743-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_unmount:2740: disk4s5 waiting for purgatory cleaner to finish
2023-06-14 10:41:18.389828-0400  localhost kernel[0]: (apfs) <apfs`log_info> authapfs_seal_restore:482: disk4s5 integrity protection will be re-enabled
2023-06-14 10:41:18.416521-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_unmount:3074: disk4 nx_num_vols_mounted is 5
2023-06-14 10:41:18.442801-0400  localhost kernel[0]: (apfs) <apfs`apfs_vfsop_unmount> apfs: total mem allocated: 83652394 (80 mb);
—> 2023-06-14 10:41:18.469864-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_unmount:3087: all done.  going home.  (numMountedAPFSVolumes 5)
2023-06-14 10:41:18.891137-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: systemstats(108) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:18.891332-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: systemstats(108) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:18.893537-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: systemstats(108) deny(1) mach-lookup com.apple.tccd.system
2023-06-14 10:41:19.324861-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> 1 duplicate report for Sandbox: systemstats(108) deny(1) mach-lookup com.apple.tccd.system
2023-06-14 10:41:19.324865-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(374) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:19.325028-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(374) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:19.855712-0400  localhost kernel[0]: uipc_accept: peer disconnected unp_gencnt 86
2023-06-14 10:41:20.147803-0400  localhost kernel[0]: MRT[106] Corpse allowed 1 of 5
2023-06-14 10:41:20.554115-0400  localhost kernel[0]: EXC_RESOURCE -> MRT[106] exceeded mem limit: InactiveSoft 50 MB (non-fatal)
2023-06-14 10:41:20.582216-0400  localhost kernel[0]: Corpse released, count at 0
2023-06-14 10:41:21.457637-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup
2023-06-14 10:41:21.457653-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:21.654248-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:21.654846-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:25.173506-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> System Policy: mds(128) allow file-read-metadata /private/var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k/0/com.apple.nsurlsessiond
2023-06-14 10:41:25.555713-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:25.555942-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:27.689548-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup
2023-06-14 10:41:27.689557-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:27.900468-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:27.902250-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:31.778414-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:31.778607-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:33.889834-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup
2023-06-14 10:41:33.889850-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:34.093698-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: searchpartyd(318) deny(1) mach-lookup com.apple.timed.xpc
2023-06-14 10:41:34.096397-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:34.098027-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:37.895796-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:37.896107-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:40.165621-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup
2023-06-14 10:41:40.165669-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup com.apple.wifi.sharekit
—> 2023-06-14 10:41:40.198953-0400  localhost kernel[0]: (apfs) <apfs`log_debug> tx_flush:1170: disk4 xid 8417809 tx stats: # 40 finish 39 enter 229 wait 6 20916us close 739us flush 7831us
2023-06-14 10:41:40.377605-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:40.379358-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:44.177464-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:44.177708-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:46.291369-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup
2023-06-14 10:41:46.291380-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:46.503904-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:46.505552-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:50.342619-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:50.342794-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:50.346566-0400  localhost kernel[0]: uipc_accept: peer disconnected unp_gencnt 92
2023-06-14 10:41:52.462444-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup
2023-06-14 10:41:52.462463-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:52.674718-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:52.676523-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:55.005803-0400  localhost kernel[0]: uipc_accept: peer disconnected unp_gencnt 94
2023-06-14 10:41:56.549208-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:56.549449-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:58.662027-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup
2023-06-14 10:41:58.662043-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:58.873061-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:58.874740-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:42:02.753839-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) file-write-data /dev/io8log
2023-06-14 10:42:02.754104-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:42:04.865721-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup
2023-06-14 10:42:04.865732-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:42:05.069311-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:42:05.069814-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
—> 2023-06-14 10:42:05.086723-0400  localhost kernel[0]: (apfs) <apfs`log_debug> tx_flush:1170: disk4 xid 8417829 tx stats: # 60 finish 59 enter 161 wait 7 18271us close 492us flush 5541us
2023-06-14 10:42:08.649035-0400  localhost kernel[0]: busy timeout[0], (60s): 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface'

First delay is 22 seconds and the next is 25 seconds. It looks like something to do with WiFi but I do not know why. I have not changed my WiFi card and I have an Apple card installed and do not need any additional kexts (BCM94360CD).

 

I have attached my EFI to see if I have something incorrectly selected.  Any idea of where and how to track k this down? Thank you!

 

(Sorry if I have posted this in the wrong forum.)

EFI.zip

Link to comment
Share on other sites

40 minutes ago, pkdesign said:

Hopefully someone here can help me track down what is going on. There is a 47 second delay during boot which didn’t use to be there. I have indicated with an arrow the spots where there is a delay:

Timestamp                       (process)[PID]    
2023-06-14 10:41:18.335821-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_log_mount_unmount:1889: disk4s5 unmounting volume macOS, requested by: com.apple.MobileSoftwareUpdate. (pid 363); parent: launchd (pid 1)
2023-06-14 10:41:18.362743-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_unmount:2740: disk4s5 waiting for purgatory cleaner to finish
2023-06-14 10:41:18.389828-0400  localhost kernel[0]: (apfs) <apfs`log_info> authapfs_seal_restore:482: disk4s5 integrity protection will be re-enabled
2023-06-14 10:41:18.416521-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_unmount:3074: disk4 nx_num_vols_mounted is 5
2023-06-14 10:41:18.442801-0400  localhost kernel[0]: (apfs) <apfs`apfs_vfsop_unmount> apfs: total mem allocated: 83652394 (80 mb);
—> 2023-06-14 10:41:18.469864-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_unmount:3087: all done.  going home.  (numMountedAPFSVolumes 5)
2023-06-14 10:41:18.891137-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: systemstats(108) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:18.891332-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: systemstats(108) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:18.893537-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: systemstats(108) deny(1) mach-lookup com.apple.tccd.system
2023-06-14 10:41:19.324861-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> 1 duplicate report for Sandbox: systemstats(108) deny(1) mach-lookup com.apple.tccd.system
2023-06-14 10:41:19.324865-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(374) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:19.325028-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(374) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:19.855712-0400  localhost kernel[0]: uipc_accept: peer disconnected unp_gencnt 86
2023-06-14 10:41:20.147803-0400  localhost kernel[0]: MRT[106] Corpse allowed 1 of 5
2023-06-14 10:41:20.554115-0400  localhost kernel[0]: EXC_RESOURCE -> MRT[106] exceeded mem limit: InactiveSoft 50 MB (non-fatal)
2023-06-14 10:41:20.582216-0400  localhost kernel[0]: Corpse released, count at 0
2023-06-14 10:41:21.457637-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup
2023-06-14 10:41:21.457653-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:21.654248-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:21.654846-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:25.173506-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> System Policy: mds(128) allow file-read-metadata /private/var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k/0/com.apple.nsurlsessiond
2023-06-14 10:41:25.555713-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:25.555942-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(382) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:27.689548-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup
2023-06-14 10:41:27.689557-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:27.900468-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:27.902250-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:31.778414-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:31.778607-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(383) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:33.889834-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup
2023-06-14 10:41:33.889850-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:34.093698-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: searchpartyd(318) deny(1) mach-lookup com.apple.timed.xpc
2023-06-14 10:41:34.096397-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:34.098027-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:37.895796-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:37.896107-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(384) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:40.165621-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup
2023-06-14 10:41:40.165669-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup com.apple.wifi.sharekit
—> 2023-06-14 10:41:40.198953-0400  localhost kernel[0]: (apfs) <apfs`log_debug> tx_flush:1170: disk4 xid 8417809 tx stats: # 40 finish 39 enter 229 wait 6 20916us close 739us flush 7831us
2023-06-14 10:41:40.377605-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:40.379358-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:44.177464-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:44.177708-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(385) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:46.291369-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup
2023-06-14 10:41:46.291380-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:46.503904-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:46.505552-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:50.342619-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:50.342794-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(386) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:50.346566-0400  localhost kernel[0]: uipc_accept: peer disconnected unp_gencnt 92
2023-06-14 10:41:52.462444-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup
2023-06-14 10:41:52.462463-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:52.674718-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:52.676523-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:41:55.005803-0400  localhost kernel[0]: uipc_accept: peer disconnected unp_gencnt 94
2023-06-14 10:41:56.549208-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) file-write-data /dev/io8log
2023-06-14 10:41:56.549449-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(387) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:41:58.662027-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup
2023-06-14 10:41:58.662043-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:41:58.873061-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:41:58.874740-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
2023-06-14 10:42:02.753839-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) file-write-data /dev/io8log
2023-06-14 10:42:02.754104-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(388) deny(1) file-write-data /dev/io8logtemp
2023-06-14 10:42:04.865721-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup
2023-06-14 10:42:04.865732-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup com.apple.wifi.sharekit
2023-06-14 10:42:05.069311-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.beaconmanager
2023-06-14 10:42:05.069814-0400  localhost kernel[0]: (Sandbox) <Sandbox`log_kernel_report_summary> Sandbox: locationd(389) deny(1) mach-lookup com.apple.icloud.searchpartyuseragent.ownersession
—> 2023-06-14 10:42:05.086723-0400  localhost kernel[0]: (apfs) <apfs`log_debug> tx_flush:1170: disk4 xid 8417829 tx stats: # 60 finish 59 enter 161 wait 7 18271us close 492us flush 5541us
2023-06-14 10:42:08.649035-0400  localhost kernel[0]: busy timeout[0], (60s): 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface', 'IOHIDInterface'

First delay is 22 seconds and the next is 25 seconds. It looks like something to do with WiFi but I do not know why. I have not changed my WiFi card and I have an Apple card installed and do not need any additional kexts (BCM94360CD).

 

I have attached my EFI to see if I have something incorrectly selected.  Any idea of where and how to track k this down? Thank you!

 

(Sorry if I have posted this in the wrong forum.)

EFI.zip 6.33 MB · 4 downloads

 

 

I would suggest you to add the kexts, which previously were not needed in Broadcom, and add the correct parameters to the Kernel. As in the attached prints.

To me works with Ventura very nice and smooth. 

 

 

 

Captura de Tela 2023-06-30 às 14.44.36.png

Captura de Tela 2023-06-30 às 14.45.14.png

Link to comment
Share on other sites

14 hours ago, pkdesign said:

Hopefully someone here can help me track down what is going on. There is a 47 second delay during boot which didn’t use to be there. I have indicated with an arrow the spots where there is a delay:

First delay is 22 seconds and the next is 25 seconds. It looks like something to do with WiFi but I do not know why. I have not changed my WiFi card and I have an Apple card installed and do not need any additional kexts (BCM94360CD).

 

I have attached my EFI to see if I have something incorrectly selected.  Any idea of where and how to track k this down? Thank you!

 

@pkdesign There is two issues in your config.plist. But the second one, only because unserialized data, of course.

 

NOTE: This version of ocvalidate is only compatible with OpenCore version 0.9.4!


NVRAM->Add->7C436110-AB2A-4BBB-A880-FE41995C9F82->csr-active-config has illegal value!
CheckNvram returns 1 error!

PlatformInfo->Generic->SystemUUID is borked (Can only be empty, special string OEM or valid UUID)!
CheckPlatformInfo returns 1 error!

Completed validating /Users/mathieu/Downloads/EFI/OC/config.plist in 1 ms. Found 2 issues requiring attention.

"busy timeout[0], (60s): 'IOHIDInterface'"  could be related to Intel Bluetooth ? I'm not sure.

Edited by Matgen84
  • Like 1
Link to comment
Share on other sites

On 6/30/2023 at 1:47 PM, Max.1974 said:

I would suggest you to add the kexts, which previously were not needed in Broadcom, and add the correct parameters to the Kernel. As in the attached prints.

To me works with Ventura very nice and smooth.

I guess it can’t hurt to add these to see what happens. Again, the WiFi card I have is natively supported.

 

On 6/30/2023 at 1:39 PM, cankiulascmnfye said:

@pkdesign: "Tx" is related to wifi (transmit). Which OS? If it's Ventura 13.5b or Sonoma, then it's because Apple dropped the legacy 80211 family kext, so no more support for Cards with broadcom 4360 cards. 

My signature has which OS I use (Monterey).

 

21 hours ago, Matgen84 said:

 

@pkdesign There is two issues in your config.plist. But the second one, only because unserialized data, of course.

 

NOTE: This version of ocvalidate is only compatible with OpenCore version 0.9.4!


NVRAM->Add->7C436110-AB2A-4BBB-A880-FE41995C9F82->csr-active-config has illegal value!
CheckNvram returns 1 error!

PlatformInfo->Generic->SystemUUID is borked (Can only be empty, special string OEM or valid UUID)!
CheckPlatformInfo returns 1 error!

Completed validating /Users/mathieu/Downloads/EFI/OC/config.plist in 1 ms. Found 2 issues requiring attention.

"busy timeout[0], (60s): 'IOHIDInterface'"  could be related to Intel Bluetooth ? I'm not sure.

The CSR is set to work with TotalFinder and is correct for my set-up. I can try to set it to a normal value and see if that changes anything.

 

I have turned off the AORUS Pro's internal WiFi card in BIOS. Maybe it is still seeing it there? Has never been an issue until recently.

 

 

  • Like 2
Link to comment
Share on other sites

Not sure if this belongs here so forgive me if it does not.

I am going through the semi painful process of fixing my trackpads correctly and following dortania guide it says I can use the UEFI shell, so I used openshell that comes with OpenCore and ran acpidump.efi -b -n DSDT -z from my tools folder and it created 255 .dat files in my EFI folder.

Is this normal? I have renamed 2 of them to .aml as per the guide and they are identical.

Can I just delete the 254 duplicates?

This was performed on laptop 2 in my signature.

Edited by SavageAUS
Link to comment
Share on other sites

Are there any "tricks" to injecting DSDT.aml with the latest versions of Open Core?  Details below...

 

When I first used OpenCore (version 0.6.3), I used the edited DSDT.aml that I had been using with CLOVER.  My config.plist was as follows:

 

Injecting DSDT with Open Core

Spoiler

1541387235_Screenshot2023-07-04at8_49_49AM.png.21c66cfd5587d78165a3b55192c74d9a.png

 

I didn't need to drop / delete the original DSDT table, so I had no entries in the ACPI > Delete section of my OC 0.6.3 config.plist.

 

In the latest versions of OpenCore, can we still simply inject the edited DSDT via ACPI > Add (in config.plist) or do we need to also Delete the original DSDT?

 

Thank you.

Link to comment
Share on other sites

29 minutes ago, deeveedee said:

Are there any "tricks" to injecting DSDT.aml with the latest versions of Open Core?  Details below...

 

When I first used OpenCore (version 0.6.3), I used the edited DSDT.aml that I had been using with CLOVER.  My config.plist was as follows:

 

Injecting DSDT with Open Core

  Reveal hidden contents

1541387235_Screenshot2023-07-04at8_49_49AM.png.21c66cfd5587d78165a3b55192c74d9a.png

 

I didn't need to drop / delete the original DSDT table, so I had no entries in the ACPI > Delete section of my OC 0.6.3 config.plist.

 

In the latest versions of OpenCore, can we still simply inject the edited DSDT via ACPI > Add (in config.plist) or do we need to also Delete the original DSDT?

 

Thank you.

 

I never dropped the original DSDT. Do like this and open System DSDT on MaciASL.app. You'll see the injected DSDT.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

@Stefanalmare I never dropped it either.  I was just checking for @oSxFr33k who may want to use his DSDT with Open Core.  Thanks.

 

EDIT: See my comment here.

 

 

@oSxFr33k You may need ACPI > Quirks RebaseRegions and NormalizeHeaders (not sure if you need both).

Edited by deeveedee
  • Like 1
Link to comment
Share on other sites

51 minutes ago, deeveedee said:

@Stefanalmare I never dropped it either.  I was just checking for @oSxFr33k who may want to use his DSDT with Open Core.  Thanks.

 

EDIT: See my comment here.

 

 

@oSxFr33k You may need ACPI > Quirks RebaseRegions and NormalizeHeaders (not sure if you need both).


I have to go back to the huge general opencore thread or the documentation on OC but vit9696 mentions something regarding that it may not be a good idea to load a patched DSDT because in memory the unpatched DSDT is already being loaded or some pre-ACPI patching is done off the native DSDT or something in that regards, I don’t remember exact reason why to avoid it.  

Edited by oSxFr33k
Link to comment
Share on other sites

@oSxFr33k there may be issues, but you have two people here who have used DSDT with OC and the OC Sample.plist includes an example with ACPI > Add > DSDT.aml.  I think you should use your DSDT before attempting SSDT patches.  You can use your DSDT and then add SSDT patches (e.g., you can keep your NVidia patches in a separate SSDT if you want).

  • Like 2
Link to comment
Share on other sites

On 7/4/2023 at 5:43 PM, oSxFr33k said:


I have to go back to the huge general opencore thread or the documentation on OC but vit9696 mentions something regarding that it may not be a good idea to load a patched DSDT because in memory the unpatched DSDT is already being loaded or some pre-ACPI patching is done off the native DSDT or something in that regards, I don’t remember exact reason why to avoid it.  

It may be a bug of OpenCore because with Clover or Chameleon we injected custom DSDT.aml 15 years.

  • Like 1
Link to comment
Share on other sites

2 hours ago, Slice said:

It may be a bug of OpenCore because with Clover or Chameleon we injected custom DSDT.aml 15 years.

No bugs about that. Opencore just work nice with DSDT or SSDT. Fix regions is there too.

L37hKLn.png

  • Like 4
Link to comment
Share on other sites

On 7/16/2022 at 2:56 PM, antuneddu said:

@luky35 I understand that you have entered a custom entry, right ? Try like this

 

851212829_Screenshot2022-07-16alle19_53_40.thumb.png.210852f0c2fa81b657cddd60affe7a1f.png

 

It should load the Win icon

 

1642890087_Screenshot2022-07-16alle20_05_46.png.ae69a4b26ad734f746b697d0f64aaaff.png

 

 

Antuneddu, good morning!

 

 

Sorry to bother again, but could you make Manjaro icon for this theme?

 

Thanks. 

Link to comment
Share on other sites

×
×
  • Create New...