josh anderson

Progress: I stopped using only voodoops2 because my PC uses an I2C HID mouse, so I installed the voodooRMI and voodooi2c kexts. Now it sleeps properly and the trackpad quality has improved dramatically, but the system takes up to 8 minutes to boot, which is incredibly slow. Is there anything I can do? In verbose mode, it often gets stuck on something like "Iokit daemon stall (60): "pxsx". Please help, Mald0n! Thanks!! <3

Thanks for the quick reply, MaLd0n! Regarding PS2Controller: I am currently using the latest Acidanthera release (v2.3.8). Do you recommend switching to an older/specific version, or is there an ACPI patch/SSDT fix I should apply to prevent it from blocking powerd during sleep? Regarding the boot-args: These are the ones I currently have: alcid=13 -igfxdvmt -igfxsklaskbl brcmfx-driver=2 -amfipassbeta revpatch=sbvmm (Note: I am using -igfxsklaskbl to spoof my HD 520 Skylake graphics as Kaby Lake since Tahoe dropped native Skylake support). Which specific boot-args should I remove or change to clean up my config for this build? Thank you so much for your guidance!

Hello community! I've recently been experiencing a kernel panic when putting my laptop to sleep, and it seems to happen right after using OCLP-Plus, but I'm not sure. The problem is that when I put my Mac to sleep, if I open it later, I see a black screen, and it shows no signs of life whatsoever. (I have to force-shut down the motherboard using the power button for 10 seconds.) When macOS wakes up, it gives me this log: panic(cpu 0 caller 0xffffff800658f05d): thread_invoke: preemption_level 1, possible cause: blocking while holding a spinlock, or within interrupt context @sched_prim.c:3033 Panicked task 0xffffffa44f7e89a0: 5 threads: pid 108: powerd Backtrace (CPU 0), panicked thread: 0xffffffa91d921a68, Frame : Return Address 0xffffffc527a2c860 : 0xffffff8006558c61 0xffffffc527a2c8b0 : 0xffffff80066e49e2 0xffffffc527a2c8f0 : 0xffffff80066d3c98 0xffffffc527a2c9b0 : 0xffffff80064eb971 0xffffffc527a2c9d0 : 0xffffff8006559037 0xffffffc527a2cad0 : 0xffffff80065586c9 0xffffffc527a2cc40 : 0xffffff8006d9de8d 0xffffffc527a2cd30 : 0xffffff800658f05d 0xffffffc527a2cda0 : 0xffffff800658d4d0 0xffffffc527a2cdf0 : 0xffffff8006570a7b 0xffffffc527a2ce50 : 0xffffff800657086e 0xffffffc527a2ce70 : 0xffffff8006c8add9 0xffffffc527a2ce90 : 0xffffff800b455ba7 0xffffffc527a2ced0 : 0xffffff800b37bfe5 0xffffffc527a2cf10 : 0xffffff800772c1f5 0xffffffc527a2cf50 : 0xffffff80076741b2 0xffffffc527a2cf60 : 0xffffff800767d041 0xffffffc527a2cf80 : 0xffffff80066d327f 0xffffffc527a2cfe0 : 0xffffff80064eba9a 0xffffff8bed268b10 : 0xffffff8006c1933e 0xffffff8bed268b50 : 0xffffff8006c1dc88 0xffffff8bed268b90 : 0xffffff8006c8a77f 0xffffff8bed268bd0 : 0xffffff8006c909df 0xffffff8bed268c10 : 0xffffff8007ea6971 0xffffff8bed268c30 : 0xffffff8006cc5dfe 0xffffff8bed268c70 : 0xffffff8007ea69e4 0xffffff8bed268c90 : 0xffffff8006d0626d 0xffffff8bed268cc0 : 0xffffff8006682ff9 0xffffff8bed268ce0 : 0xffffff80065339ce 0xffffff8bed268d90 : 0xffffff80065479b7 0xffffff8bed268de0 : 0xffffff800654817f 0xffffff8bed268ee0 : 0xffffff80066b82e4 0xffffff8bed268fa0 : 0xffffff80064ebdd6 Kernel Extensions in backtrace: com.apple.driver.AppleACPIPlatform(6.1)[7A63549B-7274-331A-A663-41F0F8A918B0]@0xffffff800766d000->0xffffff80076e4fff dependency: com.apple.driver.AppleSMC(3.1.9)[9DE99343-1BE8-3D5A-B66D-888F7DDB866C]@0xffffff8007e5f000->0xffffff8007e78fff dependency: com.apple.iokit.IOACPIFamily(1.4)[05E5F769-5948-3540-A59F-5AC2E89C8600]@0xffffff8008690000->0xffffff8008691fff dependency: com.apple.iokit.IOPCIFamily(2.9)[D78D4F4D-377D-3B33-A576-D3D6BC090C01]@0xffffff8008bd8000->0xffffff8008c2bfff com.apple.driver.AppleAPIC(1.7)[5625BF8C-71D7-3F05-976A-55EBB4078135]@0xffffff800772b000->0xffffff800772cfff dependency: com.apple.iokit.IOPCIFamily(2.9)[D78D4F4D-377D-3B33-A576-D3D6BC090C01]@0xffffff8008bd8000->0xffffff8008c2bfff as.acidanthera.voodoo.driver.PS2Controller(2.3.8)[AD57755B-578F-330B-BC04-E4DA3948BCC9]@0xffffff800b379000->0xffffff800b390fff dependency: com.apple.iokit.IOACPIFamily(1.4)[05E5F769-5948-3540-A59F-5AC2E89C8600]@0xffffff8008690000->0xffffff8008691fff com.apple.driver.AppleSmartBatteryManager(161.0)[6929CEE6-BF48-3A83-A647-3AE2EBDEFCFD]@0xffffff8007e8f000->0xffffff8007eacfff dependency: com.apple.driver.AppleSMC(3.1.9)[9DE99343-1BE8-3D5A-B66D-888F7DDB866C]@0xffffff8007e5f000->0xffffff8007e78fff dependency: com.apple.iokit.IOACPIFamily(1.4)[05E5F769-5948-3540-A59F-5AC2E89C8600]@0xffffff8008690000->0xffffff8008691fff dependency: com.apple.iokit.IOSMBusFamily(1.1)[4FC7A2D0-E249-3883-A1DA-9E5D62F4DC5D]@0xffffff8008d19000->0xffffff8008d1afff as.acidanthera.voodoo.driver.PS2Trackpad(2.3.8)[B9AA4F88-F52F-37AB-B46E-98465B2099A1]@0xffffff800b447000->0xffffff800b46afff dependency: as.acidanthera.voodoo.driver.PS2Controller(2.3.8)[AD57755B-578F-330B-BC04-E4DA3948BCC9]@0xffffff800b379000->0xffffff800b390fff dependency: com.apple.iokit.IOHIDFamily(2.0.0)[2814B105-22A3-3DE2-BB54-E9CC1D380575]@0xffffff80087ea000->0xffffff8008864fff Process name corresponding to current thread (0xffffffa91d921a68): powerd Boot args: alcid=13 -igfxdvmt -igfxsklaskbl brcmfx-driver=2 -amfipassbeta revpatch=sbvmm Mac OS version: 25F71 Kernel version: Darwin Kernel Version 25.5.0: Mon Apr 27 20:31:18 PDT 2026; root:xnu-12377.121.6~2/RELEASE_X86_64 Kernel UUID: AB956DA9-C0C4-3C62-B5AD-5D3FCCB651A3 roots installed: 0 KernelCache slide: 0x0000000006200000 KernelCache base: 0xffffff8006400000 Kernel slide: 0x00000000062e8000 Kernel text base: 0xffffff80064e8000 __HIB text base: 0xffffff8006300000 System model name: MacBookPro16,2 (Mac-5F9802EFE386AA28) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 167499862474563 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000985719cd8737 Sleep : 0x000098563a08e240 0x0000000044fc674e 0x0000984a6a2a38cb Wake : 0x0000985641e0591e 0x000000004534c26a 0x000098563a8c8d66 Compressor Info: 2% of compressed pages limit (OK) and 9% of segments limit (OK) with 1 swapfiles and OK swap space Zone info: Zone map: 0xffffff991c7e8000 - 0xffffffb91c7e8000 . VM : 0xffffff991c7e8000 - 0xffffff9de94b4000 . RO : 0xffffff9de94b4000 - 0xffffff9f82e58000 . GEN0 : 0xffffff9f82e58000 - 0xffffffa44fb24000 . GEN1 : 0xffffffa44fb24000 - 0xffffffa91c7f0000 . GEN2 : 0xffffffa91c7f0000 - 0xffffffade94bc000 . DATA : 0xffffffb2b6188000 - 0xffffffb91c7e8000 Metadata: 0xffffff8beda18000 - 0xffffff8c0da18000 Bitmaps : 0xffffff8c0da18000 - 0xffffff8c0fe18000 Extra : 0 - 0 . GEN3 : 0xffffffade94bc000 - 0xffffffb2b6188000 That's what it shows when I restart my laptop. I've attached the latest OpenCore log I have, it's from a few days ago, and my IOregistry in case that helps. I'm considering using your new tool I saw today, DMI DECODE HARDWARE; it's worth trying: OP LOG AND IOREGISTRY.zip If someone could help me identify the problem, I would really appreciate it. I'm used to going to sleep with my laptop asleep so that the next day I can simply open the lid and continue from where I left off. Lately, it happens every time I put my laptop to sleep, not every two days like it used to. Thanks!! <3

any advance??

Hi MaLd0n, I have another question regarding Bluetooth stability. I’m currently using a BCM94352Z and the Bluetooth experience is very poor. This is what macOS reports: Controller: Address: 18:4F:32:F4:4C:52 State: On Chipset: THIRD_PARTY_DONGLE Firmware Version: v8718 c5876 Transport: UART The main problem is real-world usage: I have to stay within ~1 meter or devices disconnect Frequent audio cuts and instability Very unreliable with AirPods and headsets It’s basically unusable for daily use. Because of this, I’m considering switching to Intel AX210. In your experience: How stable is Bluetooth on AX210 in macOS Tahoe? Is it good enough for daily use (headphones, audio, etc.)? What is the best setup for AX210 on Tahoe (kexts, config, etc.)? My goal is stable WiFi + Bluetooth without using OCLP. Thanks.

Hi MaLd0n, I’m looking for a WiFi/Bluetooth card recommendation for macOS Tahoe (26). My priorities are: Maximum stability on Tahoe No OCLP or root patches (I want full SIP and SecureBoot enabled) Best possible Bluetooth performance for daily use I don’t care about AirDrop, Continuity or any Apple ecosystem features. From what I’ve researched, AirportItlwm doesn’t work on Tahoe and only itlwm + HeliPort is usable (GitHub), so I’m considering Intel cards like AX210. In your experience: Which card is currently the most stable on Tahoe without OCLP? Is AX210 still the best option, or is there something better now? Which setup gives the most stable Bluetooth for daily usage? Thanks.

Hi, I have a technical question regarding Intel AX210 compatibility on modern macOS versions. I’m currently using a BCM94352Z, but it has become increasingly unstable on macOS Sequoia, and I’m planning to upgrade to macOS Tahoe. Because of this, I’m considering switching to an Intel AX210 for better long-term stability. I’d like to clarify a few points: Is the Intel AX210 fully functional on macOS Tahoe (26) using AirportItlwm? Is the boot argument -ibtcompatbeta strictly required for Bluetooth on Tahoe? How stable is Bluetooth with IntelBluetoothFirmware in daily use? Between AirportItlwm and itlwm + HeliPort, which setup is currently more reliable on Tahoe? Are there any major limitations (e.g., AirDrop, Handoff, Continuity features) when using AX210 on these newer macOS versions? My main goal is achieving stable and consistent WiFi + Bluetooth performance for daily usage. Thanks in advance.

Someone? help!

HP Pavilion 14 AL001LA – Intel i5-6200U – Sequoia Test Update macOS Version: Sequoia (not Monterey) Graphics: Intel HD 520 (Kaby Lake simulation applied, 00001B59) HDMI / DisplayPort Tests: IORegistryExplorer shows: AppleIntelFramebuffer@0 → connector type: 02 00 00 00, display pipe: 00 00 00 00 AppleIntelFramebuffer@1 → connector type: 08 00 00 00, display pipe: ff ff 00 00 AppleIntelFramebuffer@2 → connector type: 04 00 00 00, display pipe: ff ff 00 00 Manual framebuffer patches applied (pipe / bus / type / flags) following Dortania / WEG guide: framebuffer-patch-enable: 01000000 framebuffer-con1-enable: 01000000 framebuffer-con1-index: 01000000 framebuffer-con1-busid: 01000000 framebuffer-con1-pipe: 01000000 framebuffer-con1-type: 08000000 framebuffer-con1-flags: 00000000 framebuffer-con2-enable: 01000000 framebuffer-con2-index: 02000000 framebuffer-con2-busid: 02000000 framebuffer-con2-pipe: 02000000 framebuffer-con2-type: 04000000 framebuffer-con2-flags: 00000000 Result: HDMI still shows pipe ff ff 00 00; no signal on monitor. LSPCON / HDMI 2.0 compatibility not verified; likely required if using HDMI 2.0. Suggested next step: Confirm if this laptop uses LSPCON for HDMI 2.0. If yes, try: enable-lspcon-support: 01000000 framebuffer-con1-has-lspcon: 01000000 framebuffer-con1-preferred-lspcon-mode: 01000000 Bluetooth Status (Sequoia): Chipset: Third-Party Dongle (BCM20702A0) Driver: AppleUSBXHCISPTLP Address: 18:4F:32:F4:4C:52 Firmware: v8718 c5876 Maximum range: <3 meters Connected devices: AirPods Pro 2, TG-184 headphones Transport: UART Manufacturer ID: 0x004C (Apple) USB Devices: USB 3.0 Bus – PCI IDs: 0x9d2f / 0x0021 / Vendor: 0x8086 Bluetooth Adapter BCM20702A0 – Vendor 0x0a5c / Product 0x6417 – Integrated – Max 12 Mb/s HP Wide Vision HD Camera – Vendor 0x04f2 / Product 0xb56d – Integrated – Max 480 Mb/s USB Receiver – Vendor/Product 0x1919 – Max 12 Mb/s Notes / Observations: macOS Sequoia requires Kaby Lake spoofing for proper graphics support. HDMI channel assignment fails even after applying patches; likely due to HD 520 + Kaby Lake framebuffer layout mismatch. Bluetooth works but has very limited range (<3 meters), much worse than on Ventura. AirPods disconnect quickly, AirDrop partially works. Wi-Fi restored successfully via OCLP + BCM94352Z patch. All USB devices are detected and powered correctly. Questions for the community: Does anyone know if HP Pavilion 14 AL001LA uses LSPCON for HDMI 2.0 output? Any suggestions to fix HDMI pipe assignment on Sequoia? Is there a recommended fix for the extremely limited Bluetooth range in Sequoia? Thanks for the reply. I checked my framebuffer connectors in IORegistryExplorer. My connectors appear as: Framebuffer@0 → eDP → connector-type <02000000> → pipe <00000000> Framebuffer@1 → HDMI → connector-type <00080000> → pipe Framebuffer@2 → DP → connector-type <00040000> → pipe Internal display works correctly but HDMI does not output signal. It looks like HDMI and DP connectors are not getting a valid pipe assignment. Is this likely a framebuffer layout mismatch for Skylake HD520 on macOS Sequoia? Help me mald0n. i use this pc for my school and work 😭

Thanks for the reply. I checked my framebuffer connectors in IORegistryExplorer. My connectors appear as: Framebuffer@0 → eDP → connector-type <02000000> → pipe <00000000> Framebuffer@1 → HDMI → connector-type <00080000> → pipe Framebuffer@2 → DP → connector-type <00040000> → pipe Internal display works correctly but HDMI does not output signal. It looks like HDMI and DP connectors are not getting a valid pipe assignment. Is this likely a framebuffer layout mismatch for Skylake HD520 on macOS Sequoia?

Hi! As I mentioned in a previous post about macOS Tahoe, I said in my last message that I had created an EFI for macOS Sequoia and would use OCLP to restore Wi-Fi (since my BCM94352z chipset is the only limiting factor for macOS Sequoia, and thanks to OCLP it's fixed). The problem is that now I don't have HDMI working, and I need it because I use a second monitor and a TV. I study and work with my Hackintosh and enjoy streaming occasionally, but with this problem, I haven't been able to use the other monitors. The root patch with OCLP was successful, and I have Wi-Fi, but when I modify anything in my EFI, I lose Wi-Fi immediately and have to patch again and reset NVRAM in OpenCore Booter. I've tried different bootargs and adding the FRAMEBUFFER PATCHES to NVRAM, but I still haven't been able to enable HDMI. Another problem I have is that before, with macOS Ventura, Bluetooth had a much better range of up to 10 meters. (AirPods Pro 2) but now it's ridiculously worse. After taking two steps away from my laptop, the Bluetooth becomes unreliable, and on the third step, the AirPods disconnect. AirDrop only works partially; I can receive from my iPhone to my laptop, but when I send, no devices appear (which I desperately need, and the AirPods too). If anyone else has this problem, please help! I need to be productive again. Thanks!

I created an EFI for macOS Sequoia using the BCM94352Z Wi-Fi/Bluetooth card. I also prepared a USB drive with all the required resources (OCLP installer, kexts, and tutorials) to apply the root patch after installation. Before proceeding with the installation, I wanted to share my EFI and IOREG files so someone with more experience could review them and tell me if everything looks correct or if there is anything I should fix or improve. For now, I plan to stay on macOS Sequoia and wait at least 6 months before considering an update to macOS Tahoe. I am currently downloading macOS Sequoia 15.7.4 (24G517). Any advice or feedback would be greatly appreciated. EFI + IOREG: https://drive.google.com/drive/folders/1ogQ21ClR87YahY-3rF1ze-K2HycTk6Tn

Hello, im in macOS ventura an i want to update to the newest version of macos, but i my unic limitation is this that is only support natively in macos ventura an - can i install macos tahoe with this card? what configurations i will need? and, if i not can install tahoe, how i will install sequoia with this card?

What WiFi card do you recommend for my laptop with an NGFF M.2 Key A/E slot to have native WiFi and Bluetooth support in macOS Sequoia and Tahoe, including full Continuity (AirDrop, Handoff, AirPlay, etc.)? If there is no fully compatible card for my port type, would you recommend using an adapter instead? Please recommend me the best option, MaLd0n 🙏

I have a question regarding the BCM94352Z on macOS Sequoia. Since official support was removed after Ventura, I understand that OCLP root patches are commonly used to restore WiFi functionality. However, I would like to know if it is possible to use AppleBCMWLANCompanion.kext with VT-d enabled in order to avoid applying root patches. Is there a way to inject the proper Device ID and use AppleBCMWLANCompanion.kext (with AirportBrcmFixup if needed) so that WiFi works without relying on root patches? The goal is to keep the system as close to stock as possible and simplify future updates. Has anyone successfully achieved this configuration on Sequoia? Any clarification or guidance would be greatly appreciated. Thank you.