similar to: [PATCH]recent change in udev rules is not complete

Displaying 20 results from an estimated 1000 matches similar to: "[PATCH]recent change in udev rules is not complete"

2007 Sep 28
1
nut + usb + udev with kernel 2.6.22
Hi all, Here's a brief history of my adventure: I purchased a CyberPower 685 AVR and decided to connect it through USB to my Gentoo linux machine running kernel 2.6.22. While the device was detected properly and added to /dev, it was added with the wrong permissions (gid was set to 'usb' instead of 'nut', as it was expected to be according to the rules under
2011 Jul 21
1
Udev rules troubles: incorrect ACTION expression?
G'day, all! 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:
2012 May 09
3
SMART3000RM2U?
Can anyone point me to information for getting the Tripplite SMART3000RM2U to work with NUT? Our newer Tripplite units seem to work with the usbhid-ups driver, but these older ones seem to need something different. So far I have had little success getting tripplite_usb to work. [root at banyan ~]# tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.1)
2011 Aug 19
2
Debian squeeze: nut udev message at computer startup
Hi. I'm using nut with debian squeeze. When the computer boots and nut is loaded, I get the following messages: "Starting the hotplug events dispatcher: udevdudevd [451]: 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 . Synthesizing the initial hotplug
2007 Sep 05
2
Krauler UP-D1200VA
Hello. I have this UPS: Krauler UP-D1200VA Megatec 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:
2015 Jan 30
5
Error: Connection failure: Connection refused
Hello list, I am configuring NUT on a Dell workstation that is connected to an APC Back UPS Pro 1300, and I am running into an issue where starting everything manually seems to be successful, but fails when using the init.d scripts. The short story is that I get the following error when trying to check the status of the UPS: [root at mypc:/etc/nut]# upsc apc_pro1300 at localhost Error:
2020 Jul 22
1
AVRX750/500 issues
I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe
2019 Dec 11
1
[EXTERNAL] Re: Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting
Thought 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
2020 Jul 22
3
AVRX750/500 issues
Thanks for chiming in @David Zomaya. Tripp Lite replaced my AVRX550U once thinking that the powering back on was a defective unit, but the replacement does the same thing. The SN on the first one is 2935AVHOM87BB00152. NUT has my model listed as protocol 2010, so that needs to be corrected to 2012, but I'm not sure if anyone is doing active development on it right now. I also have a
2007 Feb 03
2
Powerware 5110
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
2009 Jan 15
2
Squirrel 1.4.8-8.el3.centos.1
Hi, Last tuesday I upgraded squirrelmail on two centos-3 mailservers. squirrelmail-1.4.8-8.el3.centos.1, 2.4.21-58.ELsmp, CentOS release 3.9, httpd 2.0.46 Since then I have some users who have problems with their sessions. They are logout out every now and them, and some sent mails have another user address in the From header. It looks like squirrel is mixing up sessions? Those users have used
2011 Sep 24
0
Adding device: EitanVT650 to udev nut-usbups.rules?
Hi, I have a UPS device that seems to work fine with the blazer_usb driver. (I have guessed the driver by googling up the "Product" usb string 010937). However, it does not appear in the supported list, and I had to manually add a udev rule for granting access to the 'nut' user. Would be nice if the info I provide below could be used to help the project/future users to
2011 Jul 27
0
udev regression in 2.6.1 (was: new entry in nut-usbups.rules for orvaldi ups)
Hi Pawel, 2011/7/26 Pawel Sikora <pluto at agmk.net> > On Tuesday 26 of July 2011 14:33:15 you wrote: > > Hi Pawel, > > > > 2011/7/26 Pawel Sikora <pluto at agmk.net> > > > > > Hi, > > > > > > i have an orvaldi ups > > > http://en.orvaldi.com/index.php/en/product_catalog/product_view/11/162 > > > and it works
2008 Mar 14
1
Sucess with Powerware 5115A over USB!
THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0
2006 Jun 14
3
Trouble Configuring NUT with Gamatronic USB
Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P:
2009 Mar 17
2
problem with ldap
Hi, dovecot-1.2 from hg.dovecot.org openldap-2.4.11 passdb.o: In function `passdbs_init': /home/src/dovecot-1.2/src/auth/passdb.c:230: undefined reference to `passdb_ldap' userdb.o: In function `userdbs_init': /home/src/dovecot-1.2/src/auth/userdb.c:177: undefined reference to `userdb_ldap' collect2: ld returned 1 exit status -- Xueron Nee http://www.xueron.com
2010 May 12
2
Help with interpolation
Hi, I have a two Colum matrix ( I named it holder) as shown bellow. It seems to be three columns, but the first column contains the row names. I am trying to fill all NAs by linear interpolation the known values in the matrix. I tried using the interpNA function, but I get an error message: > interpNA(holder, method = "linear") Error in approx(idx, x[idx], 1:n, method = method, f
2014 Apr 23
2
Problem making usbhid-ups working on Centos 5.7
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.
2010 Dec 23
1
[nut-commits] svn commit r2777 - in trunk: data docs/man drivers scripts/hal scripts/hotplug scripts/udev
2010/12/22 Arjen de Korte <adkorte-guest at alioth.debian.org> > Author: adkorte-guest > Date: Wed Dec 22 20:31:42 2010 > New Revision: 2777 > URL: http://trac.networkupstools.org/projects/nut/changeset/2777 > > Log: > Don't version generated files > > Deleted: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap >
2009 Jan 15
1
[nut-commits] svn commit r1734 - in trunk/scripts: hal hotplug udev
Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Thu Jan 15 20:02:22 2009 > New Revision: 1734 > > Log: > Freshly generated USB helper files > > Modified: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap > trunk/scripts/udev/nut-usbups.rules.in Questions is, should we try