Ian Osgood wrote: > dmesg errors: > xhci_hcd 0000:00:14.0: xhci_run > xhci_hcd 0000:00:14.0: Failed to enable MSI-X > xhci_hcd 0000:00:14.0: failed to allocate MSI entry > xhci_hcd 0000:00:14.0: No msi-x/msi found and no IRQ in BIOS > xhci_hcd 0000:00:14.0: startup error -22 > xhci_hcd 0000:00:14.0: USB bus 3 deregistered > xhci_hcd 0000:00:14.0: can't derive routing for PCI INT A > xhci_hcd 0000:00:14.0: init 0000:00:14.0 fail, -22 > xhci_hcd: probe of 0000:00:14.0 failed with error -22 Either the firmware isn't setting up interrupt routing correctly (less common) or it is not passing correct data structures to the kernel about how interrupt routing has been set up (very common) or the kernel does not have support compiled-in for the particular type of data structures specifying interrupt routing which are passed by the firmware (there are at least four kinds, some firmware provides all of them since different OSes understand different types, and often the different data is inconsistent). The no MSI is strange though. Could you also send lspci -vvnn output, ran as root? //Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
