I've tried to uninstall the Intel USB 3.0 extensible host controller driver. Re-installation of the latest driver from Intel failed and I got a BSOD during the installation. I updated my BIOS with the latest firmware from HP and the BSOD ceased but the driver still wouldn't install properly. I get an installation error and after restarting the USB 3.0 controller is installed but not USB 3.0 Hub which shows to be an Unknown Device. The driver installation log reveals the details below.
You need to update that PCI bus driver. That's the driver for the USB3PCIe bridge controller, and if it says the one already installed is newer, then it's likely a mismatched version to the XHCI and root hub drivers.
Hi Fernando,Installed (have disk method) controller driver then hub driver V 188.8.131.52 x64 on my PC ASUS P8Z77-V Deluxe W7 SP1 x64.Here below are the bench results.Working OK for me.Many thanks.
eXtensible Host Controller Interface (xHCI) is a computer interface specification that defines a register-level description of a host controller for Universal Serial Bus (USB), which is capable of interfacing with USB 1.x, 2.0, and 3.x compatible devices. The specification is also referred to as the USB 3.0 host controller specification.
The xHCI is a radical break from the previous generations of USB host controller interface architectures (i.e. the Open Host Controller Interface (OHCI), the Universal Host Controller Interface (UHCI), and the Enhanced Host Controller Interface (EHCI)) on many counts.Following are the key goals of the xHCI architecture:
When USB was originally developed in 1995, it was targeted at desktop platforms to stem the proliferation of connectors that were appearing on PCs, e.g. PS/2, serial port, parallel port, game port, etc., and host power consumption was not an important consideration at the time. Since then, mobile platforms have become the platform of choice, and their batteries have made power consumption a key consideration. The architectures of the legacy USB host controllers (OHCI, UHCI, and EHCI) were very similar in that the "schedule" for the transactions to be performed on the USB were built by software in host memory, and the host controller hardware would continuously read the schedules to determine what transactions needed to be driven on the USB, and when, even if no data was moved. Additionally, in the case of reads from the device, the device was polled each schedule interval, even if there was no data to read.
Legacy USB host-controller architectures exhibit some serious shortcomings when applied to virtualized environments. Legacy USB host-controller interfaces define a relatively simple hardware data-pump; where critical state related to overall bus-management (bandwidth allocation, address assignment, etc.) resides in the software of the host-controller driver (HCD). Trying to apply the standard hardware IO virtualization technique - replicating I/O interface registers - to the legacy USB host controller interface is problematic because critical state that must be managed across virtual machines (VMs) is not available to hardware. The xHCI architecture moves the control of this critical state into hardware, enabling USB resource management across VMs. The xHCI virtualization features also provide for:
The EHCI utilizes OHCI or UHCI controllers as "companion controllers", where USB 2 devices are managed through the EHCI stack, and the port logic of the EHCI allows a low-speed or full-speed USB device to be routed to a port of a "companion" UHCI or OHCI controller, where the low-speed or full-speed USB devices are managed through the respective UHCI or OHCI stack. For example, a USB 2 PCIe host controller card that presents 4 USB "Standard A" connectors typically presents one 4-port EHCI and two 2-port OHCI controllers to system software. When a high-speed USB device is attached to any of the 4 connectors, the device is managed through one of the 4 root hub ports of the EHCI controller. If a low-speed or full-speed USB device is attached to connectors 1 or 2, it will be routed to the root hub ports of one of the OHCI controllers for management, and low-speed and full-speed USB devices attached to connectors 3 or 4 will be routed to the root hub ports of the other OHCI controller. The EHCI dependence on separate host controllers for high-speed USB devices and the group of low-speed and full-speed USB devices results in complex interactions and dependencies between the EHCI and OHCI/UHCI drivers.
Support for Streams was added to the USB 3.0 SuperSpeed specification, primarily to enable high performance storage operations over USB. Classically there has been a 1:1 relationship between a USB endpoint and a buffer in system memory, and the host controller solely responsible for directing all data transfers. Streams changed this paradigm by providing a 1-to-many "endpoint to buffer" association, and allowing the device to direct the host controller as to which buffer to move. The USB data transfers associated with a USB Stream endpoint are scheduled by the xHCI the same as any other bulk endpoint is, however the data buffer associated with a transfer is determined by the device.
The EHCI specification was defined by Intel to support USB 2.0 devices. The EHCI architecture was modeled after the UHCI and OHCI controllers, which required software to build the USB transaction schedules in memory, and to manage bandwidth and address allocation. To eliminate a redundant industry effort of defining an open version of a USB 2.0 host controller interface, Intel made the EHCI specification available to the industry with no licensing fees.
xHCI 1.0 controllers have been shipping since December 2009. Linux kernels since 2009 contain xHCI drivers, but for older kernels there are drivers available online. Windows drivers for XP, Vista, and Windows 7 are available from the respective xHCI vendors. xHCI drivers for embedded system are available from MCCI, Jungo, and other software vendors. xHCI IP blocks are also available from several vendors for customization in SOC environments. xHCI 1.1 controllers and devices began shipping in 2015.
ASMedia ASM3242 is a Universal Serial Bus xHCI host controller, bridging PCI Express to USB3.2 20Gbps, compliant with USB3.2 Specification Revision 1.0 and Intel eXtensible Host Controller Interface specification revision 1.1. It also supports backward compatible with legacy USB function and devices, compliant with USB Attach SCSI Protocol revision 1.0, supporting the function of debugport on USB3.2 port.ASMedia ASM3242 also supports the function of Multiple INs to achieve fully utilization rate of 20Gbps data rate, taking advantage of the available bandwidth of USB3.2 Gen2 x2 bus. ASM3242 supports one USB3.2 20Gbps port and perform trusting high speed bandwidth with PCI Express Gen3 x4. It uses advance process with low voltage supply, following standard PCI Express/USB Link power management and advance chip power management to reduce total power consumption efficiently under idle/standby state.ASM3242 integrates ASMedia self-designed PCI Express/SuperSpeed USB/USB2.0 PHY, supporting in box driver of Microsoft® Windows and various Linux kernels. The application of ASM3242 includes Motherboard, Desktop PC, Notebooks, Workstations, Servers, Add-in cards, PCI Express based embedded platform.
ASMedia ASM3241 is a Universal Serial Bus xHCI host controller, bridging PCI Express to USB3.2 20Gbps, compliant with USB3.2 Specification Revision 1.0 and Intel eXtensible Host Controller Interface specification revision 1.1. It also supports backward compatible with legacy USB function and devices, compliant with USB Attach SCSI Protocol revision 1.0, supporting the function of debugport on USB3.2 port.ASMedia ASM3241 also supports the function of Multiple INs to achieve fully utilization rate of 20Gbps data rate, taking advantage of the available bandwidth of USB3.2 Gen2 x2 bus. ASM3241 supports one USB3.2 20Gbps port and perform trusting high speed bandwidth with PCI Express Gen3 x2. It uses advance process with low voltage supply, following standard PCI Express/USB Link power management and advance chip power management to reduce total power consumption efficiently under idle/standby state.ASM3241 integrates ASMedia self-designed PCI Express/SuperSpeed USB/USB2.0 PHY, supporting in box driver of Microsoft® Windows and various Linux kernels. The application of ASM3241 includes Motherboard, Desktop PC, Notebooks, Workstations, Servers, Add-in cards, PCI Express based embedded platform.
After deploying Win7 for these models there is an unknown device in device manager. We copied the Dell cab file to the system and let device manager search for the driver. A new driver called Intel USB 3.0 extensible host controller will be installed and a few more drivers. I think the exact inf is iusb3xhd.sys.
Microsoft provides a new USB driver stack for USB 3.0 in Windows 8. The new stack includes an in-box host controller driver that works with all available controllers. We recommend that you do not load a 3 rd party driver for your USB 3.0 controller (or XHCI controller) on Windows 8 because of compatibility issues. Different USB 3.0 controllers vary slightly in speed, however all USB 3.0 controllers are significantly faster than 2.0 controllers.
If thisscenario is detected when the server is running, when a user connects a new SDcard, then the cards are not managed by the Cisco Flexible Flash controller. This does not affect thehost enumeration. You must pair the cards to manage them. You can pair thecards using the Reset Partition Defaults or Synchronize Card Configuration options.
This task results in the host re-scanning all the virtual drives, and a loss of virtual drive connectivity. We recommend that you configure the Cisco Flexible Flash controller properties before using any virtual drives, or power down the host prior to starting this task 2b1af7f3a8