RE: DBT-120 Revision A/2

RE: DBT-120 Revision A/2

[Curtis Lehman]

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,

Curtis Lehman

Sr. Software Engineer
Air Cell, Inc
1172 Century Drive
Building B, Suite 280
Louisville, CO 80027
Direct: 303-379-0232
FAX: 303-379-0201
Email: clehman@aircell.com
www.aircell.com




 -----Original Message-----
From: 	Kieran S. Hagzan [mailto:ksh4250@hagzan.homelinux.org] 
Sent:	Tuesday, May 27, 2003 1:02 AM
To:	Curtis Lehman
Subject:	DBT-120 Revision A/2

Hello Sir:
	I am affiliated with the Laboratory for Applied Computing at
R.I.T. and we have recently purchased a number of D-Link DBT-120 Revision
A/2 USB Bluetooth dongles.  I have patched the kernel with marcel
holtman's kernel patch and have compiled-in all protocols.  When I do a
"cat /proc/bus/usb/devices | grep 'e0'", I get the following:

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=(none)
I:  If#= 1 Alt= 0 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=(none)
I:  If#= 1 Alt= 1 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=(none)
I:  If#= 1 Alt= 2 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=(none)
I:  If#= 1 Alt= 3 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=(none)
I:  If#= 1 Alt= 4 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=(none)
I:  If#= 1 Alt= 5 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=(none)

* an "lsmod" gives the following:
Module                  Size  Used by    Tainted: P
nvidia               1541536  18
ip6_tables             13464   0  (unused)
ip_conntrack           21728   0  (unused)
rfcomm                 34944   0  (unused)
bnep                   11000   0  (unused)
l2cap                  19244   1
dummy                   1212   0  (unused)
ipt_REJECT              2968   2  (autoclean)
iptable_filter          1740   1  (autoclean)
ip_tables              12824   2  [ipt_REJECT iptable_filter]
hci_usb                 7644   0  (unused)
bluez                  36516   0  [rfcomm bnep l2cap hci_usb]

* So yay, the USB subsystem has identified the device...
* I have also installed bluez-utils, bluez-libs, and bluez-bluefw.
* However, at this point when I say "hcitool scan" or "hciconfig hci0 up",
  I get the following:
"Device is not available.: Success"

** Could you either point me in the direction of a step that I have missed
or a step I am leaving out perhaps?? Any guidance would be greatly
appreciated.

We are testing the feasibility of a new ad-hoc network
security paradigm, and we wish to do it with real bluetooth devices to
generate an accurate simulation. We undoubtedly cannot access the protocol
stack on a Windows machine...big surprise...


Thank you so much!


-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

RE: DBT-120 Revision A/2

[Curtis Lehman]

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