similar to: Please help installing libusb-win32.

I'm trying to use NUT with PowerCom RPT-1000AP on CentOS 6/7 ups.conf: [RPT-1000] ??? driver = "usbhid-ups" ??? port = "auto" ??? vendorid = "0D9F" ??? productid = "0004" ??? product = "HID UPS Battery" ??? serial = "004-0D9F-000" ??? vendor = "POWERCOM Co.,LTD" ??? bus = "002" ??? pollfreq = 10 ??? offdelay = 120

On Jul 16, 2019, at 3:52 AM, Patrick M. Hausen wrote: > The OS is FreeBSD: > > FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64 > > This is the device: > > ugen0.6: <POWERCOM Co.,LTD HID UPS

Hi Charles, > Sigh, I wish the vendors wouldn't change operation without changing identifiers. > > Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. From PCM_USB_LIST_device2014.pdf attached

On Nov 12, 2014, at 3:53 AM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > Hi Charles, > >> Sigh, I wish the vendors wouldn't change operation without changing identifiers. >> >> Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? > > No-no, there is no an old 0x0004 or new 0x0004

Hi Guys, Am a Linux newbie and need some help setting up this UPS with NUT on Cent OS 5.6. So basically I have the following packages installed with yum: libusb-devel-0.1.12-5.1.x86_64 libusb-devel-0.1.12-5.1.i386 libusb-0.1.12-5.1.x86_64 libusb-0.1.12-5.1.i386 nut-2.2.2-1.el5.x86_64 When I run service ups start I get the following: Starting UPS driver controller:

Dear nut users, I am running nut-2.6.0 on Slackware-Linux-13.37.0 with kernel 2.6.37.6. I am trying to get the software work for a repotec UPS with model name: RPT-1003AU. The UPS communicates with the computer via USB. I know that the model is not officially supported but I want to try out whether it will work with some of the repotec drivers. Here is the result with the genericups upstype=13

Hi list here is the patch to make fentonups recognize some PowerCOM's UPS's, and to setup terminal lines for them (at least for SMK-1500a) as powercom's original upsmon do. fentonups -x powercom works correctly with SMK-1500a (it screamed ''Communications with UPS lost - check cabling' or 'Short read during UPS id sequence' without this patch). Sorry for

Hello. I've been trying to got it work but haven't luck. I'm using NUT 2.6.0-1 under Windows XP with libusb driver installed (USB\VID_0D9F&PID_0004&REV_0001). I had tryed all options with such config: *PWCOM] driver = usbhid-ups port = auto vendorid = 0d9f desc = "Powercom BNT-800AP" type=BNT* * *Here is output from CMD:*

Hi, Arjen; I am new to linux and not sure how to create the PowerCom-usb driver. So could you please compile powercom-usb file for me. I am happy to test it out with the USB PowerCom Ups. Thanks, Paul MCSE/MCSA/MCP ------------------------------ Message: 2 Date: Mon, 03 Sep 2007 11:13:32 +0200 From: Arjen de Korte <nut+users at de-korte.org> Subject: Re: [Nut-upsuser] Powercom USB UPS is

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o

Hello world, As posted at https://github.com/networkupstools/nut/issues/300#issuecomment-969385505 and https://github.com/networkupstools/nut/issues/300#issuecomment-970243340 in greater detail, during the past weekend I have updated the "libusb-1.0" and "libusb-1.0+0.1" branches in NUT repository, so their proposed changes are integrated over the past few years of

Hello world, As posted at https://github.com/networkupstools/nut/issues/300#issuecomment-969385505 and https://github.com/networkupstools/nut/issues/300#issuecomment-970243340 in greater detail, during the past weekend I have updated the "libusb-1.0" and "libusb-1.0+0.1" branches in NUT repository, so their proposed changes are integrated over the past few years of

On Sun, Dec 14, 2014 at 07:22:01PM -0500, Mark LaPierre wrote: > On 12/14/14 07:29, ken wrote: > > uname -r; rpm -q libusb > > CentOS 6.6 says: > [mlapier at mushroom ~]$ uname -r; rpm -q libusb > 2.6.32-504.1.3.el6.i686 > libusb-0.1.12-23.el6.i686 CentOS 5 has: libusb-0.1.12 CentOS 6 has: libusb-0.1.12 libusb1-1.0.9 CentOS 7 has: libusb-0.1.4 libusbx-1.0.15

Trying to install Canon printer driver package (rpm), I get a dependency error: libusb-1.0.so.0 is needed.... The version currently installed on my 5.9 system is libusb-0.1.12-6.el5 and, AFAIK (per yum), no upgrade to that is available. So question: Do higher centos versions have libusb-1.0.so ? (We could perform a quick inventory with: uname -r; rpm -q libusb Thanks.

I've missed that one, already a month ago! investigation needed... -- Arnaud ---------- Forwarded message ---------- From: Daniel Drake <dsd at gentoo.org> Date: 2008/5/26 Subject: [fprint] libusb-1.0 enters beta To: fprint at reactivated.net Hi, libusb-1.0 has entered beta. http://www.reactivated.net/weblog/archives/2008/05/libusb-10-enters-beta/ libusb-1.0 is the lowest level

CentOS Errata and Bugfix Advisory 2011:1498 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1498.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 7d2661ef76a592b0742f34abc20ba700 libusb-0.1.12-6.el5.i386.rpm 565c12782b350526c032d83e362f06b5 libusb-0.1.12-6.el5.x86_64.rpm 6c35a97adc73c5b361b3f56a2c582a45

On Nov 26, 2017, at 3:15 PM, Sam Varshavchik wrote: > > Charles Lepple writes: > >> still looking for volunteers to test the libusb-1.0 code on FreeBSD and other systems. > > On Fedora 27, running commit 2999c95f0: Thanks for checking this. I should have been more clear in the second email in the thread, but commit 2999c95f0 is on the original "libusb-1.0"

Hi, I've been asked to find out some answers from libusb maintainer, so I'm forwarding them: - Why nut uses legacy libusb-0.1 api and not libusb 1.0 ? - Is there any plan to update it to libusb 1.0? Thanks, Michal

I just upgraded the FreeBSD buildbot machine from 6.4 to 8.0, and I ran across some interesting differences. The libusb API that we use (0.1) is available in /usr/include/usb.h and /usr/lib/libusb.* as before, but it seems to be the compatibility layer from libusb 1.0. However, it doesn't include the libusb-config binary. This is from the 'ports' Makefile for NUT: ########## - -

NUT developers, just thought I'd share some notes and ideas on using valgrind against the NUT USB drivers on Linux. Stepping back a bit, I wanted to make sure that the tripplite_usb driver* wasn't using any uninitialized memory, or leaking memory over time. valgrind (specifically, the memcheck tool) runs the code in a special dynamic translator that checks every memory access to see if