![]() Jul 16 12:39:40 i3-4130 kernel: usb 3-9: new full-speed USB device number 10 using xhci_hcd Journal begins at Sun 15:51:53 CEST, ends at Fri 12:46:36 CEST. I3-4130:~ # journalctl -since 12:30 _KERNEL_SUBSYSTEM=usb I plugged in a ‘Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)’ and it readily tries to connect with devices found: i3-4130:~ # bluetoothctlĬontroller xx:xx:xx:xx:xx:xx i3-4130 But the error is too widely spread it seems. Sorry, my bad, wasn’t very clear: the device never worked on openSUSE, will get a laptop today with a Windows 10 just to rule out a defective product. Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3įakeMoth-PC:/home/fakemoth # hcitool scanįakeMoth-PC:/home/fakemoth # hciconfig hci0 upĬan't init device hci0: Operation not supported (95)įakeMoth-PC:/home/fakemoth # bluetoothctlĪny ideeas, any experience with this? I read about recompiling the kernel but it is overkill, isn’t there some module or something I can just load? Thanks! TX bytes:368 acl:0 sco:0 commands:30 errors:0įakeMoth-PC:/home/fakemoth # hciconfig -a hci0įeatures: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87 RX bytes:574 acl:0 sco:0 events:30 errors:0 So the device works and it’s a Cambridge chip, but:īD Address: 00:1A:7D:DA:71:11 ACL MTU: 679:9 SCO MTU: 48:16 Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)Īctive: active (running) since Sun 10:02:40 EEST 30min agoĪug 02 10:02:40 FakeMoth-PC systemd: Starting Bluetooth service.Īug 02 10:02:40 FakeMoth-PC bluetoothd: Bluetooth daemon 5.48Īug 02 10:02:40 FakeMoth-PC bluetoothd: Starting SDP serverĪug 02 10:02:40 FakeMoth-PC bluetoothd: Bluetooth management interface 1.14 initializedĪug 02 10:02:40 FakeMoth-PC systemd: Started Bluetooth service.įakeMoth-PC:/home/fakemoth # dmesg | grep Bluetoothġ6.667986] Bluetooth: HCI device and connection manager initializedġ6.667989] Bluetooth: HCI socket layer initializedġ6.667990] Bluetooth: L2CAP socket layer initializedġ6.667992] Bluetooth: SCO socket layer initializedĢ2.211247] Bluetooth: BNEP (Ethernet Emulation) ver 1.3Ģ2.211248] Bluetooth: BNEP filters: protocol multicastĢ2.211251] Bluetooth: BNEP socket layer initializedīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supplyīus 001 Device 005: ID 1532:006c Razer USA, Ltdīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub This is like the third piece of s… bought (at least is Bluetooth 5.0, if it would work) and I am out of ideas… Was running Leap 15.1 with the latest stable 5.7 kernel, but I upgraded to 15.2 with the 5.3 kernel, my Vega 64 wouldn’t run on 4.x versions. I am running 16.04 so things might be different. Failed to set mode: Failed (0x03) for Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) on ubuntu 20.04. 1 Answer Sorted by: 0 I also have this device - the Cambridge Silicon Radio Bluetooth Dongle. By default it will be set as a "Generic Bluetooth Radio", but you need to select "Generic Bluetooth Adapter"Ĭonnecting to bluetooth devices natively is just soo much better and a seamless process to switch devices rather than use the TP-Link driver software.Hello, need some help with a Bluetooth dongle, just can’t make it work. HSP/HFP with 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) 3. Update driver, and pick from a list of available driver.Find the wherever the dongle was listed as or listed under some name. ![]() Basically had to go into Device Manager.The latest Windows 10 update #2004 broke my bluetooth setup completely, and the TP Link 400 YOU! Your solution worked for me. The real problem with the TP-Link's driver software is that it can only pair with one device at a time, and the pairing process is forced to have to connect only using the bluetooth icon in the taskbar. Audio output to my bluetooth headphones is constatanly out of sync by 1-2 seconds at worst. So the driver software you can install from TP link technically works ( ), but let be honest it is very slow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |