Question How to install non-native Gen 2x2 USB-C HUB on CPU direct PCIe?

Dec 30, 2023
7
0
10
Windows installs ASMEDIA USB 3.2 eXtensible Host Controller with a USB 3.0 hub. SYBA USB-C 3.2 GEN 2x2 PCIe3x4 adapter card, built on ASMEDIA 3242 controller. it is installed on CPU direct PCIe lanes. (LGA2011) Physical USB-C out back of case. No restrictions by Microsoft on this configuration. Windows 10 x64 Pro. Card is not ASMEDIA 3142 upgrade, so USB 3.1 drivers are not compatible. mob bios Hyper V in ON, plus functional on op sys. Windows installs ASMEDIA USB 3.2 eXtensible Host Controller with a generic USB 3.0 HUB. HUB is not the USB-C superfast one promised by both the card manufacturer and promised USB standards. If understanding of Microsoft Virtualization is required to use the product as advertised than BIO.
 
7UP to unzip downloaded files, 10x. As the printed paper note said, Microsoft ASMEDIA USB 3.2 eXtensible host controller driver is automatically installed. Downloadable USB 3.1 drivers are HARDWARE INCOMPATIBLE with the ASMEDIA 3242 USB Controller chip. The HARDWARE INCOMPATIBLE drivers are for firmware upgraded ASMEDIA 3142 USB 3.1 controllers. Clearly, the 3242 is not just a 3142 with upgraded firmware. Microsoft provides USB-C HUB drivers with new mob having embedded ASMEDIA 3242. Both hardware/software/firmware giants have failed to own up to the PCIe card blunder.

The PCIe card is non-returnable, now. I could put ASMEDIA 3142 firmware onto its ASMEDIA3242 USB host controller. I could also try virtual device schemes in Windows. Using an updatable USB-C HUB driver to match the Microsoft ASMEDIA USB 3.2 eXtensible host controller would be the simple solution. Neither public nor private solutions seem to be available, which would assure the advertised functions, of the PCIe product.
 
I used AOMEI to test speeds of a Samsung T7. I only have 40 MB/s. Need to pull card-and talk to mfg. Syba. Windows 22H2 identifies it as ASMEDIA USB 3.2 and uses a general USB 3.0 HUB. It arrived last May as one of the first 3.2 gen2x2 cards. It requires a SATA power connector just to function. No PD and no Video. USB 3.1 gen 2x2 is same as 3.2 gen2 x2, So, it is likely a lame firmware flash, which might be easily corrected without postage.
 
Last edited:
When finding the original instructions and tag for the SD-PEX20235, there is an explanation about it being a 3.2 Specification Revision 1.0 for PCI-e 3. Contents list the card, a CD and a User Manual. Driver listed as Buit-In for Windows 8 and above. No CD. Listed Drivers-Download site listed is a scam site. Card has ASMEDIA3.2 eXtensible host driver information. Does not identify the connector as a superspeed USB 3.2 2x2 type C. SATA power for Devices connected. ASMEDIA3242 chip is capable of 20Gbps, at about 1050 GByte speed. No joy with this particular Syba card which gives 44 MByte speed on Generic USB 3.0 HUB which is slow.
 
The ASMEDIA USB 3.2 eXtensible v 1.1 does not describe anything. It is taken from the device description. USB 3.1 and USB 3.2 are same except for PD standards. On-Board 2 chips double the 10Gbs speed, Motherboard BIOS has NO SUPERSPEED. This external facing USB-C is not Microsoft controlled. NOT POSSIBLE TO INSTALL DRIVERS? History shows the inhibited installation and a zero value in a registry. No Group Policy configurations. No Chipset to DMI 2.0. No monitored USB data rate possible. When I solve this problem, I will likely need to purchase a Powered HUB to do some tasks with old IDE. I just am not willing to purchase hardware or computers, which don't have improvements. This software issue is inconvenient. Having any standards and policies is becoming an arduous business.
 
My SMBios for my LGA2011 motherboard is not quite as advanced as is some newer ones. I need to install the superspeed USB into the PCIe which is a root hub installation. So, I will put the installation files onto a USB2 and load the drivers from Bios. Every motherboard and SMBios is different. I think that the USB is opened and installed in Bios. I cannot add it in SMBios, on this older system. Installing the device into the PCIe should make it visible to Windows. It has been a long time since I first installed the (chipset) RAID and its IRSTe program. This should be a similar installation, to that.
 
Solved. The version of Microsoft installed software -eXtensible USB ASMEDIA3.2 v1.1 is correct. The USB 3.0 HUB had to be reloaded as Generic Superspeed. The ASMEDIA 3.1 drivers don't load on my system. The crux of the matter was the VC+++ loading programs. I think it was the VC++ 2015 was updated 3 years ago when Windows 11 came in. And the continuously updating VC++ version was updated one last time without it being included into a Windows Update. I uninstalled the older updates for each version and keep only the last update for each year (version). Only keep one update for each version. Reboot and reload like you would a car computer before you take an emissions test. I also found a cable which was only 10 Gbps. And, I reloaded earlier versions of BIOS and made sure that they load and function with the new hardware. Rates are 1077MBps Read and at least 1040 MBps Write on Samsung T7 drive.