Thanks.
Max
At 05:43 AM 6/26/2003, Steve Dillon wrote:
>On Wed, 2003-06-25 at 09:20, Marcel Holtmann wrote:
>
>> send me a patch for the README file of bluez-bluefw and I will apply it.
>>
>> Regards
>>
>> Marcel
>Here's a readme for the bluefw package. CC'ing the group in case somebody is
>searching through it.
>
>Steve
>
>
>
>Before you start with this package you will want to have enabled bluetooth
>support in the
>kernel and have installed at least the bluez-utils and bluez-libs packages.
>
>BUILDING:
>
>To build run the 'standard' build commands:
>>./configure
>>make
>>su
>>make-install
>
>Quick Installation Test: (Most devices that use this driver are
>usb dongles.. so I'll refer to the bluetooth device as a dongle
>from now on). Plug the dongle in the USB port and:
>>[root@rhat hotplug]# /sbin/hciconfig
>>hci0: Type: USB
>> BD Address: 00:03:C9:2B:9E:2E ACL MTU: 377:10 SCO MTU: 16:0
>> UP RUNNING PSCAN ISCAN
>> RX bytes:93 acl:0 sco:0 events:12 errors:0
>> TX bytes:296 acl:0 sco:0 commands:12 errors:0
>
>If you get this display (with a valid BD Address line), You're all set, bluez
>has found
>your device and is ready for you to configure what you want to use the device
>for.
>
>
>If you get this:
>>[root@rhat hotplug]# /sbin/hciconfig
>>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:0 acl:0 sco:0 commands:0 errors:0
>Note: No valid BD Address. Then chances are that the hcid daemon is not
>running.
>To check:
>> ps -aux | grep hcid
>To start on redhat:
>> /etc/init.d/bluetooth start
>
>
>OTHER PROBLEMS:
>These usually stem from problems with the hotplug scripts package. If you are
>still having
>problems get the latest from http://linux-hotplug.sourceforge.net/. You can
>check
>your version via:
>>[root@rhat steved]# rpm -q hotplug
>>hotplug-2003_05_01-1
>
>
>My RedHat 9.0 had an older hotplug rpm (2002_04_01-17) and I had problems with
>rpm -U since
>there is now two packages. You probably want to backup your /etc/hotplug
>directory before
>continuing. Here's what I did on RedHat, other distributions will vary.
>>[root@rhat steved]# rpm -e hotplug --nodeps
>>[root@rhat palm]# rpm -i hotplug-base-2003_05_01-1.noarch.rpm
>>warning: hotplug-base-2003_05_01-1.noarch.rpm: V3 DSA signature: NOKEY, key
>>ID db2dfb29
>>[root@rhat palm]# rpm -i hotplug-2003_05_01-1.noarch.rpm
>>warning: hotplug-2003_05_01-1.noarch.rpm: V3 DSA signature: NOKEY, key ID
>>db2dfb29
>
>After you have upgraded your hotplug packages verify that:
>/etc/hotplug/usb/bluefw
>and
>/etc/hotplug/usb/bluefw.usermap
>are still intact (else.. make install of the bluefw package again).
>
>Unplug and replug the USB dongle now to test new hotplug.
>Successful /var/log/messages:
>>Jun 25 22:18:17 rhat kernel: usb.c: USB disconnect on device 00:1f.4-1
>>address 4
>>Jun 25 22:18:17 rhat devlabel: devlabel service started/restarted
>>Jun 25 22:18:26 rhat kernel: hub.c: new USB device 00:1f.4-1, assigned
>>address 5
>>Jun 25 22:18:27 rhat kernel: usb.c: USB device 5 (vend/prod 0xa5c/0x2033) is
>>not claimed by any active driver.
>>Jun 25 22:18:30 rhat bluefw[5772]: Loading firmware to usb device 0a5c:2033
>>Jun 25 22:18:32 rhat bluefw[5772]: FW loaded
>>Jun 25 22:18:32 rhat kernel: usb.c: USB disconnect on device 00:1f.4-1
>>address 5
>>Jun 25 22:18:33 rhat devlabel: devlabel service started/restarted
>>Jun 25 22:18:33 rhat kernel: hub.c: new USB device 00:1f.4-1, assigned
>>address 6
>
>More problems?
>Verify that the /proc/bus/usb directory exists. If not there, you need
>re-compile kernel with
>USB Support-> Preliminary USB Filesystem (CONFIG_USB_DEVICEFS)
>
>Final hotplug help:
>The hotplug script /etc/hotplug/usb.agent is called when a new USB device is
>plugged in.
>It makes extensive use of functions in /etc/hotplug/hotplug.functions. Both
>of these scripts
>have an option to turn on debugging by editing the files. They work by
>looking through the
>loadable kernel modules looking for device id's that match the new USB device.
> If no
>kernel modules are foud, it searches through *.usermap files looking for
>matching matching device
>ID's.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: INetU
>Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>_______________________________________________
>Bluez-users mailing list
>Bluez-users@xxxxxxxxxxxxxxxxxxxxx
>https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
|
