Hi Arjen, Thanks for your answer. If you have time to support me, I will for sure follow you, providing all the information you need. I'm a software designer too, so don't hesitate to ask for some particular build or to make changes at source code level.
Looking at the rejected earlier message, I'd say you have a Belkin OEM > device that has a very broken report descriptor. You may want to > checkout the recently released nut-2.6.0 version. But I'm almost > certain that the fixes in the HID parser are not going to solve this > problem and that instead the problem is in the UPS itself. We may or > may not be able to work around this, but in that case we will need > lots of support from you (and you must be willing/capable to run the > development version too). > I have built the nut-2.6.0 version. I did not want to completely uninstall my 2.4.3 version, which had been so gracefully installed by the debian package system... So, I tried to install only the 2.6.0 drivers, and forced nut to use them, by creating a new directory called /lib/nut-2.6, and making a symbolic link: /lib/nut -> /lib/nut-2.6. Please tell me if this is a right approach, to use the 2.6 HID parser. >From this test, it seems that you were right: the UPS is still reported as "OB", and some information (like the serial number, e.g) are missing from the upsc report. > > > I would like to paste also a complete tracing of "/lib/nut/usbhid-ups > -DDDDD > > -a liebert", but the message would become too big. > > Then use gzip to compress it before attaching. We really need the full > listing as an attachment, not inline in a message. > Ok, I will do in this way. Please find attached the log of "/lib/nut/usbhid-ups -DDDDD -a liebert", produced with the 2.6 driver. Thank you for your support. Kind regards, -- Pier
nut-usbhid-2.6-20110207.log.gz
Description: GNU Zip compressed data
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
