RE: DBT-120 Revision A/2

["Curtis Lehman" <clehman@aircell.com>]

Glad to help. Good luck with your project. :)

- Curt

 -----Original Message-----
From: 	Kieran S. Hagzan [mailto:ksh4250@hagzan.homelinux.org] 
Sent:	Wednesday, May 28, 2003 8:20 AM
To:	Curtis Lehman
Cc:	Linux-Hotplug-Devel (E-mail); Bluez-Users (E-mail)
Subject:	RE: DBT-120 Revision A/2



On Tue, 27 May 2003, Curtis Lehman wrote:

> Hi Kieran,
>
> 	 I would download a handy little utility called usbview, http://www.kroah.com/linux-usb/. It makes looking at what the PC thinks is plugged into the USB ports a lot easier. Until I had the proper drivers installed, sometimes the system would see the dongle, but not properly identify it. I could tell it wasn't right by what usbview thought was plugged in. Once it was properly detected, usbview called the dongle a BCM2033 and said the manufacturer was BroadComm Corp.
> To get the D-Link to work, I simply was using the latest 9.0 Red Hat release with latest updates to all the BlueZ files you mentioned. I didn't actually recompile my kernel. To get the proper drivers the D-Link needs, I also had to update the hotplug driver to the latest version.  (http://sourceforge.net/projects/linux-hotplug/)
> You might also want to check out your /etc/Bluetooth/hcid.conf file. I edit mine a little to get the system to work. I ended up setting pairing mode to multi, but I am not really sure if this made any difference or what effect it had.
> Give the above changes a try. Until you get the usbview to properly identify the dongle, I wouldn't even worry about the hciconfig command. Let me know if this helps and were you get to. I will be glad to try and help some more if your still stuck.

Thank you very much. After installing USBView and updating HotPlug, the
only thing I had left to do was to determine which bus number and device
number were assigned to the dongle, and feed them  to bluefw. In my case,
the command was:

   bluefw usb 001/003

Now when I say hciconfig, I get the happy result of:

   hci0:   Type: USB
           BD Address: 00:80:C8:50:F4:52 ACL MTU: 377:10  SCO MTU: 16:0
           UP RUNNING PSCAN ISCAN
           RX bytes:63 acl:0 sco:0 events:7 errors:0
           TX bytes:278 acl:0 sco:0 commands:8 errors:0

And the hci_usb driver now powers the device at the USB core level:

   D:  Ver= 1.01 Clsà(unk. ) Sub\x01 Prot\x01 MxPSd #Cfgs=  1
   I:  If#= 0 Alt= 0 #EPs= 3 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb

I might add that according to Marcel Holtman, the bluez-kernel-2.3 release
is FAR out of date and any kernel versions 2.4.20 and lower NEED to be
patched to take full advantage of the protocol stack, there is no other
way apparently. I can't verify the integrity of this claim, of course, but
his patches did work in place of the bluez-kernel package. Personally, I was
using a RedHat 8 minimal install with most anything from GNU compiled from hand,
along with kernel 2.4.20 compiled by hand.


Thanks Again!!

-Kieran S. Hagzan
 System Administrator's Group

   Rochester Institute of Technology
   Rm. 3590 - Building 70 - R.I.T. -
   Golisano College of Computing and Information Sciences
   102 Lomb Memorial Drive
   Rochester, NY, 14623
   (585)-475-7969

 Send E-Mail To:
 ---------------
 HERE: <a href="mailTo:ksh4250@cs.rit.edu">Kieran S. Hagzan - Work</a><br>
  OR
 HERE: <a href="mailTo:ksh4250@hagzan.homelinux.org">Kieran S. Hagzan - Home</a><br>





-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel