similar to: nut with hal on Fedora 8

Hi fellows, I'm really pleased to announce that a first stage of NUT and HAL [1] integration has been reached: NUT drivers (in fact, only newhidups, tripplite_usb and bcmxcp_usb for the moment) can feed HAL data. It's a "quick and dirty" hack, as a proof of concept, and there is still lots of things to be done, both on NUT and HAL sides. But it's a good base, and very

I was getting: "Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not permitted" so I manually installed the udev rules the source (I installed the Gentoo ebuild). I am now getting: # upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using

Hi All, I've been trying to trace the cause of a hang on a 5.6 i386 system. After running for almost a year, it hung last week, when I plugged in a screen it was blank, machine was unresponsive to the keyboard, over the network ssh and other daemons didn't respond but the thing has two network cards and routing from one to the other was still working. So the kernel was up and I

I've tried several recipes found with google, but hal likes to grab the USB ups before nut can get it. There are a number of klugey workarounds, like turn off port power until ready to start nut (so that hal doesn't see the UPS). Or killall hal-addon-hid-ups before starting nut. Here is one of recipes I googled: https://github.com/sdgathman/trippfix/blob/master/halpolicy.fdi It

Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . On November 9, 2024 1:25:29 PM EST, Bill Gee <bgee at campercaver.net> wrote: >Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS

On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: > >> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:

Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS seeing the UPS at a low level. I looked through /dev/ but did not see a device that jumps out as the UPS. ===================== [root at mythtv rules.d]# dmesg | grep -i 0764 [ 2.021485] usb 1-1.8: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01 [ 2.049515]

On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: >> >>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage

Greets all; I was just booted to mdv-2010-x64 where I found my lack of sound problems. Whoopy ding... But when I rebooted to fedora, now the driver cannot disconnect and gain access to the ups. I installed the 52-nut udev file in /etc/udev.d, and it reads that it should setup /dev/hiddev0 like this and with 0664 perms when it finds that ups: crw-rw-r-- 1 root nut 180, 0 2010-01-03 20:51

Hello, I've had this same model CyberPower connected to a linux server and a freebsd server. [root at sensor003 menon]# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus

Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as? On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote: >Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. > >I updated the system yesterday

On Tuesday 21 January 2020 19:52:01 Charles Lepple wrote: > sudo lsusb -v -d 0764:0501 copious output, containing this: idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0501 CP1500 AVR UPS bcdDevice 0.01 iManufacturer 3 CPS iProduct 1 CP625HGa I take it that this is evidence they don't follow the spec to the letter.

Hi, is there anybody understanding HAL? I use CentOS 4 (RHEL 4) I need set specific mount options for USB flash disk. I found I can do it in /usr/share/hal/fdi/95userpolicy/storage-policy.fdi <?xml version="1.0" encoding="ISO-8859-1"?><!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="volume.fstype"

I'm new to R and very excited about its possibilities. But I'm struggling with some very simple things, probably because I haven't found the correct documentation. Here's a simple example which illustrates several of my problems. Suppose I want to have a regexp match against a string, and return all the matching substrings in a vector of strings. regexp <-

Can you try starting the driver with higher debug verbosity to see more details, e.g. add `debug_min = 6` to the `ups.conf` section, or stop the auto-starting driver attempts and run the driver program with CLI options? * https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity With `upsdrvctl` driven attempts, you may also be in conflict with a generated `nut-driver at

On Tuesday 14 January 2020 00:03:09 Gene Heskett wrote: > On Monday 13 January 2020 22:42:46 Charles Lepple wrote: > > On Jan 13, 2020, at 10:17 PM, Gene Heskett wrote: > > >>> (I was looking at the hid-subdrivers.txt file in the latest NUT > > >>> tree, which has the command line amended to not generate that > > >>> "too many non-option

Citeren Charles Lepple <clepple at gmail.com>: >> Another thing, loosely related to this, is how we are going to deal with the >> 'generic' VID:PID combinations in some of the USB drivers, for example the >> megatec_usb and (new) blazer_usb drivers. At present, in the megatec_usb >> driver we have several VID:PID combinations for USB-to-serial converters

I also am wondering if the message about libusb driver missing might be the real problem. Checking my system, I see this: =================== [root at mythtv dev]# ll /dev/bus/usb/001 total 0 crw-rw-r--+ 1 root root 189, 0 Nov 9 08:21 001 crw-rw-r--+ 1 root root 189, 1 Nov 9 08:21 002 crw-rw-r--+ 1 root root 189, 2 Nov 9 08:21 003 crw-rw-r--+ 1 root dialout 189, 3 Nov 10 09:43 004

Thanks for the tip, Jim. I just figured out what is going on. The system is now working. ==> This one is on me. <== The root cause was the specification of the bus number in the ups.conf file. Here is what it looks like now: ============ [cyberpower] driver = "usbhid-ups" port = "auto" vendorid = "0764" productid =

Hi Patrick, 2010/11/15 Patrick O'Malley > I've confirmed that the CyberPower CP1350AVRLCD works with nut using > the USB port and the usbhid-ups driver. It is not on your list. > Thanks! > have you checked all variables, and most of all that shutdown works as expected? ie http://new.networkupstools.org/user-manual.html#Testing_shutdowns please also send us an upsc output.