From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 Description of problem: in contrast to Fedora Core 1, Hotplugging a BlueFritz! USB dongle into the usb port (usb 1.1) under Fedora Core 2 does not work. Reason could be that a firmware download does not work. /var/log/messages: Aug 15 14:30:31 my_notebook kernel: usb 1-1: configuration #1 chosen from 2 choices Aug 15 14:30:31 my_notebook kernel: bfusb_probe: Firmware request failed Aug 15 14:30:31 my_notebook kernel: bfusb: probe of 1-1:1.0 failed with error -5 Aug 15 14:30:31 my_notebook usb.agent[25125]: Keeping default configuration with /sys//devices/pci0000:00/0000:00:07.2/usb1/1-1 Also didnt work after making the directory /usr/lib/hotplug/firmware. After placing old firmware releases into this directory (bfubase.frm) the dongle is recognised: /var/log/messages: Aug 15 14:34:13 my_notebook kernel: usb 1-1: configuration #1 chosen from 2 choices Aug 15 14:34:14 my_notebook kernel: Bluetooth: BlueFRITZ! USB loading firmware Aug 15 14:34:15 my_notebook usb.agent[25217]: Keeping default configuration with /sys//devices/pci0000:00/0000:00:07.2/usb1/1-1 Aug 15 14:34:18 my_notebook kernel: Bluetooth: BlueFRITZ! USB device ready but does not work (probably due to the old firmware?) hciconfig gives: 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 ciptool search gives: Searching ... No devices in range or visible Version-Release number of selected component (if applicable): bluez-bluefw-1.0-2 How reproducible: Always Steps to Reproduce: 1.Unplug BlueFritz! USB Dongle 2.Plug BlueFritz! USB Dongle 3. Actual Results: Connecting to bluetooth devices does not work. Expected Results: Bluetooth devices should be recognised Additional info: I first thought that it was due to the missing directory but creating this did not change the problem. The missing directory has been brought up in Bug # 124488
bluez-bluefw is obsolete. The kernel should load the firmware for itself, and seems to have done so in your case. Does your device work if you bring it up manually ('hciconfig hci0 up')? Is hcid running? It should be doing this.
Closing after a period of inactivity. I _think_ the problem you're seeing is just that you weren't running hcid. Please re-open if you still have a problem.