Internal laptop bluetooth device not detected on dell Inspiron 1545

Bug #342025 reported by kdawgud on 2009-03-12
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Undecided
Unassigned

Bug Description

Broadcom Bluetooth device on Dell Inspiron 1545 is not detected in Jaunty. I previously tried the 8.10 live cd and thought it found the device (though I'm not sure - didn't use it. I'll try it again later).

lspci and dmesg are attached.

ubuntu@ubuntu:~$ hcitool dev
Devices:

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:27:53 UTC 2009 x86_64 GNU/Linux

kdawgud (kleber) wrote :
kdawgud (kleber) wrote :
description: updated
kdawgud (kleber) wrote :
kdawgud (kleber) on 2009-03-13
description: updated
Peter Antoniac (pan1nx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in bluez.

For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

Mario Limonciello (superm1) wrote :

Are you dual booting this system? Is the device enabled in Windows? It seems a high percentage of the Dell bluetooth adapters must not be disabled in Windows for them to function in Linux.

kdawgud (kleber) wrote :

Yes, I am dual booting. I booted back into windows to ensure bluetooth is turned on, and its still not recognized. I am running Jaunty Alpha 6 64-bit now, btw (no change - still not detected).

kdawgud (kleber) wrote :

I seem to have gotten the internal bluetooth adapter working on my laptop. Initially, I could not get my laptop to find the phone. However, I did finally get my phone to find the laptop using the kde bluetooth controlling software. This bug can be closed.

Peter Antoniac (pan1nx) wrote :

This bug report is being closed due to your last comment regarding this being fixed. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Thank you and have a nice day...

Peter Antoniac (pan1nx) wrote :

This bug report is being closed due to your last comment regarding this being fixed.

Changed in bluez (Ubuntu):
status: New → Invalid
celiapgt (sixxties0207) wrote :

Although this bug report is closed, I want to say that I have a Dell Inspiron 1545 with Broadcom Bluetooth device not detected. I installed kbluetooth4 as kdawgud said, but in my case I had no luck. The dev is not detected:

$ sudo hid2hci
Switching device 413c:8162 to HCI mode was successful

$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 04d9:0499 Holtek Semiconductor, Inc.
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 05ca:180a Ricoh Co., Ltd
Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 413c:8162 Dell Computer Corp.
Bus 003 Device 003: ID 413c:8161 Dell Computer Corp.
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

It's not there. However, the kernel knows about it:

$ dmesg | grep Bluetooth
[ 0.596009] Bluetooth: Core ver 2.13
[ 0.596020] Bluetooth: HCI device and connection manager initialized
[ 0.596020] Bluetooth: HCI socket layer initialized
[ 3.293890] Bluetooth: L2CAP ver 2.11
[ 3.293892] Bluetooth: L2CAP socket layer initialized
[ 3.293894] Bluetooth: SCO (Voice Link) ver 0.6
[ 3.293896] Bluetooth: SCO socket layer initialized
[ 3.293930] Bluetooth: RFCOMM socket layer initialized
[ 3.293937] Bluetooth: RFCOMM TTY layer initialized
[ 3.293938] Bluetooth: RFCOMM ver 1.10
[ 15.255648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.255652] Bluetooth: BNEP filters: protocol multicast

celiapgt (sixxties0207) wrote :

Forgot to say that I am using Ubuntu Jaunty:

$ cat /etc/issue
Ubuntu 9.04 \n \l
$ uname -a
Linux XENA 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009 i686 GNU/Linux

Peter Antoniac (pan1nx) wrote :

Thanks for the updates! I reopened the bug since it seems to be there. I don't know that platform so, I cannot say wheter is in the usb/hal/u-dev or in the kernel... Marked it as new, perhaps someone can check it more closely...

Changed in bluez (Ubuntu):
status: Invalid → New
description: updated
Mario Limonciello (superm1) wrote :

With Ubuntu 9.04 the hid2hci command should automatically be handling this. Make sure you have the latest bluez updates, and then try to run

$ sudo hid2hci --tohci

You should hopefully have the device on the bus after that.

Changed in bluez (Ubuntu):
status: New → Incomplete
Mario Limonciello (superm1) wrote :

Make sure bluez is fully updated and then run this command:

$sudo hid2hci --tohci

See if the device is on your bus after that.

celiapgt (sixxties0207) wrote :

@Mario
I checked and bluez is installed with the latest update. Then I sudo hid2hci as you suggested. Then I did sudo lsusb and the output does not indicate any Bluetooth device:

sudo hid2hci --tohci
Switching device 413c:8162 to HCI mode was successful
celita@XENA:~$ sudo lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 04d9:0499 Holtek Semiconductor, Inc.
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 05ca:180a Ricoh Co., Ltd
Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 413c:8162 Dell Computer Corp.
Bus 003 Device 003: ID 413c:8161 Dell Computer Corp.
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

My laptop bluetooth device is not detecting any other Bluetooth pair device elsewhere...

celiapgt (sixxties0207) wrote :

This is what I get from dmesg:

$ sudo dmesg | grep Bluetooth
[ 0.600009] Bluetooth: Core ver 2.13
[ 0.600020] Bluetooth: HCI device and connection manager initialized
[ 0.600020] Bluetooth: HCI socket layer initialized
[ 3.337895] Bluetooth: L2CAP ver 2.11
[ 3.337896] Bluetooth: L2CAP socket layer initialized
[ 3.337899] Bluetooth: SCO (Voice Link) ver 0.6
[ 3.337900] Bluetooth: SCO socket layer initialized
[ 3.337935] Bluetooth: RFCOMM socket layer initialized
[ 3.337941] Bluetooth: RFCOMM TTY layer initialized
[ 3.337943] Bluetooth: RFCOMM ver 1.10
[ 15.166854] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.166857] Bluetooth: BNEP filters: protocol multicast

Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions