Contribute
Register

No bluetooth with BCM94352HMB

Status
Not open for further replies.
i read again the guide but i can't understand what patch i have to use. i-m so sorry...
i did usb6 series patch and IRQ fix as you said, but i really don't know what i have to do.
 
dxmorgan said:
i read again the guide but i can't understand what patch i have to use. i-m so sorry...
i did usb6 series patch and IRQ fix as you said, but i really don't know what i have to do.
Click to expand...

Let's see what you currently have....

Download patchmatic: https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/RehabMan-patchmatic-2015-0107.zip
Extract the 'patchmatic' binary from the ZIP. Copy it to /usr/bin, such that you have the binary at /usr/bin/patchmatic.

In terminal,
Code: 
if [ -d ~/Downloads/RehabMan ]; then rm -R ~/Downloads/RehabMan; fi
mkdir ~/Downloads/RehabMan
cd ~/Downloads/RehabMan
patchmatic -extract

Note: It is easier if you use copy/paste instead of typing the commands manually.

Post contents of Downloads/RehabMan directory (as ZIP).

Also, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

And output from:
Code: 
kextstat|grep -y acpiplat
kextstat|grep -y appleintelcpu
kextstat|grep -y applelpc

Also, post /Extra folder. Please eliminate 'themes' directory, especially if you have an overabundance of themes installed.

Also post output of:
Code: 
sudo touch /System/Library/Extensions && sudo kextcache -u /
 
ok, output of
kextstat|grep -y acpiplat
kextstat|grep -y appleintelcpu
kextstat|grep -y applelpc




Last login: Sat Jan 9 16:45:04 on ttys000
MBP-di-Andrew:~ AndrewCullenMacBookPro$ kextstat|grep -y acpiplat
13 2 0xffffff7f82636000 0x65000 0x65000 com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>
MBP-di-Andrew:~ AndrewCullenMacBookPro$ kextstat|grep -y appleintelcpu
22 0 0xffffff7f824c5000 0x2b000 0x2b000 com.apple.driver.AppleIntelCPUPowerManagement (218.0.0) <7 6 5 4 3 1>
30 0 0xffffff7f824c0000 0x3000 0x3000 com.apple.driver.AppleIntelCPUPowerManagementClient (218.0.0) <7 6 5 4 3 1>
MBP-di-Andrew:~ AndrewCullenMacBookPro$ kextstat|grep -y applelpc
90 0 0xffffff7f82362000 0x3000 0x3000 com.apple.driver.AppleLPC (1.7.3) <80 12 5 4 3>
MBP-di-Andrew:~ AndrewCullenMacBookPro$


output of sudo touch /System/Library/Extensions && sudo kextcache -u /


MBP-di-Andrew:~ AndrewCullenMacBookPro$ 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 -67030 0xFFFFFFFFFFFEFA2A for kext VoodooHDA.kext
kext file:///System/Library/Extensions/RealtekRTL81xx.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelBacklight.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext GenericUSBXHCI.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext GPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Broadcom_WiFi.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext file:///System/Library/Extensions/AHCI_3rdParty_SATA.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
Invalid signature -67030 for kext <OSKext 0x7f8a13a04570 [0x7fff7ab89ed0]> { URL = "VoodooHDA.kext/ -- file:///System/Library/Extensions/", ID = "org.voodoo.driver.VoodooHDA" }
MBP-di-Andrew:~ AndrewCullenMacBookPro$


very very thanks for your support
 

Attachments

  • Extra.zip
    43.4 KB · Views: 54
  • RehabMan.zip
    28.2 KB · Views: 45
  • MacBook Pro di Andrew.ioreg
    1.4 MB · Views: 47
dxmorgan said:
...
very very thanks for your support
Click to expand...

ACPI is not patched per guide. Be certain to apply all "common patches" as listed in the guide.

EHCI not working.

Try without GenericUSBXHCI.kext (there are patches for AppleUSBXHCI.kext). Note that -gux_defer_usb2 is only for Intel USB3.

Try without USBLegacyOff.

Try with disabling USB3 in BIOS.

Always check system.log. No chance of USB working if you're still getting the USB related errors.
 
i applied all common patches, removed GenericUSBXHCI.kext, boot with USBBusFix flag.

now my webcam is functional, but i have still problem with EHCI as reported in system.log

Jan 9 18:29:59 localhost kernel[0]: USBF: 2.361 EHCI controller unable to take control from BIOS
Jan 9 18:29:59 localhost kernel[0]: USBF: 2.371 AppleUSBEHCI:: unable to obtain ownership: 0xe00002be
Jan 9 18:29:59 localhost kernel[0]: USBF: 2.380 AppleUSBEHCI::UIMInitialize - Error occurred (0xe00002be)
Jan 9 18:29:59 MacBook-Pro-di-Andrew.local com.apple.usbmuxd[72]: usbmuxd-345.70 on Jan 26 2015 at 16:55:11, running 64 bit

with USBLegacyOff=Yes same problem.

edit:

now i tried to boot without any of this flag and removed GenericUSBXHCI.kext.
Now, my USB2 ports are functional, USB3 not, webcam is functional and i see something new under system profile/USB.
now it appears BCM20702A0 but wit this information.
BCM20702A0:

Product ID: 0x22be
Vendor ID: 0x0a5c (Broadcom Corp.)
Version: 1.12
Serial Number: 000000000000
Speed: Up to 12 Mb/sec
Manufacturer: Broadcom Corp
Location ID: 0x1d150000 / 3
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)
Built-In: Yes

under bluetooth no information.

in system.log
09/01/16 18:47:43,000 kernel[0]: USBF: 2.277 EHCI controller unable to take control from BIOS
09/01/16 18:47:43,000 kernel[0]: USBF: 2.277 AppleUSBEHCI:: unable to obtain ownership: 0xe00002be
09/01/16 18:47:43,000 kernel[0]: USBF: 2.277 AppleUSBEHCI::UIMInitialize - Error occurred (0xe00002be)
09/01/16 18:47:43,760 com.apple.usbmuxd[72]: usbmuxd-345.70 on Jan 26 2015 at 16:55:11, running 64 bit
09/01/16 18:54:03,761 com.apple.usbmuxd[72]: usbmuxd-345.70 on Jan 26 2015 at 16:55:11, running 64 bit
09/01/16 18:55:41,000 kernel[0]: USBMSC Identifier (non-unique): 1407033910010555 0x90c 0x1000 0x1100, 2

should i try USBFixOwnership=Yes ? (edit: tried but not fix the problem. i think it is useful only with clover)
 
dxmorgan said:
i applied all common patches, removed GenericUSBXHCI.kext, boot with USBBusFix flag.

now my webcam is functional, but i have still problem with EHCI as reported in system.log

Jan 9 18:29:59 localhost kernel[0]: USBF: 2.361 EHCI controller unable to take control from BIOS
Jan 9 18:29:59 localhost kernel[0]: USBF: 2.371 AppleUSBEHCI:: unable to obtain ownership: 0xe00002be
Jan 9 18:29:59 localhost kernel[0]: USBF: 2.380 AppleUSBEHCI::UIMInitialize - Error occurred (0xe00002be)
Jan 9 18:29:59 MacBook-Pro-di-Andrew.local com.apple.usbmuxd[72]: usbmuxd-345.70 on Jan 26 2015 at 16:55:11, running 64 bit

with USBLegacyOff=Yes same problem.

edit:

now i tried to boot without any of this flag and removed GenericUSBXHCI.kext.
Now, my USB2 ports are functional, USB3 not, webcam is functional and i see something new under system profile/USB.
now it appears BCM20702A0 but wit this information.
BCM20702A0:

Product ID: 0x22be
Vendor ID: 0x0a5c (Broadcom Corp.)
Version: 1.12
Serial Number: 000000000000
Speed: Up to 12 Mb/sec
Manufacturer: Broadcom Corp
Location ID: 0x1d150000 / 3
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)
Built-In: Yes

under bluetooth no information.

in system.log
09/01/16 18:47:43,000 kernel[0]: USBF: 2.277 EHCI controller unable to take control from BIOS
09/01/16 18:47:43,000 kernel[0]: USBF: 2.277 AppleUSBEHCI:: unable to obtain ownership: 0xe00002be
09/01/16 18:47:43,000 kernel[0]: USBF: 2.277 AppleUSBEHCI::UIMInitialize - Error occurred (0xe00002be)
09/01/16 18:47:43,760 com.apple.usbmuxd[72]: usbmuxd-345.70 on Jan 26 2015 at 16:55:11, running 64 bit
09/01/16 18:54:03,761 com.apple.usbmuxd[72]: usbmuxd-345.70 on Jan 26 2015 at 16:55:11, running 64 bit
09/01/16 18:55:41,000 kernel[0]: USBMSC Identifier (non-unique): 1407033910010555 0x90c 0x1000 0x1100, 2

should i try USBFixOwnership=Yes ? (edit: tried but not fix the problem. i think it is useful only with clover)
Click to expand...

No idea without ioreg.
 
sorry, here it is
 

Attachments

  • MacBook Pro di Andrew.ioreg
    1.4 MB · Views: 55
ok, this is what i did.

1 removed BrcmPatchRAM.kext BrcmFirmwareRepo.kext with rm -rf
2 did repair permission and rebuild cache
3 download again the kexts
4 installed both kexts with kext wizard
5 did repair permission and rebuild cache

didn't fix yet...

i post new ioreg

i don't understand what i'm doing wrong

this is the output of 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 -67030 0xFFFFFFFFFFFEFA2A for kext VoodooHDA.kext
kext file:///System/Library/Extensions/RealtekRTL81xx.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelBacklight.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext GPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Broadcom_WiFi.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext file:///System/Library/Extensions/AHCI_3rdParty_SATA.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
Invalid signature -67030 for kext <OSKext 0x7f849c300ea0 [0x7fff7d327ed0]> { URL = "VoodooHDA.kext/ -- file:///System/Library/Extensions/", ID = "org.voodoo.driver.VoodooHDA" }
MBP-di-Andrew:~ AndrewCullenMacBookPro$




Should i change "disabled_IOResources" to "IOResources"? or is it only for Clover?

or should i patch BroadcomUSBBluetoothHCIController.kext with my bluetooth Vendor/Device ID?

is there a way to force load BrcmPatchRam.kext? because i install it in the proper way and i'm sure of it


EDIT: i don't know why but BTFirmwareUploader.kext fix my problem. now bluetooth shows up and is functional. i really don't know what is the problem with BrcmpatchRAM.kext

so sorry but now i have another problem. i enable file tranfer, internet sharing, instant hotspot, handoff and continuity but i can't find my iphone for hotspot and for airdrop and if open pages on my iphone i can't see the continuity app in the left corner of the screen . if i search for my iphone in mac bluetooth panel nothing appears. do you any idea why?
 

Attachments

  • MacBook Pro di Andrew.ioreg
    1.4 MB · Views: 67
dxmorgan said:
...
didn't fix yet...

i post new ioreg
Click to expand...

Your device, 0a5c:22be is not supported by BrcmPatchRAM.

You might check in Windows to see which firmware is loading.

Or purchase a compatible BCM94352HMB instead (eg. AzureWave AW-CE123H).
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top