From: Graham Clifford <graham@vbbs.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] VMWare 5.0 and those timeout messages
Date: Thu, 01 Sep 2005 23:09:37 -0400 [thread overview]
Message-ID: <C67EA7517BB4704094D63F03A1C8536C0318C0@pluto.sfcomputing.local> (raw)
Hello,
I have been having a lot of trouble getting a Broadcom device working
properly under Fedora 4 (Kernel 2.6.11) in a VMWare 5.0 session. I was
wondering if anyone had managed to get this working? I found an article
in the archives from the beginning of the year with a similar problem
(see http://sourceforge.net/mailarchive/message.php?msg_id=10640453).
I get the following messages in my /var/log/messages file.
**************************************************
Sep 1 21:42:22 localhost hcid[2714]: Bluetooth HCIdaemon
Sep 1 21:42:22 localhost kernel: Bluetooth: Core ver2.7
Sep 1 21:42:22 localhost kernel: NET: Registeredprotocol family 31
Sep 1 21:42:22 localhost kernel: Bluetooth: HCIdevice and connection
manager initialized
Sep 1 21:42:22 localhost kernel: Bluetooth: HCIsocket layer initialized
Sep 1 21:42:39 localhost kernel: usb 1-1: new fullspeed USB device
using uhci_hcd and address 2
Sep 1 21:42:42 localhost kernel: Bluetooth: BroadcomBlutonium firmware
driver ver 1.0
Sep 1 21:42:42 localhost kernel: usbcore: registerednew driver bcm203x
Sep 1 21:42:42 localhost kernel: Bluetooth: HCI USBdriver ver 2.8
Sep 1 21:42:42 localhost kernel: usbcore: registerednew driver hci_usb
Sep 1 21:42:48 localhost kernel: usb 1-1: USBdisconnect, address 2
Sep 1 21:42:50 localhost kernel: usb 1-1: new fullspeed USB device
using uhci_hcd and address 3
Sep 1 21:42:51 localhost hcid[2714]: HCI dev 0registered
Sep 1 21:43:01 localhost hcid[2926]: Can't initdevice hci0: Connection
timed out (110)
**************************************************
hciconfig -a shows
**************************************************
[root@localhost ~]# hciconfig -a
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO
MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0
**************************************************
and lsusb shows
**************************************************
[root@localhost ~]# lsusb
Bus 001 Device 003: ID 0a5c:2001 Broadcom Corp.
Bus 001 Device 001: ID 0000:0000
**************************************************
I can provide /proc/bus/usb/devices if need be.
I've tried lots of different versions of bluez, and
the old bluefw....nothing seems to work!
Help!
Thank you kindly in advance
Graham
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-09-02 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 3:09 Graham Clifford [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-02 2:07 [Bluez-users] VMWare 5.0 and those timeout messages Clifford Graham
2005-09-03 4:30 ` Mark Rasmussen
2005-09-03 4:30 ` Mark Rasmussen
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=C67EA7517BB4704094D63F03A1C8536C0318C0@pluto.sfcomputing.local \
--to=graham@vbbs.com \
--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