similar to: USBDEVFS_CONTROL failed

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:

Not of a big help here, but I think it's a voltronic power vesta 650: http://www.voltronicpower.com/oCart2/index.php?route=product/product&path=37&product_id=52 If that is the case, it should work both with the blazer drivers (i.e. all but the shutdown sequence) and with the now defunct voltronic ones. With arno's words: "We are currently merging a new driver to replace

On Nov 8, 2013, at 3:23 AM, Josu Lazkano wrote: > Hello, I have a Salicru SPS One 700VA device, I want to manage it with > Debian Whezzy. > > I read some information in the net about how to configure but I can > not get it working. I'm assuming you mean this blog post? http://blog.ciberterminal.net/2013/04/28/ups-salicru-en-nut/ > Could you help with this? > >

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, I have a Salicru SPS One 700VA device, I want to manage it with Debian Whezzy. I read some information in the net about how to configure but I can not get it working. Could you help with this? This is the log when I connect the USB: [ 3194.688204] usb 4-4: new low-speed USB device number 2 using ohci_hcd [ 3194.857239] usb 4-4: New USB device found, idVendor=0665, idProduct=5161 [

Hello all, I have a Salicru UPS (Salicru SPS One 700VA) working great in Debian Wheezy, but I want to move it to a OpenWRT router. I configured same as in Debian but I can not get it working: # upsd Network UPS Tools upsd 2.6.5 fopen /var/run/upsd.pid: No such file or directory listening on 192.168.1.240 port 3493 /etc/nut/ is world readable Can't connect to UPS [salicru]

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

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

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:

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:

Thanks Charles, This is the permission tree: # ls -l /dev/bus/usb/001/001 crw-r--r-- 1 root root 189, 0 Feb 8 20:23 /dev/bus/usb/001/001 If I attache the USB cable there is nothing in dmesg, and there is nothing in lsusb: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It looks like it is not detected. In Debian it looks great: # lsusb Bus 004 Device

On Feb 8, 2015, at 2:29 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > # upsd > Network UPS Tools upsd 2.6.5 > fopen /var/run/upsd.pid: No such file or directory > listening on 192.168.1.240 port 3493 > /etc/nut/ is world readable > Can't connect to UPS [salicru] (blazer_usb-salicru): No such file or directory Check the messages from the blazer_usb driver when

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.

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

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

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:

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