Didn’t work. I’ll check for time outs.
Weird thing is, this device worked with a different USB Hub …
On 3/03/2011 11:14 AM, William Pretty Security Inc wrote:
Tried ‘hcitool dev’
All I got back was:
Followed by nothing L No devices listed …
Had similar trouble with dlink bluetooth usb dongles.
The way around it was to have an init script
and insert a delay and then call hcid/bluetoothd
Haven't need it with 2.6.36.
Are you getting any boot messages on hci or bluetooth time outs ?
Try running bluetoothd (as root or sudo) and see if hcitool can then find the device
UTS CRICOS Provider Code:
DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology, Sydney. Before opening any attachments, please check them for viruses and defects.
found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.872 / Virus Database: 271.1.1/3475 - Release Date: 03/02/11 14:34:00