similar to: Can't claim USB device

Lee Gold <leegold at operamail.com> writes: > Ubuntu Server 12.04, Nut installed with sudo apt-get install nut > ... > Tried this and got error message: > Can't claim USB device [0764:0501]: could not detach kernel driver from > interface 0: Operation not permitted Did you reboot after installing the nut package? Just a couple days ago I connected up a USB UPS to a Red

The reboot worked. Thank You! Now I get: $ sudo upsdrvctl start [sudo] password for wsadmin: Network UPS Tools - UPS driver controller 2.6.3 Network UPS Tools - Generic HID driver 0.35 (2.6.3) USB communication driver 0.31 Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) I'm going to do: mkdir /var/run/nut chown root:nut /var/run/nut chmod

I rebooted machine and nut cannot connect to the UPS. mythuser at amethi:/etc$ sudo /lib/nut/usbhid-ups -DD -a CyberUPS1 Network UPS Tools - Generic HID driver 0.42 (2.7.4.1) USB communication driver (libusb 1.0) 0.02 0.000000 debug level is '2' 0.000499 upsdrv_initups... 0.005722 Checking device (8087/8000) 0.005753 Failed to open device, skipping. (Access

I've been running the Debian packaged 2.4.3 for a while, working find. When 2.6.0-1 just pushed through to debian, things have stopped working :( I checked what had been the usual suspects in past problems, namely permissions problems in /dev/bus/usb, but all seems in order: $ lsusb ... Bus 009 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS $ ls -l /dev/bus/usb/009/002

# export USB_DEBUG=5 # /usr/local/ups/bin/usbhid-ups -a CP550SLG -DDDDD Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 0.000000 debug level is '5' 0.000426 upsdrv_initups... usb_set_debug: Setting debugging level to 5 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 001 usb_os_find_busses: Found 002

Arjen, I just installed openSuSE 11.1. I though it would be simple to setup the same CyberPower CP1000AVRLCD on the same machine that we worked through the 20+ voltage issue with, but usbhis-ups driver is failing for some reason. I have gotten the output I remember you needing from the last issue for you. What do you think the problem might be? Here is the information: First the logs from the

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

I can't seem to find the info I'm looking for in google, hopefully someone has dealt with these sorts of issues in the past. I have a machine where my messages file keeps getting lines like: Mar 13 18:34:43 nemesis kernel: usb 2-6: reset high speed USB device number 2 using ehci_hcd Mar 13 18:34:57 nemesis kernel: usb 2-6: reset high speed USB device number 2 using ehci_hcd Mar 13

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

On 12/08/2016 09:38 PM, Charles Lepple wrote: > On Dec 8, 2016, at 7:56 PM, Jack McGee <jack at greendesk.net> wrote: >> I rebooted machine and nut cannot connect to the UPS. > Any messages from the kernel regarding USB HID drivers? (Check dmesg and/or journalctl.) dmesg: [ 1.658554] usb 3-5: new full-speed USB device number 4 using xhci_hcd [ 1.787602] usb 3-5: New USB

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]

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

Trying to get a Tripp-Lite to work with nut--Ubuntu 10.10. I was getting the error message "unable to claim USB device", tried to unbind the drivers to that device, and had the following delightful experience. In short, continue to get the same problem, and the drivers bound themselves back. Any suggestions? ----------- usb.conf has the following: [Tripp-Lite] driver = usbhid-ups port

Trying to configure multiple UPS on one Raspberry Pi 4 (Bullseye). Issue: Whenever more than one is plugged in, one shows as all - as in "upsc x" for all of them shows identical information for one UPS rather distinct for each plugged in. OS: /proc/version = "Linux version 5.10.103-v7l+ (dom at buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU

On 2020-08-19 17:36, Louis van Dyk wrote: > Hi > > BACKGROUND INFO: > I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux.  They don't provide software for it for Linux, only for Windows. > Referring links: > https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html >

Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here:

i can't seem to get newhidups to detect my UPS.. i'm using nut-2.0.3 (tried both the rpm from fc5-updates and compiling my own) here is the entry for the UPS in /proc/bus/usb/devices T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0764 ProdID=0501 Rev= 0.01 S: Manufacturer=CPS S: Product=UPS

I'm trying to get a CyberPower PP1100 working with NUT on a Fedora 16 system and not having much luck. Kernel: 3.4.4-4.fc16.x86_64 #1 SMP Thu Jul 5 20:01:38 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux NUT (installed from Fedora RPM): nut-client-2.6.4-1.fc16.x86_64 nut-2.6.4-1.fc16.x86_64 libusb: libusb-devel-0.1.3-9.fc16.x86_64 libusb1-1.0.9-0.6.rc1.fc16.x86_64

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: 0764:0501, UPS.PowerSummary.Voltage reports 26.6 for the 24V batteries so when the 0.667 battery scale is applied that goes down to 17.7V. upsc output: battery.charge: 100

This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD.