From: Alex <welpan@gmx.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Error message
Date: Fri, 21 May 2004 20:51:07 +0200 [thread overview]
Message-ID: <200405212051.07773.welpan@gmx.de> (raw)
In-Reply-To: <1085161340.22191.32.camel@pegasus>
Am Freitag, 21. Mai 2004 19:42 schrieben Sie:
> Hi Alex,
>
> > > there is no CSR chip in this dongle.
> >
> > KMelektronik cheat, thats not fine.
>
> yes they did. Where do you bought it? If the error still exists after
> disabling SCO support I must try to get one of these.
>
> > > What is the content of /proc/bus/usb/devices with the dongle attached?
> >
> > E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> > E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> > I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> > I: If#= 1 Alt= 1 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=hci_usb
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> > I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> > I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> > I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> > I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>
> You missed some information at the top.
>
> > > > Kernel with Bluez-modules and USB drivers
> > >
> > > Use patch-2.6.6-mh1 to prevent some USB related bugs.
> >
> > I use the patch ( I did it like the description), so that was my last
> > hope to find the error by myself
>
> If you already use 2.6.6-mh1 then it is good to say that ;)
>
> However disable CONFIG_BT_HCIUSB_SCO and try again.
That was it, the dongle is running.
Thank you very much for your help.
Best Regards
Alex
next prev parent reply other threads:[~2004-05-21 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 14:11 [Bluez-users] Error message Alex
2004-05-21 16:32 ` Michal Semler
2004-05-21 16:36 ` Marcel Holtmann
[not found] ` <200405211909.59769.welpan@gmx.de>
2004-05-21 17:26 ` Marcel Holtmann
2004-05-21 17:40 ` Alex
2004-05-21 17:42 ` Marcel Holtmann
2004-05-21 18:51 ` Alex [this message]
2004-05-21 19:20 ` Marcel Holtmann
2004-05-24 22:09 ` Alex
2004-05-24 23:01 ` Marcel Holtmann
2004-05-25 12:10 ` Alexander Berger
2004-05-25 12:10 ` Alexander Berger
2004-05-21 18:05 ` Simon Huggins
2004-05-21 17:25 ` Nicholas A. Preyss
2004-05-21 17:28 ` Alex
2004-05-21 17: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=200405212051.07773.welpan@gmx.de \
--to=welpan@gmx.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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