Try running "hciconfig hci0 reset" and see if you can scan after that. My dell bluetooth started doing exactly what you describe when I upgraded my bluez to a more recent version. Too bad, I have to have this workaround in my local startup script and also in my resume from hibernation script. But lots of people are starting to have this problem so hopefully they will fix it soon.

Hamid MENOUAR wrote:

Dear bluez users,

In order to make my laptop (OS: Fedora Core 2) communicate with some bluetooth device through an ANYCOM Bluetooth USB Adapter, I have installed the Bluez packages (bluez-libs bluez-libs bluez-utils bluez-hcidump bluez-utils-cups).

But, when trying to detect nearby active bluetooth devices, using "hcitool scan" non of the devices are detected, wheras the same configuration works very well with windows.

so, that's what I get on my terminal:

>[root@localhost root]# hciconfig
>hci0:   Type: USB
>        BD Address: 00:16:38:CA:56:A8 ACL MTU: 1017:8 SCO MTU: 64:1
>        UP RUNNING
>        RX bytes:93 acl:0 sco:0 events:12 errors:0
>        TX bytes:296 acl:0 sco:0 commands:12 errors:0
>
>[root@localhost root]# hcitool scan
>Scanning ...
>Inquiry failed: Connection timed out

One more thing is that, when loading the bluez module it says that the module is not found

>[root@localhost root]# modprobe bluez

>FATAL: Module bluez not found.

It would be very much helpful if someone knows how to solve the problem.

Thanks so much in advance,
Menouar
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
  