similar to: blazer_usb and USBDEVFS_CONTROL failed

On Nov 25, 2013, at 4:56 PM, Fabio Cecamore wrote: > 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 "ret

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:

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:

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

2013/12/9 Fabio Cecamore <ceca_89 at hotmail.com>: > and the UPS don't wake up after the whiteout.. 2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: > desc = "AtlantisLand Host Power 851+" Is your UPS an 'Atlantis Land Host Power 851' or an 'Atlantis Land One Power 841+'? The first one should be using a slighty modified version of the

2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: > Hi all, Hi > I've problem with the management of my AtlantisLand UPS, the UPS don't want > to wake up after the whiteout and I don't have any idea why.. Some (very old) units are known to have problems with small values for ondelay (hence the default 3 minutes value):

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

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

Hi all, I've problem with the management of my AtlantisLand UPS, the UPS don't want to wake up after the whiteout and I don't have any idea why.. This is the ups.conf: [ups] driver = blazer_usb subdriver = cypress vendorid = 0665 productid = 5161 port = auto desc = "AtlantisLand Host Power 851+" pollinterval = 10 offdelay = 60 this is the upsc result: battery.charge: 100

Thanks for your reply Hyouko, these are the actual not working parameters: driver.parameter.offdelay: 60 driver.parameter.ondelay: 5 ups.delay.shutdown: 60 ups.delay.start: 300 and the UPS don't wake up after the whiteout.. My UPS is not so old :( Il 09/12/2013 16.04, hyouko at gmail.com ha scritto: > 2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: >> Hi all, > Hi

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

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:

On Sep 21, 2015, at 7:38 AM, Charles Lepple <clepple at gmail.com> wrote: > > (please keep the list CC'd) > >> On Sep 21, 2015, at 5:09 AM, Uro? Gaber <uros.gaber at gmail.com <mailto:uros.gaber at gmail.com>> wrote: >> >> Hi. >> No for me nutdrv_qx driver is not working with this UPS. >> Here's log: >> Sep 21 11:06:39

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

Hi, Sometime ago I asked the question about getting nut to run on my iMac as I was having trouble getting the USB driver to behave with OS X. The same driver under LINUX is fine. It was suggested that the better option might be to run nut on a Rasberry PI instead and monitor the nut daemon from the iMac. Well I have bought a Rasberry PI, I have other things planned for it. I have installed nut

On Nov 25, 2014, at 8:17 PM, Victor Porton <porton at narod.ru> wrote: > Well, also below in dmesg: > > [ 190.249219] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 -110 is -ETIMEDOUT. > 26.11.2014, 03:05, "Victor Porton" <porton at narod.ru>: >> A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the

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 -

Well, also below in dmesg: [ 190.249219] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 26.11.2014, 03:05, "Victor Porton" <porton at narod.ru>: > 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

Hello, I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being halted upon booted up. Is it possible to use megatec_usb driver in the new version? # NUT