[Nut-upsuser] Question on EATON UPS

[Jim Klimov]

The "unknown" fields mean the driver did not get that piece of information
from libusb. In case of Manufacturer/Product which are unknown in the later
post, but known in the first, I suppose you had another driver running, or
the kernel still owned it (udev misbehavior, not handing it off after
reconnections, etc.) and so exclusive access was not given to the new
(currently reporting) process.

The "Device" matching specifically had a problem fixed in the master branch
a few months ago. You can try to comment it away from your ups.conf for a
quick workaround, and match by remaining fields (assuming their values are
correct).

Hope this helps,
Jim Klimov

On Thu, Mar 9, 2023 at 7:51 PM Laurent Taieb via Nut-upsuser <
nut-upsuser at alioth-lists.debian.net> wrote:

> Thanks Larry,
>
> I tried.
>
> Got the following traces and the driver doesn’t start.
>
>
>
>  1.036797       [D2] - VendorID: 0463
>
>    1.036812     [D2] - ProductID: ffff
>
>    1.036826     [D2] - Manufacturer: unknown
>
>    1.036840     [D2] - Product: unknown
>
>    1.036872     [D2] - Serial Number: unknown
>
>    1.036912     [D2] - Bus: 002
>
>    1.036942     [D2] - Device: unknown
>
>    1.036965     [D2] - Device release number: 0001
>
>    1.036980     [D2] Trying to match device
>
>    1.037008     [D2] match_function_subdriver (non-SHUT mode): matching a
> device...
>
>    1.037044     [D3] match_function_regex: matching a device...
>
>    1.037102     [D2] Device matches
>
>    1.037131     [D2] Reading first configuration descriptor
>
>    1.037187     [D3] libusb_kernel_driver_active() returned 1 (driver
> active)
>
>    1.037220     [D2] successfully set kernel driver auto-detach flag
>
>    1.040994     [D2] Claimed interface 0 successfully
>
>    1.041063     [D3] nut_usb_set_altinterface: skipped
> libusb_set_interface_alt_setting(udev, 0, 0)
>
>    1.041438     [D2] Unable to get HID descriptor (Pipe error)
>
>    1.041480     [D3] HID descriptor length (method 1) -1
>
>    1.041530     [D3] HID descriptor, method 2: (9 bytes) => 09 21 10 01
> 21 01 22 e1 01
>
>    1.041566     [D3] HID descriptor length (method 2) 481
>
>    1.041605     [D2] HID descriptor length 481
>
>    1.041926     [D2] Unable to get Report descriptor: Resource
> temporarily unavailable
>
>
>
> Any idea ?
>
>
>
> Thanks
>
> Laurent
>
>
>
> *De : *Nut-upsuser <nut-upsuser-bounces+laurenttaieb=
> free.fr at alioth-lists.debian.net> au nom de Larry Fahnoe via Nut-upsuser <
> nut-upsuser at alioth-lists.debian.net>
> *Répondre à : *Larry Fahnoe <fahnoe at fahnoetech.com>
> *Date : *jeudi 9 mars 2023 à 18:59
> *À : *nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org>
> *Objet : *Re: [Nut-upsuser] Question on EATON UPS
>
>
>
> On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser <
> nut-upsuser at alioth-lists.debian.net> wrote:
>
>
>
> The UPS has been defined in ups.conf as:
>
> [myups3]
>
> driver : usbhid-ups
>
> port = auto
>
> vendorid = 0463
>
> productid = ffff
>
> desc = "5S"
>
> bus = 002
>
> device = 014
>
> pollonly
>
> I have only:
>
> [ups02]
> driver=usbhid-ups
> port=auto
>
> serial = [redacted]
>
>
>
> I have an Eaton 5P750 connected via USB and agree, a less specific entry
> in ups.conf works fine for me:
>
>
>
> [ups]
>
>         driver = usbhid-ups
>
>         port = auto
>
>         vendorid = 0463
>
>
>
> --Larry
>
>
>
> _______________________________________________ Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230323/af7971ca/attachment.htm>