linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 205821] New: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Date: Tue, 10 Dec 2019 11:24:53 +0000	[thread overview]
Message-ID: <bug-205821-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=205821

            Bug ID: 205821
           Summary: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
                    Dongle (HCI mode)
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19.0-6-amd64
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: demonik_82@mail.ru
        Regression: No

$ hcitool dev
Devices:
$ hcitool scan
Device is not available: No such device

$ lsusb
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 003: ID 040b:2000 Weltrend Semiconductor 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset
   Active: active (running) since Tue 2019-12-10 15:23:47 +05; 53min ago
     Docs: man:bluetoothd(8)
 Main PID: 604 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 3.0M
   CGroup: /system.slice/bluetooth.service
           └─604 /usr/lib/bluetooth/bluetoothd

rfkill list all
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

journalctl -b | grep firmware
дек 10 15:23:48 dev NetworkManager[606]: <info>  [1575973428.5871]
manager[0x557f0fb14020]: monitoring kernel firmware directory '/lib/firmware'.
дек 10 15:23:51 dev kernel: r8169 0000:03:00.0: firmware: direct-loading
firmware rtl_nic/rtl8168f-1.fw
дек 10 15:24:16 dev systemd[1]: Startup finished in 8.999s (firmware) + 6.482s
(loader) + 4.575s (kernel) + 45.463s (userspace) = 1min 5.521s.

hciconfig
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
        DOWN 
        RX bytes:574 acl:0 sco:0 events:30 errors:0
        TX bytes:368 acl:0 sco:0 commands:30 errors:0

hciconfig hci0 up
Can't init device hci0: Operation not supported (95)

Help please

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-12-10 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 11:24 bugzilla-daemon [this message]
2019-12-11  7:17 ` [Bug 205821] ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) bugzilla-daemon
2020-01-12 10:34 ` bugzilla-daemon
2020-03-16 16:54 ` bugzilla-daemon
2022-10-15 18:45 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-205821-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).