Bluetooth adapter configuration issue (ID 0a12:0001)
Bluetake
Works out-of-the-box in Ubuntu v10.04 ~ 11.04 but stopped working reliably in 11.10, frequent kernel panics and other general not good stuff, [Bug: 901770] $ lsusb
Bus 007 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) $ hciconfig -a hci0
Manufacturer: Cambridge Silicon Radio (10) Might need same fix as Belkin : add blacklist hci_usb to /etc/modprobe.d/blacklist.conf , and add hci_usb reset=1 to /etc/modules
- to install kernel 5.5.2 kernel. But it failed to login, so I’ve purged it and returned to my 5.3.0-29-generic kernel.
- to do the next, but it failed:
$ make -C /lib/modules/$(uname -r)/build M=$PWD modules make: Entering directory '/usr/src/linux-headers-5.3.0-29-generic' CC [M] /home/spacer/kernel/bluetooth/hci_vhci.o /home/spacer/kernel/bluetooth/hci_vhci.c: In function ‘vhci_create_device’: /home/spacer/kernel/bluetooth/hci_vhci.c:134:2: warning: dereferencing ‘void *’ pointer 134 | *skb_put(skb, 1) = 0xff; | ^~~~~~~~~~~~~~~~ /home/spacer/kernel/bluetooth/hci_vhci.c:134:19: error: invalid use of void expression 134 | *skb_put(skb, 1) = 0xff; | ^ /home/spacer/kernel/bluetooth/hci_vhci.c:135:2: warning: dereferencing ‘void *’ pointer 135 | *skb_put(skb, 1) = dev_type; | ^~~~~~~~~~~~~~~~ /home/spacer/kernel/bluetooth/hci_vhci.c:135:19: error: invalid use of void expression 135 | *skb_put(skb, 1) = dev_type; | ^ /home/spacer/kernel/bluetooth/hci_vhci.c: In function ‘vhci_get_user’: /home/spacer/kernel/bluetooth/hci_vhci.c:203:19: error: ‘HCI_BREDR’ undeclared (first use in this function) 203 | if (dev_type != HCI_BREDR && dev_type != HCI_AMP) | ^~~~~~~~~ /home/spacer/kernel/bluetooth/hci_vhci.c:203:19: note: each undeclared identifier is reported only once for each function it appears in /home/spacer/kernel/bluetooth/hci_vhci.c: In function ‘vhci_open_timeout’: /home/spacer/kernel/bluetooth/hci_vhci.c:307:43: error: ‘HCI_BREDR’ undeclared (first use in this function) 307 | vhci_create_device(data, amp ? HCI_AMP : HCI_BREDR); | ^~~~~~~~~ /home/spacer/kernel/bluetooth/hci_vhci.c: At top level: /home/spacer/kernel/bluetooth/hci_vhci.c:352:3: error: ‘const struct file_operations’ has no member named ‘aio_write’ 352 | .aio_write = vhci_write, | ^~~~~~~~~ /home/spacer/kernel/bluetooth/hci_vhci.c:352:15: error: positional initialization of field in ‘struct’ declared with ‘designated_init’ attribute [-Werror=designated-init] 352 | .aio_write = vhci_write, | ^~~~~~~~~~ /home/spacer/kernel/bluetooth/hci_vhci.c:352:15: note: (near initialization for ‘vhci_fops’) /home/spacer/kernel/bluetooth/hci_vhci.c:352:15: error: initialization of ‘ssize_t (*)(struct file *, const char *, size_t, loff_t *)’ from incompatible pointer type ‘ssize_t (*)(struct kiocb *, const struct iovec *, long unsigned int, loff_t)’ [-Werror=incompatible-pointer-types] /home/spacer/kernel/bluetooth/hci_vhci.c:352:15: note: (near initialization for ‘vhci_fops.write’) cc1: some warnings being treated as errors make[1]: *** [scripts/Makefile.build:290: /home/spacer/kernel/bluetooth/hci_vhci.o] Error 1 make: *** [Makefile:1655: _module_/home/spacer/kernel/bluetooth] Error 2 make: Leaving directory '/usr/src/linux-headers-5.3.0-29-generic'
Bluetooth в Linux — опять облом
Втыкнул его, ничего не произошло. Пославил метапакет bluetooth. Он потянул за собой bluez. Все встало без проблем, но на рабочем столе при втыкании адаптера ничего не происходит. Смотрю модули ядра. Вроде модуль есть:
# lsmod | grep blue bluetooth 103750 1 btusb rfkill 18516 1 bluetooth crc16 12327 1 bluetooth
Решил посмотреть, а есть хоть какой процесс, который за bluetooth отвечает. Такого процесса нет:
# ps aux | grep blue root 12765 0.0 0.0 4572 932 pts/0 S+ 23:03 0:00 grep blue
# /etc/init.d/bluetooth start [ ok ] Starting bluetooth: bluetoothd.
# /etc/init.d/bluetooth status [FAIL] bluetooth is not running . failed!
Дальше мысли кончаются. Насколько я понимаю, пока демон не запустится, ничего работать не будет, и искать вменяемый гуишный интерфейс бессмысленно. Куда копать?
гм. если демон запустился и умер, значит нужно в логи глянуть. Обычно помогает.
Ну вот единственное что нашел в /var/log/daemon.log:
May 20 22:54:43 pangolinux dbus[2079]: [system] Reloaded configuration May 20 22:54:43 pangolinux bluetoothd[12248]: Bluetooth daemon 5.23 May 20 22:54:43 pangolinux bluetoothd[12248]: Failed to access management interface May 20 22:54:43 pangolinux bluetoothd[12248]: Adapter handling initialization failed May 20 22:54:43 pangolinux dbus[2079]: [system] Reloaded configuration May 20 22:57:18 pangolinux bluetoothd[12394]: Bluetooth daemon 5.23 May 20 22:57:18 pangolinux bluetoothd[12394]: Failed to access management interface May 20 22:57:18 pangolinux bluetoothd[12394]: Adapter handling initialization failed
Тот же самый временной промежуток в /var/log/syslog:
May 20 22:54:43 pangolinux dbus[2079]: [system] Reloaded configuration May 20 22:54:43 pangolinux bluetoothd[12248]: Bluetooth daemon 5.23 May 20 22:54:43 pangolinux bluetoothd[12248]: Failed to access management interface May 20 22:54:43 pangolinux bluetoothd[12248]: Adapter handling initialization failed May 20 22:54:43 pangolinux dbus[2079]: [system] Reloaded configuration May 20 22:55:01 pangolinux CRON[12295]: (root) CMD (/usr/bin/gputemp.sh) May 20 22:55:01 pangolinux CRON[12296]: (root) CMD ( /usr/bin/gputemp.sh) May 20 22:55:02 pangolinux CRON[12309]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) May 20 22:55:02 pangolinux sSMTP[12311]: Creating SSL connection to host May 20 22:55:02 pangolinux sSMTP[12312]: Creating SSL connection to host May 20 22:55:02 pangolinux sSMTP[12311]: SSL connection using RSA_AES_128_CBC_SHA1 May 20 22:55:02 pangolinux sSMTP[12312]: SSL connection using RSA_AES_128_CBC_SHA1 May 20 22:55:04 pangolinux sSMTP[12311]: Sent mail for root@gmail.com (221 2.0.0 closing connection o138sm1611624lfo.55 - gsmtp) uid=0 username=root outbytes=665 May 20 22:55:05 pangolinux sSMTP[12312]: Sent mail for root@gmail.com (221 2.0.0 closing connection s18sm2177096ljd.3 - gsmtp) uid=0 username=root outbytes=615 May 20 22:56:01 pangolinux CRON[12319]: (root) CMD (/usr/bin/gputemp.sh) May 20 22:56:01 pangolinux CRON[12320]: (root) CMD ( /usr/bin/gputemp.sh) May 20 22:56:01 pangolinux sSMTP[12334]: Creating SSL connection to host May 20 22:56:01 pangolinux sSMTP[12333]: Creating SSL connection to host May 20 22:56:02 pangolinux sSMTP[12334]: SSL connection using RSA_AES_128_CBC_SHA1 May 20 22:56:02 pangolinux sSMTP[12333]: SSL connection using RSA_AES_128_CBC_SHA1 May 20 22:56:04 pangolinux sSMTP[12334]: Sent mail for root@gmail.com (221 2.0.0 closing connection h72sm2222588ljh.57 - gsmtp) uid=0 username=root outbytes=615 May 20 22:56:05 pangolinux sSMTP[12333]: Sent mail for root@gmail.com (221 2.0.0 closing connection 22sm2183964ljv.67 - gsmtp) uid=0 username=root outbytes=665 May 20 22:57:01 pangolinux CRON[12347]: (root) CMD ( /usr/bin/gputemp.sh) May 20 22:57:01 pangolinux CRON[12354]: (root) CMD (/usr/bin/gputemp.sh) May 20 22:57:01 pangolinux sSMTP[12362]: Creating SSL connection to host May 20 22:57:01 pangolinux sSMTP[12361]: Creating SSL connection to host May 20 22:57:01 pangolinux sSMTP[12362]: SSL connection using RSA_AES_128_CBC_SHA1 May 20 22:57:01 pangolinux sSMTP[12361]: SSL connection using RSA_AES_128_CBC_SHA1 May 20 22:57:03 pangolinux sSMTP[12362]: Sent mail for root@gmail.com (221 2.0.0 closing connection a79sm2134170ljb.54 - gsmtp) uid=0 username=root outbytes=615 May 20 22:57:04 pangolinux sSMTP[12361]: Sent mail for root@gmail.com (221 2.0.0 closing connection a17sm1659402lfg.51 - gsmtp) uid=0 username=root outbytes=665 May 20 22:57:18 pangolinux bluetoothd[12394]: Bluetooth daemon 5.23 May 20 22:57:18 pangolinux bluetoothd[12394]: Failed to access management interface May 20 22:57:18 pangolinux bluetoothd[12394]: Adapter handling initialization failed
Xintrea ★★★★★ ( 20.05.17 22:48:57 MSK )
Последнее исправление: Xintrea 20.05.17 22:55:06 MSK (всего исправлений: 1)
Linux Mint Forums
Cambridge Silicon Radio, Ltd Bluetooth Dongle — Not Connecting
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
Cambridge Silicon Radio, Ltd Bluetooth Dongle — Not Connecting
Post by Mihail-Cosmin » Sun Feb 02, 2020 8:08 am
I have a Bluetooth Dongle: Cambridge Silicon Radio, Ltd Bluetooth Dongle, that shows on my system (Linux Mint 19.3), but doesn’t work to connect in any way.
When scanning with my phone I can see this device «00:1A:7D:DA:71:10» but when I try to pair, it doesn’t connect.
Also from my laptop if I use blueman to search for devices I get this error:
Does anyone have any idea how I can fix this?
One more thing, the reason I bought this dongle was because my laptop integrated bluetooth adapter also wasn’t working.
Maybe these 2 issues are connected?
I would be happy if either of the 2 Bluetooth adapters could work.
Some additional info on my system:
System: Host: mihailcosmin-HP-Pavilion-Notebook Kernel: 5.3.0-28-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 tk: Gtk 3.22.30 wm: xfwm4 dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Pavilion Notebook v: N/A serial: Chassis: type: 10 serial: Mobo: HP model: 80B5 v: 81.32 serial: UEFI: American Megatrends v: F.45 date: 04/28/2017 Battery: ID-1: BAT0 charge: 35.0 Wh condition: 35.0/35.0 Wh (100%) volts: 16.6/14.6 model: Hewlett-Packard Primary serial: status: Full Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M215 2nd Gen serial: charge: 100% status: Discharging CPU: Topology: Quad Core model: AMD A10 Extreme Edition Radeon R8 4C+8G bits: 64 type: MCP arch: Excavator rev: 1 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 15969 Speed: 2520 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 2520 2: 2624 3: 1863 4: 1894 Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard Carrizo driver: amdgpu v: kernel bus ID: 00:01.0 chip ID: 1002:9874 Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 chip ID: 1002:6900 Display: x11 server: X.Org 1.19.6 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon R7 Graphics (CARRIZO DRM 3.33.0 5.3.0-28-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD Kabini HDMI/DP Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:01.1 chip ID: 1002:9840 Device-2: AMD Family 15h Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:09.2 chip ID: 1022:157a Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8136 IF: eno1 state: down mac: Device-2: Broadcom and subsidiaries BCM43142 802.11b/g/n vendor: Hewlett-Packard driver: wl v: kernel port: e000 bus ID: 03:00.0 chip ID: 14e4:4365 IF: wlo1 state: dormant mac: Device-3: Realtek RTL8812AU 802.11a/b/g/n/ac WLAN Adapter type: USB driver: 88XXau bus ID: 2-3.1:5 chip ID: 0bda:8812 IF: wlx24050ff6a47a state: up mac: Drives: Local Storage: total: 931.51 GiB used: 288.43 GiB (31.0%) ID-1: /dev/sda vendor: Seagate model: ST1000LM014-1EJ164-SSHD size: 931.51 GiB speed: 6.0 Gb/s serial: Partition: ID-1: / size: 804.52 GiB used: 288.39 GiB (35.8%) fs: ext4 dev: /dev/sda14 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002 Hub: 1-1:2 info: Advanced Micro Devices ports: 4 rev: 2.0 chip ID: 0438:7900 Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002 Device-1: 2-1:2 info: Chicony type: Video driver: uvcvideo rev: 2.0 chip ID: 04f2:b50d Device-2: 2-2:3 info: Broadcom type: driver: btusb rev: 2.0 chip ID: 0a5c:216d Hub: 2-3:4 info: Realtek ports: 4 rev: 2.1 chip ID: 0bda:5411 Device-3: 2-3.1:5 info: Realtek RTL8812AU 802.11a/b/g/n/ac WLAN Adapter type: Network driver: 88XXau rev: 2.0 chip ID: 0bda:8812 Device-4: 2-3.2:6 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID driver: logitech-djreceiver,usbhid rev: 2.0 chip ID: 046d:c52b Device-5: 2-3.4:7 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: Bluetooth driver: btusb rev: 2.0 chip ID: 0a12:0001 Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 chip ID: 1d6b:0003
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:10 ACL MTU: 640:4 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1110 acl:0 sco:0 events:58 errors:0
TX bytes:1700 acl:0 sco:0 commands:60 errors:0
hci0: Type: Primary Bus: USB
BD Address: 60:6D:C7:E0:8F:90 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:1542 acl:0 sco:0 events:79 errors:0
TX bytes:1840 acl:0 sco:0 commands:79 errors:0