Displaying 20 results from an estimated 2000 matches similar to: "newhidups USBDEVFS_CONTROL failed: ret -110 messages"
2007 Jun 27
1
Using MGE UPS's with NUT and openSUSE
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
2006 Apr 26
2
newhidups dies after a few hours
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
2006 May 20
0
Re: Centos/RHEL with MGE UPS Protection Centers (usb)
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
2014 Mar 07
2
blazer_usb rqt 33 rq 9 len 8 ret -110
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:
2006 Apr 14
3
Cyberpower 900AVR/BC900D newhidups problem
I'm trying to get nut to work with a Cyberpower 900AVR. There are many
different products known by this name, but this one has the extra name
'BC900D'.
I am told by a cyberpower tech that this one should talk exactly the
same USB protocol as the 685AVR, which was recently made to work with
newhidups.
Unfortunately, when I run the SVN checkout (trunk) of nut-2.1, I get:
sstreet
2014 Mar 08
1
blazer_usb rqt 33 rq 9 len 8 ret -110
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 Nov 25
4
blazer_usb and USBDEVFS_CONTROL failed
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
2014 Apr 03
2
Eaton Nova AVR repeated USBDEVFS_CONTROL failed cmd usbhid-ups
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
2009 Nov 23
1
USBDEVFS_CONTROL failed cmd usbhid-ups
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
2015 Feb 03
0
USBDEVFS_CONTROL failed
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:
2006 Oct 16
1
Problems with newhidups and Smart-UPS 750
Hello,
I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups.
Without any reason, nut/upsmon shut down my PC:
>>>
Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71
Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery
Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost
2014 Apr 04
0
Eaton Nova AVR repeated USBDEVFS_CONTROL failed cmd usbhid-ups
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:
2006 Jul 20
2
CyberPower CP1200AVR/BC1200D problems
I recently purchased a CyberPower CP1200AVR UPS and am trying to get NUT
2.0.3 or NUT 2.1.0 to work with the newhidups driver, but am having
little success. Before I purchased I did some googling and saw people
talking about problems so I'm guessing it may not be supported yet? I
did find some posts about people getting it to (sort of) work with some
hacks, but couldn't tell if they
2011 Oct 01
1
USB CyberPower
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:
2013 Nov 26
0
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
2008 Apr 08
1
USB trouble / nut 2.2.1 / MGE Protection Center 675
Hi,
There is many (20 per day on average) messages like:
kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161
rq 1 len 2 ret -110
usbhid-ups[6768]: HIDGetDataValue: Connection timed out
What can be done do correct that problem?
best regards,
Franck
my configuration:
debian etch
nut 2.2.1 (recompiled source from testing to use latest version before
posting here) updated
2010 Oct 13
1
Powercom WOW-525U nut configuration
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 -
2003 Dec 11
0
Error setting up USB FXS
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:
2006 Apr 04
2
newhidups crashes intermittently (double free or corruption)
Hi,
I'm running nut 2.0.3 on Gentoo connected to an MGE ProtectionCenter
675. newhidups intermittently crashes. Any ideas?
N.
# /usr/lib/nut/newhidups -a mgeups
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3)
Detected a UPS: MGE UPS SYSTEMS/PROTECTIONCENTER
Using subdriver: MGE HID 0.8
This is the error I'm getting
*** glibc detected *** /usr/lib/nut/newhidups: double free or
2018 Dec 02
0
MGE EllipseMAX 1500 shuts down after a few hours
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