Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 20, 2017, at 6:00 AM, Manuel Wolfshant wrote: > >On 06/20/2017 04:08 AM, Charles Lepple wrote: >> [...] >> It does not get a length for method 1, so it moves on to method 2, which >> gets a length, but fails to get the rest of the descriptor. This is what is >> happening to lsusb, too (tries to fetch 549 bytes, gets only 9). > and is there anything I can do to fix, short of hoping to receive an updated > unbroken firmware for the UPS from a support team which ignores me ? I can't speak for Eaton, but given what I have seen so far, the symptoms do not necessarily point to the UPS. If I search my copy of the NUT mailing lists for "lsusb" and "incomplete report descriptor", I see two cases of a Liebert GXT-3, one CyberPower PP1100, one older Tripp-Lite unit, and an APC Smart-UPS 1000. That sample set is not large enough to isolate the problem to a specific kernel, distribution or motherboard. Hopefully Eaton has a larger set of data points. >>> However I am using the very same package on my personal workstation (which >>> is also running CentOS 6 but has a whole lot of packages installed either >>> from 3rd party repos or built by me ) since Fri 09 Jan 2015 (I needed it >>> for heimdall ) and I had zero issues so far. >> Can you be more specific about this? What hardware are you testing libusbx >> 1.0.19 with? > Gigabyte F2A88X-D3H with AMD A8-6600K works fine with heimdall which I used > to connect to a Samsung S2+ and now to a Samsung A3 (2016) . Some similar > board ( I do not recall exactly what model was it, could have been either > identical or DH3 which is basically the same motherboard with some minor > modifications) was used by my colleague from the IT support dept 2-3 years > ago with my phone as well. The packages that I have installed are : Oh, I thought you meant that libusbx was working fine with another UPS. I don't know whether the 5E1500I is a 1.5 Mbit/sec or 12 Mbit/sec device, but I suspect that the other USB devices you are testing are faster than that. (Bear in mind that 480 Mbit/sec generally uses a different host controller interface, and 5.0 Gbit/sec uses a different PHY layer as well.) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/20/2017 04:08 AM, Charles Lepple wrote:
[...]
It does not get a length for method 1, so it moves on to method 2, which gets a
length, but fails to get the rest of the descriptor. This is what is happening
to lsusb, too (tries to fetch 549 bytes, gets only 9).
and is there anything I can do to fix, short of hoping to receive an
updated unbroken firmware for the UPS from a support team which ignores me ?
However I am using the very same package on my personal workstation (which is
also running CentOS 6 but has a whole lot of packages installed either from 3rd
party repos or built by me ) since Fri 09 Jan 2015 (I needed it for heimdall )
and I had zero issues so far.
Can you be more specific about this? What hardware are you testing libusbx
1.0.19 with?
Gigabyte F2A88X-D3H with AMD A8-6600K works fine with heimdall which I
used to connect to a Samsung S2+ and now to a Samsung A3 (2016) . Some
similar board ( I do not recall exactly what model was it, could have
been either identical or DH3 which is basically the same motherboard
with some minor modifications) was used by my colleague from the IT
support dept 2-3 years ago with my phone as well. The packages that I
have installed are :
[wolfy@wolfy ~]$ rpm -qa \*usb\* kernel --qf
"%{name}-%{version}-%{release} %{arch} %{vendor} %{installtime:date}
\n"|sort
kernel-2.6.32-642.13.1.el6 x86_64 CentOS Wed 18 Jan 2017 03:13:27 AM EET
kernel-2.6.32-642.15.1.el6 x86_64 CentOS Mon 27 Feb 2017 10:19:39 AM EET
kernel-2.6.32-696.1.1.el6 x86_64 CentOS Fri 14 Apr 2017 01:39:36 AM EEST
kernel-2.6.32-696.3.1.el6 x86_64 CentOS Thu 01 Jun 2017 12:52:38 AM EEST
kernel-2.6.32-696.el6 x86_64 CentOS Thu 30 Mar 2017 05:16:05 PM EEST
libusb-0.1.12-23.el6 i686 CentOS Wed 17 Sep 2014 01:07:21 AM EEST
libusb-0.1.12-23.el6 x86_64 CentOS Tue 16 Sep 2014 04:59:09 PM EEST
libusbx-1.0.19-2.el6 x86_64 (none) Fri 09 Jan 2015 03:56:43 PM EET
pyusb-1.0.0-1.el6 noarch Fedora Project Tue 10 Jan 2017 12:18:30 PM EET
usbredir-0.5.1-3.el6 x86_64 CentOS Fri 13 May 2016 12:02:18 PM EEST
usbutils-003-6.el6 x86_64 CentOS Fri 13 May 2016 12:10:19 PM EEST
[wolfy@wolfy ~]$ uname -r
2.6.32-696.3.1.el6.x86_64
The culprit is occurring on a Dell R310 which has:
# rpm -qa \*usb\* kernel --qf "%{name}-%{version}-%{release} %{arch}
%{vendor} %{installtime:date} \n"|sort
kernel-2.6.32-696.1.1.el6 x86_64 CentOS Thu 13 Apr 2017 07:10:32 PM CEST
kernel-2.6.32-696.3.1.el6 x86_64 CentOS Wed 31 May 2017 11:44:08 PM CEST
kernel-2.6.32-696.el6 x86_64 CentOS Sun 02 Apr 2017 12:16:24 AM CEST
libusb-0.1.12-23.el6 x86_64 CentOS Thu 17 Jan 2013 02:22:38 PM CET
libusbx-1.0.19-2.el6 x86_64 (none) Mon 19 Jun 2017 10:21:55 AM CEST
usbutils-003-6.el6 x86_64 CentOS Fri 13 May 2016 04:29:50 PM CEST
# uname -r
2.6.32-696.3.1.el6.x86_64
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
