search for: usb3

Hi Folks, CentOS 5.5 x86_64 Asrock-Board with 2 USB3 plugs. Normally USB3-drive is detected. But occasionaly after "umount" next time this drive or other ones will not be detected. I have to boot the PC - than it works - till next unrecognition. On USB2 plugs all works correct. No messages in /var/log/messages nor dmesg. What happens...

I replaced my development machine with 6 cores, 32 GB etc. I thought it would be simply inserting the existing HDDs and changing /etc/sysconfig/ifcfg-eth0 but, * in the UEFI "BIOS" USB2 and USB3 work. * in C5.11 USB2 works but USB3 does not. * in C6.5 (my install disk; OS be updated to C6.8) USB2 works but USB3 does not. On both C5 and C6 lsusb shows an entry for the plugged-in keyboard (USB2 socket) and for the wireless mouse (USB2 socket) but nothing else. Please does anyone have any...

Hi All, Scientific Linux 7.2 # rpm -qa \*kvm\* qemu-kvm-1.5.3-105.el7_2.3.x86_64 pcp-pmda-kvm-3.10.6-2.el7.x86_64 qemu-kvm-common-1.5.3-105.el7_2.3.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64 Question: when I set "Controller USB" to "USB3", what USB3 driver do I use to install Window 7? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

...gt; > Scientific Linux 7.2 > > # rpm -qa \*kvm\* > qemu-kvm-1.5.3-105.el7_2.3.x86_64 > pcp-pmda-kvm-3.10.6-2.el7.x86_64 > qemu-kvm-common-1.5.3-105.el7_2.3.x86_64 > libvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64 > > Question: when I set "Controller USB" to "USB3", what > USB3 driver do I use to install Window 7? > > Many thanks, > -T > Hi, These days when creating and installing Windows virtual machines, I tend to use ISO images for the install process. Windows 7 ISO images can be downloaded from: https://www.microsoft.com/en-gb/s...

Usage: usbversion=1|2|3 (default=0, no usb controller defined) Specifies the type of an emulated USB bus in the guest. 1 for usb1, 2 for usb2 and 3 for usb3, it is available only with upstream qemu. The old usb and usbdevice parameters cannot be used with this. Changes from v6: - now usbversion cannot be used with usb and usbdevice parameters - now default is 0 (no usb controller defined) Will be used only with usb redirection (from spice client) and...

Hi people. I had finally cross my USB to my DomU windows XP, justs 1 issue: USB 2.0 not working only 1.1 is working. I would to confirm with others that have the MoBo ASUS M4A89TD Pro/USB3 if u have been able to passthrough the USB ports to HVM windows? I had try different settings on my BIOS, different settings on Xen 4.1, this under Centos x64 AMD Athlon II 640. I receive the message: non-page-aligned MMIO BAR went I try to start my hvm with xm xm create hvm... xm pc...

...does either esata or USB 3.0. My new motherboard (ASUS M5A99X EVO R2.0) supports both, so I've tried both (of course, can't have a feature without at least giving it a whirl! :)). esata seems to work fine, I can copy gigs 'n gigs of data to it using the esata connection. however, with USB3 it works for a bit then something goes wonky... After copying some hundreds of megabytes (and I don't know if it is a consistent number or not) suddenly my C6 box starts reporting write errors. some investigation shows that /dev/sdc (and /dev/sdc1) no longer exist on the system. it takes a reb...

Hi all! I'm building a raid box to use for backups, connectivity will be either USB3 or esata. Looking for suggestions on backup software I can use. I know there's rsync, which may be a good solution. I also find backupPC at epel, backintime also at epel, kbackup. DejaDup looks interesting, but none of the repos I'm set up to use shows it being available. some small det...

On Thu, Jan 15, 2015 at 10:18:18PM +0100, Gerd Hoffmann wrote: > Hi, > > > QEMU side is still undergoing polishing, but is already testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be

On Thu, Jan 15, 2015 at 10:18:18PM +0100, Gerd Hoffmann wrote: > Hi, > > > QEMU side is still undergoing polishing, but is already testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be

...: new USB bus registered, assigned bus number 1 [ 4.410347] orion-ehci f1058000.usb: irq 41, io mem 0xf1058000 [ 4.442309] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00 [ 4.448564] hub 1-0:1.0: USB hub found [ 4.452407] hub 1-0:1.0: 1 port detected [ 4.456717] xhci-hcd f10f0000.usb3: xHCI Host Controller [ 4.462059] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2 [ 4.469634] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010 [ 4.478201] xhci-hcd f10f0000.usb3: irq 48, io mem 0xf10f0000 [ 4.484272] hub 2-0:1.0: US...

...tem was acting like wine was not installed. So I followed some advice I found and purged the package from my system and redownloaded it, which still made no difference. I've just tried restarting after wiping it from the system, and this is what I've tried since: Code: xbmc at xbmc-H67N-USB3-B3:~$ wine The program 'wine' can be found in the following packages: * wine1.2 * wine1.3 Try: sudo apt-get install <selected package> xbmc at xbmc-H67N-USB3-B3:~$ sudo apt-get install wine1.3 [sudo] password for xbmc: Reading package lists... Done Building dependency tree R...

...is a single msix_init() call. xhci is doing that too: 00000000febf0000-00000000febf3fff (prio 1, RW): xhci 00000000febf0000-00000000febf003f (prio 0, RW): capabilities 00000000febf0040-00000000febf043f (prio 0, RW): operational 00000000febf0440-00000000febf044f (prio 0, RW): usb3 port #1 00000000febf0450-00000000febf045f (prio 0, RW): usb3 port #2 00000000febf0460-00000000febf046f (prio 0, RW): usb3 port #3 00000000febf0470-00000000febf047f (prio 0, RW): usb3 port #4 00000000febf0480-00000000febf048f (prio 0, RW): usb2 port #1 00000000febf0490-...

...is a single msix_init() call. xhci is doing that too: 00000000febf0000-00000000febf3fff (prio 1, RW): xhci 00000000febf0000-00000000febf003f (prio 0, RW): capabilities 00000000febf0040-00000000febf043f (prio 0, RW): operational 00000000febf0440-00000000febf044f (prio 0, RW): usb3 port #1 00000000febf0450-00000000febf045f (prio 0, RW): usb3 port #2 00000000febf0460-00000000febf046f (prio 0, RW): usb3 port #3 00000000febf0470-00000000febf047f (prio 0, RW): usb3 port #4 00000000febf0480-00000000febf048f (prio 0, RW): usb2 port #1 00000000febf0490-...

...: new USB bus registered, assigned bus number 1 [ 4.417416] orion-ehci f1058000.usb: irq 41, io mem 0xf1058000 [ 4.452186] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00 [ 4.458441] hub 1-0:1.0: USB hub found [ 4.462269] hub 1-0:1.0: 1 port detected [ 4.466572] xhci-hcd f10f0000.usb3: xHCI Host Controller [ 4.471914] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2 [ 4.479489] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010 [ 4.488057] xhci-hcd f10f0000.usb3: irq 48, io mem 0xf10f0000 [ 4.494130] hub 2-0:1.0: US...

...ew full-speed USB device number 3 using xhci_hcd > Jul 1 07:15:06 pygeum kernel: [ 31.836441] usb 3-1: device descriptor read/64, error -110 > Jul 1 07:15:06 pygeum kernel: [ 47.452351] usb 3-1: device descriptor read/64, error -110 > Jul 1 07:15:06 pygeum kernel: [ 47.560390] usb usb3-port1: attempt power cycle > Jul 1 07:15:06 pygeum kernel: [ 48.212366] usb 3-1: new full-speed USB device number 4 using xhci_hcd > Jul 1 07:15:06 pygeum kernel: [ 53.468442] xhci_hcd 0000:39:00.0: Timeout while waiting for setup device command > Jul 1 07:15:06 pygeum kernel: [ 5...

...1.0, legacy support usb2: <SiS 5571 USB controller> on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf7004000-0xf7004fff irq 11 at device 3.3 on pci0 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: <EHCI (generic) USB 2.0 controller> on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered When I plug my digital camera in, I g...

Hello All, after update to Centos7.5 all our Latitudes 3570 - some 150- suffer usb problems. Plug and play doesn't work any more, people need to insert usb devices - mouse, keyboard, eidreader - first and then boot in order to use them. dmesg | tail -n15 gives these EM: [ 25.164396] usb 1-8: device descriptor read/64, error -110 [ 25.418387] usb 1-8: new full-speed USB device number 6

When I plug in my device which is USB 2.0 into a 3.0 slot (cause that is all I have) [495042.943074] usb 5-2: new low-speed USB device number 6 using xhci_hcd [495043.100076] usb 5-2: device descriptor read/64, error -71 I receive the above error. Is there a flag or setting that tells the USB to in a 2.0 mode ? Thanks, Jerry

...xhci is > doing that too: > > 00000000febf0000-00000000febf3fff (prio 1, RW): xhci > 00000000febf0000-00000000febf003f (prio 0, RW): capabilities > 00000000febf0040-00000000febf043f (prio 0, RW): operational > 00000000febf0440-00000000febf044f (prio 0, RW): usb3 port #1 > 00000000febf0450-00000000febf045f (prio 0, RW): usb3 port #2 > 00000000febf0460-00000000febf046f (prio 0, RW): usb3 port #3 > 00000000febf0470-00000000febf047f (prio 0, RW): usb3 port #4 > 00000000febf0480-00000000febf048f (prio 0, RW): usb2 port #1 &gt...