Jump to content

josh anderson

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

1 Neutral
  1. https://drive.google.com/file/d/1VCwDgdErdYMj_njX5Z2dSXVmmMtwHOfU/view?usp=sharing, https://drive.google.com/file/d/1nvayc3wPIL1WVx85OGrQCdGY4E0a9ocB/view?usp=sharing, https://drive.google.com/file/d/1qNa7Bom09n0kUFAjb-hj-ZJiVVg6ytct/view?usp=sharing Hi MaLd0n, thanks for your reply. I’m attaching: - My EFI folder - An IOREG captured WITHOUT Broadcom kexts loaded Unfortunately, I cannot provide an IOREG with Broadcom enabled because the system never reaches the desktop. As soon as AirportBrcmFixup.kext (even alone) is loaded, the boot stalls at: IOKit daemon stall (60s): "pxsx" So the IOREG I’m providing is from a successful boot without any Broadcom kexts. Please let me know if this is sufficient to analyze the PCI / PXSX issue on this HP Pavilion. Thanks in advance for your time.
  2. Hi MaLd0n, thanks for the reply. Just to clarify, I’m already using BlueToolFixup.kext, BrcmFirmwareData.kext and BrcmPatchRAM3.kext, with the correct loading order, as detailed in my post. I’ve also tested fresh downloads from official Acidanthera releases. The issue is not Bluetooth-related. The system stalls with “IOKit daemon stall (60s) ‘pxsx’” even when only AirportBrcmFixup.kext is loaded, with no BT kexts at all. Without any Broadcom kexts, the system boots perfectly. This points to a PXSX / PCI bridge initialization issue on this HP Pavilion when Broadcom kexts are present, rather than missing or misconfigured Bluetooth kexts. If you’ve seen a similar pxsx stall on HP hardware or have insight into a PCI/ACPI-level workaround, I’d really appreciate your input. Thanks.
  3. Hey everyone, I'm dealing with a persistent IOKit daemon stall issue on my HP Pavilion 14 al-001la with BCM94352Z WiFi/Bluetooth card running macOS Monterey. I've exhausted almost every solution I can find and need help. **Hardware:** - HP Pavilion 14 al-001la laptop - BCM94352Z WiFi/Bluetooth card - macOS Monterey **The Issue:** System boots perfectly without WiFi/BT kexts, but stalls at "iokit daemon stall (60s) 'pxsx'" when I add Broadcom kexts. This happens even with just the WiFi kext (AirportBrcmFixup.kext) - no Bluetooth kexts needed. **Everything I've Tried:** ### USB Port Mapping: - ✅ USB port mapping with Hackintool (system boots fine without kexts) - ✅ Disabled XhciPortLimit in config.plist [1](#44-0) - ✅ Removed all Hackintool-generated SSDTs, kept only essential ones (SSDT-PLUG, SSDT-EC-USBX) ### HP-Specific Configuration: - ✅ Added HP-specific quirks: UnblockFsConnect and LapicKernelPanic [2](#44-1) - ✅ Set DisableIoMapper: YES [3](#44-2) ### Boot Arguments Tested: - ✅ npci=0x2000 - ✅ npci=0x3000 - ✅ dart=0 - ✅ -wegnoegpu -igfxnotelemetryload - ✅ Various combinations of the above ### Kext Configuration: - ✅ Proper loading order for BCM94352Z in Monterey [4](#44-3) : 1. Lilu.kext (first) 2. BrcmFirmwareData.kext 3. BrcmPatchRAM3.kext 4. AirportBrcmFixup.kext 5. BlueToolFixup.kext [5](#44-4) ### ACPI Solutions: - ✅ Created SSDT-PXSX-OFF.aml to disable the problematic device: ```asl DefinitionBlock ("", "SSDT", 2, "OC", "PXSXOFF", 0x00000000) { External (_SB_.PCI0.PXSX, DeviceObj) Scope (_SB_.PCI0.PXSX) { Method (_STA, 0, NotSerialized) { Return (Zero) } } } Additional Notes: ✅ System boots perfectly without any Broadcom kexts ✅ Issue occurs with just AirportBrcmFixup.kext (no Bluetooth kexts needed) ✅ Tried fresh kext downloads from official acidanthera releases ✅ Above 4G Decoding not available in HP BIOS (tried npci workarounds) The Problem: The "pxsx" device appears to be an internal PCI bridge that macOS can't initialize when Broadcom kexts are loaded. This seems to be a hardware-specific conflict between my HP Pavilion's PCI configuration and the BCM94352Z card. What I Need: Has anyone encountered this specific "pxsx" stall issue with HP hardware and Broadcom cards? Are there any other solutions I haven't tried? Could this be a fundamental incompatibility between my HP Pavilion's PCI layout and the BCM94352Z? Any help would be greatly appreciated. I'm at the point where I might need to consider a different WiFi card or wait for kext updates. Thanks in advance!
×
×
  • Create New...