From: Marcel Holtmann <marcel@holtmann.org>
To: "Jörg Esser" <jackfritt@boh.de>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something
Date: Thu, 18 Jul 2013 07:13:33 -0700 [thread overview]
Message-ID: <36A79410-3FA3-408F-BA16-6A30568A7035@holtmann.org> (raw)
In-Reply-To: <51E7ED11.7010103@boh.de>
Hi Joerg,
> don´t know if it is wrong to post under the same topic which is more than one year old.
> Ref to it is here.
> http://www.spinics.net/lists/linux-bluetooth/msg18763.html
> There was never an answer to the latest question from Michael if there will be a solution.
>
> I also tried to get this to run with my latest kernel 3.10 under debian 7 without success.
> Will there be a solution or should I open my real trashbin?(other sticks are working so far for me) :)
>
> Let me know if you need more info´s on that.
>
> Thx,
> Joerg
>
> My syslog says:
> Jul 18 15:11:10 debian-capi kernel: [ 64.808373] usb 1-3: new full-speed USB device number 5 using ohci_hcd
> Jul 18 15:11:10 debian-capi kernel: [ 65.277828] usb 1-3: New USB device found, idVendor=057c, idProduct=3800
> Jul 18 15:11:10 debian-capi kernel: [ 65.277834] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> Jul 18 15:11:10 debian-capi kernel: [ 65.277838] usb 1-3: Product: Bluetooth Device
> Jul 18 15:11:10 debian-capi kernel: [ 65.277841] usb 1-3: Manufacturer: Bluetooth Device
> Jul 18 15:11:10 debian-capi kernel: [ 65.277844] usb 1-3: SerialNumber: CC1C8D0E0400
> Jul 18 15:11:10 debian-capi bluetoothd[2199]: HCI dev 0 registered
> Jul 18 15:11:10 debian-capi bluetoothd[2199]: Listening for HCI events on hci0
> Jul 18 15:11:11 debian-capi bluetoothd[2894]: Can't init device hci0: Invalid request code (56)
any chance you can run btmon and see if we have failing HCI commands during the setup phase.
> debian-capi:~# lsusb -v -d 057c:3800
Can you include /sys/kernel/debug/usb/devices from this device.
Regards
Marcel
next prev parent reply other threads:[~2013-07-18 14:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 13:26 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something Jörg Esser
2013-07-18 14:13 ` Marcel Holtmann [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-11-18 15:28 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
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=36A79410-3FA3-408F-BA16-6A30568A7035@holtmann.org \
--to=marcel@holtmann.org \
--cc=jackfritt@boh.de \
--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 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.