similar to: More information on USB bus

Maybe a kernel USB issue, but people on this list may have encountered this issue. I am testing a new UPS (EATON 5E 1500iUSB) and am having a problem with the USB connection failing. My old UPS (EATON Ellipse MAX 1500) works just fine with the latest f30. Both devices identify as ID 0463:ffff MGE UPS Systems UPS To narrow the focus I booted recent live CDs on a PC that has no other USB devices

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, I have a eaton 1500 that connects to an Ubuntu Xenial box via USB. The UPS works, however exactly *ever 5 minutes* it disconnects and reconnects and I see this in syslog: Mar 10 19:50:32 spike kernel: usb 4-5: USB disconnect, device number 103 Mar 10 19:50:33 spike kernel: usb 4-5: new low-speed USB device number 104 using ohci-pci Mar 10 19:50:34 spike kernel: usb 4-5: New USB device found,

Hi everybody, I installed and configured Nut 2.4.3 on Debian Squeeze, using package. It monitors an MGE Pulsar 1500 UPS in standalone mode. Here are parts of upsmon.conf : SHUTDOWNCMD "/bin/bash /root/extinction.sh >> /var/log/ups/ups.log 2>>&1" NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh" [...] NOTIFYFLAG ONBATT SYSLOG+EXEC At startup, driver, upsd and upsmon

Hi Greg, I haven’t but I will give that a shot later this week and advise. Thanks for the tip. Thank you, David Zomaya Technical Support [cid:image007.png at 01D525AF.B38D63F0] 1111 W. 35th Street | Chicago, IL 60609 USA 773.869.1156 | david_zomaya at tripplite.com [cid:image008.png at 01D525AF.B38D63F0]<http://www.tripplite.com/> From: Nut-upsuser

Charles, So I installed a minimal CentOS 6.5 installation on the Fedora box this morning and I got the same issue. Below are the kernel versions used. CentOS 6.5 Minimal - [root at nemo tmp]# uname -a Linux nemo 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root at nemo tmp]# rpm -qa | grep nut nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64

A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the UPS; the webcam is idVendor=17a1, idProduct=0128): [ 1.317085] usb 4-1: new high-speed USB device number 2 using ehci-pci [ 1.405223] tsc: Refined TSC clocksource calibration: 3395.557 MHz [ 1.405228] Switching to clocksource tsc [ 1.449642] usb 4-1: New USB device found, idVendor=8087, idProduct=0024 [ 1.449648]

Arno, thanks for taking the time to write back and no worries about lag, we're all busy and I'm grateful there is a community to interact with to begin with. You're right - the problem went away once I actually configured nut. I guess I was too "cautious" and when I saw the errors I thought something was wrong with the usb connection and didn't try to get nut going

I do not see /dev/sd* for this USB Jun 27 17:53:54 host.example.net kernel: : usb 4-9: new high speed USB device number 3 using xhci_hcd Jun 27 17:53:54 host.example.net kernel: : usb 4-9: New USB device found, idVendor=0781, idProduct=5567 Jun 27 17:53:54 host.example.net kernel: : usb 4-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 27 17:53:54 host.example.net kernel: : usb

On 10/07/15 04:26, Charles Lepple wrote: > On Jul 9, 2015, at 9:43 AM, paul at paulcarmichael.org wrote: > >> Is there currently a way of implementing NUT with an Ovislink Chrome 1500 UPS? > > Not sure. There was a thread in February talking about an Ovislink Chrome 1000, but I don't think we ever resolved what was causing the "Device busy" error: > >

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 have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU:

Ok, so I have made some progress that seems to suggest the initial “fix” I stumbled upon isn’t required. I haven’t yet worked backwards to figure out reasons why our customers have had similar complaints or solve the problem on the CentOS VM yet, but that is on the todo list. I am hoping it ends up just being not enabling the service on startup, but I can’t say that explains away all the symptoms

Good day! I'm struggling to connect by Advice Partner PRPC650 UPS to Nut. The UPS uses USB for communication and the current problem is that serial device (/dev/ttyUSB*) is not detected. OS is Debian Lenny (same behavior on Ubuntu Hardy). Did anyone have any success with this UPS? Here is what my dmesg and udevmonitor say (on Debian): dmesg: usb 2-3: new low speed USB device using ohci_hcd

Package: xen-hypervisor-3.4-amd64 and linux-image-2.6.32-5-xen-amd64 Version: 3.4.3-1 and 2.6.32-15 Hello all, GRUB-PC does not automatically populate Xen related parameters in /boot/grub/grub.cfg so I added them manually (see below). All the packages involved on my Dell PowerEdge R710 running Debian GNU/Linux Squeeze AMD64 are from the Squeeze repository. There are four (4) 1TB SATA HDD

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

Updates on this: 1) Making progress in the related Dev list thread here: https://alioth-lists.debian.net/pipermail/nut-upsdev/2019-June/007440.html I’ll keep that thread up to date with progress as I go. But if there are specific things it would make sense to test here, just let me know. Otherwise, I figure reducing redundancy makes sense? 2) I tried disabling usbcore.autosuspend, but

Hey, was wondering if I could get a quick sanity check. We have a SmartUPS 1500 RM2U which we have connected to a box via USB. It seems like every 40-45 seconds it becomes disconnected and reconnected. Though this only happens when we have NUT enabled, otherwise it's fine. When it is disconnecting and reconnecting running lsusb doesn't show it disconnecting. After having it sit like that

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

Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,