![]() ![]() It seems raspbian sees and identifies the UPS (the lsusb command), but the NUT cannot determine the UPS. I do not understand the reason for the problem. Here it is (my device is second 0D9F/0004 $ sudo /lib/nut/usbhid-ups -DD -a SPIDERĠ.003509Ĝhecking device (0424/7800) (001/005)Ġ.004522ĝevice does not match - skippingĠ.004647Ĝhecking device (0D9F/0004) (001/004)Ġ.008052 Unable to get HID descriptor (error sending control message: Broken pipe)Ġ.008657 Unable to get Report descriptor: Broken pipe I learned to get debug information from the UPS draver in the NUT. Network UPS Tools - Generic HID driver 0.41 (2.7.4) Network UPS Tools - UPS driver controller 2.7.4 USB 2.0 Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root $ sudo upsdrvctl start USB 2.0 Hubīus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. Tell me please, can I solve the problem now? Perhaps there are some tweaks in the NUT or in the $ lsusbīus 001 Device 004: ID 0d9f:0004 Powercom Co., Ltdīus 001 Device 005: ID 0424:7800 Standard Microsystems Corp.īus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. I read that Raspberry works in a special way with USB, but on past Raspberry models, people have successfully used the UPS of this company. Raspberry sees the UPS, but the driver does not cling. But my Raspberry Pi 3b + doesn’t work with the same UPS, and with same NUT configuration. Everything works in VMware Workstation 15 Player. I was able to make NUT and my Powercom UPS (USB port) work under the Raspberry Pi Desktop.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |