similar to: hidups can't find device

is there a way to override the productid (like -x productid=1234) when using newhidups? just thought i'd try it with the F6C1500-TW-RK over usb. i was able to get hidups to work using the below settings, but it provides limited information. my ups.conf entry: [belkin] driver = hidups port = /dev/usb/hiddev0 and the output of upsc: gateway:/etc/nut# upsc

2006/1/13, Paul Mogren <fkamogee@yahoo.com>: > > This thread is FYI. I don't need any help here. > no, but some details for those who will read it, maybe ;-) I have SUSE 10.0 and an MGE Ellipse. I installed the NUT package from MGE. > > 1) The generated ups.conf pointed to a bad location: > /dev//dev/input/event0 > who generated that ? it seems like an old hiddev

I am forwarding the below message. Does anybody on this list know anything about this problem? Petr - perhaps you should switch from the "hidups" to the "newhidups" driver. I believe it supported the APC Back UPS even in NUT 2.0.2, and it certainly does so in the Development version that you can get from CVS (see the NUT download page). Also, could you post the output of

I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list said I should use either the newhidups or hidups driver. I looked in the installation and I found headers and c files to create these drivers (I think), but in /usr/local/ups/bin there is no driver named, "newhidups or

Hello, I have encountered problems trying to set up nut to work with APC BackUps Pro CS connected over USB to an AMD64 machine running Debian. While apcupsd works fine with that device, whenever I start upsd I get the following messages in syslog: hidups[23159]: Startup successful upsd[23160]: Connected to UPS [apc1]: hidups-hiddev0 upsd[23161]: Startup successful hidups[23159]: Unhandled event:

Hi! I've got a Mandrake 2006.0 machine and a APC Back-UPS Pro 500/1000/1500 (from lsusb). The Mandrake package version of nut is 2.0.1 and hidups actually detects the UPS, however I get loads of these: Sep 12 18:26:11 vader hidups[7658]: Ignoring x86 page event 0xff860080 (0) Sep 12 18:26:11 vader hidups[7658]: Unhandled event: 0x840058 (6) Sep 12 18:26:11 vader hidups[7658]: Unhandled

Hi, is there a way to use my Belkin F6H650 on the USB port? I already installed usbhid-support, but neither the hidups worked (reports "/dev/usb/hiddev0 is not a UPS") nor genericups with upstype=7 and the hiddev set as device ("ioctl TIOCMSET: Invalid argument") worked. I have installed the debian sarge package of nut 2.0.1 (2.0.1-4) Regards, Philipp

Hi, I'm new to nut, just installed it. I configured it using the hidups driver to work with my APC BackUPS: # upsc apc350@localhost battery.charge: 100 battery.runtime: 885 battery.voltage: 13.5 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.delay.shutdown: -1 ups.delay.start: 0 ups.load: 660 ups.mfr: American Power Conversion ups.model: Back-UPS CS 350

Hello, I have installed my Samba as a PDC with LDAP Backend, it worked fine, I was able to join the Domain with a Windows XP Client.But Today when i started the server, i can't join a domain anymore. I also can't add users to ldap anymore with smbldap-tools i always get this failure message: 3444 Use of uninitialized value in substitution (s///) at /usr/share/perl5/smbldap_tools.pm line

On opensuse 10.3, i installed nut and configured my ups.conf like i did it on opensuse 10.2 by putting (10.3 , nut 2.2.0): [MGEpc675] driver = usbhid-ups port = auto desc = "MGEpc675" instead of (10.2 , nut 2.0.4) : [MGEpc675] driver = newhidups port = auto desc = "MGEpc675" But it doesn't work. It appears that upsdrvctl

I'd like to submit a patch to the 'hidups' driver. I'm a bit new to open-source development model, so I hope I'm not committing a faux paus by just posting it here. I did verify that the problem still exists (by source code inspection) in the latest dev snapshot, which is nut-2.0.3-pre2. I'm using nut-2.0.2 myself. The problem is when I'm connecting to my APC

I Seem to have made some progress in getting nut-2.0.5 installed, but hidups still has a version number of 0.13. First is hidups 0.13 the correct version? if not how do I find the correct version. Second if my Geek Squad GS1285U UPS is not supported how do I proceed. I have been a programmer for 35 years(mostly high level computer aided design), written code in 20 some languages, am retired

Hello Linas, > Just wanted to inform You (for the compatibility list), that HP R/T2200 works perfectly with the hidups driver. Thank You very much for NUT! :) > > # upsc hp at localhost > battery.charge: 100 > battery.chemistry: PbAC > battery.voltage: 22.7 > driver.name: hidups > driver.parameter.port: /dev/usb/hiddev0 > driver.version: 2.0.5 > ups.delay.shutdown:

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hello, I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups. Without any reason, nut/upsmon shut down my PC: >>> Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost

Greetings: I've been following through the instructions on how to connect an APC BackUPS 650 ES to USB, and have it monitored with NUT... I know my system can SEE the UPS, as DMESG shows this: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-1 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver I can see

Regards I am installing NUT for the UPS Skate UPS-2200D, the UPS have conection with USB to PC and i have problems to configure nut the ups is conected and Linux report this config Aug 19 23:34:56 dakota kernel: [22393.099595] usb 2-2: new low speed USB device using uhci_hcd and address 7 Aug 19 23:35:06 dakota kernel: [22403.186326] usb 2-2: Product: MEC0002 Aug 19 23:35:06 dakota kernel:

Hello, For a while I have been running NUT 2.0.0 just fine with my APC Back-UPS RS 800 using the usbhid interface. I decided to upgrade to 2.0.2, and all went well (upsc and upsd/upsmon seem happy to talk to the UPS), but I am getting a ton of these messages in my syslog: Jul 6 17:12:45 yggdrasil kernel: usb-uhci.c: interrupt, status 3, frame# 780 Jul 6 17:12:50 yggdrasil kernel:

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't