public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stuart Pook <kernel6org@pook.es>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez/git + 2.6.27-rc8 + Belkin F8T017 -> Can't read class of adapter
Date: Mon, 06 Oct 2008 22:45:44 +0200	[thread overview]
Message-ID: <1223325944.11272.227.camel@violet.holtmann.net> (raw)
In-Reply-To: <48EA7770.30307@pook.es>

Hi Stuart,

> > Why your application gives up prematurely is still unclear to me.
> 
> I must admit this what interests me most.
> 
> I wondered if it was by old USBBT100 Bluetooth dongle that is causing
> my problems. I thus bought a Belkin F8T017 (Bluetooth v2.1 Class I).
> It works even less than my old Linksys USBBT100.
> 
> bluetoothd (from git) says:
> 
> bluetoothd[3517]: HCI dev 0 up
> bluetoothd[3517]: Can't read class of adapter on /org/bluez/hci0: Input/output error (5)

loas btusb or hci_usb with reset=1 and show me the content
of /proc/bus/usb/devices to add a permanent quirk.

Regards

Marcel



  reply	other threads:[~2008-10-06 20:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 21:03 bluez-4.9 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect: Operation not permitted Stuart Pook
2008-09-30 23:26 ` David Sainty
2008-10-01 17:30   ` Stuart Pook
2008-10-04  3:47     ` Luiz Augusto von Dentz
2008-10-04 11:25       ` Stuart Pook
2008-10-04 11:51         ` Marcel Holtmann
2008-10-04 23:24           ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect(): Connection timed out (110) Stuart Pook
2008-10-05 17:50             ` Johan Hedberg
2008-10-05 19:17               ` Stuart Pook
2008-10-05 20:07               ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> Invalid read of size 4 Stuart Pook
2008-10-06  8:47                 ` Johan Hedberg
2008-10-06 10:52                   ` Johan Hedberg
2008-10-06 18:38                     ` Stuart Pook
2008-10-06 19:56                     ` Stuart Pook
2008-10-06 20:31                       ` Johan Hedberg
2008-10-06 20:56                         ` bluez/git + 2.6.27-rc8 + SCO headset -> SIGSEGV Stuart Pook
2008-10-06 21:03                           ` Marcel Holtmann
2008-10-06 21:10                             ` Stuart Pook
2008-10-06 21:21                               ` Marcel Holtmann
2008-10-06 22:40                                 ` bluez/git + 2.6.27-rc8 + bluetoothd " Stuart Pook
2008-10-07  5:34                                   ` Johan Hedberg
2008-12-06 12:15                                     ` bluez-4.22 + twinkle -> Unable to lock headset Stuart Pook
2008-12-08 18:42                                       ` Luiz Augusto von Dentz
2008-12-09 12:23                                         ` sreevani medhahal
2008-10-06 20:39                   ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> Can't read class of adapter Stuart Pook
2008-10-06 20:45                     ` Marcel Holtmann [this message]
2008-10-06 21:55                       ` Stuart Pook
2008-10-06 22:38                         ` Marcel Holtmann
2008-10-06 23:17                           ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> works with reset=1 Stuart Pook

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=1223325944.11272.227.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=johan.hedberg@gmail.com \
    --cc=kernel6org@pook.es \
    --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