Atheros Bluetooth: IOath3kfrmwr.kext: Not Working (AR3011)

[RehabMan]

That's the strange part - even when I install my backed-up/original IOUSBHostFamily.kext, it's the same issue.

Must be an invalid backup or other changes you've made to /S/L/E.

I'll try again tonight and if it still doesn't work, I'll make a separate port injector kext for my USB issues and do a reinstall.

You can restore kexts by running the installer without erasing the partition.

When in doubt, fresh install to erased partition.

 

[Rytz]

Must be an invalid backup or other changes you've made to /S/L/E.
You can restore kexts by running the installer without erasing the partition.
When in doubt, fresh install to erased partition.

Thanks RehabMan. I'll post my results tonight.

I ordered the Broadcom PCIe for grins. I'm going to try it out either way. Only $20 on Amazon. Maybe I'll get better WiFi / Bluetooth connections.

 

[Rytz]

Did a reinstall of Capitan Beta 8 (not reformatted). Looks like EHCI kexts are loading which is good:

rytzs-MacBook-Pro:~ rytz$ sudo touch /System/Library/Extensions && sudo kextcache -u /
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext toledaARPT.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBXHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOUSBHostFamily.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IOath3kfrmwr.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext HDAEnabler3.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIDebug.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBacklight.kext

rytzs-MacBook-Pro:~ rytz$ kextstat | grep HCI
   42    1 0xffffff7f8130a000 0x3f000    0x3f000    com.apple.driver.usb.AppleUSBXHCI (1.0.1) 4403E9E6-6C93-3156-8B64-EC9CCDCA4BBC <41 11 7 5 4 3 1>
   43    0 0xffffff7f8134f000 0x19000    0x19000    com.apple.driver.usb.AppleUSBXHCIPCI (1.0.1) 0C1BCBE3-D8CA-396E-861C-A391C7ABCB6A <42 41 12 11 7 5 4 3 1>
   49    3 0xffffff7f81877000 0x16000    0x16000    com.apple.iokit.IOAHCIFamily (2.8.0) 83F8EA09-9119-3A84-8CB4-64E57F74F4FB <5 4 3 1>
   50    0 0xffffff7f826b3000 0x1c000    0x1c000    com.apple.driver.AppleAHCIPort (3.1.5) E445D8EB-F0A1-30C7-9917-7285BCB74C37 <49 12 5 4 3 1>
   51    1 0xffffff7f8136c000 0x3f000    0x3f000    com.apple.driver.usb.AppleUSBEHCI (1.0.1) 1B26B7B7-B450-3629-81F4-582930375538 <41 11 7 5 4 3 1>
   52    0 0xffffff7f8143b000 0x8000     0x8000     com.apple.driver.usb.AppleUSBEHCIPCI (1.0.1) CA019BDA-FCDB-3DE1-AF3E-118CCF573640 <51 41 12 11 7 5 4 3 1>
   59    0 0xffffff7f8189d000 0x19000    0x19000    com.apple.iokit.IOAHCIBlockStorage (2.8.0) E2ACBE69-9A1A-3150-8FB1-D3688155284C <49 16 6 5 4 3 1>
   61    0 0xffffff7f81890000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (2.6.2) 6A42D5CD-B74E-3266-9214-EBDCA1DD2594 <60 49 5 4 3 1>

I still get the same "Bluetooth: Not Available". Tried reinstalling IOath3kfrmwr.kext but no change. Manually loading has no effect.

USB ports are working correctly. I'm using the "no restrictions" approach. Any other things I can try?

Attached my ioreg.

Thanks.

 

[Rytz]

OK, was doing a bit more digging on the USB-front. I used SIV on Windows to give me some detailed info on the USB layout. Looks like Bluetooth is on port 5 on XHCI. I'll have to do some more testing with this on the Mac-side.

 

[RehabMan]

Did a reinstall of Capitan Beta 8 (not reformatted). Looks like EHCI kexts are loading which is good:

rytzs-MacBook-Pro:~ rytz$ sudo touch /System/Library/Extensions && sudo kextcache -u /
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext toledaARPT.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBXHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOUSBHostFamily.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IOath3kfrmwr.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext HDAEnabler3.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIDebug.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBacklight.kext

Not good. Why are the kexts patched?

USB ports are working correctly. I'm using the "no restrictions" approach. Any other things I can try?

No idea what you mean by "no restrictions". Without a port injector, there is still filtering based on DSDT content.

Attached my ioreg.

Something still wrong with USB2 kext (EHC). Restore kexts to vanilla.

 

[RehabMan]

OK, was doing a bit more digging on the USB-front. I used SIV on Windows to give me some detailed info on the USB layout. Looks like Bluetooth is on port 5 on XHCI. I'll have to do some more testing with this on the Mac-side.

If true, note that port5 is not enabled under XHC.

You need to use an injector. See example in my u430 project.

 

[Rytz]

If true, note that port5 is not enabled under XHC.

You need to use an injector. See example in my u430 project.

As I write this, I'm using my bluetooth mouse .

Turns out my DSDT was disabling access to my bluetooth USB port (HS05), along with those other hidden ports.

HS05 and those other hidden ports are referencing UPCI:

    Scope (_SB.PCI0.XHC.RHUB.HS05)
    {
        Method (_UPC, 0, Serialized)  // _UPC: USB Port Capabilities
        {
            Return (UPCI)
        }

        Method (_PLD, 0, Serialized)  // _PLD: Physical Location of Device
        {
            Return (PLD5)
        }
    }

Looking at UPCI:

        Name (UPCI, Package (0x04)
        {
            //Zero,  // RYTZ: original 
            //0xFF,  //
            0xFF,    // RYTZ: modified to turn on (enables bluetooth)
            0xFF,    // 
            Zero, 
            Zero
        })

The above change exposed the remaining ports and allowed bluetooth to be found by the system. Port restrictions must also be removed with injector or by editing AppleUSBEHCIPCI.kext and AppleUSBXHCIPCI.kext.

As a bonus, looks like my webcam was picked up (see screenshot).

The only side effect is a longer boot time by about 5 seconds. I'm going to try restricting those other unused ports in AppleUSBXHCIPCI.kext and just leave Bluetooth and USB enabled.

As for now, my system has everything that I need working. Thanks for hanging in there with me, RehabMan!


(PS: I wonder how my bluetooth worked in Yosemite? Was the system not reading my DSDT properly?)

 

[Rytz]

Attaching my fixes for reference. IOUSBHostFamily.kext reverted back to original system version.

rytzs-MacBook-Pro:~ rytz$ sudo touch /System/Library/Extensions && sudo kextcache -u /
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext toledaARPT.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RYTZUSBPortInjector.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IOath3kfrmwr.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext HDAEnabler3.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIDebug.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBacklight.kext

Some important notes:

> EHC1/2 are renamed to EH01/2 in DSDT to avoid apple conflicts.  They are identified as so in the injector.
> XHC is labeled as XHC in DSDT (no changes required).
> "AppleUSBXHCILPTH1 > IOPCIPrimaryMatch" must match IOreg: added to injector and changed to "0x9cb18086"
> Injector removes all port restrictions (no entries under IOProviderMergeProperties).  Bootup seems normal again after a couple boots.

These fixes all for Acer Aspire E5-771-74E7.

 

[RehabMan]

As I write this, I'm using my bluetooth mouse .

Turns out my DSDT was disabling access to my bluetooth USB port (HS05), along with those other hidden ports.

Yes. You can either fix DSDT or use a port injector. Using a port injector is easier than fixing DSDT...

(PS: I wonder how my bluetooth worked in Yosemite? Was the system not reading my DSDT properly?)

10.10 USB drivers do not use ACPI as extensively as 10.11.

 

[glofter1]

Hi I need help to fix my AR3011 Bluetoth problem.
SO I thing that problem comping from USB. but I can not fix it.
my machine is Toshiba L755-1nk , also I have UP720200 USB3 / 1 port that I active work with fill speed but in not showing in system report / usb.

I have DSDT patch for UD720200 , and I load in PR02 , but still same problem , no Bluetooth.
please help