Results 1 to 4 of 4

Thread: Kali 1.0.9 HDD X64 how to confirm bluetooth operational dell Insp 5748

  1. #1
    Join Date
    2014-Nov
    Posts
    3

    Question Kali 1.0.9 HDD X64 how to confirm bluetooth operational dell Insp 5748

    Hi Folks,
    I'm having some issues getting bluetooth running on my Dell Inspiron Laptop running Kali 1.0.9.. It seems to think it's running, and if I boot into windows it sees BT devices.. Are there more packages that I need to install? What am I missing?

    Code:
    root@pcname:~# /etc/init.d/bluetooth status
    [FAIL] bluetooth is not running ... failed!
    root@pcname:~# /etc/init.d/bluetooth start
    [ ok ] Starting bluetooth: bluetoothd rfcomm.
    root@pcname:~# /etc/init.d/bluetooth status
    [ ok ] bluetooth is running.
    root@pcname:~# hcitool -i hci0 scan
    Scanning ...
    root@pcname:~# hciconfig hci0
    hci0:	Type: BR/EDR  Bus: USB
    	BD Address: x:x:x:x:x:x  ACL MTU: 1021:8  SCO MTU: 64:1
    	UP RUNNING PSCAN 
    	RX bytes:1480 acl:0 sco:0 events:73 errors:0
    	TX bytes:1278 acl:0 sco:0 commands:72 errors:0
    
    root@pcname:~# 
    root@pcname:~# rfkill list
    0: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    root@pcname:~#

  2. #2
    Join Date
    2014-Jan
    Posts
    15
    What is the chipset of the bluetooth device ?
    output of lsusb please

    I had issue with the one in my inspiron 15 (3521) laptop because it needed a firmware to properly work.

    It was as if it was working as you described but did not in fact.

    look at /var/log/syslog for errors like the one I got which was:
    bluetooth hci0: firmware: brcm/BCM43142A0-0a5c-21d7.hcd will not be loaded

    I had to grab the firmware from windows driver file, convert, and import the file. More info at https://bugs.launchpad.net/ubuntu/+s...x/+bug/1065400

  3. #3
    Join Date
    2014-Nov
    Posts
    3
    Yes, I have a Broadcom chipset that would show in lsusb..Well, on a hunch I decided to check for a bios update.. I just purchased this laptop Insp (5748) and had assumed the latest bios would be on it. Re-flashed and BOOMSAUCE!!! I can BT like a Mo-Fo!!
    pre bios re-flash lsusb output:
    Code:
    Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. 
    Bus 001 Device 004: ID 0a5c:21d7 Broadcom Corp. 
    Bus 001 Device 003: ID 0c45:6a04 Microdia 
    Bus 001 Device 002: ID 8087:8000 Intel Corp. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 002 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
    Bus 002 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  4. #4
    Join Date
    2014-Nov
    Posts
    3
    apparently until i reboot now it doesn't work anymore.. any suggestions for a kali friendly BT adapter? This I believe is the section from syslog where bluetooth loads up.
    Code:
    Nov 27 22:43:12 pcname dbus[2607]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Nov 27 22:43:44 pcname bluetoothd[3522]: Bluetooth daemon 4.99
    Nov 27 22:43:44 pcname bluetoothd[3522]: Starting SDP server
    Nov 27 22:43:44 pcname bluetoothd[3522]: Failed to init alert plugin
    Nov 27 22:43:44 pcname bluetoothd[3522]: Failed to init time plugin
    Nov 27 22:43:44 pcname bluetoothd[3522]: Failed to init gatt_example plugin
    Nov 27 22:43:44 pcname bluetoothd[3522]: Listening for HCI events on hci0
    Nov 27 22:43:44 pcname kernel: [  124.580877] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    Nov 27 22:43:44 pcname kernel: [  124.580888] Bluetooth: BNEP filters: protocol multicast
    Nov 27 22:43:44 pcname kernel: [  124.580906] Bluetooth: BNEP socket layer initialized
    Nov 27 22:43:46 pcname kernel: [  126.589536] Bluetooth: hci0 command 0x1003 tx timeout
    Nov 27 22:43:46 pcname bluetoothd[3522]: HCI dev 0 up
    Nov 27 22:43:46 pcname bluetoothd[3522]: Proximity GATT Reporter Driver: Operation not permitted (1)
    Nov 27 22:43:46 pcname kernel: [  126.660763] Bluetooth: RFCOMM TTY layer initialized
    Nov 27 22:43:46 pcname kernel: [  126.660783] Bluetooth: RFCOMM socket layer initialized
    Nov 27 22:43:46 pcname kernel: [  126.660796] Bluetooth: RFCOMM ver 1.11
    Nov 27 22:43:46 pcname bluetoothd[3522]: Unable to load keys to adapter_ops: Function not implemented (38)
    Nov 27 22:43:46 pcname bluetoothd[3522]: Adapter /org/bluez/3522/hci0 has been enabled
    Nov 27 22:45:27 pcname bluetoothd[3522]: Terminating
    Nov 27 22:45:27 pcname bluetoothd[3522]: Stopping hci0 event socket
    Nov 27 22:45:27 pcname bluetoothd[3522]: Stopping SDP server
    Nov 27 22:45:27 pcname bluetoothd[3522]: Exit
    Nov 27 22:45:33 pcname bluetoothd[3566]: Bluetooth daemon 4.99
    Nov 27 22:45:33 pcname bluetoothd[3566]: Starting SDP server
    Nov 27 22:45:33 pcname bluetoothd[3566]: Failed to init alert plugin
    Nov 27 22:45:33 pcname bluetoothd[3566]: Failed to init time plugin
    Nov 27 22:45:33 pcname bluetoothd[3566]: Failed to init gatt_example plugin
    Nov 27 22:45:33 pcname bluetoothd[3566]: Listening for HCI events on hci0
    Nov 27 22:45:35 pcname kernel: [  235.583032] Bluetooth: hci0 command 0x1003 tx timeout
    Nov 27 22:45:35 pcname bluetoothd[3566]: HCI dev 0 up
    Nov 27 22:45:35 pcname bluetoothd[3566]: Proximity GATT Reporter Driver: Operation not permitted (1)
    Nov 27 22:45:35 pcname bluetoothd[3566]: Unable to load keys to adapter_ops: Function not implemented (38)
    Nov 27 22:45:35 pcname bluetoothd[3566]: Adapter /org/bluez/3566/hci0 has been enabled
    Last edited by 0ddB411; 2014-11-28 at 23:29.

Similar Threads

  1. Replies: 8
    Last Post: 2017-05-25, 05:02
  2. Troubleshooting - Confirm nvidia drivers
    By jamesmartin in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2015-09-11, 14:57

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •