Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Usb 3.1 Extensible Host Controller - 1.10 (microsoft) Download
148 views
Skip to first unread message
Nancie Fazzari
Jan 15, 2024, 8:49:49 PM1/15/24
to
On Intel 10th gen processor system, USB host controller is using Windows inbox driver (USBXHCI.sys). The device name is Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) in Device Manager. But I cannot find this string in usbxhci.inf under c:\windows\INF. Actually, I cannot find the string in any INF files under c:\windows\INF. I want to know where this device name comes from. Is it from the Intel chipset or usbxhci.sys, or anywhere else?
usb 3.1 extensible host controller - 1.10 (microsoft) download
DOWNLOAD https://t.co/RUPmdx59F8
While I am just as apt as anyone to blame Microsoft for a buggy OS, the fact that this is a host controller / usb issue does imply something hardware.Since I have set all of my mice and keyboards to "do not wake up", perhaps the problem was in the usb controllers or hubs.
First thing I did was go to device manager and uninstall that driver (the usb 3 host controller).I was hoping it would just disable the USB 3 ports, but it basically shut down all usb, so my mouse and keyboard would not work.I turned off the machine from the front panel, and restarted it.The OS found "new" hardware, reinstalled the driver and devices.Once booted, I tried to sleep - same problem, system woke right up.So, resetting the driver did not help.
I have been searching the web and found multiple threads regarding the conflict between the Intel and VH host controllers.
Do you have any info about that? I apologize for being pushy, but this is really important for me right now.
We are using a paid VH server for our security tokens and I cannot do my job...
Well I'm eating my own words this morning "if it ain't broke don't break it". It broke out of the blue all by itself. As mentioned above I didn't do anything at all since last posting (thank god I didn't). I was only running on the 531.86 Game Ready Driver. I was flying over LA in the UH-60 and all of a sudden the screen froze, I got this buzzing sound and my computer shut down (literally shut right off). It reset everything, I can't even get FS2 or FS4 up in the Nvidia control panel listing in the drop down menu. I had to reset my audio, roll back the driver to 457.85 and did a test run with FS4 and all is back to normal. There was a problem that was discovered by Lenovo with this PC model called out by owners on the Lenovo forum and it was determined by Lenovo that they had to release a BIOS patch to permanently disable the "Nvidia USB 3.10 extensible Host controller - 1.10 Microsoft" in the device manager. As I understood it when I found out, owners couldn't update their graphic drivers without their PC's crashing and having audio issues. But some owners were having no issues after the patch as they updated their drivers. I wasn't so lucky as I just found out. I will say I will never buy another Lenovo PC again and I have always been an IBM (Lenovo), Lenovo fan for years. Next time I buy a PC its a Mac. Not happy. No more tweaking and messing around with graphic stuff. No wonder I didn't all those years up till now. Grrrrr
IMPORTANT - the video shown above was a demonstration of what was technically possible at the time it was produced, however it is not a recommended or supported configuration by Plugable. To expand further, most modern Windows systems with built-in USB 3.0 host controllers have internal limitations in regard to how many USB devices can be properly recognized, even with the addition of USB hubs. Often adding a large number of USB devices to a modern USB 3.0 system will not work (this demonstration was done with a USB 2.0 only system). As a result, the maximum number of displays Plugable officially supports adding to a Windows system with our DisplayLink-based products is six.
For reference, I attach screen snip from my Device Manager for Win7. You will notice a specific controller for USB 2.0. Which does not appear in Win 10 device manager. There I have only Intel(r) USB 3.1 eXtensible Host Controller 1.10 (Microsoft) with USB Root Hub (USB 3.0), and UCM-UCSI ACPI Device. I wonder if this causes problems for USB 2.0. The ASCAP software seems to know that USB 2.0 is being used, but does seem to struggle to read the frames.
The eXtensible Host Controller Interface (xHCI) is a technical specification that provides a detailed framework for the functioning of a computer's host controller for Universal Serial Bus (USB). Known alternately as the USB 3.0 host controller specification, xHCI is designed to be backward compatible, supporting a wide range of USB devices from older USB 1.x to the more recent USB 3.x versions.
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.
f448fe82f3
usb 3.1 extensible host controller - 1.10 (microsoft) download
DOWNLOAD https://t.co/RUPmdx59F8
While I am just as apt as anyone to blame Microsoft for a buggy OS, the fact that this is a host controller / usb issue does imply something hardware.Since I have set all of my mice and keyboards to "do not wake up", perhaps the problem was in the usb controllers or hubs.
First thing I did was go to device manager and uninstall that driver (the usb 3 host controller).I was hoping it would just disable the USB 3 ports, but it basically shut down all usb, so my mouse and keyboard would not work.I turned off the machine from the front panel, and restarted it.The OS found "new" hardware, reinstalled the driver and devices.Once booted, I tried to sleep - same problem, system woke right up.So, resetting the driver did not help.
I have been searching the web and found multiple threads regarding the conflict between the Intel and VH host controllers.
Do you have any info about that? I apologize for being pushy, but this is really important for me right now.
We are using a paid VH server for our security tokens and I cannot do my job...
Well I'm eating my own words this morning "if it ain't broke don't break it". It broke out of the blue all by itself. As mentioned above I didn't do anything at all since last posting (thank god I didn't). I was only running on the 531.86 Game Ready Driver. I was flying over LA in the UH-60 and all of a sudden the screen froze, I got this buzzing sound and my computer shut down (literally shut right off). It reset everything, I can't even get FS2 or FS4 up in the Nvidia control panel listing in the drop down menu. I had to reset my audio, roll back the driver to 457.85 and did a test run with FS4 and all is back to normal. There was a problem that was discovered by Lenovo with this PC model called out by owners on the Lenovo forum and it was determined by Lenovo that they had to release a BIOS patch to permanently disable the "Nvidia USB 3.10 extensible Host controller - 1.10 Microsoft" in the device manager. As I understood it when I found out, owners couldn't update their graphic drivers without their PC's crashing and having audio issues. But some owners were having no issues after the patch as they updated their drivers. I wasn't so lucky as I just found out. I will say I will never buy another Lenovo PC again and I have always been an IBM (Lenovo), Lenovo fan for years. Next time I buy a PC its a Mac. Not happy. No more tweaking and messing around with graphic stuff. No wonder I didn't all those years up till now. Grrrrr
IMPORTANT - the video shown above was a demonstration of what was technically possible at the time it was produced, however it is not a recommended or supported configuration by Plugable. To expand further, most modern Windows systems with built-in USB 3.0 host controllers have internal limitations in regard to how many USB devices can be properly recognized, even with the addition of USB hubs. Often adding a large number of USB devices to a modern USB 3.0 system will not work (this demonstration was done with a USB 2.0 only system). As a result, the maximum number of displays Plugable officially supports adding to a Windows system with our DisplayLink-based products is six.
For reference, I attach screen snip from my Device Manager for Win7. You will notice a specific controller for USB 2.0. Which does not appear in Win 10 device manager. There I have only Intel(r) USB 3.1 eXtensible Host Controller 1.10 (Microsoft) with USB Root Hub (USB 3.0), and UCM-UCSI ACPI Device. I wonder if this causes problems for USB 2.0. The ASCAP software seems to know that USB 2.0 is being used, but does seem to struggle to read the frames.
The eXtensible Host Controller Interface (xHCI) is a technical specification that provides a detailed framework for the functioning of a computer's host controller for Universal Serial Bus (USB). Known alternately as the USB 3.0 host controller specification, xHCI is designed to be backward compatible, supporting a wide range of USB devices from older USB 1.x to the more recent USB 3.x versions.
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.
f448fe82f3
0 new messages