search for: 52_nut

hi NUT 2.4.3 on new server can not see serial number, but old nut on different hardware can? I have 2 USB-hid ups from APC, 1500 and 3000 RM, i use the serial number to identify them. However my new UPS monitor server can not see the serial number? It works on Linux dkserver 2.6.22.18-vs2.2.0.6 #1 SMP Sat Feb 16 20:54:32 CET 2008 i686 GNU/Linux debian package 2.2.2-6.5 it does not work on

...trlist">hald-addon-usbhid-ups</merge> <merge key="battery.type" type="string">ups</merge> </match> </match> I also noticed I have a udev rules file: [root at phoenix docs]# grep -A 2 -i cyberpower /etc/udev/rules.d/52_nut-usbups.rules # CyberPower - usbhid-ups ATTR{idVendor}=="0764", ATTR{idProduct}=="0005", MODE="664",GROUP="uucp" ATTR{idVendor}=="0764", ATTR{idProduct}=="0501", MODE="664",GROUP="uucp" I stopped and restarted the hal...

...script copied from the tar ball scripts/udev/52-nut-usbups.rules): # Krauler UP-M500VA - blazer_usb ATTR{idVendor}=="0001", ATTR{idProduct}=="0000", MODE="664", GROUP="nut" However it appears not to work. Incidentally, it DID work when I still had the old 52_nut-usbups.rules file left over from the apt install. I could ls -al the appropriate bus/device in /dev/bus/usb and see it was owned by root:nut. As part of troubleshooting I have removed the 52_nut-usbups.rules that was left over from apt install and copied the 52-nut-usbups.rules file from the 2.6.0...

...detected. I got it working > after playing with it some, and figured I'd let someone else know how it > works. Again, if there is someone/someplace else I need to send this, > let me know. > > It is not recognized by udev, so I added the following rule to > /etc/udev/rules.d/52_nut-usbups.rules > > SYSFS{idVendor}=="0764", SYSFS{idProduct}=="0601", MODE="664", GROUP="nut" > > > Then, since the usbhid-ups does not recognize it, I had to add > productid=0601 to /etc/nut/ups.conf. My configuration looks like this: >...

Arnaud et al, I have been meaning to collect some of the documentation updates for permission-related errors, and I was wondering if you would mind if we moved the scripts/udev/README and scripts/hotplug/README files out of scripts/ and into the docs/ directory (probably docs/permissions.txt). We could also cover the *BSD /dev/usb* permission issues there, as well. Any thoughts on this? -- -

...is 2.2.2-6.4, debian lenny The ups we use is a tripplite OMNIVS1000 USB The drivers i tried are tripplite_usb and usbhid-ups, googled very long about the problems, but didn't get it to run. Does someone has experiences or similar problems? lsusb and lsmod are all right in /etc/udev/rules.d/52_nut-usbups.rules I found one line according to the modell ---- # Tripp Lite - tripplite_usb SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="0001", MODE="664", GROUP="nut" # Tripp Lite - usbhid-ups SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="1003",...

...NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 i haven't altered any udev configuration on either host and so they have identical /etc/udev/rules.d/52_nut-usbups.rules files (part of the debian package presumably). it looks like the relevant section is: # Powerware - bcmxcp_usb SYSFS{idVendor}=="0592", SYSFS{idProduct}=="0002", MODE="664", GROUP="nut" SYSFS{idVendor}=="06da", SYSFS{idProduct}==&quot...

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

...ng directory `/home/software/nut/nut-2.2.2/scripts/hotplug' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/software/nut/nut-2.2.2/scripts/hotplug' Making all in udev make[2]: Entering directory `/home/software/nut/nut-2.2.2/scripts/udev' cp nut-usbups.rules 52_nut-usbups.rules make[2]: Leaving directory `/home/software/nut/nut-2.2.2/scripts/udev' Making all in hal make[2]: Entering directory `/home/software/nut/nut-2.2.2/scripts/hal' cp ups-nut-device.fdi 20-ups-nut-device.fdi make[2]: Leaving directory `/home/software/nut/nut-2.2.2/scripts/hal'...