public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Shepherd <robshep@informatics.bangor.ac.uk>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Rob is an idiot [ was: No communication with USB BT device ]
Date: Sun, 20 Jun 2004 14:09:50 +0100	[thread overview]
Message-ID: <40D58C9E.5010001@informatics.bangor.ac.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]

marcel wrote:

> Hi Rob,
> 
> 
>>> No HCI connection is possible with my Belkin Bluetooth module. (CSR chip)
>>> 
>>> __System__
>>> 
>>> Linux kernel 2.6.7
>>> 
>>> bluez-libs-2.7
>>> bluez-utils-2.7
>>> bluez-pin-0.23
>>> bluez-hcidump-1.8
>>> 
>>> __output__
>>> 
>>> $ dmesg | grep -i usb
>>> sbcore: registered new driver usbfs
>>> usbcore: registered new driver hub
>>> USB Universal Host Controller Interface driver v2.2
>>> uhci_hcd 0000:00:07.2: Intel Corp. 82371AB/EB/MB PIIX4 USB
>>> uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
>>> hub 1-0:1.0: USB hub found
>>> usbcore: registered new driver usblp
>>> drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
>>> Initializing USB Mass Storage driver...
>>> usbcore: registered new driver usb-storage
>>> USB Mass Storage support registered.
>>> usbcore: registered new driver usbhid
>>> drivers/usb/input/hid-core.c: v2.0:USB HID core driver
>>> usb 1-1: new full speed USB device using address 2
>>> Bluetooth: HCI USB driver ver 2.6
>>> usbcore: registered new driver hci_usb
>>> 
>>> __Order of events__
>>> 
>>> Boot system
>>> insert dongle [no hotplug system running]
>>> modprobe hci_usb
>>> /etc/init.d/bluetooth start [HIDP complains (ignoring)]
>>> 
>>> hciconfig shows...[no device params read from device]
>>> 
>>> 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:6 acl:0 sco:0 commands:2 errors:0
>>> 
>>> hciconfig hci0 up times out.
>>> 
>>> hcidump show a hci_rlsf command but no response from chip.
>>> 
>>> This device works fine with Widcomm drivers/stack/application
>>> 
>>> when same machine is booted into windows XP (shudder)
>>> 
>>> Where might I be going wrong, What else could I try?
> 
> 
> what does /proc/bus/usb/devices and lspci say?
> 
> Regards
> 
> Marcel

Sorry about this problem, It turns out the machine  I was logging in to was actually linux 
running in a VMware system on WinXP.

I discovered this when lspci showed a VMWare IDE Bus.

I've since got hold of the machine, Rsync'd the linux off VMware and onto a native 
partition and it works fine..

At least now you know it won't work with VMWare 4.0

sorry again

keep up the good work

Rob



-- 
/**
  *	Rob Shepherd,
  *	University Of Wales, Bangor,
  *	School of Informatics,
  *	Dean Street,
  *	Bangor,
  *	Gwynedd, UK     /\  /\
  * 	LL57 1UT       /  \/  \ /\
  * 	--------------/---/    \--\----
  *
  *	robshep@informatics.bangor.ac.uk
  *
  * 	+44 (0) 1248 38 27
  */

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3230 bytes --]

                 reply	other threads:[~2004-06-20 13:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40D58C9E.5010001@informatics.bangor.ac.uk \
    --to=robshep@informatics.bangor.ac.uk \
    --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