0a12 0001 bluetooth linux

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' 

Источник

Читайте также:  Asus k52f bluetooth drivers

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)

Читайте также:  Bmw e90 дооснащение bluetooth

Источник

Debian User Forums

install bluetooth adapter 0a12:0001 Cambridge Silicon Radio

install bluetooth adapter 0a12:0001 Cambridge Silicon Radio

#1 Post by SImon2020 » 2020-01-27 16:16

Hi there, I tried to get the adapter to run, but I failed so far.

What I did:
Plug the adapter, install some packages:
apt install pulseaudio-module-bluetooth bluez-firmware btscanner blueman bluez bluez-tools libpam-blue python-bluez
sudo apt-get install bluetooth bluez libbluetooth-dev libudev-dev libcap2-bin

Some outputs that might be helpful:

simon@debian-simon:~$ lsusb Bus 002 Device 002: ID 1058:25a1 Western Digital Technologies, Inc. Elements / My Passport (WD20NMVW) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0451:16a8 Texas Instruments, Inc. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002:[b] ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)[/b] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
simon@debian-simon:~$ sudo journalctl -f -- Logs begin at Mon 2020-01-27 13:13:33 CET. -- Jan 27 16:56:29 debian-simon kernel: usb 1-2: new full-speed USB device number 6 using xhci_hcd Jan 27 16:56:29 debian-simon kernel: usb 1-2: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 Jan 27 16:56:29 debian-simon kernel: usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Jan 27 16:56:29 debian-simon kernel: usb 1-2: Product: USB1.1-A Jan 27 16:56:29 debian-simon systemd[1]: Starting Load/Save RF Kill Switch Status. Jan 27 16:56:29 debian-simon systemd[1]: Started Load/Save RF Kill Switch Status. Jan 27 16:56:29 debian-simon systemd[1]: Reached target Bluetooth.
simon@debian-simon:~$ bluetoothctl [bluetooth]# list [bluetooth]# devices No default controller available [bluetooth]#

Unfortunately, google lead me to this page and I followed the steps:
https://www.raspberrypi.org/forums/view . 4#p1384009

Читайте также:  Adding bluetooth to computer

I think this destroyed some dependencies. Before I running the stuff in the post, I had:

simon@debian-simon:~$ dpkg -l blue* Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ Name Version Architektur Beschreibung +++-==============-============-============-================================= ii bluetooth 5.50-1 all Bluetooth support (metapackage) ii bluez 5.50-1 amd64 Bluetooth tools and daemons un bluez-alsa  (keine Beschreibung vorhanden) un bluez-audio  (keine Beschreibung vorhanden) un bluez-cups  (keine Beschreibung vorhanden) un bluez-gnome  (keine Beschreibung vorhanden) un bluez-input  (keine Beschreibung vorhanden) un bluez-network  (keine Beschreibung vorhanden) ii bluez-obexd 5.50-1 amd64 bluez obex daemon un bluez-pan  (keine Beschreibung vorhanden) un bluez-serial  (keine Beschreibung vorhanden) un bluez-utils  (keine Beschreibung vorhanden) simon@debian-simon:~$
simon@debian-simon:~$ sudo dpkg -l blue* [sudo] Passwort für simon: dpkg-query: Kein Paket gefunden, das auf bluez-5.50 passt dpkg-query: Kein Paket gefunden, das auf bluez-5.50.tar.xz passt dpkg-query: Kein Paket gefunden, das auf bluez-firmware.deb passt

Sorry its partly in German, hope thats enough info. Can someone give me a hint here? Or recommend some other bluetooth adapter, that might work better?

Источник

Оцените статью
Adblock
detector