Detlef.Jochem at web.de
2021-May-18 12:29 UTC
[Nut-upsuser] PowerWalker VI 650 SB - Driver failed to start
An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210518/30968f29/attachment.htm>
Jim Klimov
2021-Jun-13 14:24 UTC
[Nut-upsuser] PowerWalker VI 650 SB - Driver failed to start
Hello, Looking at logged NUT issue discussions like https://github.com/networkupstools/nut/issues/475, https://github.com/networkupstools/nut/issues/483 and https://github.com/networkupstools/nut/issues/646 I see people did have success with models named similar to yours. So generally it should be supported, with "liebert-hid" or better with "mge-hid" subdriver according to reports... But then there were also users for whom it did not work, and those for whom it disconnected after a few hours (causing a Stale Data problem). I would suggest first ruling out systemic issues (device node permissions vs. user the driver runs as, some kernel quirks?, possibly a libusb version mismatch - official NUT releases only offered libusb-0.1 compatibility and solutions for libusb-1.0 were not merged yet, but there are branches on GitHub to try if you would - linked from issue #300). Those "no route to host" and "no such file" lines look most incorrect. Does `nut-scanner` also fail to find and connect to the device? Do you have udev or similar system that might grab the device and not let NUT have it? You can also try to pick configuration options in ups.conf section for your device, or via `-x` CLI options while you experiment on command line, such as to try setting the subdriver to use, or the `usb_set_altinterface=1` so that the NUT driver tells libusb to disconnect other consumers from the device, if I read the docs correctly. Finally, it feels feasible that like some other recent devices, this one might have a new revision where USB HID is not exposed on "interface 0" - there is a PR open at https://github.com/networkupstools/nut/pull/1044 to handle other interface numbers, so far for a couple of known devices where that is needed. Jim On Tue, May 18, 2021 at 2:42 PM Detlef via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote:> I need help to find a way to start the usbhid-ups driver successfully, i > always get a failed status after start of the driver > > THX > > > > used environment: > > - > > OS: 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 > GNU/Linux > - > > NUT version 2.7.4 > - > > NUT installation method: apt-get install nut > - > > UPS: PowerWalker VI 650 SB > - > > problem description, with any relevant traces, like system log > excerpts, and driver debug output > - > > lsusb > Bus 001 Device 003: ID 0764:0601 Cyber Power System, Inc. > PR1500LCDRT2U UPS > - cat /etc/nut/ups.conf > # Set maxretry to 3 by default, this should mitigate race with slow > devices: > maxretry = 3 > [PowerWalker650] > driver = usbhid-ups > port = auto > desc = "server" > > - upsdrvctl start > 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 > No matching HID UPS found > Driver failed to start (exit status=1) > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > No matching HID UPS found > Driver failed to start (exit status=1) > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > No matching HID UPS found > Driver failed to start (exit status=1) > - > > You can obtain the latter using the following command, as root and > after having stopped NUT: > > /path/to/driver -DD -a <upsname> > > /lib/nut/usbhid-ups -DD -a PowerWalker650 > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > 0.000000 debug level is '2' > 0.003634 upsdrv_initups... > 0.026290 Checking device (1D6B/0003) (002/001) > 0.043513 - VendorID: 1d6b > 0.044473 - ProductID: 0003 > 0.044928 - Manufacturer: unknown > 0.045433 - Product: unknown > 0.045847 - Serial Number: unknown > 0.046276 - Bus: 002 > 0.046843 - Device release number: 0419 > 0.047250 Trying to match device > 0.047684 Device does not match - skipping > 0.050203 Checking device (0764/0601) (001/003) > 0.053610 - VendorID: 0764 > 0.054105 - ProductID: 0601 > 0.054620 - Manufacturer: 1 > 0.055013 - Product: 650 > 0.055434 - Serial Number: > 0.055845 - Bus: 001 > 0.056418 - Device release number: 0200 > 0.056845 Trying to match device > 0.057251 Device matches > 0.057334 failed to claim USB device: could not claim interface > 0: No such file or directory > 0.057475 failed to detach kernel driver from USB device: could > not detach kernel driver from interface 0: No route to host > 0.057554 failed to claim USB device: could not claim interface > 0: No such file or directory > 0.057600 failed to detach kernel driver from USB device: could > not detach kernel driver from interface 0: No route to host > 0.057768 failed to claim USB device: could not claim interface > 0: No such file or directory > 0.057825 failed to detach kernel driver from USB device: could > not detach kernel driver from interface 0: No route to host > 0.057870 failed to claim USB device: could not claim interface > 0: No such file or directory > 0.058006 failed to detach kernel driver from USB device: could > not detach kernel driver from interface 0: No route to host > 0.058050 Can't claim USB device [0764:0601]: could not detach > kernel driver from interface 0: No route to host > > > _______________________________________________ > 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/20210613/0d6d33c5/attachment.htm>