[Gutsy] Bluetooth radio not enabled for Dell Bluetooth Adaptor

Bug #160754 reported by brunes
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

This may be related to #156879, but the symptoms are quite different.

I have the built-in internal Dell bluetooth module on a D810 laptop. This module worked fine with 7.04, but in Gutsy (7.10), it does not work anymore. hciconfig reports the device, and says it is 'UP", but I can confirm from my PDA that there is no bluetooth radio present in the area. Furthermore, the 'Blue' light on my laptop is not on - this says to me that the bluetooth radio is not enabled even though the kernel for some reason thinks it is.

hcitool commands such as 'scan' all report no errors either to console or in dmesg - but they do nothing.

jasonk@zipedo ~ $ dmesg | grep -i blue
[ 16.388000] Bluetooth: Core ver 2.11
[ 16.388000] Bluetooth: HCI device and connection manager initialized
[ 16.388000] Bluetooth: HCI socket layer initialized
[ 16.436000] Bluetooth: HCI USB driver ver 2.9
[ 37.992000] Bluetooth: L2CAP ver 2.8
[ 37.992000] Bluetooth: L2CAP socket layer initialized
[ 38.080000] Bluetooth: RFCOMM socket layer initialized
[ 38.080000] Bluetooth: RFCOMM TTY layer initialized
[ 38.080000] Bluetooth: RFCOMM ver 1.8

jasonk@zipedo ~ $ hcitool dev
Devices:
        hci0 00:10:C6:37:64:AB

jasonk@zipedo ~ $ hciconfig
hci0: Type: USB
        BD Address: 00:10:C6:37:64:AB ACL MTU: 192:8 SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:9832 acl:0 sco:0 events:1013 errors:0
        TX bytes:625 acl:0 sco:0 commands:29 errors:0

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.