similar to: USB 2.0 device on a USB 3.0 plug

On 2/16/2017 9:58 AM, Jerry Geis wrote: > 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 ? USB 1

On 10 August 2014 09:05, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > > Error -32 is EPIPE, which means that the PC didn't see a reply from the device during the descriptor read. I don't know that we have ever successfully run one of these issues to ground. > Considering Eaton do

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 here? Board failure - or other reasons? Some

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

----- Oorspronkelijk bericht ----- Van: "Nataraj" <incoming-centos at rjl.com> Aan: "CentOS mailing list" <centos at centos.org> Verzonden: Maandag 2 juli 2018 23:21:39 Onderwerp: Re: [CentOS] usb problem on Dell Latitude 3570 On 07/02/2018 01:49 AM, johan.vermeulen7 at telenet.be wrote: > Hello All, > > after update to Centos7.5 all our Latitudes 3570 -

On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > I have tried to plug it into every USB port (including the USB 3.0 > ones) and I still get these errors. I discovered that power cycling > the UPS will fix it for a while, and also unplugging and replugging > the USB cable will also fix it sometimes. Error -32 is EPIPE, which means that the PC

Hi, I recently purchased a new Easton 5E UPS. I plugged the USB cable into my computer so I could use the NUT UPS tools. However every so often NUT fails to connect to the device after a boot. Looking at dmesg I see errors like this: [ 3.277075] usb 1-9: new low-speed USB device number 6 using xhci_hcd [ 3.302091] usb 1-9: device descriptor read/8, error -32 [ 3.430241] usb 1-9: device

We plan to use new digital voice recorders. Products are available from Olympus, Sony, and others.? All of these digital voice recorders offer file-based audio storage.? We would like to take advantage of this feature and move the files to our computers. It is not clear whether there is a difference in the product features described as "USB connection" and "USB direct

Hi, I have an IBM xSeries server... and the digium card is sharing IRQ with USB and giving me crackling audio. >>> cat /proc/interrupts >>> >>> It brings up these results: >>> 0: 10566547 IO-APIC-edge timer >>> 1: 9 IO-APIC-edge i8042 >>> 2: 0 XT-PIC cascade >>> 8: 1

https://bugs.freedesktop.org/show_bug.cgi?id=109681 Bug ID: 109681 Summary: Nvidia GT710 => nouveau + wayland + swayWM => crash when use acceleration (open Firefox) Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

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

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

On 02/16/2017 12:28 PM, John R Pierce wrote: > USB 1 and 2 used 4 pins. USB 3 ports have an ADDITIONAL 5 pins, the > original 4 are used for USB 1/2 operation, the new 5 only for USB 3 > operation. they are effectively two completely independent controllers. Do you mean USB type C? USB 3 is supported and most commonly uses type A plugs & ports, which should support older

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

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote: > > > And I wonder if the XEN_DOMCTL_irq_permission aka, > > > xc_domain_irq_permission > > > had been called. I remember that at some point we missed it for > > > Xend.. > > > > > False alarm. > > It was all in Linux. Attached are four patches (the first two > are for

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

On Aug 6, 2019, at 7:04 AM, Stephen John Smoogen <smooge at gmail.com> wrote: > > On Mon, 5 Aug 2019 at 19:49, Warren Young <warren at etr-usa.com> wrote: > >> On Aug 5, 2019, at 11:25 AM, Stephen John Smoogen <smooge at gmail.com> >> wrote: >>> >>> On Mon, 5 Aug 2019 at 13:17, Jerry Geis <jerry.geis at gmail.com> wrote:

Hello, Help me please with *newhidups* setup. Does it work for someone on *BSD ? Here is the data. --------------------------------------------------------------- *** FreeBSD root.srv# uname -a FreeBSD xxxxxx.dyndns.info 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Tue Feb 8 07:38:22 UTC 2005 admin@temp.botka.homeunix.org:/usr/src/sys/i386/compile/SRV i386 *** NUT ver.2.0.3 root.srv# ll /var/db/pkg/