Thanks again. So one more bit (other than indeed different libusb versions) that could potentially come into play is bitness - armv7l builds are 32-bit, right?
One idea from here is to have you run the driver programs directly with high debug verbosity, e.g. `usbhid-ups -DDDDDD -s Liebert` to compare the two walls of text (at some debug level it spews byte data seen from libusb); this might be more convenient to proceed with as a github issue. Another idea, if you would be comfortable building NUT from source, would be to check if NUT v2.8.0 (and/or current git master) mis-behaves similarly if built in the Debian 11 32-bit environment against libusb-0.1. So to dissect if the issue is between NUT 2.7.4 and 2.8.0 or in the OS environment/dependencies somehow. This can get you started: https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests (take care to `configure --with-usb=libusb-0.1 ...`) - notably, you won't have to *install* this build over what have you in the OS to just test the newly built driver. Jim On Thu, Mar 21, 2024 at 7:18 AM Juan Carlos Fischer < juancarlos.fisc...@gmail.com> wrote: > Hello! > > NUT 2.7.4 > Raspberry Pi 4 Model B Rev 1.5 8 GB "Raspbian GNU/Linux 11 > (bullseye)" Linux raspberrypi 5.15.32-v7l+ #1538 SMP Thu Mar 31 > 19:39:41 BST 2022 armv7l GNU/Linux > > pi@raspberrypi:~ $ sudo ldd /lib/nut/usbhid-ups > > linux-vdso.so.1 (0xbec53000) > /usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => > /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f83000) > libusb-0.1.so.4 => /lib/arm-linux-gnueabihf/libusb-0.1.so.4 (0xb6f4e000) > libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6f22000) > libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6dce000) > /lib/ld-linux-armhf.so.3 (0xb6f98000) > > NUT 2.8.0 > Raspberry Pi 4 Model B Rev 1.5 8 GB "Debian GNU/Linux 12 (bookworm)" Linux > raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 > aarch64 GNU/Linux > > pi@raspberrypi:~ $ sudo ldd /lib/nut/usbhid-ups > > linux-vdso.so.1 (0x0000007f9051c000) > libusb-1.0.so.0 => /lib/aarch64-linux-gnu/libusb-1.0.so.0 > (0x0000007f90410000) > libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000007f90260000) > /lib/ld-linux-aarch64.so.1 (0x0000007f904df000) > libudev.so.1 => /lib/aarch64-linux-gnu/libudev.so.1 (0x0000007f90210000) > libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 > (0x0000007f901e0000) > > Best regards, > -jcf > > > On Wed, Mar 20, 2024 at 5:10 PM Jim Klimov <jimklimov+...@gmail.com> > wrote: > >> Thanks. >> >> Can you please also check (e.g. with ldd `which usbhid-ups`) which >> `libusb` variant (1.0 or 0.1) was the 2.7.4 version of the driver running >> with? >> I wonder if the two generations of that library got something >> differently?.. >> >> The commit I mentioned - >> https://github.com/networkupstools/nut/commit/207fed2282 - which added >> the exponent checks, was from 2012 and should be in 2.7.4 as well :-\ >> >> Checked: it is - >> https://github.com/networkupstools/nut/blob/v2.7.4/drivers/belkin-hid.c#L157-L194 >> >> Are the two tests running on otherwise the same HW/OS setup? >> >> Jim >> >> >> On Wed, Mar 20, 2024 at 9:01 PM Juan Carlos Fischer < >> juancarlos.fisc...@gmail.com> wrote: >> >>> Hello! >>> Thanks for answering. >>> This is the result using version 2.7.4: >>> >>> Network UPS Tools - UPS driver controller 2.7.4 >>> Network UPS Tools - Generic HID driver 0.41 (2.7.4) >>> USB communication driver 0.33 >>> Using subdriver: Belkin/Liebert HID 0.17 >>> >>> battery.charge: 100 >>> battery.charge.low: 38 >>> battery.charge.warning: 38 >>> battery.type: PbAc >>> battery.voltage: 13.9 >>> battery.voltage.nominal: 12.0 >>> device.mfr: Emerson Network Power >>> device.model: LiebertPSA >>> device.serial: >>> device.type: ups >>> driver.name: usbhid-ups >>> driver.parameter.bus: 001 >>> driver.parameter.pollfreq: 30 >>> driver.parameter.pollinterval: 2 >>> driver.parameter.port: auto >>> driver.parameter.productid: 0001 >>> driver.parameter.synchronous: no >>> driver.parameter.vendorid: 10AF >>> driver.version: 2.7.4 >>> driver.version.data: Belkin/Liebert HID 0.17 >>> driver.version.internal: 0.41 >>> input.frequency: 50.0 >>> input.voltage: 221.8 >>> output.voltage: 222.6 >>> ups.load: 8 >>> ups.mfr: Emerson Network Power >>> ups.model: LiebertPSA >>> ups.productid: 0001 >>> ups.serial: >>> ups.status: OL CHRG >>> ups.vendorid: 10af >>> >>> Regards, >>> >>> Juan Carlos >>> >>> On Wed, Mar 20, 2024 at 4:22 PM Jim Klimov <jimklimov+...@gmail.com> >>> wrote: >>> >>>> Hello, >>>> >>>> For clarity: what changed with the move from NUT v2.7.4 to 2.8.0 - >>>> the warnings "became reported", or the highlighted values became zeroes >>>> (and were valid non-zero numbers with older NUT - so a regression)? >>>> >>>> It seems the message is specific to the subdriver and comes from >>>> commit 207fed2282 and a change to the method involved was just recently >>>> experimentally proposed in >>>> https://github.com/networkupstools/nut/issues/2271 discussion comments >>>> (refinement to consider merging as a pull request pending). >>>> >>>> Thanks, >>>> Jim >>>> >>>> On Wed, Mar 20, 2024 at 3:33 PM Juan Carlos Fischer via Nut-upsuser < >>>> nut-upsuser@alioth-lists.debian.net> wrote: >>>> >>>>> Hello everyone >>>>> >>>>> I'm using: Raspberry Pi 4 Model B Rev 1.5 8 GB "Debian GNU/Linux 12 >>>>> (bookworm)" >>>>> >>>>> It all started when I updated from version 2.7.4 to version 2.8.0 and >>>>> the consequences were the following: >>>>> >>>>> pi@raspberrypi:~ $ sudo upsdrvctl start >>>>> >>>>> Network UPS Tools - UPS driver controller 2.8.0 >>>>> Network UPS Tools - Generic HID driver 0.47 (2.8.0) >>>>> USB communication driver (libusb 1.0) 0.43 >>>>> Using subdriver: Belkin/Liebert HID 0.18 >>>>> LineVoltage exponent looks wrong, but not correcting. >>>>> LineVoltage exponent looks wrong, but not correcting. >>>>> LineVoltage exponent looks wrong, but not correcting. >>>>> ConfigVoltage exponent looks wrong, but not correcting. >>>>> >>>>> pi@raspberrypi:~ $ upsc Liebert >>>>> >>>>> Init SSL without certificate database >>>>> battery.charge: 100 >>>>> battery.charge.low: 38 >>>>> battery.charge.warning: 38 >>>>> battery.type: PbAc >>>>> >>>>> *battery.voltage: 0.0 <------------battery.voltage.nominal: 0.0 >>>>> <----------* >>>>> device.mfr: Emerson Network Power >>>>> device.model: LiebertPSA >>>>> device.serial: >>>>> device.type: ups >>>>> driver.name: usbhid-ups >>>>> driver.parameter.bus: 001 >>>>> driver.parameter.pollfreq: 30 >>>>> driver.parameter.pollinterval: 15 >>>>> driver.parameter.port: auto >>>>> driver.parameter.productid: 0001 >>>>> driver.parameter.synchronous: auto >>>>> driver.parameter.vendorid: 10AF >>>>> driver.version: 2.8.0 >>>>> driver.version.data: Belkin/Liebert HID 0.18 >>>>> driver.version.internal: 0.47 >>>>> driver.version.usb: libusb-1.0.26 (API: 0x1000109) >>>>> input.frequency: 49.9 >>>>> >>>>> *input.voltage: 0.0 <---------------output.voltage: 0.0 >>>>> <--------------* >>>>> ups.load: 9 >>>>> ups.mfr: Emerson Network Power >>>>> ups.model: LiebertPSA >>>>> ups.productid: 0001 >>>>> ups.serial: >>>>> ups.status: OL CHRG >>>>> ups.vendorid: 10af >>>>> >>>>> Except for those marked, all values are correct. >>>>> >>>>> Any help would be appreciated. >>>>> >>>>> Regards, >>>>> >>>>> Juan Carlos >>>>> >>>>> _______________________________________________ >>>>> Nut-upsuser mailing list >>>>> Nut-upsuser@alioth-lists.debian.net >>>>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >>>>> >>>>
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
