USB Bluetooth Dongle not recognized
Hi,
I'm trying to get my Yakumo USB Bluetooth Dongle to work (the same dongle works on Suse 9.3 but doesn't on 10.0 now :confused: ). All bluez-packages are installed.... When I plug in the dongle /var/log/messages tells me Code:
Nov 11 18:41:10 linux kernel: usb 3-1: new full speed USB device using uhci_hcd and address 3 When I unplug the dongle I get a KBluetoothD message which says "Bluetooth adapter was unplugged".... hmm, why it recognize it when I unplug it !? Code:
inux:/home/heart # /etc/init.d/bluetooth status Code:
53: USB 00.0: 11500 Bluetooth Device Regards, Heart |
Exact same problem
I've got a belkin f8t003 ver 2 usb dongle. I get these lines in the messages log
Code:
Nov 25 19:22:51 linux hcid[15612]: HCI dev 0 unregistered Nov 25 19:22:51 linux kernel: usb 1-1: USB disconnect, address 2 Nov 25 19:22:57 linux kernel: usb 1-1: new full speed USB device using uhci_hcd and address 3 Nov 25 19:22:57 linux hcid[15612]: HCI dev 0 registered Nov 25 19:23:03 linux kernel: hci_cmd_task: hci0 command tx timeout It seems as hough the kbluetooth program stalls untill I remove the dongle, if you click the grey icon while the dongle is inserted, nothing happens until you remove the dongle. I also get three "Could not connect to sdp server" warnings that I used to get on Suse 9.3, but on that Suse the bluetooth got initialized right after the last warning. |
Hm, can't get it to work until now :(
...on Suse9.3 it worked too here (as said)! |
SuSE made considerable changes in the are of auto-mounting. When I first installed 10.0 there were some quirks with USB memory sticks. It was possible for Linux to remember a stick was plugged in but get confused about permissions. Removing the stick and plugging it back in brought everything into sync. It would appear that updates via SuSE watcher have fixed that problem. So I have two suggestions 1st have you been updating? 2nd will re-inserting after removal get it to work?
|
Quote:
re-inserted: 1000 times... :( |
Two things , Heart ,
Does the Light on Dongle Blinks , [ If it has Light ] Second, please , can you specify what are connecting to the system through Bluetooth Dongle ? You look fully familiar with Bluetooth Functioning in Linux. So if you can not sort it out then......... any way, I think i may help you if you illustrate a little more your problem........ Regards. |
Mine does, blinks that is.
|
@Be.Gurmeet.Be
I think I'm one little move away from goal... I've tried it in the console... - plugged in my usb bluetooth stick (light blinks on the stick) - then Code:
# hciconfig Code:
linux:/home/heart # hciconfig hci0 up Then I want to do the last step Code:
# rfcomm connect 0 00:0E:07:85:94:A3 1 Shouldn't come now the pin request?! So only one step left I think.. If you have an idea please let me know! Thanks |
I don't know if you have control over bluetooth timeouts. You might look at making timeouts longer. Its not beyond possible that the default connect timeout is too short.
|
Perhaps:
- make sure that rfcomm and l2cap are loaded as modules - make sure udev is running/enabled - tail -f /var/log/syslog - hcitool info 00:0E:07:85:94:A3 ... and post the log messages |
Hmmm, played again and again with the pin file and also in yast - bluetooth with secrets disabled and enabled it again, restartet bluetooth service.... and so on...
Then obex push (send file from pc) worked and also after some testing the obex ftp from konqueror worked. Now I also can make my rfcomm0 ..... The only thing which doesn't work is when I try to send a file from my phone to the pc the phone says "send" but at my pc I don't get a dialog which ask me how to store this file. So it goes to nirvana I think... As said from konqueror-obex-ftp I come to my phone folder structure and can copy files from handy to pc! |
Heart,
Bluetooth has protocols which are subject to the variability of software. Your phone may be the culprit or perhaps Linux needs to be a bit more forgiving of Bluetooth protocols. OpenSuSE may want to look into this. Why not report it as a potential bug. Excuse my curiosity, but are you a Brit? The UK is the only place I remember hearing a cell phone called a handy. |
...we say "Handy" in germany here ;)
|
dear heart,
so far as concern to the files which sent successfully to your System from Phone Check ; /var/lib/bluetooth Directory all the successfully sent files will be there. usually , Linux does not show any progress bar while file is being transferred to system. any thing else. regards.................... Just Explain, if any thing else you are find wrong with Linux. Be.Gurmeet.Be |
Quote:
Is there a config file where I can change this directory (for example that send files were transfered to my home directory)? |
Haven't tried to send a file from my phone, but everything seems to work now. As I suspected it was the kbluetoothd who stopped functioning. Just stop it before you insert the dongle, insert dongle, do a hciconfig hci0 up then restart kbluetoothd. Except for an error messge about device number in hcid.conf, everything seems to work fine:)
by the way, try out the remote controls in your k700, it now works as mouse input and everything;) |
...works now as it should with k700i here, boot pc, plugin usb bluetooth dongle, enable BT on k700i and I can browse/send files, use kmobiletools and so on...
The last thing what doesn't work is "paring".. When I browse to my k700i folders I have to allow this on the phone directly on every folder change :( Also when I send a file from k700i to the pc it is successfull but shouldn't be there a pin code request?! And when my friend sends a file to pc he get's this pin request dialog and a popup where he must select the folder where the file should be stored, why does this not work here :(? Thanks |
Bletooth BD Address remains 00:00:00:00:00:00 plz help
[root@smitdesk Blue]# hciconfig
hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN RX bytes:417 acl:0 sco:0 events:18 errors:0 TX bytes:319 acl:0 sco:0 commands:18 errors:0 [root@smitdesk Blue]# hci0 up bash: hci0: command not found [root@smitdesk Blue]# hciconfig hci0 up [root@smitdesk Blue]# hciconfig hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN RX bytes:417 acl:0 sco:0 events:18 errors:0 TX bytes:319 acl:0 sco:0 commands:18 errors:0 [root@smitdesk Blue]# hciconfig hci0 up [root@smitdesk Blue]# hciconfig -a hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN RX bytes:417 acl:0 sco:0 events:18 errors:0 TX bytes:319 acl:0 sco:0 commands:18 errors:0 |
anything missing here?
[root@smitdesk Blue]# rpm -qa|grep blue
bluez-utils-3.15-3mdv2008.0 gnome-bluetooth-0.9.1-1mdv2008.0 bluez-pin-0.30-6mdv2008.0 kdebluetooth-1.0-0.beta8.5mdv2008.0 libkdebluetooth0-1.0-0.beta8.5mdv2008.0 nautilus-sendto-bluetooth-0.12-3mdv2008.0 bluez-gnome-0.9-1mdv2008.0 bluez-firmware-1.2-3mdv2008.0 bluez-hcidump-1.40-1mdv2008.0 libbluez2-3.15-1mdv2008.0 [root@smitdesk Blue]# service bluetooth restart ERROR: Module rfcomm is in use [ OK ] ERROR: Module l2cap is in use by hidp,rfcomm Starting Bluetooth services: [ OK ] [root@smitdesk Blue]# hciconfig -a hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN RX bytes:1018 acl:0 sco:0 events:30 errors:0 TX bytes:614 acl:0 sco:0 commands:30 errors:0 |
Quote:
The end result is that you should take it back whence it came and get a new one. The long story is available at http://www.google.com |
All times are GMT -5. The time now is 03:59 PM. |