From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Broadcomm usb dongle problems.
Date: Mon, 29 Nov 2004 02:32:17 +0100 [thread overview]
Message-ID: <1101691937.9527.3.camel@pegasus> (raw)
In-Reply-To: <E1CYXHQ-0006VU-6W@sc8-sf-mx2.sourceforge.net>
Hi,
> Well it looks like that from the all dongles in the world I bought the one
> that is have problems.
>
> I will appreciate any help with this issue.
>
> Here is the info:
>
> [root@anubis ~]# hciconfig -a
> hci0: Type: USB
> BD Address: 00:0C:55:FA:3E:21 ACL MTU: 377:10 SCO MTU: 16:0
> UP RUNNING
> RX bytes:159 acl:0 sco:0 events:23 errors:0
> TX bytes:837 acl:0 sco:0 commands:23 errors:0
> Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Can't read local name on hci0. Input/output error(5)
> [root@anubis ~]# hcid -n
> hcid[8179]: Bluetooth HCI daemon
> hcid[8179]: Starting security manager 0
> hcid[8181]: Can't set scan mode on hci0. Device or resource busy(16)
> hcid[8181]: Can't set auth on hci0. Device or resource busy(16)
> hcid[8181]: Can't set encrypt on hci0. Device or resource busy(16)
> hcid[8179]: Exit.
> [root@anubis ~]# lsusb
> Bus 003 Device 001: ID 0000:0000
> Bus 002 Device 006: ID 0a5c:3503 Broadcom Corp.
> Bus 002 Device 005: ID 0a5c:3502 Broadcom Corp.
> Bus 002 Device 004: ID 0a5c:2009 Broadcom Corp.
> Bus 002 Device 003: ID 0a5c:3535 Broadcom Corp.
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
this is the one that still has problems. What kernel are you using? If
the latest 2.6.10-rc2 or 2.6.9-mh4 are not working then someone needs to
send me one of these so I can take a closer look at the problem. The
dongle 0a5c:200a from Broadcom is working fine.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-11-29 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 13:07 [Bluez-users] State of snd-bt-sco Carlos Azevedo
2004-11-28 16:31 ` Brad Midgley
2004-11-28 17:52 ` Marcel Holtmann
2004-11-28 22:10 ` [Bluez-users] Broadcomm usb dongle problems Moran
2004-11-29 1:32 ` Marcel Holtmann [this message]
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=1101691937.9527.3.camel@pegasus \
--to=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox