https://bugzilla.novell.com/show_bug.cgi?id=257303 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |ciriarte@personal.net.py ------- Comment #25 from oneukum@novell.com 2007-05-08 02:06 MST ------- Yes, devices that need a reset to work are known. There's a short list of them in the kernel. This from #13 adds your device to that list: @@ -98,6 +98,9 @@ /* Canyon CN-BTU1 with HID interfaces */ { USB_DEVICE(0x0c10, 0x0000), .driver_info = HCI_RESET }, + /* Broadcom Corp - BCM2045 */ + { USB_DEVICE(0x413c, 0x8126), .driver_info = HCI_RESET }, + { } /* Terminating entry */ }; Devices on that list should print debugging output twice: - if (test_bit(HCI_QUIRK_RESET_ON_INIT, &hdev->quirks)) + if (test_bit(HCI_QUIRK_RESET_ON_INIT, &hdev->quirks)) { + BT_DBG("Acting on reset quirk."); hci_send_cmd(hdev, OGF_HOST_CTL, OCF_RESET, 0, NULL); and - if (reset || id->driver_info & HCI_RESET) + if (reset || id->driver_info & HCI_RESET) { set_bit(HCI_QUIRK_RESET_ON_INIT, &hdev->quirks); + BT_DBG("Setting reset quirk."); + } Yet, your dmesg shows neither, which I find very odd. 0x413c:0x8126 is the correct id for your device, isn't it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.