similar to: usb problem on Dell Latitude 3570

----- 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 07/02/2018 01:49 AM, johan.vermeulen7 at telenet.be wrote: > 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]

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

After resuming more than once on battery these HP Ivybridge laptops, the XHCI devices stop working. Have anyone seen this before? I wanted to check before diving in deeper. Let me know if you have any ideas. Thanks! Facts - Xen 4.0.3, Linux 3.2.7 PVOPs - Happens on HP Ivybridge. Doesn''t happen on very similar HP Sandybridge Clash system. - Happens on battery, but not on AC. -

On 9/23/2020 1:09 PM, Stuart D. Gathman wrote: > I solved this problem a few years back. > > https://github.com/sdgathman/trippfix > > The short answer is USB is broken on the model (but the power management > is excellent, handling switchover to generator power without a hitch). > > The workaround is to do a usb port power off when the Tripplite USB > hangs.  But hubs

On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell <bferrell at baywinds.org> wrote: >On 9/30/20 8:52 AM, H wrote: >> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >Family USB 3.0 xHCI Controller >My system has these: > >00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >Family USB xHCI (rev 05) >00:1a.0 USB controller: Intel

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

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

On 9/30/20 8:52 AM, H wrote: > 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller My system has these: 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8

Installed a new Tripplite Smart1500LCD on a CentOS 7 host using the usb connector. Nut does connect: $upsc ups battery.charge: 100 battery.runtime: 1407 battery.type: PbAC ... But after a half hour or so the connection is lost. Restarting nut re-establishes the connection. Any idea what might be causing the dissconnection?

Hi, I'm trying to assign a complete USB Hub to my Windows 10 guest, using libvirt 1.3. Following the documentation, I tried adding the following to the definition of my guest: ... <devices> ..    <hub type='usb'>       <address type='usb' bus='1' port='10.2'/>     </hub> .. </devices> To get the correct port, I used lsusb:

On 09/29/2020 11:11 PM, Bruce Ferrell wrote: > On 9/29/20 7:21 PM, H wrote: >> kernel: usb 1-9: unable to read config index 0 descriptor/all > > Those error messages mean that the device isn't responding to the Get-Descriptor request. > > I think a step back and checking the usb subsystem, in general, might be a good idea: > > Let's start with the full output of

On Sat, Nov 16, 2013 at 11:14 PM, EGO.II-1 <eoconnor25 at gmail.com> wrote: > On 11/16/2013 10:04 PM, Michael B Allen wrote: >> Broke affinity for irq 27 > Found this online....don't know if it pertains to your issue, but check > it out. > > https://www.centos.org/forums/viewtopic.php?t=3941 Unfortunately updating the BIOS did not fix the problem (even though the

I recently purchased a UPS from http://www.microcenter.com/product/470131/5E_1,100W_2,200VA_6-Outlet_UPS It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS SKU: 147140 Mfr Part #: 5E2200USB-LA UPC: 743172064875 "The Eaton 5E is an essential line interactive UPS that provides cost effective and reliable power protection against power outages and bad power quality. Thanks to its small

Hi. I have a Supermicro 5018D-FN4T (Xeon D-1541 based SBC) that I use for virtualization. I?m running Centos 7.3 on it (updated), with the CentOS-QEMU-EV.repo repository as the source for virtualization packages. I run an Ubuntu 16.04-2 guest VM on it, which is ordinary enough. What?s perhaps less ordinary is that I?ve attached a Lexar Media, Inc. ?Lexar Professional Workflow CR1 CFast 2.0 USB

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

On Jan 1, 2014, at 3:50 PM, Ariel Wainer wrote: > On 01/01/14 17:33, Charles Lepple wrote: >> Disappointing. I will add a note in the man page for that, too. (Maybe >> it is only after the UPS is in the low battery state? You mentioned >> that it did shut down when you did the capture with the Windows >> software.) > > Yes, but I think it was because the battery

Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or? I am running CentOS 7. Thanks.

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