similar to: mge pc 675 does not work with usb-hidups

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

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

Hi there I have a Mustek PowerMust 1000 USB using serial port /dev/ttyS0. I use nut 2.2.1 with the megatec driver on Debian Lenny (testing), running on an AMD64 X2. (I was using a Debian Etch as slave, but to keep it simple I turned it off) My problem is that sometimes the UPS is running OK, but when the message "UPS is trimming incoming voltage" appears on knutclient (i.e. OL TRIM in

I almost had nut_2.0.5-3_i386.deb (from http://packages.debian.org/unstable/admin/nut - installed via dpkg, not via repository) working: * problems with getting it to come up during boot * monitoring via knutclient was OK * shutdown on low battery worked adequately, if not quite as described) and newhidups suddenly stopped talking to my Belkin F6C550-AVR . It's only been in use for a

Hi, There is many (20 per day on average) messages like: kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -110 usbhid-ups[6768]: HIDGetDataValue: Connection timed out What can be done do correct that problem? best regards, Franck my configuration: debian etch nut 2.2.1 (recompiled source from testing to use latest version before posting here) updated

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

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

Hello, I try to install my APC Back-UPS RS 800 on my debian system (Etch): Linux aigner 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 GNU/Linux When i try to start the driver an i use hidups i get this failure massage: aigner:/lib/nut# upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: HID UPS driver 0.13 (2.0.4) Warning: This is an experimental driver.

I'll be back one more time perhaps I found the reason of these errors Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale it happens when daemon upsd et upsmon are started after the boot obviously, there isn't any errors when upsd and upsmon are started at boot following later ... -----Message d'origine----- De : goudard sabine Envoy? : mardi

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:

I have a MGE Evolution 3000 connected via USB to a linux server (HP Proliant G3). The server is running kernel 2.4.30 and nut-2.0.3. But before nut trying to connect to the UPS, I guess HID doesn't work as long as I get a message like this in dmesg: -------------------------------------------------- usb.c: new device strings: Mfr=4, Product=136, SerialNumber=50 usb.c: USB device number 2

Browsing through the newhidups.c code, I stumbled across the following: /* master list of avaiable subdrivers */ static subdriver_t *subdriver_list[] = { #ifndef SHUT_MODE &generic_subdriver, #endif &mge_subdriver, #ifndef SHUT_MODE &apc_subdriver, &belkin_subdriver, &tripplite_subdriver, NULL #endif }; Shouldn't the 'NULL' terminator be outside the

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be

When I disconnect my UPS from the wall, I have to wait 15-30 seconds before the USB drier 'polls' this information and tells me that the UPS is on battery power (via knutclient or syslog via nut): ups@p34 POWER ALERT on Fri Jan 26 12:49:29 EST 2007 With a serial connection, I would get the alerts IMMEDIATELY (0.5-1 seconds) after disconnecting the UPS. My new machine does not have a

OPENSOURCE wrote: > > I hope this answer your questions, and I hope you're ready to wait a bit > more. > Sure, NP for me, thanks for the feedback Arnaud. I have to admit that past days im having the syslog with a lil more activity from the new usb attached unit (ellipse ASR 1000 VA) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2-pre2) Detected an UPS: MGE UPS

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with nut-2.0.1 (the standard "sarge" packages). I have it connected through USB, and I'm using newhidups. However, about once a day the driver looses contact with the UPS and I have to restart NUT to get it to drop the "data stale" nonsense (it happens more often than this, but most times it recovers without

Hi I try since a week to run my MGE Protection Center under Suse Linux 9.3. At the MGE site i found an HowTo. I have installed NUT an create the=20 configs but at boot the newhidups driver say=B4s "no USB/HID UPS found".=20= Anyone an Idea? Johannes Schatz=

Hi Raphael, btw, are you 2 bugs today a simple coincidence with my linkedIn invitation yesterday? ;-) 2008/10/4 Raphael Geissert <atomo64 at gmail.com>: > Package: nut > Version: 2.2.2-8 > Severity: wishlist > Tags: patch > > Attached is a patch adding "support" for tripplite's avr750u UPS. > Issues: > * productid still needs to be specified in

I was looking at how other drivers deal with outlet collections, and I noticed some differences between newhidups in 2.0.4 (from Debian's 2.0.4-2.3) and the SVN trunk (rev 723) on an Evolution. Full diff is below, but here are the highlights: * MGE HID 0.9 vs 1.0 * outlet.#.switch seems to have moved to the commands outlet.#.load.{on,off} Then I found this in the ChangeLog: * fix