similar to: News about libusb-1.0(+0.1) support effort

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

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"

> >> # nut-scanner >> Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. > > Although I suspect that the USB portion of nut-scanner could probably be replaced with a small shell script that parses the output of lsusb, this shouldn't be too hard to fix. Logged, in case it

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 -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

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: # nut-scanner Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. There's also a bug in the configure script on 64 bit

Hi all, I am doing some final testing of the libusb-1.0 branch (specifically https://github.com/zykh/nut.git branch libusb-1.0+0.1 @ dfd514e7), and I am running across a regression in usbhid-ups relative to the previous libusb-0.1 code running on FreeBSD. Basically, the master (2.7.4+; c703fa75) code was able to start running as root, drop privileges (usually to uucp, the default for the ports

On Sep 10, 2019, at 10:40 AM, grumpy at mailfence.com wrote: > > i have a OMNIVS1500XL > i have used nut for several years on a full sized pc with no problems > i am trying to get nut working with this ups on a raspberry pi > i tried with a pi 3b running raspbian stretch > i tried with a pi 3b running raspbian buster The “unable to handle kernel paging request” points to a

Hi Charles, Upsmart version is 1.5, copyright says 2012-2014 the github issue seems a bit worse, since it reports: received 10 (85) 1.158700 read: UPS No Ack whereas my system reports : 6.239688 Full update... 6.239776 send: Q1 6.261270 received 47 (40) 6.261371 read: (234.0 000.0 234.0 012 49.9 27.4 29.0 00001000 but it keeps repeating the last line,

On Nov 22, 2017, at 7:39 PM, Charles Lepple <clepple at gmail.com> wrote: > > The new branch will only attach to the device if I pass the '-u root' flag to usbhid-ups. fixed: https://github.com/networkupstools/nut/compare/dfd514e...80bc452 still looking for volunteers to test the libusb-1.0 code on FreeBSD and other systems.

On Mar 22, 2017, at 6:27 AM, Marc Kessels <marc at kessels.name> wrote: > > with NUT, I am able to connect to the UPS using the blazer_usb and nutdrv_qx. However, the reported values are constant, and only change if I run the UPSmart tool (It can run in parallel). What can I do to get NUT to receive updated values? Which version (and how old) is UPSmart? This just came up in a

On Apr 25, 2013, at 9:42 AM, Christian Wiese wrote: > I created a pull request #27 which is fixing the issue. > > # nut-scanner -qNU > [nutdev1] > driver = "usbhid-ups" > port = "auto" > vendorid = "051D" > productid = "0002" > product = "Back-UPS ES 700G FW:871.O2 .I USB FW:O2" > serial = "5B1243T01934"

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

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

I doesn't fix any problems but I think it is nicer code. :-) I don't think we want to call usb_detach_kernel_driver_np unless we claimed the device. $ diff -uw libusb.c.bak libusb.c.new --- libusb.c.bak 2010-05-11 09:35:39.000000000 -0400 +++ libusb.c.new 2010-05-11 09:32:44.000000000 -0400 @@ -206,18 +206,21 @@ upsdebugx(2, "failed to

Hello! I have an UPS made by Powercom company; the model of the UPS is RPT-800A. This UPS has a USB port, which can be used to connect the UPS to a PC and read various data from the UPS (percentage of load, input voltage, output voltage, etc.). So I download the NUT binary package for Windows, install and set it up using manual. Everything works fine for a few hours (I can get the data I

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 ) i386: 7d2661ef76a592b0742f34abc20ba700 libusb-0.1.12-6.el5.i386.rpm 6c35a97adc73c5b361b3f56a2c582a45 libusb-devel-0.1.12-6.el5.i386.rpm Source: