hub 9-0:1.0: unable to enumerate USB device on port 1" usb 9-1: device not accepting address 6, error -71 usb 9-1: Device not responding to set address. " usb 9-1: Device not responding to set address. However I got a new, different device and the same problem popped up again. I almost forgot about all this - I never could get that adapter working and disposed of it recently. New cpuinfo, modules, ioports, iomem, lspci, scsi info Thank you for your assistance, I wish it would have worked. Incidentally this is the USB to 1XSATA/1XIDE device. I'll be throwing it out and chalking it up to experience. I must have corrupted the firmware because the device is no longer detected on Linux or Windows. And now the drive no longer even spins up, I get nothing but the power light on USB 2.0, on USB 3.0 the USB 3.0 light flashes quickly but the drive doesn't spin up. There has been no change in operation unfortunately - I still can no longer get it to work at all in either USB 2.0 or USB 3.0. Using Prolific's EEPROM reader/writer I flashed the latest firmware (20120326) and it seemed to proceed fine but their tool still reports the old 20110316 firmware. So rather than throw it out, I decided to take a look at the firmware as you suggest. A reboot won't allow it to recover either. It always fails on USB 3.0 and will only run once or twice on USB 2.0 before failing there as well. The device is now no longer working for me at all, even using my little workaround. I didn't see your comments because they occurred after the bug was closed. It may take me a few days to figure it all out. I don't have too much experience recompiling a kernel and none at all applying a patch, but I'll do some research. The drive connected to this device mounts and seems to work as normal, albeit at USB 2.0 speeds.
#Via xhci driver windows 10 vl805 keygen#
![via xhci driver windows 10 vl805 via xhci driver windows 10 vl805](https://wallpapershome.com/images/wallpapers/edge-5120x2880-windows-10-windows-10x-microsoft-8k-22713.jpg)
init: ureadahead-other main process (2914) terminated with status 2" EXT4-fs (sdc1): mounted filesystem with ordered data mode. sd 8:0:0:0: Assuming drive cache: write through sd 8:0:0:0: No Caching mode page present sd 8:0:0:0: Attached scsi generic sg3 type 0 scsi 8:0:0:0: Direct-Access SAMSUNG SP2514N VF10 PQ: 0 ANSI: 0 " usb 2-4: new high-speed USB device number 3 using ehci_hcd Then plugging the device into a USB 2.0 port, dmesg reads: Sudo modprobe usbcore old_scheme_first=1 use_both_schemes=0 Originally tested in kernel 3.2.0, also tested in 3.4.0, same results. Lsb_release -rd: "Description: Ubuntu 12.04 LTS
![via xhci driver windows 10 vl805 via xhci driver windows 10 vl805](https://www.10wallpaper.com/wallpaper/1920x1080/1603/2016_Windows_10_scenery_theme_desktop_wallpaper_09_1920x1080.jpg)
The controller seems to be Prolific Technology PL2773. "Bus 002 Device 005: ID 067b:2773 Prolific Technology, Inc." Lsusb doesn't list any new devices on USB 3.0 mode, but in USB 2.0 mode: hub 9-0:1.0: unable to enumerate USB device on port 2" usb 9-2: device not accepting address 21, error -71 usb 9-2: device not accepting address 20, error -71 usb 9-2: device not accepting address 19, error -71 usb 9-2: Device not responding to set address. " usb 9-2: Device not responding to set address. It worksįine in USB 2.0 mode, but it does not work in USB 3.0. This is in a Vantec CB-ISATAU3, an IDE/SATA USB3.0 adapter. Cpuinfo, modules, ioports, iomem, lspci, scsi info