Summary: | Error "hci_usb_intr_rx_submit: hci0 intr rx submit failed" with BCM2045 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vince C. <vincent.cadet> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic-t-567524.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Vince C.
2007-11-29 10:14:25 UTC
What are you trying to do exactly/which services don't work? You don't need any /dev/hci? device for hciconfig -a to work... Also, net-wireless/bluez-utils version? /etc/conf.d/bluetooth configuration? # hciconfig -a hci0: Type: USB BD Address: 00:A0:96:1F:B3:A8 ACL MTU: 128:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:1141 acl:0 sco:0 events:43 errors:0 TX bytes:501 acl:0 sco:0 commands:33 errors:0 Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'notorcomp (0)' Class: 0x000100 Service Classes: Unspecified Device Class: Computer, Uncategorized HCI Ver: 1.1 (0x1) HCI Rev: 0x72 LMP Ver: 1.1 (0x1) LMP Subver: 0x72 Manufacturer: Cambridge Silicon Radio (10) # ls /dev/hci* ls: cannot access /dev/hci*: No such file or directory (In reply to comment #1) > What are you trying to do exactly/which services don't work? You don't need >any /dev/hci? device for hciconfig -a to work... The error message hci_usb_intr_rx_submit: hci0 intr rx submit failed urb ffff81007f6ac0a8 err -28 doesn't look quite normal to me. While trying to solve the problem by myself I found many references to /dev/hci0. (unless I didn't understand, which is also possible.) > Also, net-wireless/bluez-utils > version? /etc/conf.d/bluetooth configuration? The packages: - net-wireless/bluez-libs-2.25 (0) - net-wireless/bluez-utils-2.25-r1 (0) /etc/conf.d/bluetooth: HCID_ENABLE=true HCID_CONFIG="/etc/bluetooth/hcid.conf" SDPD_ENABLE=true HIDD_ENABLE=false HIDD_OPTIONS="" HID2HCI_ENABLE=false RFCOMM_ENABLE=true RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf" DUND_ENABLE=false DUND_OPTIONS="--listen --persist" PAND_ENABLE=false PAND_OPTIONS="--listen --role NAP" Changed the bug title to the syslog error message. Reopened the bug. It turned out to be a problem with missing modules. I've tested my BT hardware with another distribution LiveCD and it worked. So I concluded it was probably due to missing drivers. I had followed the Wiki at that time but I don't exclude some more checks must be made for Dell laptops. I'll post comments when I've found exactly what were the missing drivers. I've roughly copied the working kernel configuration to my laptop and recompiled my kernel. Now my BT hardware works and hciconfig returns meaningful data instead of just zeroes. you can use sys-kernel/kccmp to compare .config files if you think that would be helpful. (In reply to comment #6) > you can use sys-kernel/kccmp to compare .config files if you think that would > be helpful. Thanks a lot, Mike; I didn't know of that tool. I used diff -y instead. Note however both kernels are quite different (2.6.20 series, generic on Ubuntu and I'm using a Dell-specific 2.6.23). I know my kernel options almost by heart ;-) and I'm nearly sure the missing drivers were about non-standard serial ports. |