You are not logged in.
Pages: 1
Topic closed
Hallo,
Well. I can't get bluetooth to work. I have 3 different Bluetooth Dongles to test. lsusb lists them like this:
Bus 001 Device 027: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 026: ID 057c:3800 AVM GmbH BlueFRITZ! Bluetooth Stick
Bus 002 Device 014: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)2 Obviously have the same chip. On my fathers Fedora box all these dongles work. So I started the bluetooth daemon. I connected all 3 sticks and this is what my messages.log tells me:
May 25 18:33:57 aseria hcid[30513]: Bluetooth HCI daemon
May 25 18:33:57 aseria hidd[30515]: Bluetooth HID daemon
May 25 18:34:06 aseria usb 2-9: new full speed USB device using ohci_hcd and address 15
May 25 18:34:07 aseria usb 2-9: configuration #1 chosen from 1 choice
May 25 18:34:08 aseria usb 1-2.4: new full speed USB device using ehci_hcd and address 29
May 25 18:34:08 aseria usb 1-2.4: configuration #1 chosen from 1 choice
May 25 18:34:13 aseria usb 1-2.3: new full speed USB device using ehci_hcd and address 30
May 25 18:34:13 aseria usb 1-2.3: configuration #1 chosen from 1 choiceThey are not recognized. hcid should detect them according to http://wiki.archlinux.org/index.php/Bluetooth
After searching the forums the solution for others was to turn on dbus. But my dbus is on.
lsmod | grep blue:
bluetooth 56484 8 hidp,hci_vhci,hci_uart,bpa10x,bfusb,rfcomm,l2cap,hci_usbhcitool lists no available devices. What am I missing? Someone has an idea?
Stefan
Last edited by Noneus (2008-05-25 19:42:10)
Offline
Could you post the output of "hciconfig"?
My blog: blog.marcdeop.com
Jabber ID: damnshock@jabber.org
Offline
[root@aseria bluetooth]# hciconfig
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
hci1: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
hci2: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
[root@aseria bluetooth]# hcitool dev
Devices:Hmm. Do I need to power them on? If I only connect one, it doesn't work too btw.
UPDATE: hciconfig hci0 up did the job. thanks for the hint.
Last edited by Noneus (2008-05-25 19:41:52)
Offline
Hello,
I have the same issue, I can't get my hands-free kit to work. I want to use it with skype or whatever, but when I try to connect it, i've got:
[bluetooth]# connect 0C:E0:E4:3A:D6:ED
Attempting to connect to 0C:E0:E4:3A:D6:ED
[CHG] Device 0C:E0:E4:3A:D6:ED Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 0C:E0:E4:3A:D6:ED Connected: no
[bluetooth]# info 0C:E0:E4:3A:D6:ED
Device 0C:E0:E4:3A:D6:ED
Name: PLT_ML20
Alias: PLT_ML20
Class: 0x200404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)I did your manipulation, and I have
`--> sudo modprobe rfcomm
`--> sudo rfcomm bind rfcomm0 0C:E0:E4:3A:D6:ED
`--> ls /dev |grep rfcomm
rfcomm0But I can't get it to work as an audio device, it still make when I try to connect it:
[bluetooth]# connect 0C:E0:E4:3A:D6:ED
[CHG] Device 0C:E0:E4:3A:D6:ED Connected: yes
[CHG] Device 0C:E0:E4:3A:D6:ED Connected: nowhat am I doing wrong?
Thanks in advance ![]()
Offline
Offline
Pages: 1
Topic closed