Kernel panik when activating IntelBTPatcher.kext on SEQUOIA > Bluetooth higher 5.1 #486
Comments
|
problem confirmed but I am personally fine with the bluetooth on sequoia without the use of this kext. (intel 8260) I believe that just disabling this kext will do the trick |
|
Sorry, but BT 5.3 need this Kext. |
|
try this configuration: IntelBluetoothFirmware.kext |
Check this README. |
|
I have the same issue. Do you know the solution? |
anonymous-writer
changed the title
|
Thanks for the answers. |
anonymous-writer
changed the title
How long has it been since you last read the IntelBTPatcher README? |
|
There is clearly written "Do not use it on Monterey". Which certainly means beginning from Monterey do not use this kext. It would be really great if only those who have experience with Intel and Bluetooth higher than 5.1 answered in this post. |
|
BlueToolFixup.kext.zip but add nvram setting bluetoothExternalDongleFailed DATA 00 bluetoothInternalControllerInfo DATA 0000000000000000000000000000
|
|
@Lorys89 , I don't need this: I only use the start parameter: When created from your source code, the kext doesn't work for me. For whatever reason. |
Use this |
This one worked. But apparently it doesn't work again on Beta 2. |
I follow your instruction and bluetooth can be turn on but failed to discover. Is there an order for sort these kext? |
|
Thanks so much mate! Now bluetooth works flawless in Sequoia Beta 2 with Intel AX201. |
I tried this kext but don't work on my Intel AX200, can you explain wich kext did you use and if nvram setting is mandatory. |
|
Thanks. Works again on beta 2. Have to perform NVRAM Clear to make it work too. |
I add these kexts with order like the images below, IntelBluetoothFirmware, IntelBTPatcher and BlueToolFixup i got from Lorys89 and add two NVRAM follow Lorys89's instruction |
|
Worked on one device,
|
|
tested |
|
Yep. panic(cpu 2 caller 0xffffff801ff0b314): IOGMD: not wired for the IODMACommand @IOMemoryDescriptor.cpp:3248
Panicked task 0xffffff905870dd60: 201 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff9058723b30, Frame : Return Address
0xffffffa0cc5e7530 : 0xffffff801f75bd51 mach_kernel : _handle_debugger_trap + 0x4c1
0xffffffa0cc5e7580 : 0xffffff801f8c8b3c mach_kernel : _kdp_i386_trap + 0x11c
0xffffffa0cc5e75c0 : 0xffffff801f8b81bb mach_kernel : _kernel_trap + 0x48b
0xffffffa0cc5e7680 : 0xffffff801f6f1971 mach_kernel : _return_from_trap + 0xc1
0xffffffa0cc5e76a0 : 0xffffff801f75c047 mach_kernel : _DebuggerTrapWithState + 0x67
0xffffffa0cc5e77a0 : 0xffffff801f75b6e2 mach_kernel : _panic_trap_to_debugger + 0x1e2
0xffffffa0cc5e7810 : 0xffffff801ffd37d8 mach_kernel : _panic + 0x81
0xffffffa0cc5e7900 : 0xffffff801ff0b314 mach_kernel : __ZNK25IOGeneralMemoryDescriptor19dmaCommandOperationEjPvj + 0x894
0xffffffa0cc5e7970 : 0xffffff801ff0b5e1 mach_kernel : __ZN25IOGeneralMemoryDescriptor18getPhysicalSegmentEyPyj + 0x291
0xffffffa0cc5e7a50 : 0xffffff801ff0731c mach_kernel : __ZN18IOMemoryDescriptor9readBytesEyPvy + 0xfc
0xffffffa0cc5e7ab0 : 0xffffff802365992e com.zxystd.IntelBTPatcher : __ZL17asyncIOCompletionPvS_ij + 0x55
0xffffffa0cc5e7b00 : 0xffffff80220663e9 com.apple.iokit.IOUSBHostFamily : __ZN17AppleUSBIORequest8completeEv + 0xff1
0xffffffa0cc5e7cf0 : 0xffffff802117ad3b com.apple.driver.usb.AppleUSBCommon : __ZN24AppleUSBRequestCompleter20completeRequestQueueEP11queue_entry + 0x469
0xffffffa0cc5e7ef0 : 0xffffff802117a8b4 com.apple.driver.usb.AppleUSBCommon : __ZN24AppleUSBRequestCompleter12checkForWorkEv + 0x132
0xffffffa0cc5e7f20 : 0xffffff801fef6b0e mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x13e
0xffffffa0cc5e7f60 : 0xffffff801fef6146 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffffa0cc5e7fa0 : 0xffffff801f6f119e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.driver.usb.AppleUSBCommon(1.0)[066E3BA0-D5FC-3355-A355-BD6E44833135]@0xffffff8021178000->0xffffff802117bfff
com.apple.iokit.IOUSBHostFamily(1.2)[A7025865-1246-3750-8AC9-9F9410682BCC]@0xffffff8022014000->0xffffff8022088fff
dependency: com.apple.driver.AppleBusPowerController(1.0)[27641E32-63A0-37ED-B1F7-326703B80BA4]@0xffffff8020b51000->0xffffff8020b54fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A0274F23-311D-30DC-8C78-0BF4109AD475]@0xffffff8020e67000->0xffffff8020ea0fff
dependency: com.apple.driver.AppleSMC(3.1.9)[4364B20F-0128-324C-AC42-FC3382C9784A]@0xffffff8020f59000->0xffffff8020f72fff
dependency: com.apple.driver.usb.AppleUSBCommon(1.0)[066E3BA0-D5FC-3355-A355-BD6E44833135]@0xffffff8021178000->0xffffff802117bfff
dependency: com.apple.driver.AppleUSBHostMergeProperties(1.2)[E25ABE12-F5BF-36EC-B326-EF93B6C57C40]@0xffffff80220e7000->0xffffff80220e7fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[5CCDA23F-974B-36FE-991B-F492F97C7C90]@0xffffff802177c000->0xffffff802177dfff
com.zxystd.IntelBTPatcher(2.5)[B4EA6DBC-E3C8-317A-B35F-6907682E6485]@0xffffff8023658000->0xffffff8023661fff
dependency: as.vit9696.Lilu(1.6.8)[A4396287-D274-3C4A-B816-67B9F9022E01]@0xffffff80232c6000->0xffffff802334dfff
dependency: com.apple.iokit.IOUSBHostFamily(1.2)[A7025865-1246-3750-8AC9-9F9410682BCC]@0xffffff8022014000->0xffffff8022088fff
Process name corresponding to current thread (0xffffff9058723b30): kernel_task
Boot args: revpatch=sbvmm keepsyms=1 agdpmod=pikera debug=0x100 -revbeta -alcbeta
Mac OS version:
24A5309e
Kernel version:
Darwin Kernel Version 24.0.0: Wed Jul 31 21:46:13 PDT 2024; root:xnu-11215.0.199.501.2~1\/RELEASE_X86_64
Kernel UUID: 881546EF-0391-38D6-8C65-E3C0F28EA3BB
roots installed: 0
KernelCache slide: 0x000000001f400000
KernelCache base: 0xffffff801f600000
Kernel slide: 0x000000001f4e4000
Kernel text base: 0xffffff801f6e4000
__HIB text base: 0xffffff801f500000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 18602640201
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000000454cdc5e5
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001c9de283d1 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff80576d3000 - 0xffffffa0576d3000
. PGZ : 0xffffff80576d3000 - 0xffffff80596d4000
. VM : 0xffffff80596d4000 - 0xffffff8525ed3000
. RO : 0xffffff8525ed3000 - 0xffffff86bf6d3000
. GEN0 : 0xffffff86bf6d3000 - 0xffffff8b8bed3000
. GEN1 : 0xffffff8b8bed3000 - 0xffffff90586d3000
. GEN2 : 0xffffff90586d3000 - 0xffffff9524ed3000
. GEN3 : 0xffffff9524ed3000 - 0xffffff99f16d3000
. DATA : 0xffffff99f16d3000 - 0xffffffa0576d3000
Metadata: 0xffffffa0a0dfb000 - 0xffffffa0c0dfb000
Bitmaps : 0xffffffa0c0dfb000 - 0xffffffa0c3dfb000
Extra : 0 - 0 |
|
Seems to be on specific devices, works for me on Intel BE200 and AX210 (I think that was the 6E one anyways) both vPro variants. The older one (also cnvi) seems to have the issue. I added the anyaddr boot-arg, and the variables with the 0's before using the updated kext on all machines. |
Do you know why my Logitech Craft keyboard will not connect? I used your kexts to get bluetooth working again on the 15.1 dev beta, and everything else connects okay - but not the craft keyboard. I saw some posts a while back about the MX series of keyboards having issues with the paring step, but didn't seem to help me. I'm wondering if the Craft has it's own circumstances. I can't imagine it could be THAT different from the MX since they're basically the same keyboard |
15.0 Beta3～8 IntelBTPatcher.kext Kernel panik |
|
Fix that works on my Intel AX-210 (non vPro) on 15.0 stable |
|
|
|
Works for me too! Thanks :) |
I'm still having an issue getting my MX keys/Logitech Craft connected, even using these kexts. Did you use them together with @Lorys89 BlueToolFixup.kext? Could you post your EFI? @plooshi I'm also using the AX211, not the AX210. I figured they would work the same, but is there something I need to do to make my card work with your kexts? |
@plooshi should I download and test the artifact from here https://github.com/plooshi/IntelBluetoothFirmware/actions/runs/12435770165 |
they should work fine. i'm on an ax210 with upstream intelbluetoothfirmware & bluetoolfixup, only thing changed is intelbtpatcher. also the ax211 is also just the cnvi version of the ax210, so it's basically the same shipset just w/ some of the stuff moved to the PCH |
yes |
|
use intelbluetoothfirmware & intelbtpatcher from my build, and latest bluetoolfixup release |
Gave it a go. Still no dice. In fact, it kept auto-disabling my bluetooth every 30 seconds or so, and I had to keep toggling it back on. When I try to connect the Logitech Craft keyboard, after trying to connect it shows up like this: It shows that it's 'connected', but it's still in the nearby devices list, and it's not actually connected in reality. Also, just to clarify, should I be using IntelBluetoothInjector.kext or not? I tried with both with & without and it made no difference. I read somewhere that it should be in the kexts folder but disabled in the config file, so it's always been like that. Here is my EFI folder, if you wanna take a look and see if there's another issue i'm doing wrong: |
having same issue with xbox wireless controller. going to take a look. |
|
i reversed a check, whoopsie |
Still same thing. 'Fake' connects. What are the changes? I'm also resetting NVRAM between booting when I change the kexts. |
looks like it's some issue with it sending extra zero packets for some reason, i'll look into it |
|
it's still sending extra packets even on the older version. hmm. |
|
IntelBTPatcher.kext.zip |
|
silly pods: yeah it seems it can connect BLE devices fine (idk why airpods are ble but aight, xbox controllers just hate pairing with anything from my experience) |
@plooshi I used this build instead of the release build in the intelwireless repo and I was able to connect a Logitech Wave Keys keyboard via Bluetooth which previously did not work (I was able to only connect a K380 keyboard via Bluetooth which is a smaller KB). Thanks a lot for tweaking the kext. |
enjoy! |
|
looks like the airpods case does BLE, makes sense |
Still doesn't seem to want to work :(
|
no idea, might be sum with the device. does it connect in other oses? |
Yeah - it connects to the same build/mobo but when booted in Windows 11, but not in MacOS. Interestingly, it does connect to my M1 Macbook Pro running the same version (15.1.1) of Sequoia. It also never connected to any previous version of MacOS via bluetooth on this build, so it's defintely an issue with my EFI I think. |
|
could be |
https://github.com/plooshi/IntelBluetoothFirmware/actions/runs/12448046467 can you try this build? |
|
only kext updated is intelbluetoothfirmware, show system information & see if you can connect |
Tried this build, it's the same still unfortunately. It sees it, attemps to connect but can't. I noticed when connecting to other devices, when connecting there is a pop up window that has a code to type in on the keyboard to complete the connection. This seems to be where it hangs when trying to connect. Could there be something from preventing the pairing code from generating? |
i think that's only used on some bluetooth devices to do encryption, and i might know why |
https://github.com/plooshi/IntelBluetoothFirmware/actions/runs/12449520285 try this |
Same outcome :( |
no idea, could be the device. sorry :( |
Thanks for trying anyhow |
and others
Have you read the docs?
Yes
macOS Version
macOS 15
Kext Version
v2.4.0
Wireless Adapter Model and USB Product ID
Intel AX-210
Description
Kernel panik when activating IntelBTPatcher.kext. Panic attached.
Info in System Report - Bluetooth
Relevant log output
Kernel Panic Logs
The text was updated successfully, but these errors were encountered: