From: Marcel Holtmann <marcel@holtmann.org>
To: ben4fun <ben_4_fun@freenet.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] can't establish a connection
Date: Tue, 17 Aug 2004 09:36:17 +0200 [thread overview]
Message-ID: <1092728177.31651.6.camel@pegasus> (raw)
In-Reply-To: <1092727197.12606.1.camel@localhost>
Hi Ben,
> I still cannot use my broadcom bluetooth dongle. It doesn't seem to be a
> usb relevant problem. (as far as I know, cause I'm a newbie).
>
> This is what I get when I plug my dongle.
>
> tail -f /var/log/messages | grep usb
>
> Aug 16 11:17:25 localhost kernel: usb 1-1: new full speed USB device
> using address 10
> Aug 16 11:17:27 localhost kernel: usb 1-1.1: new full speed USB device
> using address 11
> Aug 16 11:17:28 localhost kernel: hci_usb_isoc_rx_submit: hci0 isoc rx
> submit failed urb c1cb1014 err -90
> Aug 16 11:17:28 localhost kernel: hci_usb_isoc_rx_submit: hci0 isoc rx
> submit failed urb c1cb1014 err -90
> Aug 16 11:17:30 localhost kernel: usb 1-1.2: new full speed USB device
> using address 12
> Aug 16 11:17:31 localhost kernel: input: USB HID v1.11 Keyboard
> [0a5c:3502] on usb-0000:00:07.2-1.2
> Aug 16 11:17:32 localhost kernel: usb 1-1.3: new full speed USB device
> using address 13
> Aug 16 11:17:33 localhost kernel: input: USB HID v1.11 Mouse [0a5c:3503]
> on usb-0000:00:07.2-1.3
>
>
> lsusb
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 013: ID 0a5c:3503 Broadcom Corp.
> Bus 001 Device 012: ID 0a5c:3502 Broadcom Corp.
> Bus 001 Device 011: ID 0a5c:200a Broadcom Corp.
> Bus 001 Device 010: ID 0a5c:3535 Broadcom Corp.
> Bus 001 Device 001: ID 0000:0000
>
> I read your article Marcel Broadcom devices with bluetooth support but
> the command HCI_Reset, returned an error. Do you have a clue?
install a kernel where this problem is fixed.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-08-17 7:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 21:50 [Bluez-users] can't establish a connection ben4fun
2004-08-05 22:51 ` Marcel Holtmann
[not found] ` <1091747064.6143.25.camel@localhost>
2004-08-05 23:22 ` Marcel Holtmann
[not found] ` <1091748784.6143.28.camel@localhost>
2004-08-05 23:50 ` Marcel Holtmann
2004-08-06 0:16 ` Bc. Michal Semler
[not found] ` <1091809290.4570.9.camel@localhost>
2004-08-06 16:27 ` Bc. Michal Semler
2004-08-06 16:39 ` ben4fun
2004-08-09 21:40 ` Nicholas A. Preyss
2004-08-17 7:20 ` ben4fun
2004-08-17 7:36 ` Marcel Holtmann [this message]
2004-08-17 7:49 ` Bc. Michal Semler
2004-08-17 20:53 ` ben4fun
2004-08-17 21:42 ` Marcel Holtmann
2004-08-17 21:49 ` ben4fun
2004-08-18 7:37 ` Marcel Holtmann
[not found] ` <1092728742.12606.5.camel@localhost>
2004-08-17 8:01 ` 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=1092728177.31651.6.camel@pegasus \
--to=marcel@holtmann.org \
--cc=ben_4_fun@freenet.de \
--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