Bug 187105
| Summary: | usb ups persmissions not correct (included a possible fix in udev). | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kapoios Kanenas <firewalkergr> | ||||||||||
| Component: | nut | Assignee: | Than Ngo <than> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 5 | CC: | kay.sievers | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2006-04-24 16:50:29 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Description of problem:
nut user is not able to write USB UPS device.
lsusb
...
Bus 001 Device 005: ID 0463:ffff MGE UPS Systems UPS
...
LANG=C ls -l /dev/bus/usb/001/005
crw-r--r-- 1 root nut 189, 4 Mar 28 17:46 /dev/bus/usb/001/005
As result nut fails:
anarchos64[tasos]:/etc/udev/rules.d$ sudo service ups start
Starting upsdrvctl: Network UPS Tools - UPS driver controller 2.0.2
Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2)
No USB/HID UPS found
Driver failed to start (exit status=1)
[FAILED]
nut works ok if you change the permissions to 664 and the group to nut for the
device
Find attached a udev rule file to fix the permissions.
Version-Release number of selected component (if applicable):
rpmquery nut
nut-2.0.2-6.2
Matching on a single 0xffff value to identify a UPS sounds pretty wrong. USB UPS'es are usually HID devices and can identified as such, is that different for you UPS? You may run: udevinfo -a -p /class/usb_device/usbdevX.Y for the device to look for a better match. Created attachment 127522 [details]
mge ups rules
My mistake I forgot to add the vendor id. Find the rules with vendor ID attached. I'm pretty sure we better identify the UPS's by its generic class and not by vendor/product. Can you please attach the udevinfo -a output. Created attachment 127523 [details]
udevinfo -a -p /class/usb_device/usbdev1.3
It's the 1.3
Besides the product the manufacturer and the vendor/product ids, I don't see
anything else , class & subclass are zero.
Is there another variable that identifies this as a UPS device ?
Oh, that thing again. :) It's a kind of mess with the usb devices, interfaces and the userspace access nodes. They are at different levels in sysfs. We will hopefully be able to solve that proper with a future version of the usb userspace access, which is currently under development, and that exports an individual device node for every interface. The information about your UPS is likely at the interface level, which unfortunately is not reachable from within the event for the usb device node: grep . /sys/devices/pci0000:00/0000:00:02.0/usb1/1-3/*-*/* Can you please attach the output (or just the section for the UPS) of: lshal to see if HAL can recognize your device correctly. Created attachment 127525 [details]
lshal output (only the ups)
here it is, it has only the sections with mge ups vendor id.
Thanks for all the infos. Seems there is currently no easy way to solve that. Listing vendor/product should be fine then. Thanks again. *** This bug has been marked as a duplicate of 189674 *** |
Created attachment 126911 [details] udev rule file to change permissions for USB UPS devices