From: Alastair Tse <liquidx@gentoo.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian
Date: Fri, 28 Jul 2006 00:18:19 +0100 [thread overview]
Message-ID: <1154042299.16913.6.camel@localhost> (raw)
Hi,
I'm also experiencing the same behaviour as Felix with a Belkin dongle
(Broadcom) with bluez-libs-3.2, bluez-utils-3.2. This is where ISCAN is
not set even though it is enabled in hcid.conf. I've compiled from
source on a Gentoo Linux box.
One additional thing that I would like to add is that I see this in my
syslog:
Jul 28 00:10:15 qoo hcid[23009]: HCI dev 0 registered
Jul 28 00:10:15 qoo hcid[23009]: Device hci0 has been added
Jul 28 00:10:15 qoo hcid[23009]: Register path:/org/bluez/hci0
fallback:0
Jul 28 00:10:15 qoo hcid[23009]: HCI dev 0 up
Jul 28 00:10:15 qoo hcid[23009]: Starting security manager 0
Jul 28 00:10:16 qoo hcid[23009]: Can't write inquiry mode for hci0:
Connection timed out (110)
If I use Felix's workaround by enabling ISCAN using 'hciconfig hci0
piscan' after the device is up, that error message about inquiry mode
does not come up.
Here is my hciconfig -a before using the workaround 'hciconfig hci0
piscan':
liquidx@qoo /usr/portage $ hciconfig -a
hci0: Type: USB
BD Address: 00:03:C9:2D:3E:8F ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING PSCAN
RX bytes:408 acl:0 sco:0 events:18 errors:0
TX bytes:320 acl:0 sco:0 commands:18 errors:0
Features: 0xff 0xfd 0x05 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'qoo'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing, Object
Transfer, Audio
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x2 LMP Ver: 1.1 (0x1) LMP Subver:
0x1007
Manufacturer: Broadcom Corporation (15)
Hope this helps with nailing down the problem.
Cheers,
Alastair
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2006-07-27 23:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 23:18 Alastair Tse [this message]
2006-07-28 1:32 ` [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian Marcel Holtmann
2006-07-28 9:43 ` Alastair Tse
2006-07-29 12:58 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 10:40 Felix Homann
2006-07-27 10:43 ` Marcel Holtmann
2006-07-27 10:58 ` Felix Homann
2006-07-27 11:04 ` Marcel Holtmann
2006-07-29 12:26 ` Felix Homann
2006-07-29 12:42 ` Marcel Holtmann
2006-07-27 20:08 ` Felix Homann
2006-07-28 1:20 ` Marcel Holtmann
2006-07-28 9:00 ` Felix Homann
2006-07-28 9:09 ` Marcel Holtmann
2006-07-28 9:28 ` Felix Homann
2006-07-28 9:38 ` Marcel Holtmann
2006-07-28 10:03 ` Felix Homann
2006-07-28 10:06 ` Marcel Holtmann
2006-07-28 10:14 ` Felix Homann
2006-07-28 10:33 ` Marcel Holtmann
2006-07-28 10:46 ` Felix Homann
2006-07-28 10:51 ` Marcel Holtmann
2006-07-28 10:40 ` hugues
2006-07-28 11:07 ` Felix Homann
2006-07-28 15:00 ` Felix Homann
2006-07-28 15:07 ` Marcel Holtmann
2006-07-29 12:11 ` Felix Homann
2006-07-29 12:33 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1154042299.16913.6.camel@localhost \
--to=liquidx@gentoo.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.