<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/13/2017 05:48 PM, Arnaud Quette
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">Hi Manuel<br>
</div>
</blockquote>
<br>
Hi Arno<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-06-07 14:40 GMT+02:00 Charles
Lepple <span dir="ltr"><<a target="_blank"
href="mailto:clepple@gmail.com" moz-do-not-send="true">clepple@gmail.com</a>></span>:<br>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex" class="gmail_quote"><span
class="gmail-">On Jun 7, 2017, at 5:47 AM, Manuel
Wolfshant <<a
href="mailto:wolfy@nobugconsulting.ro"
moz-do-not-send="true">wolfy@nobugconsulting.ro</a>>
wrote:<br>
><br>
> If that matters, the OS is a fully updated
CentOS 6.9 and this (latest stable ) version of nut
was packaged by me. The problem appears on any of the
USB ports ( well, I tried the 2 in front and one in
the back of the server ).<br>
><br>
> lsusb -v reports:<br>
</span>...<br>
<span class="gmail-">> wDescriptorLength
549<br>
> Warning: incomplete report descriptor<br>
> Report Descriptor: (length is 9)<br>
> Item(Main ): (null), data=none<br>
<br>
</span>Because both NUT and lsusb are having trouble
retrieving the HID Report Descriptor, I think the
problem is at a lower level: probably between the UPS,
the kernel, and the USB HCI. The archives have a number
of unresolved emails about the 5E and "broken pipe"
errors.<br>
<br>
Probably worth checking with Eaton, too.<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Charles is right in both the fact
that the issue is (or at least seems to be) upstream to NUT,
and also that it's worth checking with "Eaton"<br>
</div>
</div>
</div>
</blockquote>
<br>
I've approached "them" ( apparently my request for supported
landed at after-sales support/Romania ) as soon as Charles replied.
Unfortunately the "dialogue" rather stalls, they seem to have a
policy to not send more than one email every 3 days. Leaving aside
that after telling them that I am using an <b>USB </b>unit (and
providing USB-related logs ) they wanted to know if I was using <b>SNMP</b>.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">
<div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Could you please tell me your kernel
</div>
</div>
</div>
</blockquote>
[root@belgrade ~]# uname -r<br>
2.6.32-696.3.1.el6.x86_64<br>
<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">
<div>
<div class="gmail_extra">and libusb (0.1) version?<br>
</div>
</div>
</div>
</blockquote>
[root@belgrade ~]# rpm -qa libusb<br>
libusb-0.1.12-23.el6.x86_64<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">
<div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Would you also be able to test some
github code?<br>
</div>
<div class="gmail_extra">We have the libusb-1.0 branch that
provides both libusb 1.0 support (interesting to test to see
if the problem still happens) along with few other
improvements (though these should not help for your issue):
<a
href="https://github.com/networkupstools/nut/tree/libusb-1.0"
moz-do-not-send="true">https://github.com/networkupstools/nut/tree/libusb-1.0</a><br
clear="all">
</div>
<div class="gmail_extra"><br>
</div>
</div>
</div>
</blockquote>
I can and I will test ( tomorrow, probably ).<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">
<div>
<div class="gmail_extra">Don't hesitate if you need more
guidance for trying this branch.<br>
</div>
</div>
</div>
</blockquote>
Do you happen to know how can I find the version of firmware run by
the UPS, in _my_ conditions ( remote + the previously mentioned
errors) ? The guys who contacted me from Eaton did not reply yet to
my email sent yesterday.<br>
<br>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">
<div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">FYI, I've just made a test with the
same unit, on a Debian jessie (kernel 3.16.43-2, libusb
0.1.12-25) both with 2.7.4 and the latest git master, and it
works fine:<br>
<br>
battery.charge: 62<br>
battery.runtime: 2725<br>
battery.type: PbAc<br>
device.mfr: EATON<br>
device.model: 5E 1500i<br>
device.type: ups<br>
<a href="http://driver.name" moz-do-not-send="true">driver.name</a>:
usbhid-ups<br>
[...]<br>
<br>
</div>
</div>
</div>
</blockquote>
I was expecting it to work fine, given
<a class="moz-txt-link-freetext" href="https://risc-a-day.blogspot.ro/2014/09/getting-my-ups-to-work-with-linux.html">https://risc-a-day.blogspot.ro/2014/09/getting-my-ups-to-work-with-linux.html</a>
( before the purchase I assumed the units to be similar, modulo the
maximum power )<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAFm_bUgTKYqA6zGhMue8RTWVqa9yV022P4OYn9Y2owkebb5mXA@mail.gmail.com">
<div dir="ltr">
<div>
<div class="gmail_extra">cheers,<br>
</div>
<div class="gmail_extra">Arno<br>
</div>
</div>
</div>
</blockquote>
thanks a lot. I will come back with more data once I test the github
code ( yes, I know, everybody hates this kind of <span
id="result_box" class="short_text" lang="en"><span class="">threats
:) )<br>
<br>
wolfy</span></span>
</body>
</html>