On May 13, 2019, at 12:51 AM, David C. Rankin wrote: > > Consider adding the information about the permission errors and Udev rule to > tuser-manual.html. That is the first place I thought to look, but either it > missed the information of it wasn't there. > We do have this in the FAQ, though I realize we don't have many links from the main user manual:
https://networkupstools.org/docs/FAQ.html#_my_usb_ups_is_supported_but_doesn_8217_t_work I made a note to update this: https://github.com/networkupstools/nut/issues/696 Was the AUR package missing a udev entry for that UPS? If so, is it in the upstream NUT repository? The UDEV files are generated from the C source of the drivers, so in your case, that would be this table: https://github.com/networkupstools/nut/blob/master/drivers/cps-hid.c#L56 Another possibility is that the AUR package puts the udev file in the wrong place relative to other system-provided udev files, as was the case in Debian: https://github.com/networkupstools/nut/issues/140 If the AUR package doesn't run the udevadm command that you mentioned as part of its postinstall script (or equivalent script), I would recommend that you file a bug with the packagers. _______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
