search for: 2a37

...Network UPS Tools - UPS driver controller 2.7.2.6_RTD ... > 0.000137 Shutdown UPS: rtdups > 0.000160 exec: /usr/local/ups/bin/usbhid-ups -a rtdups -k > Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) > USB communication driver 0.32 > Can't claim USB device [2a37:5110]: No such file or directory > 0.007491 Driver failed to start (exit status=1) > ----------------------------------------------------------------------------------------------- Hello Bob, What happens if you execute the command /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD B...

...en device, skipping. (Permission denied) 0.004504 Checking device (1D6B/0001) (007/001) 0.004518 Failed to open device, skipping. (Permission denied) 0.004530 Checking device (1D6B/0001) (006/001) 0.004545 Failed to open device, skipping. (Permission denied) 0.004555 Checking device (2A37/5110) (001/005) 0.005862 - VendorID: 2a37 0.005876 - ProductID: 5110 0.005884 - Manufacturer: RTD Embedded Technologies, Inc. 0.005891 - Product: UPS25110 0.005898 - Serial Number: 123456789ABC 0.005906 - Bus: 001 0.005914 Trying to match device 0.005927 Device matches 0....

..., 2015, at 8:49 AM, Rob Groner <rgroner at RTD.com> wrote: > > Charles, > > 3.16.6.-2-desktop I think that corresponds to this file: http://lxr.free-electrons.com/source/drivers/usb/core/devio.c?v=3.16 (but I don't see anything obvious there) What does "lsusb -vvv -d 2a37:" return? Usually I'd say run that as root when the driver isn't running, but I'm looking for the device descriptor, which should be available regardless. The version number of your driver says "2.7.2.6_RTD". Which Git revision does that correspond to in the NUT reposito...

...e: > Well, I tried the same script method with openSUSE 13.2, and it still did not execute. > > So I tried the system method, and it worked 1 time out of 3 attempts. I captured the last failure: > 2015-09-04T11:43:38.825317-04:00 linux-5048 upsdrvctl[1887]: Can't claim USB device [2a37:5110]: No such file or directory > 2015-09-04T11:43:38.825970-04:00 linux-5048 upsdrvctl[1887]: Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) > 2015-09-04T11:43:38.826243-04:00 linux-5048 upsdrvctl[1887]: USB communication driver 0.32 > 2015-09-04T11:43:38.826934-04:00 linux-50...

rtd at linux-5048:~> lsusb -vvv -d 2a37: Bus 001 Device 005: ID 2a37:5110 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProto...

...r) (power value 1) Using power down flag file /etc/killpower rtd at linux-5048:~> sudo /usr/local/ups/sbin/upsdrvctl shutdown Network UPS Tools - UPS driver controller 2.7.2.6_RTD Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB communication driver 0.32 Can't claim USB device [2a37:5110]: No such file or directory Driver failed to start (exit status=1) ----------------------------------------------------------------------------------------------- I executed lsusb to verify the USB device is there, and it is. I tried the shutdown command again with debug enabled, but it did...

...71657 - Manufacturer: Linux 3.16.6-2-desktop uhci_hcd 0.071662 - Product: UHCI Host Controller 0.071668 - Serial Number: 0000:00:1d.0 0.071673 - Bus: 006 0.071677 Trying to match device 0.071687 Device does not match - skipping 0.071741 Checking device (2A37/5110) (001/005) 0.073249 - VendorID: 2a37 0.073262 - ProductID: 5110 0.073268 - Manufacturer: RTD Embedded Technologies, Inc. 0.073274 - Product: UPS25110 0.073279 - Serial Number: 123456789ABC 0.073285 - Bus: 001 0.073290 Trying to match device 0...

Hello Bob, > I had preferred the shutdown script method because it was a little more > straight-forward, and possibly more portable. This guide is meant to > help people get the UPS up and running, whatever their Linux distro. I > don't know how common the systemd implementation is across various Linux > distros. You will need to support Linux systems with and without

On Sep 9, 2015, at 9:40 AM, Rob Groner <rgroner at RTD.com> wrote: > > I'm not sure which USB lib it compiled against. What does this return? ldd /path/to/driver -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150909/ba08f4c0/attachment.html>

Roger, Well, I tried the same script method with openSUSE 13.2, and it still did not execute. So I tried the system method, and it worked 1 time out of 3 attempts. I captured the last failure: 2015-09-04T11:43:38.825317-04:00 linux-5048 upsdrvctl[1887]: Can't claim USB device [2a37:5110]: No such file or directory 2015-09-04T11:43:38.825970-04:00 linux-5048 upsdrvctl[1887]: Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) 2015-09-04T11:43:38.826243-04:00 linux-5048 upsdrvctl[1887]: USB communication driver 0.32 2015-09-04T11:43:38.826934-04:00 linux-5048 upsdrvctl[18...

.../sec %CPU 100 5101 96.4 28041 21.4 10717 15.0 4909 91.8 52454 19.0 27812.5 97.3 The block reads on ext2 seem a bit exagerated. Kudos Stephen! -- Carlos Morgado - chbm(at)chbm(dot)nu - http://chbm.nu/ -- gpgkey: 0x1FC57F0A http://wwwkeys.pgp.net/ FP:0A27 35D3 C448 3641 0573 6876 2A37 4BB2 1FC5 7F0A

> On Sep 9, 2015, at 10:12 AM, Rob Groner <rgroner at RTD.com> wrote: > > linux-5048:/home/rtd # ldd /usr/local/ups/bin/usbhid-ups > linux-vdso.so.1 (0x00007fff403fc000) > libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f7c34b56000) The last line seems to indicate that it is the real libusb-0.1, not -compat. What kernel version on openSUSE? --