[Release] macOS Sequoia 15.0

chris1111 · October 10, 2024

53 minutes ago, anullpointerexception said:
Good evening,

I'm not sure if this is the correct thread for my issue, so I apologize if it's not.
I successfully updated my second Hackintosh to macOS Sequoia, and everything is working perfectly except for one issue: Bluetooth.

I’ve updated all my kexts to the latest versions, but for some reason, I can't activate Bluetooth. Under macOS Sonoma, I used earlier versions of the same kexts without any issues, but on Sequoia, Bluetooth just won't turn on. If I enable it, the toggle stays on for a few seconds and then switches to "Disabled" again.

This is what
 log show --last boot | grep -i brcm
shows:
2024-10-10 20:41:38.313039+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.lvs1974.AirportBrcmFixup
2024-10-10 20:41:38.313131+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.lvs1974.AirportBrcmFixup) in helper to process load notification
2024-10-10 20:41:38.313537+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.acidanthera.BrcmFirmwareStore
2024-10-10 20:41:38.313626+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.acidanthera.BrcmFirmwareStore) in helper to process load notification
2024-10-10 20:41:38.315757+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: com.apple.driver.AirPort.BrcmNIC
2024-10-10 20:41:38.315828+0200 0x3d2      Default     0x0                  120    0    kernelmanagerd: Received kext load notification: as.acidanthera.BrcmPatchRAM3
2024-10-10 20:41:38.315914+0200 0x892      Error       0x0                  309    0    kernelmanager_helper: Could not process load notification in helper: Could not find: Did not find identifier (as.acidanthera.BrcmPatchRAM3) in helper to process load notification
I did add the following kexts for Bluetooth:

bluetoothExternalDongleFailed and bluetoothInternalControllerInfo is also set.

Port Mapping is also done:

IOReg:

Any insights or suggestions would be greatly appreciated! Thanks in advance

If you use a dongle USB Bluetooth you need only BlueToolFixup.kext disable other bluetooth kext

anullpointerexception · October 11, 2024

10 hours ago, chris1111 said:

If you use a dongle USB Bluetooth you need only BlueToolFixup.kext disable other bluetooth kext

I am using a Dell DW1830 NGFF WiFi-Card installed in the Wi-Fi slot on my Motherboard. I don‘t know why its not working, I did install Sonoma yesterday on a spare SSD for testing purposes and Bluetooth and WiFi are working perfectly fine under Sonoma.

Edited October 11, 2024 by anullpointerexception

Max.1974 · October 11, 2024

Are you using Dual Boot with Windows ? Maybe firmware injection incompatíble with macOS. Are try reset nvram?

Maybe you should try this command

sudo pkill bluetoothd

And check AirPort kexts if you really need all this 3 versions.

I saw your usb internal ports. Its seems you not need all of them mapping internal.

Check your plist XHCI Port limit is enable and try extract with Hackintool kext under usbmap and them replace it with usbports and SSDTs.

Add device fake ID properties too with compatible for your DW1830.

Use device native number id

Need use too acpi wake your devices xhci

I think you need check here.

Broadcom fix

Edited October 11, 2024 by Max.1974

XanthraX · October 11, 2024

It worked normal for me, but not incremental. Had to download about 14G. Not disabled any kext.

deeveedee · October 11, 2024

On my HackMini8,1 booting Sequoia 15.1 Beta with OC 1.0.2, Microsoft Remote Desktop (now "Windows App") still has connectivity issues over Ethernet that can be resolved by setting Ethernet to "Inactive" and then back to "Active." Sequoia 15.0.1 (Release) does not have this issue. My hack's details are as follows:

HP EliteDesk 800 G4 Mini with Radeon RX 560x dGPU (Ethernet: Intel i219LM)
Open Core 1.0.2, IntelMausi.kext 1.0.7
SMBIOS macMini8,1
Windows App (MS Remote Desktop) v11.0.5 (2401)

deeveedee · October 11, 2024

@anullpointerexception Very nice screenshots. Unfortunately, not helpful (for me). I would recommend always posting your EFI when asking for help.

Just a guess since there's not enough information to diagnose - depending on the version of BluetoolFixup.kext that you are using, you may need a Beta boot arg (either use -btlfxbeta or -lilubetaall). Do you need a beta boot arg? You can tell if BluetoolFixup.kext is working properly by looking at System Report and confirming that Bluetooth Chipset is reported as "THIRD_PARTY_DONGLE."

Screenshot2024-10-11at7_48_59AM.png.5e78466c9616ded279ffe0b102e006d8.png

Again, you'll get a lot better support if you post your EFI. If it's too big to post, post only the OC/config.plist and OC/Kexts. If still too big, post your EFI to external storage and provide a link. Less screen shots, more EFI.

EDIT: If you determine that the beta boot-arg fixes your problem, you can upgrade to the latest BluetoolFixup.kext 2.6.9 (available in Acidanthera's BrcmPatchRAM package) which natively supports Sequoia without the beta boot-arg.

Edited October 11, 2024 by deeveedee

chris1111 · October 11, 2024

6 hours ago, anullpointerexception said:

I am using a Dell DW1830 NGFF WiFi-Card installed in the Wi-Fi slot on my Motherboard. I don‘t know why its not working, I did install Sonoma yesterday on a spare SSD for testing purposes and Bluetooth and WiFi are working perfectly fine under Sonoma.

OK you have a Mini PCI

Did you try a Reset NVRAM from Opencore

deeveedee · October 11, 2024

@chris1111 Forgive me for my laugh emoji on your last post. I thought you were joking. My mistake.

anullpointerexception · October 12, 2024

Thank you guys for your suggestions, I tried everything but Bluetooth still doesn't work.

Here is a Google Drive Link for my current EFI. https://drive.google.com/file/d/1_MOVpa52eBXMWJZnGlMSKWdrFm76LiMG/view?usp=sharing

All kexts are already updated, that was the first thing I checked before creating my post:

On 10/10/2024 at 9:03 PM, anullpointerexception said:

I’ve updated all my kexts to the latest versions

I don't really know what is happening tbh.
The logs are really interesting:

Wall Clock adjustment detected - results might be strange while using --end
2024-10-10 21:29:55.365096+0200 0xed12     Activity    0x729db              1916   0    bluetoothd: (libsystem_info.dylib) Membership API: translate identifier
2024-10-10 21:29:55.365530+0200 0xed12     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] XpcMBFrameworkConnection connectionID:38 name:<private> accessLevel:2
2024-10-10 21:29:55.365533+0200 0xed12     Default     0x0                  1916   0    bluetoothd: (libxpc.dylib) [com.apple.xpc:connection] [0x7fea6d825850] activating connection: mach=false listener=false peer=true name=com.apple.server.bluetooth.general.xpc.peer[158].0x7fea6d825850
2024-10-10 21:29:55.365598+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdSessionAttach" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.365610+0200 0xed12     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] BTSessionMsgHandler::handleAttachMsg name:<private>
2024-10-10 21:29:55.365619+0200 0xed12     Error       0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Failed to retrieve signing ID. ManagedConfigOverride state is false.
2024-10-10 21:29:55.365630+0200 0xed12     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Sending 'session attached' event for session "com.apple.WindowServer-MBF-158-38-unique-id-HIDRemoteAACPServer"
2024-10-10 21:29:55.365636+0200 0xed12     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Attached session for "com.apple.WindowServer-MBF-158-38-unique-id-HIDRemoteAACPServer" with session: 0x7fea6dd13980, session handle: 0xfc6b0000
2024-10-10 21:29:55.365639+0200 0xed12     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Sending the reply now sessionID:fc6b0000 result:0
2024-10-10 21:29:55.365653+0200 0xed12     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Done sending the reply now
2024-10-10 21:29:55.365655+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdSessionAttach" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.365741+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdAccessoryGetDefaultMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.365756+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Adding handle-identifier mapping for handle : 0xfc6b0001 	 with pid "158", pidVersion "100000" for session com.apple.WindowServer-MBF-158-38-unique-id-HIDRemoteAACPServer
2024-10-10 21:29:55.365767+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdAccessoryGetDefaultMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.365831+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdAccessoryAddCallbacksMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.365851+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdAccessoryAddCallbacksMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.365949+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdDeviceServiceAddCallbacksMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.365974+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdDeviceServiceAddCallbacksMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.366048+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdLocalDeviceGetDefaultMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.366062+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Adding handle-identifier mapping for handle : 0xfc6b0002 	 with pid "158", pidVersion "100000" for session com.apple.WindowServer-MBF-158-38-unique-id-HIDRemoteAACPServer
2024-10-10 21:29:55.366074+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdLocalDeviceGetDefaultMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.366161+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdLocalDeviceGetConnectedDevicesMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:55.366186+0200 0xed12     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdLocalDeviceGetConnectedDevicesMsg" from session "com.apple.WindowServer-MBF-158-38"
2024-10-10 21:29:56.508403+0200 0xed12     Default     0x0                  1916   0    bluetoothd: (libxpc.dylib) [com.apple.xpc:connection] [0x7fea6dc232a0] activating connection: mach=false listener=false peer=true name=com.apple.bluetooth.xpc.peer[549].0x7fea6dc232a0
2024-10-10 21:29:56.508424+0200 0xed12     Info        0x0                  1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] XPC connection start: audioaccessoryd:549
2024-10-10 21:29:56.508654+0200 0xed12     Default     0x0                  1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] UpdateIdentities: 0 total
2024-10-10 21:29:56.508659+0200 0xed12     Default     0x0                  1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonServer] UpdateIdentities: 0 mapped, 0 total
2024-10-10 21:29:56.508661+0200 0xed12     Default     0x0                  1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonServer] Identities re-evaluate: Identities SA 0 / Other 0 / Devices 0
2024-10-10 21:29:56.508728+0200 0xed12     Default     0x0                  1916   0    bluetoothd: (libxpc.dylib) [com.apple.xpc:connection] [0x7fea6dc232a0] invalidated because the client process (pid 549) either cancelled the connection or exited
2024-10-10 21:29:56.508745+0200 0xed12     Info        0x0                  1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] XPC connection ended: audioaccessoryd:549
2024-10-10 21:29:59.997256+0200 0xed12     Default     0x0                  1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager] SPLocalBeaconManager periodic action dispatch timer fired
2024-10-10 21:29:59.997262+0200 0xed12     Activity    0x729dc              1916   0    bluetoothd: (SPOwner) SPLocalBeaconManager: timerFired
2024-10-10 21:29:59.997263+0200 0xed12     Default     0x729dc              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager] SPLocalBeaconManager periodic action timer fired
2024-10-10 21:29:59.997274+0200 0xed12     Activity    0x729dd              1916   0    bluetoothd: (SPOwner) SPLocalBeaconManager: notifyBeaconingKeysChangedBlockWithCompletion:
2024-10-10 21:29:59.997278+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager] SPLocalBeaconManager: SPI: -[SPLocalBeaconManager notifyBeaconingKeysChangedBlockWithCompletion:]_block_invoke
2024-10-10 21:29:59.997402+0200 0xed4d     Info        0x0                  1916   0    bluetoothd: (CoreAnalytics) [com.apple.CoreAnalytics:client] Dropping "com.apple.security.LegacyAPICounts" as it isn't used in any transform (not in the config or budgeted?)
2024-10-10 21:29:59.998024+0200 0xed4d     Info        0x0                  1916   0    bluetoothd: (CoreAnalytics) [com.apple.CoreAnalytics:client] Dropping "com.apple.security.LegacyAPICounts" as it isn't used in any transform (not in the config or budgeted?)
2024-10-10 21:29:59.998115+0200 0xed12     Error       0x729dd              1916   0    bluetoothd: (IOKit) IOPMAssertionCreateWithProperties: io_pm_assertion_create failed with error 0xe00002c1
2024-10-10 21:29:59.998122+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:powerManagement] IOPMAssertionCreateWithProperties <private> failed with error: (-536870207)
2024-10-10 21:30:00.024824+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager] Calling beaconingKeyChangedBlock with 5 .nearOwner keys.
2024-10-10 21:30:00.025394+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager]   key: <private> (2024-10-10T19:30:00Z - 2024-10-10T19:45:00Z)
2024-10-10 21:30:00.025873+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager]   key: <private> (2024-10-10T19:45:00Z - 2024-10-10T20:00:00Z)
2024-10-10 21:30:00.026343+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager]   key: <private> (2024-10-10T20:00:00Z - 2024-10-10T20:15:00Z)
2024-10-10 21:30:00.026814+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager]   key: <private> (2024-10-10T20:15:00Z - 2024-10-10T20:30:00Z)
2024-10-10 21:30:00.027283+0200 0xed12     Default     0x729dd              1916   0    bluetoothd: (SPOwner) [com.apple.icloud.SPOwner:beaconManager]   key: <private> (2024-10-10T20:30:00Z - 2024-10-10T20:45:00Z)
2024-10-10 21:30:00.027284+0200 0xed12     Activity    0x729de              1916   0    bluetoothd: (SPOwner) SPLocalBeaconManager: Calling beaconingKeyChangedBlockWithCompletion
2024-10-10 21:30:00.027286+0200 0xed12     Default     0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] WPDSearchPartyAgent beaconManager keys updated: 5 keys
2024-10-10 21:30:00.027339+0200 0xed12     Default     0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] WPDSearchPartyAgent beacon key updated to {length = 6, bytes = 0xede8eb6f79cb}
2024-10-10 21:30:00.027349+0200 0xed12     Default     0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] ObjectDiscovery Start advertising for process bluetoothd (1916) of type 18 with advertising interval 3200 (2000.00 ms)
2024-10-10 21:30:00.027358+0200 0xed4d     Default     0x729dd              1916   0    bluetoothd: (FMCoreLite) [com.apple.icloud.FMCore:XPCActivity] <FMXPCActivity: 0x7fea7980fcd0>: updateCriteria called on FMXPCActivity
2024-10-10 21:30:00.027364+0200 0xed12     Default     0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] ObjectDiscovery updated advertising options: <private>
2024-10-10 21:30:00.027387+0200 0xed12     Default     0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] ObjectDiscovery advertising data has changed: YES
2024-10-10 21:30:00.027388+0200 0xed12     Error       0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] ObjectDiscovery -[WPDObjectDiscoveryManager updateAdvertiser] updated with error: Trying to update advertiser but peripheral manager isn't powered on
2024-10-10 21:30:00.027391+0200 0xed12     Error       0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] Trying to update advertiser but peripheral manager isn't powered on
2024-10-10 21:30:00.027397+0200 0xed4d     Default     0x729dd              1916   0    bluetoothd: (FMCoreLite) [com.apple.icloud.FMCore:XPCActivity] <FMXPCActivity: 0x7fea7980fcd0>: Keeping existing criteria for: [priority: 0 repeating: 1 delay: 5 grace: 1800 interval: 3600, options: 0x201]
2024-10-10 21:30:00.027421+0200 0xed12     Error       0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] ObjectDiscovery Advertising failed to start with error: Error Domain=WPErrorDomain Code=26 "Trying to update advertiser but peripheral manager isn't powered on" UserInfo={NSLocalizedDescription=Trying to update advertiser but peripheral manager isn't powered on}
2024-10-10 21:30:00.027423+0200 0xed12     Error       0x729de              1916   0    bluetoothd: (WPDaemon) [com.apple.bluetooth:WirelessProximity] Advertising failed to start for client <private> type 18 with error: Trying to update advertiser but peripheral manager isn't powered on
2024-10-10 21:30:05.452788+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Security] Closed device database
2024-10-10 21:30:07.135656+0200 0xedd1     Activity    0x729df              1916   0    bluetoothd: (libsystem_info.dylib) Membership API: translate identifier
2024-10-10 21:30:07.136106+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] XpcMBFrameworkConnection connectionID:39 name:<private> accessLevel:1
2024-10-10 21:30:07.136110+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: (libxpc.dylib) [com.apple.xpc:connection] [0x7fea798063b0] activating connection: mach=false listener=false peer=true name=com.apple.server.bluetooth.general.xpc.peer[520].0x7fea798063b0
2024-10-10 21:30:07.136161+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdSessionAttach" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.136172+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] BTSessionMsgHandler::handleAttachMsg name:<private>
2024-10-10 21:30:07.136180+0200 0xedd1     Error       0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Failed to retrieve signing ID. ManagedConfigOverride state is false.
2024-10-10 21:30:07.136190+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Sending 'session attached' event for session "com.apple.coreservices.useractivityd-MBF-520-39-unique-id-userActivityBTStatus"
2024-10-10 21:30:07.136215+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Attached session for "com.apple.coreservices.useractivityd-MBF-520-39-unique-id-userActivityBTStatus" with session: 0x7fea6cf2e410, session handle: 0x5d1b0000
2024-10-10 21:30:07.136223+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Sending the reply now sessionID:5d1b0000 result:0
2024-10-10 21:30:07.136233+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Done sending the reply now
2024-10-10 21:30:07.136234+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdSessionAttach" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.136343+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdLocalDeviceGetDefaultMsg" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.136379+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Adding handle-identifier mapping for handle : 0x5d1b0001 	 with pid "520", pidVersion "100002" for session com.apple.coreservices.useractivityd-MBF-520-39-unique-id-userActivityBTStatus
2024-10-10 21:30:07.136445+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdLocalDeviceGetDefaultMsg" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.136539+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdLocalDeviceAddCallbacksMsg" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.136552+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdLocalDeviceAddCallbacksMsg" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.136670+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Received MBFramework XPC message "kCBMsgIdLocalDeviceMaskCallbacks" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.136680+0200 0xedd1     Default     0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Local device event mask fffffdfe for handle : 0x5d1b0001 	 for session com.apple.coreservices.useractivityd-MBF-520-39-unique-id-userActivityBTStatus
2024-10-10 21:30:07.136692+0200 0xedd1     Info        0x0                  1916   0    bluetoothd: [com.apple.bluetooth:Server.XPC] Handled MBFramework XPC message "kCBMsgIdLocalDeviceMaskCallbacks" from session "com.apple.coreservices.useractivityd-MBF-520-39"
2024-10-10 21:30:07.213000+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] ModifyControllerSettings: CBControllerSettings, dsSt On, hwAE Yes, rssi -60, saKB Yes, saPD Yes, spSP Yes
2024-10-10 21:30:07.213026+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Sending 'session attached' event for session "com.apple.BluetoothSettings-0x74500001"
2024-10-10 21:30:07.213031+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Attached session for "com.apple.BluetoothSettings-0x74500001" with session: 0x7fea6d90f540, session handle: 0xb9ae0000
2024-10-10 21:30:07.213036+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBStackController] AddDiscoverableController: com.apple.BluetoothSettings-0x74500001
2024-10-10 21:30:07.213037+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Session "com.apple.BluetoothSettings-0x74500001" wants discoverability on
2024-10-10 21:30:07.213042+0200 0xedd1     Error       0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Ignoring discoverability change request as stack is not running
2024-10-10 21:30:07.213049+0200 0xedd1     Error       0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBStackController] ### addDiscoverableController failed
2024-10-10 21:30:07.213050+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Detach session: 0x7fea6d90f540, session handle: 0xb9ae0000
2024-10-10 21:30:07.213050+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Sending 'session detached' event for session "com.apple.BluetoothSettings-0x74500001"
2024-10-10 21:30:07.213053+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Session "com.apple.BluetoothSettings-0x74500001" wants discoverability off
2024-10-10 21:30:07.213053+0200 0xedd1     Error       0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Ignoring discoverability change request as stack is not running
2024-10-10 21:30:07.213071+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Erasing session 0x7fea6d90f540 from SessionMap for "com.apple.BluetoothSettings-0x74500001"
2024-10-10 21:30:07.213104+0200 0xedd1     Error       0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] ### ModifyControllerSettings failed: BT_ERROR_STACK_NOT_READY 'setDiscoverable failed'
2024-10-10 21:30:07.213159+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDiscovery] CBDiscovery, CID 0x74500002, DsFl 0x6082000A00000 < Connections Pairing ActiveScan Attributes BLEHID ClassicScan > changed: discoveryFlags: 0x2080000A00000 < Connections Pairing Attributes BLEHID > -> 0x6082000A00000 < Connections Pairing ActiveScan Attributes BLEHID ClassicScan >
2024-10-10 21:30:07.213177+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] Discovery Update: CBDiscovery, CID 0x74500002, DsFl 0x6082000A00000 < Connections Pairing ActiveScan Attributes BLEHID ClassicScan >, from Bluetooth:983
2024-10-10 21:30:07.213183+0200 0xedd1     Info        0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBMetricsDaemon] Metrics event report: CBDiscovery, appID com.apple.BluetoothSettings, action updt, PID 983, CID 0x74500002. count 15, dropped 0
2024-10-10 21:30:08.396194+0200 0xedd1     Default     0x6ed26              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] SetPowerState: PoweredOn
2024-10-10 21:30:08.396199+0200 0xedd1     Default     0x6ed26              1916   0    bluetoothd: [com.apple.bluetooth:Server.Core] Write default power state : 1
2024-10-10 21:30:09.330482+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDiscovery] CBDiscovery, CID 0x74500002, DsFl 0x2080000A00000 < Connections Pairing Attributes BLEHID > changed: discoveryFlags: 0x6082000A00000 < Connections Pairing ActiveScan Attributes BLEHID ClassicScan > -> 0x2080000A00000 < Connections Pairing Attributes BLEHID >
2024-10-10 21:30:09.330482+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDiscovery] CBDiscovery, CID 0x74500002, DsFl 0x2080000A00000 < Connections Pairing Attributes BLEHID > changed: discoveryFlags: 0x6082000A00000 < Connections Pairing ActiveScan Attributes BLEHID ClassicScan > -> 0x2080000A00000 < Connections Pairing Attributes BLEHID >
2024-10-10 21:30:09.330507+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] Discovery Update: CBDiscovery, CID 0x74500002, DsFl 0x2080000A00000 < Connections Pairing Attributes BLEHID >, from Bluetooth:983
2024-10-10 21:30:09.330507+0200 0xedd1     Default     0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBDaemonXPCConnection] Discovery Update: CBDiscovery, CID 0x74500002, DsFl 0x2080000A00000 < Connections Pairing Attributes BLEHID >, from Bluetooth:983
2024-10-10 21:30:09.330513+0200 0xedd1     Info        0x1d8da              1916   0    bluetoothd: (CoreUtils) [com.apple.bluetooth:CBMetricsDaemon] Metrics event report: CBDiscovery, appID com.apple.BluetoothSettings, action updt, PID 983, CID 0x74500002. count 16, dropped 0

Because this line:

[com.apple.bluetooth:CBDaemonXPCConnection] SetPowerState: PoweredOn

...should trigger the activation of Bluetooth, no?

But also:

Advertising failed to start with error: Error Domain=WPErrorDomain Code=26 "Trying to update advertiser but peripheral manager isn't powered on"

[com.apple.bluetooth:Server.Core] Ignoring discoverability change request as stack is not running

...indicate that the Bluetooth stack was not fully initialized.

Edited October 12, 2024 by anullpointerexception

bluenote56 · October 12, 2024

On 10/7/2024 at 11:25 AM, eSaF said:

Hi, I did say the EFI I posted for you was vanilla where you would have to construct further for your own preferences by adding or deleting.

On another note, I don't doubt in the slightest about your cooking skills which I am sure by the sound of it, is more proficient and tastier than your Hack skills.

Don't give up, you'll get there in the end.

GitHub - https://github.com/topics/hackintosh?o=desc&s=updated - has some examples of your machine specs with working EFI Folders that you can try to see if it can better your situation.

Good luck.

Update. Thanks to your advices I could successfully fix my Sonoma build with VDA decoder fully supported (630 headless). All apps work but Prime video which plays older movies and stalls on newer and then gives an error (???) but it's not a crucial issue. I can work with Skype.

Unfortunately it remains unknown to me why Sequoia doesn't boot without the "amfi get of my way" and therefore many Apps don't even start but I'll work on it.

Thanks

deeveedee · October 12, 2024

3 hours ago, anullpointerexception said:

Thank you guys for your suggestions, I tried everything but Bluetooth still doesn't work.

Here is a Google Drive Link for my current EFI. https://drive.google.com/file/d/1_MOVpa52eBXMWJZnGlMSKWdrFm76LiMG/view?usp=sharing

All kexts are already updated, that was the first thing I checked before creating my post:

EDIT3: @anullpointerexception See my next post.

Please get the latest BluetoolFixup.kext from here or add boot-arg ~~-btlfxbeta~~ -lilubetaall and test again. Also, while this isn't your problem, you should add bluetoothExternalDongleFailed and bluetoothInternalControllerInfo to NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82 in your config.plist.

It appears to me as though you retrieved your BluetoolFixup.kext 2.6.9 as a Beta version prior to the Sequoia update. This can be resolved by getting the release version of Bluetoolfixup.kext or adding the Beta boot-arg.

EDIT: @anullpointerexception I checked Lilu.kext and see that you are still using Lilu.kext 1.6.8. The latest release here is 1.6.9. This could also be a problem for you, since Lilu-dependent kexts may need the latest Lilu.kext for Sequoia. Please check your kexts again.

EDIT2: This is why I'm a broken record about asking people to post their EFIs. In many cases, screenshots are not sufficient for diagnosis and debugging.

Edited October 12, 2024 by deeveedee

deeveedee · October 12, 2024

3 hours ago, anullpointerexception said:

All kexts are already updated, that was the first thing I checked before creating my post:

What method do you use to confirm that you are using the latest kexts? If the link that you posted actually has your current EFI, then your kexts are not the latest.

By checking just the version number, you can see that your kexts are not updated. But even then, it is not sufficient to check only the version number in your case, because you have Beta versions of kexts where the version number has been incremented before changes were complete and released.

You also need to check the create dates of your kexts. If you are going to test with beta versions of kexts (perfectly ok), then you need to do much better record keeping to be sure that you update to release versions when they are available. I checked your EFI and see the following kexts that need to be updated. You should do a thorough check, since I may have missed some.

AirportBrcmFixup.kext
AppleALC.kext
BlueToolFixup.kext
BrcmFirmwareData.kext
BrcmPatchRAM3.kext
CPUFriend.kext
WhateverGreen.kext
VirtualSMC.kext (and its sensor kexts)
Lilu.kext
RestrictEvents.kext

If you don't want to update your kexts for some reason, then at the very least, you need to test with -lilubetaall boot-arg.

EDIT: @anullpointerexception I added RestrictEvents.kext to my list above. You should still check to be sure I didn't miss one.

EDIT2: @anullpointerexception One last thing and then I'll shut-up... When you upgrade to Open Core 1.0.2 (or any new version of OC), check your config.plist with ocvalidate (in OpenCore/Utilities/ocvalidate). In your case, you'll need to add "UEFI > Unload (Type: Array)" to your config.plist for OC 1.0.2.

Edited October 12, 2024 by deeveedee

anullpointerexception · October 12, 2024

@deeveedee

Thank you for your detailed explanation of what to check. I accidentally uploaded my old EFI to Google Drive; it seems I hadn't had enough coffee on Thursday when I was zipping and uploading that config.

I've now uploaded the latest version to Google Drive and double-checked that I'm using the latest versions of my kexts. I also upgraded to OC 1.0.2 and did an NVRAM reset. After double-checking everything, the issue with Bluetooth not turning on still remains. :wallbash:

deeveedee · October 12, 2024

@anullpointerexception I spent a lot of time reviewing the wrong EFI. I'm out of time. Good luck with this.

EDIT: @anullpointerexception That was a lot of wasted time. Drink more coffee and make sure you're actually booting from the EFI that you think you are. If you have multiple EFI's installed in your hack, that would be another place to check. I don't have any more time to spend on further reviews of this.

Edited October 12, 2024 by deeveedee

Mac Hosehead · October 12, 2024

38 minutes ago, anullpointerexception said:

After double-checking everything, the issue with Bluetooth not turning on still remains

I got tired of seeming to have to fix bluetooth after every update. I got a Broadcom BCM94360NG card and it has bluetooth with no additional kexts. I also have a Intel wireless card for WiFi and I don't have to root-patch after updates. The Broadcom card works for WiFi if I boot Ventura.

Max.1974 · October 12, 2024

56 minutos atrás, anullpointerexception disse:

@deeveedee

Obrigado por sua explicação detalhada sobre o que verificar. Eu acidentalmente carreguei meu EFI antigo no Google Drive; parece que eu não tinha tomado café suficiente na quinta-feira, quando estava compactando e enviando essa configuração.

Agora carreguei a versão mais recente no Google Drive e verifiquei novamente se estou usando as versões mais recentes dos meus kexts. Eu também atualizei para o OC 1.0.2 e fiz uma redefinição da NVRAM. Depois de verificar tudo novamente, o problema com o Bluetooth não ligando ainda permanece.

Check your XHCI Controller if you have this compatible:

PciRoot(0x0)/Pci(0x14,0x0) and PciRoot(0x0)/Pci(0x17,0x0)

(extract with Hackintool)

And try use this:

USBFIX_SLEEP por Max.1974.zip

Spoiler

bluenote56 · October 12, 2024

5 hours ago, eSaF said:

Try the AMFI.kext in the kext folder instead of the boot-arg "amfi get of my way".

Don't use both together. Insure you use the latest AMFI.kext version.

Another boot-arg you should have if you have the RestrictEvent.kext is this 'revpatch=sbvmm'.

All changes you make, reboot and clean NvRAM after. Good luck.

Well, updating the AMFI.kext to latest, without the boot arg "amfi_ etc etc" did the work. I could boot Sequoia and the Apps now work. I have an issue with pdfs and mails going black but, you know, my old good Inno3d 780 is actually "really old " and OCLP people are already making miracles with obsolete GPUs.

Anyway Insanelymac is amazing. It reminds me when I was busy testing Krell, McIntosh, Phase Linear, Conrad Johnson for the magazine. A great lab with brainstorming all around the world and noone gives up. Concerning the brainstorming I'm temporarily out at the pub.

Thanks again

Edited October 12, 2024 by bluenote56

hardcorehenry · October 13, 2024

I have Sonoma installed on different partition and it shows update available Sequoia 15.0.1. On Sequoia 15.0 (24A335) shows my Mac is up to date. Any ideas?

Spoiler

Screenshot2024-10-13at2_17_20PM.png.da3c4f109d059abb6570b190fee1eb0b.png

miliuco · October 13, 2024

@hardcorehenry

I see that you are not logged in to your Apple account. The other systems get updates notification without logged in to Apple account? This seems to be a requisite in Sequoia.

Edited October 13, 2024 by miliuco
Wrong target user

Mac Hosehead · October 13, 2024

2 hours ago, miliuco said:

This seems to be a requisite in Sequoia.

I have not logged in to my Apple account since the Sequoia install and I get nagged to log in if I restart. Yet, a few days ago I got a window asking me if I wanted to restart now or later to apply an update. I chose to restart now and it made the update to 15.0.1 which it seems that it had already downloaded. I am used to installs where incremental updates would fail and the way to do it was to download the full version. This is better I guess.

I don't know how Apple decides to roll out updates.

Slice · October 14, 2024

On 10/13/2024 at 3:19 PM, hardcorehenry said:

I have Sonoma installed on different partition and it shows update available Sequoia 15.0.1. On Sequoia 15.0 (24A335) shows my Mac is up to date. Any ideas?

Reveal hidden contents

In Sonoma to get update you can set SMBIOS as iMac19,1 or MacBookPro15,2 while on Sequoia there is no chance to do the same.

So you have to use RestrictEvents.kext or use Clover.

hardcorehenry · October 14, 2024

1 hour ago, Slice said:

In Sonoma to get update you can set SMBIOS as iMac19,1 or MacBookPro15,2 while on Sequoia there is no chance to do the same.

So you have to use RestrictEvents.kext or use Clover.

Thanks for the suggestion, I already have RestrictEvents.kext(CPU naming stuff), I wasn’t aware I’d also need revpatch=sbvmm, anyway very fast update, tomorrow testing.

Spoiler

Screenshot2024-10-14at7_20_57PM.png.b38e51e7e3b09f9a8550a35b75b8feb0.png

Edited October 14, 2024 by hardcorehenry

LockDown · October 15, 2024

7 hours ago, Slice said:

In Sonoma to get update you can set SMBIOS as iMac19,1 or MacBookPro15,2 while on Sequoia there is no chance to do the same.

So you have to use RestrictEvents.kext or use Clover.

You mean you can't get incremental update with 19.1 in sequoia without revpatch=sbvbmm?

I have no problem getting incremental even without the flag with 19,1

XanthraX · October 15, 2024

If you have SIP off, in order to use Broadcom WIFIs, you are not notified about a new Softare update coming. You have to check yourself the System Prefs > General > Software Update.

hardcorehenry · October 15, 2024

I have/had SIP on, Sequoia 15.0 was installed very recently, so I believe update 15.0.1 would eventually appear, the fact is that after adding revpatch=sbvmm(reboot) Software Update “found” it immediately.

Edited October 15, 2024 by hardcorehenry

[Release] macOS Sequoia 15.0

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites