Displaying 20 results from an estimated 2144 matches for "usbhid".
2011 Oct 01
1
USB CyberPower
...device number 5
usb 2-3: new low speed USB device number 6 using ohci_hcd
usb 2-3: New USB device found, idVendor=0764, idProduct=0501
usb 2-3: New USB device strings: Mfr=3, Product=1, SerialNumber=0
usb 2-3: Product: CP550HG
usb 2-3: Manufacturer: CPS
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len
255 ret
-110
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len
255 ret
-62
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len
9 ret -6
2
usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len
376 ret
-62
usb 2-3: u...
2019 Jul 18
1
Two APC900 UPS on the same usbbus1
On 18.07.19 04:51, Charles Lepple wrote:
> On Jul 16, 2019, at 9:43 AM, Markus Grundmann wrote:
>> Whenever I called "lsof -p <pid>" for both "usbhid-ups" processes I notice that only the ugen/1.5.0 (aka /dev/usb/1.5.0) device was used. After my "patch" the drivers was called corect with the option -x and the output of "upsc" reports the right UPS and serialno.
> Are you sure that the "serial = ..." paramete...
2019 Jul 16
2
Two APC900 UPS on the same usbbus1
...test source code and with my "patch" I was able to get the right
information from each UPS are expected (correct serial no and other).
In my ups.conf I have added the keyword "serial" to identify the right
UPS.
Whenever I called "lsof -p <pid>" for both "usbhid-ups" processes I
notice that only the ugen/1.5.0 (aka /dev/usb/1.5.0) device was used.
After my "patch" the drivers was called corect with the option -x and
the output of "upsc" reports the right UPS and serialno.
[Drivers after patch]
root 81706 0.0 0.0 11880 3040...
2015 Oct 23
2
problem with compiling on Cygwin64
Thank you for responding to my problem
I have no problem building in Debian 8 , the problem is with Cygwin64
I see that the two lines from
Cygwin64 >>
gcc -g -O2 -Wall -Wsign-compare usbhid-ups.c -o usbhid-ups
In file included from usbhid-ups.c:32:0:
And
Debian>>>
make[1]: Entering directory '/home/walter/nut/drivers'
depbase=`echo usbhid-ups.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H -I. -I../include -I../include -g -O2 -Wal...
2016 Oct 10
4
Powerwalker VI 2200VA LCD
The UPS seems to disconnect totally, i need to physically disconnect the cable to get the UPS connected again.
A reboot is not enough.
Also tried 2 different cables, the one i use now is shielded + 2 ferrite chokes to limit interference.
But i want to use NUT since i dont have enough resources to run X..
-------- Original Message --------
Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD
2011 Jan 21
1
Building nut 2.6.0 on OpenBSD 4.8 - compile issue
...ntation: no
build and install the development files: no
The compile goes well until:
Making all in drivers
gmake[1]: Entering directory `/home/downloads/nut/nut-2.6.0/drivers'
gcc -DHAVE_CONFIG_H -I. -I../include -I../include -DSHUT_MODE
-g -O2 -Wall -Wsign-compare -MT newmge_shut-usbhid-ups.o -MD -MP -MF
.deps/newmge_shut-usbhid-ups.Tpo -c -o newmge_shut-usbhid-ups.o `test
-f 'usbhid-ups.c' || echo './'`usbhid-ups.c
usbhid-ups.c: In function 'hid_ups_walk':
usbhid-ups.c:1231: error: 'EPROTO' undeclared (first use in this
function)
usbhid-ups.c:1231:...
2014 Nov 14
2
usbhid-ups must use '-u root'
Hi all,
(Keeping this in a separate email from my first one so as to not make it
horribly complex)
I've connected my Belkin F6C120auUNV UPS to my Debian 7.7.0 host via
USB, and found that the usbhid-ups driver will not start unless I use
the option '-u root', even when starting this driver as root:
root at monitor:/lib/nut# cat /etc/nut/ups.conf
[greything]
driver = usbhid-ups
port = auto
root at monitor:/lib/nut# ./usbhid-ups -a greything
Network UPS Tools - Generic HID dri...
2019 May 07
2
nut vs ups fail
...7 May 2019 08:38:44 am Charles Lepple wrote:
> On May 7, 2019, at 5:06 AM, Gene Heskett wrote:
> > New testing install(stretch)
> > pulled in nut stuff from repo.
> > copied old wheezy configs to /etc/nut, overwriting the resident
> > files can't talk to ups, missing usbhid-ups file
>
> Gene,
>
> What do you have in /etc/nut/ups.conf? (There shouldn't be any
> passwords in that one if you're using a USB-connected UPS, but check
> to be sure. Also, I don't need any of the lines starting with "#".)
[myups]
driver=usbhid-ups
port=/...
2011 Aug 31
1
Windows 2008 R2 USBHID-UPS VendorID & Serial
Hi All,
I'm trying to configure NUT 2.6.1 on Windows 2008 R2 to recognise two APC Smart-UPS 3000 devices connected via USB cables.
I have correctly installed libusb-win32, and run the driver wizard.
In my ups.conf I have :-
[Upper]
driver = usbhid-ups
port = auto
desc = "Upper Smart-UPS 3000"
vendorid = 051d
serial = "JS1011030553"
[Lower]
driver = usbhid-ups
port = auto
desc = "Lower Smart-UPS 3000"
vendorid = 051d
serial = "JS1011030544"...
2014 Nov 14
0
usbhid-ups must use '-u root'
...ctly...)
Thanks,
Greg
On 14/11/2014 9:57 pm, Greg Vickers wrote:
> Hi all,
>
> (Keeping this in a separate email from my first one so as to not make
> it horribly complex)
>
> I've connected my Belkin F6C120auUNV UPS to my Debian 7.7.0 host via
> USB, and found that the usbhid-ups driver will not start unless I use
> the option '-u root', even when starting this driver as root:
> root at monitor:/lib/nut# cat /etc/nut/ups.conf
> [greything]
> driver = usbhid-ups
> port = auto
> root at monitor:/lib/nut# ./usbhid-ups -a greything
> Ne...
2009 Sep 08
1
usbhid-ups driver can't be killed...
Hello
I'm encountering a big problem with usbhid-ups driver : the driver hangs
after loading some other modules (stale data message) !
And we can't restart it.
We load :
i2c-piix4
adm1021
adm9240
lm75
The unloading of the modules doesn't solve the problem.
# ps -eaf | grep usb
/root 188 2 0 07:29 ? 00:00:00 [ksuspend...
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 -110
Apr 3 16:41:54 kernel: [422586.086977] usb 5-1: usbfs: USBDEVFS_CONTROL
failed cmd usbhid-ups rqt 161 rq 1 len 3 ret -75
Apr 3 16:41:54 kern...
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 failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -71
Nov 23 11:38:08 i...
2015 Dec 16
1
Passing a USB hub
...b, Driver=xhci_hcd/10p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 5: Dev 110, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 52, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 53, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 1: Dev 53, If 1, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 3: Dev 54, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 3: Dev 54, If 1, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 3: Dev 54, I...
2014 Apr 19
3
usbhid-ups pull request for consideration
I've added a pull request with changes to drivers/libusb and
drivers/usbhid-ups mainly. They are to resolve issues I encountered when
setting up a Tripp Lite SMART1500LCDT, but I think they're generally useful
to the community. Here is the pull request comment I sent:
https://github.com/networkupstools/nut/pull/122
Had trouble getting nut to work for my new Tripp Lit...
2007 Oct 17
2
usbhid-ups on openSUSE 10.3 does not see MGE Ellipse 1500
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 = us...
2012 Mar 04
2
NUT Two Apc UPSes on Windows
Hi,
I've got a question about managing two UPSes under NUT.
I have two similar model APC usb-connected UPSes to work with, but don't
know how to manage them simultaneously from under Windows. Long story
short, my ups.conf looks like this:
--- ups.conf ---
[ups1]
driver= usbhid-ups
port= auto
serial=AS1054340323
[ups2]
driver= usbhid-ups
port= auto
serial=AS1026662626
--- ups.conf ---
I tried all the combinations with vendorid, productid, vendor, product as
in the manual for usbhid-ups and libusb's test
--- TestLibUsb ---
- Manufacturer : American Power Co...
2019 May 07
2
nut vs ups fail
New testing install(stretch)
pulled in nut stuff from repo.
copied old wheezy configs to /etc/nut, overwriting the resident files
can't talk to ups, missing usbhid-ups file
Found it in /lib/nut, doesn't modprobe, not in /lib/modules/kernelversion
tree.
I need to fix this, how do I proceed? A direct address path
in /etc/modules? Doesn't work..
I did try this:
root at coyote:etc$ insmod /lib/nut/usbhid-ups
insmod: ERROR: could not insert module /l...
2019 May 06
2
<APC> <Back-UPS 950> not supported by driver <usbhid-ups>
...m interface 0: No route to host
Driver failed to start (exit status=1)
Any help for me?
Kind regards
Mathias Passow
Am 6. Mai 2019 um 15:07 schrieb Charles Lepple <clepple at gmail.com>:
On May 2, 2019, at 4:08 PM, Mathias Passow wrote:
Hi, the following UPS isnt supported by the driver „usbhid-ups“.
Manufacturer: APC
Model: Back-UPS 950 (https://www.apc.com/shop/de/de/products/APC-BACK-UPS-950VA-230V-AVR-Schuko-Sockets/P-BX950U-GR)
Config:
[USV]
driver = usbhid-ups
port = auto
desc = "USV"
…
MODE=standalone
Terminal:
root at debian-jessie-final:~# sudo upsd -u root
Network...
2018 Jul 03
2
No run cmd /usbhid-ups -k !
Hi all.
UPS is Eaton 5SC 500i.
I tested three solutions:
1. swap "usbhid-ups -a qnapups" with "usbhid-ups -a qnapups -k"
Result: server shutdown, but ups does not shut off!
2. run prog with params "upsmon -c fsd"
Result: server shutdown, but ups does not shut off!
3. run prog "upscmd -u name -p passwd qnapups shutdown.return"
and ne...