Bluetooth on BCM4352 bluetooth/wifi card <Solved>

Comments

12 comments

  • Forrest Smith

    Hey Nathan,

     

    Unfortunately I don't think we have full support for these newer Broadcom chips yet - we're upgrading our kernel, and the Linux driver package with it, in v51 so that might help .

     

    Look for that update in August!

    0
    Comment actions Permalink
  • nathan bunn

    No problem, i will hold out for the next kernel! thanks for the update! good work!

    0
    Comment actions Permalink
  • Nathan

    Trying to do the same... my issue seems to be that I have the BCM43142A0 card which seems to be some kind of combo chip. I cant seem to find anything loading a btusb driver. Any suggestions? 

    0
    Comment actions Permalink
  • Nathan

    Wait... I found it, but its unclaimed. How do I fix this?   

    usb:1 UNCLAIMED
                       description: Generic USB device
                       product: BCM43142A0
                       vendor: Broadcom Corp
                       physical id: 6
                       bus info: usb@1:6
                       version: 1.12
                       serial: ACE010D91586
                       capabilities: usb-2.00
                       configuration: speed=12Mbit/s
    0
    Comment actions Permalink
  • nathan bunn

    O.K, so first login, then press control alt T, then type shell to get a terminal. Next time dmesg and it will scroll loads of text, read up in the text until you find some which say Bluetooth: xxxx. 

    Read all the bluetooth ones and if it is the same problem as me, one line will be saying driver requested XXX or similar, that tells you what the file should be called, then put it in /lib/firmware/brcm/ with the name they asked for. 

    Let me know how it goes...

    0
    Comment actions Permalink
  • Nathan

    It doesn't seem to be looking for the driver like it is for you. Here is some of the output.  

    chronos@localhost / $ dmesg |grep 1-6
    [    3.424113] usb 1-6: new full-speed USB device number 3 using xhci_hcd
    [    3.590707] usb 1-6: New USB device found, idVendor=0930, idProduct=0225
    [    3.590712] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    3.590715] usb 1-6: Product: BCM43142A0
    [    3.590717] usb 1-6: Manufacturer: Broadcom Corp
    chronos@localhost / $dmesg |grep -i blue
    [ 7.041252] toshiba_bluetooth: Detected Toshiba ACPI Bluetooth device - installing RFKill handler [ 7.041297] toshiba_bluetooth: Re-enabling Toshiba Bluetooth [ 7.153952] Bluetooth: Core ver 2.20 [ 7.153997] Bluetooth: HCI device and connection manager initialized [ 7.154004] Bluetooth: HCI socket layer initialized [ 7.154008] Bluetooth: L2CAP socket layer initialized [ 7.154019] Bluetooth: SCO socket layer initialized [ 7.199549] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 7.199559] Bluetooth: BNEP socket layer initialized
    0
    Comment actions Permalink
  • nathan bunn

    Yup seems different, good luck!

    0
    Comment actions Permalink
  • Nathan

    From what I understand from a bunch of google searches is that (more or less) UNCLAIMED means the kernel hasn't done anything with it... so I think ill just wait for the update with updated kernel.

    0
    Comment actions Permalink
  • Jesse Pierce

    Hi Nathan - we released an Early Access version with the Linux Kernel 4.4 upgrade: https://www.neverware.com/blogcontent/2016/8/3/launching-cloudready-early-access-versions-public-bug-tracker

    If you're willing to give it a shot, we'd love to hear how it goes!

    0
    Comment actions Permalink
  • Nathan

    Awesome. I'll give it a go tonight after work 😁

    0
    Comment actions Permalink
  • Nathan

    I had to make the BCM.hcd file myself but.... bluetooth is working :D 

    Its pretty flaky though. Sometimes it shows up, sometimes not. Trying to stream music to my bluetooth headset, working mostly. 

    Running the early access build off a 3.0 usb so that might be part of the issue.

    0
    Comment actions Permalink
  • Muhamad Taufik

    Hello, i know this is an old tread but can anyone teach me how to do this:

    "

    I put the file into the correct folder from the usb

    mv <path to file on usb> /lib/firmware/brcm/

    I renamed the file exactly as it wanted

    mv <old filename> BCM20702A1-0a5c-216f.hcd


     

    "

     

    how to actually write it in the terminal: mv <path to file on usb> /lib/firmware/brcm/

     

    and 

    mv <old filename> BCM20702A1-0a5c-216f.hcd

    0
    Comment actions Permalink

Please sign in to leave a comment.