References to 21be (product id) in btwusb.inf from Windows 10 driver > Device is not available: No such device Videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 Videobuf2_memops 16384 1 videobuf2_vmalloc Snd_hda_codec_generic 77824 1 snd_hda_codec_realtek Vboxdrv 454656 3 vboxnetadp,vboxnetflt,vboxpci Bluetooth: BNEP socket layer initializedīluetooth 520192 10 bnep,btbcm,btrtl,btusb,btintel Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP (Ethernet Emulation) ver 1.3 usbcore: registered new interface driver btusb Bluetooth: L2CAP socket layer initialized Bluetooth: HCI device and connection manager initialized usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 8-2: New USB device found, idVendor=0a5c, idProduct=21be usb 8-2: new full-speed USB device number 4 using uhci_hcd usb 8-2: new full-speed USB device number 3 using uhci_hcd I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > Bus 008 Device 002: ID 0a5c:21be Broadcom Corp. Also I think this problem is distribution-independent, that's why i'm asking here uname -a There are many similar questions to mine on this site but all i've seen are based on the missing firmware file. So it seems like the device does not require a firmware to be uploaded on boot like many other broadcom devices but it still does not work.ĭoes anyone has experience with broadcom devices and can help me troubleshoot the problem? Google shows that problems with broadcom devices are common and the usual solution is to extract a proprietary firmware file from the windows driver ( AskUbuntu, Arch Wiki) but in my case the driver does not specify a firmware file in the *.inf file. I'm trying to get a Broadcom Bluetooth Adapter working on Ubuntu/Linux.
0 kommentar(er)
