| View previous topic :: View next topic |
| Author |
Message |
joefish Guru


Joined: 27 Jan 2004 Posts: 316 Location: New Zealand
|
Posted: Mon Jun 13, 2011 11:33 am Post subject: Bluedevil help, please! |
|
|
Trying to get bluetooth working for the umpteenth time, here's where I'm at:
KDE 4.6.4 and latest Bluedevil (1.1-r2).
Under "configure bluetooth" my bluetooth usb-dongle is detected, and there's a red box saying "Your default bluetooth adaptor is not visible for remote devices." If I click on "fix it", the box goes away, but as soon as I go back to this screen, the red box is back. Selecting this makes no difference to "discoverable" in the context menu from the system tray. I can tick this box however, and it stays ticked (but the above red box still appears in the config box).
My phone (HTC Desire) isn't detected by Bluedevil either from Dolphin or within Bluedevil's own scan for devices section. My phone can't detect my PC. Yes, my phone is working because I can detect and pair with other devices.
/etc/init.d/bluetooth is started.
The USB dongle works with Fedora without issue.
Any help is appreciated. |
|
| Back to top |
|
 |
Herring42 Guru


Joined: 10 Mar 2004 Posts: 373 Location: Buckinghamshire
|
Posted: Mon Jun 13, 2011 12:04 pm Post subject: |
|
|
You are not alone! My previously working adaptor is also now not detected.  _________________ "The problem with quotes on the internet is that it is difficult
to determine whether or not they are genuine." -- Abraham Lincoln |
|
| Back to top |
|
 |
billium Apprentice

Joined: 22 Mar 2003 Posts: 185
|
Posted: Wed Jun 15, 2011 9:45 pm Post subject: |
|
|
I wonder if you are affected by a possible bug mentioned here
http://www.spinics.net/lists/linux-bluetooth/msg13043.html.
I am not using bluedevil, but on my PC with a TDK adapter had the "Can't init device hci0: Invalid argument (22)" that he talks of, and his cure worked, but on my Laptop I had no problems.
Just in case the link disappears, comment out line 521
| Code: | | hci_setup_event_mask(hdev); |
in net/bluetooth/hci_event.c then recompile kernel. |
|
| Back to top |
|
 |
joefish Guru


Joined: 27 Jan 2004 Posts: 316 Location: New Zealand
|
Posted: Thu Jun 16, 2011 5:06 am Post subject: |
|
|
This is what I'm getting from the command line:
| Code: | snap ~ # hcitool dev
Devices:
hci0 00:1F:81:00:02:50
snap ~ # hcitool scan
Scanning ...
Inquiry failed: Connection timed out
|
|
|
| Back to top |
|
 |
billium Apprentice

Joined: 22 Mar 2003 Posts: 185
|
Posted: Thu Jun 16, 2011 8:18 am Post subject: |
|
|
I looks like a different error then, but it may be worth trying the comment out idea as it is quick and easy to undo.
It may help Herring42 though.
What kernel are you on? |
|
| Back to top |
|
 |
joefish Guru


Joined: 27 Jan 2004 Posts: 316 Location: New Zealand
|
Posted: Thu Jun 16, 2011 8:57 am Post subject: |
|
|
I'm running 2.6.34-gentoo-r6 (yeah, a little old), and that line doesn't exist anywhere in my copy of that file  |
|
| Back to top |
|
 |
Herring42 Guru


Joined: 10 Mar 2004 Posts: 373 Location: Buckinghamshire
|
Posted: Thu Jun 16, 2011 9:45 am Post subject: |
|
|
Sadly, no help:
| Code: |
path :: ~ %% hcitool dev
Devices:
path :: ~ %% hcitool scan
Device is not available: No such device
|
_________________ "The problem with quotes on the internet is that it is difficult
to determine whether or not they are genuine." -- Abraham Lincoln |
|
| Back to top |
|
 |
billium Apprentice

Joined: 22 Mar 2003 Posts: 185
|
Posted: Fri Jul 22, 2011 8:14 pm Post subject: |
|
|
the bug I mentioned above seems to be cleared with Kernel 3.  |
|
| Back to top |
|
 |
|