[Bug 539335] [NEW] [lucid] no bluetooth device found
Stefan Fleiter
stefan.fleiter at web.de
Tue Mar 16 00:09:11 GMT 2010
Public bug reported:
Binary package hint: bluez
I have seen the other reports and do not think this is a duplicate.
I do not file this by means of ubuntu-bug because of bug 538097.
First I enabled the bluetooth device in the bios,
but still no success.
lsusb finds one:
# lsusb | grep -i broadcom
Bus 003 Device 004: ID 0a5c:4503 Broadcom Corp.
Bus 003 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
dell Wireless Tool does find the device:
# sudo dellWirelessCtl --st_bt
Radio Status for Bluetooth:
Bluetooth enabled at boot
Bluetooth supported
Bluetooth enabled
Bluetooth installed
Bluetooth controlled by wireless switch at boot
Bluetooth runtime switch control currently enabled
Status Code: 0
But hcitool does not find a device:
# hcitool dev
Devices:
bluetooth-applet says that my computer does not have any Bluetooth adapters
plugged in.
There is no bluetoothd running:
# ps ax|grep -i blue
2459 ? S 0:00 [bluetooth]
# dmesg | grep -i blue
[ 103.958629] Bluetooth: Core ver 2.15
[ 103.965446] Bluetooth: HCI device and connection manager initialized
[ 103.965449] Bluetooth: HCI socket layer initialized
[ 103.971574] Bluetooth: L2CAP ver 2.14
[ 103.971577] Bluetooth: L2CAP socket layer initialized
[ 103.992145] Bluetooth: RFCOMM TTY layer initialized
[ 103.992149] Bluetooth: RFCOMM socket layer initialized
[ 103.992150] Bluetooth: RFCOMM ver 1.11
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
Package: bluez 4.60-0ubuntu5
PackageArchitecture: amd64
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Tags: lucid
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev vboxusers video
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected lucid
** Tags added: apport-collected
** Description changed:
Binary package hint: bluez
I have seen the other reports and do not think this is a duplicate.
I do not file this by means of ubuntu-bug because of bug 538097.
First I enabled the bluetooth device in the bios,
but still no success.
lsusb finds one:
# lsusb | grep -i broadcom
Bus 003 Device 004: ID 0a5c:4503 Broadcom Corp.
Bus 003 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
dell Wireless Tool does find the device:
# sudo dellWirelessCtl --st_bt
Radio Status for Bluetooth:
Bluetooth enabled at boot
Bluetooth supported
Bluetooth enabled
Bluetooth installed
Bluetooth controlled by wireless switch at boot
Bluetooth runtime switch control currently enabled
Status Code: 0
But hcitool does not find a device:
# hcitool dev
Devices:
bluetooth-applet says that my computer does not have any Bluetooth adapters
plugged in.
There is no bluetoothd running:
# ps ax|grep -i blue
2459 ? S 0:00 [bluetooth]
# dmesg | grep -i blue
[ 103.958629] Bluetooth: Core ver 2.15
[ 103.965446] Bluetooth: HCI device and connection manager initialized
[ 103.965449] Bluetooth: HCI socket layer initialized
[ 103.971574] Bluetooth: L2CAP ver 2.14
[ 103.971577] Bluetooth: L2CAP socket layer initialized
[ 103.992145] Bluetooth: RFCOMM TTY layer initialized
[ 103.992149] Bluetooth: RFCOMM socket layer initialized
[ 103.992150] Bluetooth: RFCOMM ver 1.11
+ ---
+ Architecture: amd64
+ DistroRelease: Ubuntu 10.04
+ Package: bluez 4.60-0ubuntu5
+ PackageArchitecture: amd64
+ ProcEnviron:
+ LANGUAGE=
+ PATH=(custom, user)
+ LANG=de_DE.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
+ Tags: lucid
+ Uname: Linux 2.6.32-16-generic x86_64
+ UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev vboxusers video
--
[lucid] no bluetooth device found
https://bugs.launchpad.net/bugs/539335
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in ubuntu.
More information about the Ubuntu-bluetooth
mailing list