![]() So we now know that this Hardware ID is for the CSR Bluetooth Dongle (HCI mode). Note also the there is a Revision Number (REV) rev_2520. ![]() Likewise this identifies the product as the Bluetooth Dongle (HCI mode) device. In addition the Product ID (PID) pid_0001. The Vendor 0a12 is the Cambridge Silicon Radio, Ltd vendor code. Again we all know that CSR made most of the Bluetooth hardware on the market. Integrated Rate Matching Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.Additionally the Vendor ID (VID) 0a12 identifies the hardware vendor which we know is CSR. Hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 003: ID 0bda:0184 Realtek Semiconductor Corp. Integrated Rate Matching Hubīus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 003 Device 002: ID 2109:3431 VIA Labs, Inc. LifeCam Cinemaīus 002 Device 002: ID 8087:0024 Intel Corp. Keyboard K120īus 002 Device 003: ID 045e:075d Microsoft Corp. M105 Optical Mouseīus 002 Device 004: ID 046d:c31c Logitech, Inc. LIST OF USB DEVICES -īus 002 Device 005: ID 046d:c077 Logitech, Inc. Mc 65536 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common Snd 126976 20 snd_hda_codec_generic,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi Snd_pcm 163840 5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core Snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec LIST OF KERNEL MODULES -īluetooth 749568 12 btrtl,btintel,btbcm,bnep,btusb Bluetooth: hci0: setting interface failed (110) Bluetooth: hci0: CSR: Failed to suspend the device for our Barrot 8041a02 receive-issue workaround Bluetooth: BNEP socket layer initialized Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: hci0: CSR: Unbranded CSR clone detected adding workarounds and force-suspending once. Bluetooth: L2CAP socket layer initialized Bluetooth: HCI device and connection manager initialized ![]() SYSTEM LOGS -ĭec 16 06:37:58 xeon bluetoothd: Bluetooth daemon 5.62ĭec 16 06:37:58 xeon audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'ĭec 16 06:37:58 xeon bluetoothd: Starting SDP serverĭec 16 06:37:58 xeon bluetoothd: Bluetooth management interface 1.21 initializedĭec 16 06:37:58 xeon dbus-daemon: Activating via systemd: service name='1' unit='' requested by ':1.1' (uid=0 pid=580 comm="/usr/lib/bluetooth/bluetoothd ")ĭec 16 07:10:16 xeon dbus-daemon: Activating via systemd: service name='1' unit='' requested by ':1.93' (uid=0 pid=4429 comm="sudo bluetoothctl - show ")ĭec 16 07:10:16 xeon sudo: enitex : TTY=pts/3 PWD=/home/enitex USER=root COMMAND=/usr/bin/bluetoothctl - showĭec 16 07:12:16 xeon dbus-daemon: Activating via systemd: service name='1' unit='' requested by ':1.96' (uid=0 pid=4787 comm="sudo bluetoothctl ")ĭec 16 07:12:16 xeon sudo: enitex : TTY=pts/2 PWD=/home/enitex USER=root COMMAND=/usr/bin/bluetoothctlĭec 16 07:13:37 xeon dbus-daemon: Activating via systemd: service name='1' unit='' requested by ':1.99' (uid=0 pid=4917 comm="sudo systemctl status bluetooth ")ĭec 16 07:13:37 xeon sudo: enitex : TTY=pts/2 PWD=/home/enitex USER=root COMMAND=/usr/bin/systemctl status bluetooth ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |