HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

Post by lis » Thu, 05 Aug 2004 10:10:11



Hi,

It seems that hci_usb does not like USB 2.0: when I connect a D-Link USB
bluetooth dongle (DBT-120) to a USB 2.0 port, I get the following error
message when I try to 'hciconfig hci0 up':

hci_usb_intr_rx_submit: hci0 intr rx submit failed urb f768ae94 err -28

If I connect the same dongle through a USB 1.1 hub on the same USB 2.0
port, the device comes up and I don't get this error.

Regards,

Raf.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

Post by Marcel Hol » Tue, 10 Aug 2004 20:10:05

Hi Ralf,


about what kernel version are you talking? What USB host hardware do you
use?

Regards

Marcel


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/

 
 
 

HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

Post by lis » Sat, 21 Aug 2004 11:00:08


Marcel,

This was under 2.6.7, using ehci for USB 2.0 and uhci for 1.1.

Under 2.6.8.1 I get with USB 1.1:
usb 4-1.3: new full speed USB device using address 3
bcm203x_probe: Mini driver request failed
bcm203x: probe of 4-1.3:1.0 failed with error -5
usb 4-1.3: USB disconnect, address 3
usb 4-1.3: new full speed USB device using address 4

but USB 2.0 gives:
usb 1-3.4: new full speed USB device using address 6
ehci_hcd 0000:00:1d.7: qh f7d2d200 (#0) state 1
bcm203x_probe: Mini driver request failed
bcm203x: probe of 1-3.4:1.0 failed with error -5
usb 1-3.4: bulk timeout on ep1in
usb 1-3.4: usbfs: USBDEVFS_BULK failed ep 0x81 len 10 ret -110
usb 1-3.4: USB disconnect, address 6
usb 1-3.4: new full speed USB device using address 7
ehci_hcd 0000:00:1d.7: qh f7d2d280 (#0) state 1
hci_usb_intr_rx_submit: hci0 intr rx submit failed urb c1ad1994 err -28

If I try to do 'hciconfig hci0 up' when connected to USB 2.0 I also get
a 'hci_usb_intr_rx_submit: hci0 intr rx submit failed urb f7e22814 err
-28'.

Thanks,

PS Sorry for the late reply, I just returned from vacation.

Raf.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

Post by Marcel Hol » Sat, 21 Aug 2004 17:40:11

Hi Ralf,


your dongle looks like a Broadcom based dongle. Please include the part
from /proc/bus/usb/devices matching your device. The main problem is
that the mini driver and the firmware for the Broadcom dongle can't be
loaded throught request_firmware() by the bcm203x driver. Check the
BlueZ webpage for more details and put these files in the correct place.

Regards

Marcel


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

Post by Raf D'Hall » Sun, 22 Aug 2004 00:10:14


Okay, I had bluez-bluefw installed (Debian package) but it seems that
bluez now uses the standard firmware loading mechanism (request_firmware
()). As such, I copied the BCM2033-FW.bin and BCM2033-MD.hex files from
that package into /usr/lib/hotplug/firmware and removed bluez-bluefw.

However, I cannot find any evidence of the firmware actually being
loaded. I believe that my hotplug install is correctly installed (it can
load the ipw2100 firmware). I added some debugging
to /etc/hotplug/firmware.agent, but couldn't find any evidence of any
firmware being requested for the dongle.

Any suggestions what I could try next? Should I add USB_DEVICE(0x0a12,
0x0001) to the usb_device_id array in bcm203x.c?

BTW this used to work (but maybe this was under 2.4, using bluefw).

Raf.

/proc/bus/usb/devices for 1/19:
T: Bus=01 Lev=03 Prnt=03 Port=00 Cnt=01 Dev#= 19 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev= 4.43
C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

Post by Marcel Hol » Sun, 22 Aug 2004 15:10:07

Hi Ralf,


this is getting weird, because 0a12:0001 is a CSR based dongle and not a
Broadcom one. So firmware loading is not needed. It should simply work.
Give 2.6.8 a try.

Regards

Marcel


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)

Post by lis » Wed, 01 Sep 2004 04:20:12


Marcel,

I am sorry, I messed up: I have two D-Link dongles, I thought they were
the same. They are not!

I also seem to be having a problem with some of the my USB2.0 ports
(other devices act weird on it also). I will figure out those problems
first.

Thanks anyway!

Raf.




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/