search for: usbups_rules_end

...y thanks. Gilad -------------- next part -------------- --- 70-nut-usbups.rules 2007-09-20 17:24:41.000000000 -0700 +++ 71-nut-usbups-gilad-20070926.rules 2007-09-28 16:16:18.000000000 -0700 @@ -1,7 +1,10 @@ # udev rules for the NUT USB drivers -SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" ACTION!="add", GOTO="nut-usbups_rules_end" +SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GOTO="nut-usbups_rules_no-device-class" +SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" + +LABEL="nut-usbups_rules_no-dev...

...14:09:30 banyan upsmon[5469]: Poll UPS [tripplite at localhost] failed - Driver not connected I think the start of my trouble is I need to change the file added to /etc/udev/rules.d # This file is generated and installed by the Network UPS Tools package. ACTION!="add", GOTO="nut-usbups_rules_end" SUBSYSTEM=="usb_device", GOTO="nut-usbups_rules_real" SUBSYSTEM=="usb", GOTO="nut-usbups_rules_real" SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" LABEL="nut-usbups_rules_real" # TrippLite # e.g. ? - usbhid-ups SYSFS{id...

...! It's my second trouble with NUT. Latest nut-2.6.1.tar.gz installed from source on Xenserver 5.6 SP2, UPS is Powercom WOW--500U FW3.A4 (USB). Problem with setting permissions for udev (described in /etc/udev/rules.d/52-nut-usbups.rules file): ACTION!="add|change", GOTO="nut-usbups_rules_end" don't work for me. Only when I changed ACTION to: ACTION!="add", GOTO="nut-usbups_rules_end" (without |change) - it's began to set correct permissions 0664 for my USB UPS device as specified in 52- nut-usbups.rules file. Default for usbdev is 0640 - it's ins...

...devd [452]: BUS= will be removed in a future udev version. please use SUBSYSTEM= to match the event device. or SUBSYSTEMS= to match a parent device. in /lib/udev/rules.d/52-nut-usb.rules:6" Line 6 in "52-nut-usb.rules:6" contains the following: BUS!="usb", GOTO="nut-usbups_rules_end" I understand you're supposed to replace "BUS" with either "SUBSYSTEM" or "SUBSYSTEMS" but which one am I supposed to use in this case? I can provide more info if necessary, just let me know. Thanks. -------------- next part -------------- An H...

...tec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to: SUBSYSTEM!="usb*", GOTO="nut-usbups_rules_end" to make hotplugging work on my Gentoo 2007.0, kernel 2.6.22.1 and default Gentoo udev rules. There are 3 issues. 1. Battery charge. I attach a patch to the latest svn revision that adds information for my Krauler's b...

...I'd follow up in case someone else runs into this issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups ACTION=="add|change", SUBSYSTEM=="usb|usb_device", SUBSYSTEMS=="usb|usb_device", ATTR{idVendor}=="09ae", ATTR{idProduct}=="2012", MODE="664", GROUP="nut", RUN+="...

...vd[31526]: BUS= will be removed in a future udev version ... 098 udev version (from 2006) is required for this [2], but this is the same version as required for previous SYSFS -> ATTR change. I've discussed this with udev maintainer and the result is BUS!="usb", GOTO="nut-usbups_rules_end" should be changed to SUBSYSTEMS!="usb", GOTO="nut-usbups_rules_end" I've tested it on my machine and it works for me. Cheers, Michal [1] http://svn.debian.org/wsvn/nut/trunk/scripts/udev/?rev=2071&sc=1 [2] http://git.kernel.org/?p=linux/hotplug/udev.git;a=c...

...out to TrippLite support to ask what version of the USB HID protocol my AVR750U is using. Thanks, Scott My Configuration ################ # /etc/udev/rules.d/62-nut-usbups-custom.rules # based on the 62-nut-usbups.rules that came with the package ACTION!="add|change", GOTO="nut-usbups_rules_end" SUBSYSTEM=="usb_device", GOTO="nut-usbups_rules_real" SUBSYSTEM=="usb", GOTO="nut-usbups_rules_real" SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" LABEL="nut-usbups_rules_real" # TrippLite # e.g. TrippLite AVR750U - usbhi...

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

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

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

On Apr 23, 2014, at 3:47 AM, Frantz de Germain wrote: > I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP > 1.6/Centos 5.7) to manage a Dell UPS 2700W. > > Here is my ups.conf : > > [SU27003U-08] > driver = usbhid-ups > port = auto > desc = "SU27003U-08" > > 52-nut-usbups.rules have well been installed in

Hello, I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP 1.6/Centos 5.7) to manage a Dell UPS 2700W. Here is my ups.conf : [SU27003U-08] driver = usbhid-ups port = auto desc = "SU27003U-08" 52-nut-usbups.rules have well been installed in /lib/udev/rules.d/. I've put it in /etc/udev/rules.d/ too. I've rebooted the machine.

...his was likely a udev problem, I created the following /etc/udev/rules.d/52-nut-usbups.rules (based on an example on our database server, and changing the vendor and product id values): [root at mypc:/etc/nut]# cat /etc/udev/rules.d/52-nut-usbups.rules ACTION!="add|change", GOTO="nut-usbups_rules_end" SUBSYSTEM=="usb_device", GOTO="nut-usbups_rules_real" SUBSYSTEM=="usb", GOTO="nut-usbups_rules_real" SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" LABEL="nut-usbups_rules_real" # APC - usbhid-ups ATTR{idVendor}=="051...

...out to TrippLite support to ask what version of the USB HID protocol my AVR750U is using. Thanks, Scott My Configuration ################ # /etc/udev/rules.d/62-nut-usbups-custom.rules # based on the 62-nut-usbups.rules that came with the package ACTION!="add|change", GOTO="nut-usbups_rules_end" SUBSYSTEM=="usb_device", GOTO="nut-usbups_rules_real" SUBSYSTEM=="usb", GOTO="nut-usbups_rules_real" SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" LABEL="nut-usbups_rules_real" # TrippLite # e.g. TrippLite AVR750U - usbhi...

...ONS= # Any options to pass to upsd UPSD_OPTIONS= # # [End] /etc/ups/ups.conf contains [Gamatronic] driver= newhidups port = auto desc = "Gamatronic D-Compact" I tried to modifying /etc/udev/rules.d/nut-usbups.rules to inlcude the following lines before LABEL="nut-usbups_rules_end" to include # Gamatronic D-Compact - usbhid-ups SYSFS{idVendor}=="0925", SYSFS{idProduct}=="1234", MODE="660", GROUP="nut" I got the same results. Please help me to get nut configured correctly. Thanks Eli

I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite information I can help with, let me know. David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Charles Lepple <clepple at gmail.com> Sent: Sunday, December 8, 2019 8:36 PM To: Layne Fowler

...--------------- # /etc/nut/ups.conf pollinterval = 1 [ups] driver = usbhid-ups port = auto desc = "Tripp Lite SMART1500LCD" vendorid = 09ae productid = 2012 ondelay = -1 ------------------------------ # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups ACTION=="add|change", SUBSYSTEM=="usb|usb_device", SUBSYSTEMS=="usb|usb_device", ATTR{idVendor}=="09ae", ATTR{idProduct}=="2012", MODE="664", GROUP="nut", RUN+="...