similar to: usbhid-ups doesn't work after kernel/libs update

Hi. I use NUT on embedded system, and after update distro to fresh one I've got a non-working usbhid APC monitoring. There's 2 troubles: 1) I/O error for root on usbhid device 2) Permissions error for nut user Root log: # /usr/bin/usbhid-ups -u root -DDDDDD -a infocom Network UPS Tools - Generic HID driver 0.37 (5.1.2-beta1-28-g04cd334) USB communication driver 0.31 0.000000

Has anyone built a game with the dialplan? I would think this would most easily be managed by an AGI, but its possible with realtime extensions. The game would be like 'adventure' that I first played on a prime in 1979. Or any of the infocom games (ie zork). Infact since the infocom spec is known it might be possible to plug in the data files directly from an AGI. If anyone has done

Wow! this got long on me. The problem seems similar to the one expressed here: http://www.mail-archive.com/samba at lists.samba.org/msg111029.html but I already had server signing = no in my config, and the 4 relevant options all seem correct. client schannel = Auto server schannel = Auto client signing = auto server signing = No On one of my PC's I can see 'If possible =

Some day ago, a friend post one problem for mi. whist this texts: I have a server whit 2 interfaces of network, where eth0 is the interfaces connetc to internet and eth1 to the internal network. This server hace a Squid only, but i setting the iptables for protection to the server. Iptables run from script and in this script i setting the redirection for the other server in my internal network to

Hello, ? I sent a previous message about this case, but I'm guessing I had too much info.? I'll try to keep it simple. ? I'm looking for ways to further troubleshoot this error: [cstelter at fedorabox system]$ smbclient //fedorabox/sys Enter cstelter's password: Domain=[STELTER] OS=[Unix] Server=[Samba 3.5.6-70.fc14] smb: > dir NT_STATUS_ACCESS_DENIED listing * ???

Hi Please could someone assist me? I?e got a 3g usb dongle - Huawei E1552. [root@]# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 002: ID 03f0:8407 Hewlett-Packard Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus

hi, i've just set up two new computers each with a Powerware 3105 ups. they have identical nut configurations and identical upss which are both plugged in via usb but only one is being detected by nut. the other keeps saying: Broadcast Message from nut at server-1 (somewhere) at 14:52 ... UPS ups at localhost is unavailable i tried plugging the ups into several different usb

Dear friends, I installed NUT and followed all suggested procedures to verify if my ups is supported. No driver recognized my ups, and the genericups tests get wrong. Here I send some informations about it: The ups model is APC BZ1200-BR I use Ubuntu, and the lsusb results Bus 003 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC for ups. The

I'm using a bit of a different keyboard, the infinity ergodox [ https://input.club/devices/infinity-ergodox/]. It functions just fine as a keyboard on my host computer, but when I try to bind it to the guest, nothing seems to happen. lsusb gives its ID: Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub *Bus 005 Device 003: ID 1c11:b04d* Bus 005 Device 001: ID 1d6b:0002 Linux

Hi, i've got similar problem with an OVISLINK 1000VA UPS on Debian. I've tried to connect with it using different drivers and this is what I get with each of them: [UPS] driver = blazer_usb vendorid = 0001 productid = 0000 port = auto subdriver = phoenix sweethome:~# /lib/nut/blazer_usb -a UPS -u root -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4) 0.000000

On Dec 26, 2018, at 8:59 PM, David Melik wrote: > > root at 0.darwinheim <mailto:root at 0.darwinheim>:~# lsusb -d 051d: > root at 0.darwinheim <mailto:root at 0.darwinheim>:~# If you leave off the "-d 051d:" part, do you see anything in the listing that looks like it could be the UPS? (The 051d vendor ID is for the vast majority of APC UPS models, but we have seen

Hello list, ? ?Cannot make Evolution 850 to be recognized, maybe the problem is "Warning: incomplete endpoint descriptor" in lsusb? Details are as follows. NUT installed by download of debian package. Any ideas/suggestions are highly welcome, thanks in advance! --ValenteM = ? ?= ? ? = ? ? = Ubuntu server 12.04.1 LTS (GNU/Linux 3.2.0-35-generic x86_64) sudo dpkg -i

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

On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at skrypnyks.com> wrote: > I have searched the archives and googled this problem with usbhid-ups. I would really appreciate any help anyone could offer to solve the problem. > > System: Ubuntu 14.04.1 Trusty Tahr Which kernel version are you using? > Installed nut from Ubuntu repositories ? nut 2.7.1 > > Ups.conf file

I set the ups.conf to: driver = richcomm_usb port = auto now it is connected. There were the vendor variable and product id wrong. These are the variables i get in my OMV service output: device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto

I have searched the archives and googled this problem with usbhid-ups. I would really appreciate any help anyone could offer to solve the problem. System: Ubuntu 14.04.1 Trusty Tahr Installed nut from Ubuntu repositories - nut 2.7.1 Ups.conf file maxretry = 3 # user = nut [TrippLite] driver = usbhid-ups port = auto productid = 3016 desc = "Tripp Lite UPS,

Charles, Thank you :) Here it is : # usbhid-ups -a 5px -DDDD Network UPS Tools - Generic HID driver 0.37 (2.6.5-Unversioned directory) USB communication driver 0.31 0.000000 debug level is '4' 0.000302 upsdrv_initups... 0.161480 Checking device (0424/2512) (001/002) 0.161518 Failed to open device, skipping. (Permission denied) 0.161527 Checking device

Thanks for reply. when i try richcomm_usb or blazer_usb or other usb i get the output of : sudo /lib/nut/usbhid-ups -a trust -DD this is the output: Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 Error: UPS [trust] is for driver richcomm_usb, but I'm usbhid-ups! i tried to set the ups.conf to: [trust] driver = usbhid-ups port = auto vendorid = 0925

Hello All, I tested our new UPS yesterday. I noticed that while the blazer_ups drivers support this device, the newer nutdrv_qx does not. I suppose that this should not be the case, as nutdrv_qx will replace blazer_ups(?). Versions: I installed Nut on Ubuntu 13.10 (64 bit) from the standard package (2.6.4-2.3ubuntu2), and I also installed from the source tarball (2.7.1), into a different

Hi. Sorry for the English. Use online translator. Trying to configure Powercom Smart KING Pro 1250A and Debian Jessie. OS name and version: Debian Jessie 8.8, kernel 4.9.25-1~bpo8+1 exact NUT version: 2.7.2-4 NUT installation method: package exact device name and related information: Powercom Smart KING Pro 1250A (connect via usb; leads changed) complete problem description, with any relevant