View previous topic :: View next topic |
Author |
Message |
DrKayBee Tux's lil' helper


Joined: 11 May 2004 Posts: 143 Location: Columbus, OH
|
Posted: Tue Jun 15, 2004 2:39 am Post subject: bluetooth dongle not registering |
|
|
Hi all,
I have followed the instructions at:
https://forums.gentoo.org/viewtopic.php?t=161129&highlight=bluetooth
in an attempt to install bluetooth on my gentoo box.
lsusb shows the bluetooth dongle attached to the usb port, but the hci utilities hcitool and hciconfig show no output.
I am running kernel 2.6.5-r1 (gentoo-dev-sources), udev and the usb 2.0 subsystem. I haven't yet tried to get it working under devfs or usb 1.1.
Any ideas?
KB |
|
Back to top |
|
 |
pakman Tux's lil' helper

Joined: 06 Jan 2004 Posts: 100
|
Posted: Tue Jun 15, 2004 4:15 pm Post subject: |
|
|
Coupla ideas, try it with all of the usb drivers loaded, ohci_hcd, uhci_hcd, ehci_hcd. Since moving to 2.6 I need all of them loaded for all my USB gadgets to work. Check you have the "bluetooth" & "hci-usb" modules loaded. Re-run /etc/init.d/bluetooth start and check in dmesg.
afaik all usb bluetooth dongles work the same way driver-wise so should work on loonix. |
|
Back to top |
|
 |
rvalles Tux's lil' helper

Joined: 19 Feb 2003 Posts: 121
|
Posted: Fri Jun 18, 2004 8:54 am Post subject: |
|
|
Same problem here. Haven't used Bluetooth for 2-3 weeks, and now it seems the dongle doesn't register. I load hci_usb (and it loads bluetooth as dependency) and start the init.d script. Everything seems fine, but there's no hci0, so neither hciconfig show nothing, nor does "hcitool scan" work (Device is not available: Success) |
|
Back to top |
|
 |
pakman Tux's lil' helper

Joined: 06 Jan 2004 Posts: 100
|
Posted: Fri Jun 18, 2004 4:49 pm Post subject: |
|
|
Does the dongle show up if you do lsusb? (emerge usbutils if ya don't have it)
I'd assume if so then the problems with the bluetooth modules rather than usb.
I get:
Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd
It might be worth trying a newer kernel, I seem to remember seeing bluetooth fixes in the last few changelogs. The homepage for it is http://www.bluez.org/ According to that page theres patches in kernel 2.6.7. Working here with kernel 2.6.6 and a cheap Origo dongle. |
|
Back to top |
|
 |
DrKayBee Tux's lil' helper


Joined: 11 May 2004 Posts: 143 Location: Columbus, OH
|
Posted: Fri Jun 18, 2004 5:40 pm Post subject: |
|
|
It shows up in lsusb - it's a D-link DBT-120, Broadcom chipset. It is said working with the bluez modules.
The bluetooth subsystem is also started, but I can't get a device at hci0.
I'm running 2.6.5 gentoo... which has all the bluetooth patches in it...
Don't know what to do beyond that. It did not even detect in the knoppix26 kernel.
...still out of ideas.... |
|
Back to top |
|
 |
kevquinn Retired Dev


Joined: 27 Jun 2003 Posts: 52
|
Posted: Fri Jun 18, 2004 6:19 pm Post subject: Are all modules built? |
|
|
I know it may be obvious, but do you have all the bluetooth modules built? Initially I only built the main bluetooth module and very little worked. Also you may want to try a more recent kernel; skip 2.6.6 as it consistently oops-panicked on my machine on bootup with the dongle present and any time I removed the dongle, but 2.6.7-rc3 is peachy for me (the panics appeared when I ditched devfs and swithed to udev - which might or might not be related, I changed other things at the same time!). I have a cheap belkin bluetooth dongle; I'd expect most such dongles to be pretty much the same inside.
Relevant kernel config options I have now are:
Code: |
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
# CONFIG_BT_HCIUART_BCSP_TXCRC is not set
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
|
i.e. pretty much everything on /proc/modules shows rfcomm, l2cap and hci_usb loaded as dependencies of bluetooth, so I'm only actually using a few of the modules at the moment - that might increase if I try bluetooth networking or other functions.
BTW if you're running KDE, emerge kdebluetooth from ~x86 gives a setup that does the desktop job well (so far...). Pairing, and copying stuff to/from the mobile phone works fine. |
|
Back to top |
|
 |
DrKayBee Tux's lil' helper


Joined: 11 May 2004 Posts: 143 Location: Columbus, OH
|
Posted: Sun Jun 20, 2004 5:14 am Post subject: |
|
|
Turns out, that there is some problem uploading the firmware for the blutonium driver to the dongle. As a workaround, I was able to upload the firmware via bluefw. (emerge bluez-bluefw). This has allowed the dongle and the phone to be registered.
Now looking for fun things to do with the phone.
KB
[/update]
The error message I was getting was bcm203x probe failed (-5). The work around is to download the bluez-bluefw package from www.bluez.org, and copy the firmware files BCM2033-FW.bin and BCM2033-MD.hex into the /usr/lib/hotplug/firmware/ folder. (got the idea on bluez.org)
Yes, I am using hotplug. Now when the dongle is plugged in, it registers properly and the firmware upload works correctly.
Can this be incorporated into the ebuild itself?
[/update*] |
|
Back to top |
|
 |
|