From: Michael Schmitt <tcwardrobe@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something
Date: Fri, 18 Nov 2011 17:17:06 +0100 [thread overview]
Message-ID: <4EC68502.6020407@gmail.com> (raw)
In-Reply-To: <20111118153652.GA3647@fusion.localdomain>
Am 18.11.2011 16:36, schrieb Johan Hedberg:
> Hi Michael,
>
> On Fri, Nov 18, 2011, Michael Schmitt wrote:
>> adrastea:~# hcitool dev
>> Devices:
>> hci0 11:11:11:11:11:11
>> adrastea:~# hciconfig
>> hci0: Type: BR/EDR Bus: USB
>> BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
>> UP RUNNING PSCAN ISCAN
>> RX bytes:1461 acl:0 sco:0 events:44 errors:0
>> TX bytes:697 acl:0 sco:0 commands:44 errors:0
>>
>> hci1: Type: BR/EDR Bus: USB
>> BD Address: 00:04:0E:8C:E2:93 ACL MTU: 120:20 SCO MTU: 24:5
>> DOWN
>> RX bytes:1086 acl:0 sco:0 events:39 errors:0
>> TX bytes:171 acl:0 sco:0 commands:39 errors:0
>>
>> adrastea:~# hciconfig hci1 up
>> Can't init device hci1: Connection timed out (110)
>> adrastea:~#
> I'm pretty sure we'll at least need to see the hcidump output for the
> initialization sequence of this adapter (i.e. start hcidump before
> calling hciconfig hci0 up) and show us the output. Which Bluetooth
> version does this adapter support and how old is it?
>
> Johan
I am not sure if this is the right version you were talking about, but
here it is (from the squeeze box):
mschmitt@sogo:~$ /usr/sbin/hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
UP RUNNING PSCAN
RX bytes:969 acl:0 sco:0 events:27 errors:0
TX bytes:361 acl:0 sco:0 commands:27 errors:0
Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'sogo-0'
Class: 0x4a0100
Service Classes: Networking, Capturing, Telephony
Device Class: Computer, Uncategorized
HCI Version: 1.2 (0x2) Revision: 0x1fe
LMP Version: 1.2 (0x2) Subversion: 0x1fe
Manufacturer: Integrated System Solution Corp. (57)
greetings
Michael
next prev parent reply other threads:[~2011-11-18 16:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 15:28 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something Michael Schmitt
2011-11-18 15:36 ` Johan Hedberg
2011-11-18 15:49 ` Michael Schmitt
2011-11-18 16:21 ` Johan Hedberg
2011-11-18 16:34 ` Michael Schmitt
2011-11-18 20:30 ` Johan Hedberg
2011-11-20 15:27 ` Michael Schmitt
2011-11-27 10:04 ` Michael Schmitt
2011-11-28 8:42 ` Andrei Emeltchenko
2011-11-21 8:57 ` Andrei Emeltchenko
2011-11-21 9:12 ` Andrei Emeltchenko
2011-11-21 9:13 ` Marcel Holtmann
2011-11-21 10:22 ` Andrei Emeltchenko
2011-11-21 13:03 ` Marcel Holtmann
2011-11-21 10:35 ` Johan Hedberg
2011-11-21 13:04 ` Marcel Holtmann
2011-11-21 15:21 ` Johan Hedberg
2011-11-18 16:17 ` Michael Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-18 13:26 Jörg Esser
2013-07-18 14:13 ` Marcel Holtmann
2013-07-19 6:26 ` Jörg Esser
2013-07-19 13:49 ` Marcel Holtmann
2013-07-19 16:20 ` Johan Hedberg
2013-07-22 7:10 ` Jörg Esser
2013-07-22 14:22 ` Marcel Holtmann
2013-07-23 23:39 ` Johan Hedberg
2013-07-25 9:10 ` Jörg Esser
2013-07-25 10:55 ` Gustavo Padovan
2013-07-25 14:51 ` Marcel Holtmann
2013-07-25 14:40 ` 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=4EC68502.6020407@gmail.com \
--to=tcwardrobe@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).