similar to: usbhid-ups disconnects with Eaton Ellipse 1000S

Hi, I keep getting the following messages (or similar) in my syslog: Nov 23 11:38:08 io kernel: [763936.921566] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -110 Nov 23 11:38:08 io kernel: [763936.972569] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -75 Nov 23 11:38:08 io kernel: [763936.976568] usb 3-2: usbfs: USBDEVFS_CONTROL

I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. It happens several times a day that I get a message about Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 Apr 3 16:41:54 kernel: [422586.041057] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 3 ret

On Apr 3, 2014, at 3:40 PM, Adam Pribyl wrote: > I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. Which kernel version? > It happens several times a day that I get a message about > > Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 > Apr 3 16:41:54 kernel:

OPENSOURCE wrote: > > I hope this answer your questions, and I hope you're ready to wait a bit > more. > Sure, NP for me, thanks for the feedback Arnaud. I have to admit that past days im having the syslog with a lil more activity from the new usb attached unit (ellipse ASR 1000 VA) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2-pre2) Detected an UPS: MGE UPS

I have restored original configuration and enabled the ignorelb flag. I didn't point out in the original e-mail that after every poweroff the battery percentage is reported at 40% instead of 100% and charges slowly again to 100%. Maybe the UPS sends a LB event and shuts down immediatly as suggested in the manual. But the UPS powered off again. The variables reported by upsc can be found

The UPS is connected to the following environment: OS: Debian GNU/Linux 9.6 (stretch) NUT version: 2.7.4-5 Device output from lsusb: 0463:ffff MGE UPS Systems UPS Model name: MGE EllipseMAX 1500 URLs: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-MAX-eol.aspx?cx=97&GUID=7BB6CD53-9F6D-4D62-B326-1099F137BF8D http://powerquality.eaton.com/68558.aspx?cx=97 The problem

On Dec 1, 2018, at 3:45 PM, raul <raulvior.bcn at gmail.com> wrote: > > The UPS is connected to the following environment: > OS: Debian GNU/Linux 9.6 (stretch) > NUT version: 2.7.4-5 > Device output from lsusb: 0463:ffff MGE UPS Systems UPS > Model name: MGE EllipseMAX 1500 > URLs: >

OS name and version, *CentOS release 6.10 (Final) Linux 2.6.32-754.3.5.el6.centos.plus.x86_64 #1 SMP Wed Aug 15 02:28:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux* exact NUT version Name : nut Arch : x86_64 Version : 2.6.5 Release : 2.el6 Size : 4.2 M Repo : installed >From repo : epel Summary : Network UPS Tools URL :

I have a ups that doesn't always (sometimes it does) load NUT right. I use Gentoo: * sys-power/nut Latest version available: 2.6.0-r1 Latest version installed: 2.6.0-r1 Size of files: 1,663 kB Homepage: http://www.networkupstools.org/ Description: Network-UPS Tools License: GPL-2 The kernel is 3.0.4. Here is the dmesg output:

Dear List, I have an MGE Ellipse 1500. I run openSUSE 10.2, kernel 2.6.18, libusb 0.1.12, nut 2.0.5. ps shows that the following processes are running: /usr/lib/ups/driver/newhidups -a mgeups /usr/sbin/upsd -u root /usr/sbin/upsmon /usr/sbin/upsmon NUT operates correctly, shutting down the server after 4 minutes without power. However I'm seeing 25 to 50 messages logged each day in

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8

Hello, I have a Salicru UPS in a Debian Wheezy connected with a USB HUB: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ... Bus 001 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial The problem is that I have some failed messages: # dmesg ... [90941.136274] usb 1-3.7: usbfs:

please subscribe to the nut user mailing list ( http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser) and post the output of "/path/to/usbhid-ups -DDDDD -a <your_ups_name_in_ups.conf>" cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

hi all Using a vanilla 2.4.23, I try to setup the USB FXS interface to add an old gray 1960 rotary dial phone for a demo. But it doesn't work :( Can someone decipher the below messages and help me out here? Please ask if more info is needed roy usb.c: kusbd: /sbin/hotplug add 4 usb.c: kusbd: /sbin/hotplug add 4 usb.c: kusbd: /sbin/hotplug add 4 usb.c: kusbd: /sbin/hotplug add 4 hub.c:

2014-03-08 14:26 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > >> Are the messages a problem? Or could I ignore? > > Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query. Thanks for the

Hello list, I have a "Salicru SPS One 700VA" in a Debian Wheezy server. I configured a week ago, it works well, but today it start to show "UPS salicru at 192.168.x.x:3493 is unavailable" And I got this in the system logs: # dmesg [147080.501925] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 128 rq 6 len 255 ret -62 [147080.503913] usb 4-5: usbfs:

Dear List, I thought it might be useful if I wrote up my notes on getting an MGE UPS to work with NUT and openSUSE. The MGE UPS (an Ellipse 1500 USB) will work well with NUT and openSUSE 10.2, but not "out-of-the-box": there are some things you need to do: Intro. MGE have built rpms of NUT which greatly simplify installation. Merci MGE. I used the rpm's for nut-2.0.5 and the

Hello, I'm using NUT to manage a MGE Ellipse ASR UPS, with the newhidups driver. It works fine, except that after a few hours, I get a few errors from the kernel and the driver dies. Here's the output from the syslog: Apr 26 02:00:41 ezquiel kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Apr 26 02:00:43 ezquiel last message repeated 2 times

Hi all, I am trying to communicate to this Eaton Ellipse (see above) using nut from a Debian Squeeze system on Armel architecture. But have not succeeded so far. Version: Linux b3 2.6.39.4-11 #1 Tue Apr 3 21:45:12 FET 2012 armv5tel GNU/Linux Nut version is 2.4.3-1.1squeeze2 this information if from dpkg. NUT installation method:from debian package for armel. The problem is I cannot