similar to: newhidups dies after a few hours

Dear List, I thought it might be useful if I wrote up my notes on getting an MGE UPS to work with NUT and openSUSE. The MGE UPS (an Ellipse 1500 USB) will work well with NUT and openSUSE 10.2, but not "out-of-the-box": there are some things you need to do: Intro. MGE have built rpms of NUT which greatly simplify installation. Merci MGE. I used the rpm's for nut-2.0.5 and the

Dear List, I have an MGE Ellipse 1500. I run openSUSE 10.2, kernel 2.6.18, libusb 0.1.12, nut 2.0.5. ps shows that the following processes are running: /usr/lib/ups/driver/newhidups -a mgeups /usr/sbin/upsd -u root /usr/sbin/upsmon /usr/sbin/upsmon NUT operates correctly, shutting down the server after 4 minutes without power. However I'm seeing 25 to 50 messages logged each day in

Hello everybody, After succeeded in "tuning" nut-2.0.0's hidups and 2.0.3's newhidups on customized Linux kernels, we are now facing a new challenge : trying to install nut-2.0.5 on a RedHat ES4 which is based on a 2.6.9 kernel. I picked up the 2.0.5 source package and follow the INSTALL doc until step 6. So far so good. RH ES4 is managed by udev, therefore I presume we

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

Hello, I encounter a problem using the UPS MGE Evolution 850 VA USB with Debian Etch and the nut package available for this version. I got this error: ==syslog== Can't connect to UPS [MGE850VA] (usbhid-ups-auto): No such file or directory upsd[2767]: Startup successful upsmon[2769]: Startup successful upsd[2767]: Connection from 127.0.0.1 upsd[2767]: Client MGE at 127.0.0.1 logged

I recently purchased a CyberPower CP1200AVR UPS and am trying to get NUT 2.0.3 or NUT 2.1.0 to work with the newhidups driver, but am having little success. Before I purchased I did some googling and saw people talking about problems so I'm guessing it may not be supported yet? I did find some posts about people getting it to (sort of) work with some hacks, but couldn't tell if they

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

Hello, I'm currently try to get newhidups running with the newhidups driver from nut 2.0.2. After some USB issues (usb_claim_interface() works only as root so far) newhidups is recognizing the device. Though it doesn't detect any state changes, meaning when I run the battery test mode it's not recognized. I wanted to try the CVS version but it seems anonymous CVS is broken. The

I'm trying to get nut to work with a Cyberpower 900AVR. There are many different products known by this name, but this one has the extra name 'BC900D'. I am told by a cyberpower tech that this one should talk exactly the same USB protocol as the 685AVR, which was recently made to work with newhidups. Unfortunately, when I run the SVN checkout (trunk) of nut-2.1, I get: sstreet

Bonjour, Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous) DaneZ _____ From: DaneZ [mailto:david.guillotte@danez.no-ip.org] To: arnaud.quette@mgeups.com Sent: Sat, 08 Jul 2006 23:24:06 +0200 Subject: Fw: INFOSEC 500 XP en USB _____ Bonjour Arnaud, Je me

Hi, I'm running nut 2.0.3 on Gentoo connected to an MGE ProtectionCenter 675. newhidups intermittently crashes. Any ideas? N. # /usr/lib/nut/newhidups -a mgeups Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) Detected a UPS: MGE UPS SYSTEMS/PROTECTIONCENTER Using subdriver: MGE HID 0.8 This is the error I'm getting *** glibc detected *** /usr/lib/nut/newhidups: double free or

tags 354429 + upstream thank 2006/2/26, suicune@eml.cc <suicune@eml.cc>: > Package: nut > Version: 2.0.1-3 > > > This is the spam message: > drivers/usb/input/hid-core.c: ctrl urb status -32 received > > I never once saw this message until after I installed and configured > nut. > > Spam begins during boot and continues infinitely until reboot or nut is >

Hi Arnaud, Is there any news about this hardware,does nut managed it right now ? Is there any technical information to make it working on debian ? Thanks for your help, Regards, DaneZ _____ From: Arnaud QUETTE [mailto:Arnaud.QUETTE@mgeups.com] To: DaneZ [mailto:david.guillotte@danez.no-ip.org] Sent: Mon, 17 Jul 2006 09:07:03 +0200 Subject: Re: RE Fw: INFOSEC 500 XP

I have a ups that doesn't always (sometimes it does) load NUT right. I use Gentoo: * sys-power/nut Latest version available: 2.6.0-r1 Latest version installed: 2.6.0-r1 Size of files: 1,663 kB Homepage: http://www.networkupstools.org/ Description: Network-UPS Tools License: GPL-2 The kernel is 3.0.4. Here is the dmesg output:

I'm getting dmesg flooded with messages like this one: usbdevfs: usb_submit_urb returned -28 What's wrong? I'm using Linux kernel 2.4.32 and nut-2.0.3. The /etc/ups.conf contains [mgeups] driver = newhidups port = auto desc = "MGE UPS" Cheers, Rodrigo -- *** Rodrigo Martins de Matos Ventura <yoda@isr.ist.utl.pt> *** Web page:

The UPS is connected to the following environment: OS: Debian GNU/Linux 9.6 (stretch) NUT version: 2.7.4-5 Device output from lsusb: 0463:ffff MGE UPS Systems UPS Model name: MGE EllipseMAX 1500 URLs: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-MAX-eol.aspx?cx=97&GUID=7BB6CD53-9F6D-4D62-B326-1099F137BF8D http://powerquality.eaton.com/68558.aspx?cx=97 The problem

Hi, I keep getting the following messages (or similar) in my syslog: Nov 23 11:38:08 io kernel: [763936.921566] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -110 Nov 23 11:38:08 io kernel: [763936.972569] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -75 Nov 23 11:38:08 io kernel: [763936.976568] usb 3-2: usbfs: USBDEVFS_CONTROL

2006/10/2, Peter Selinger <selinger@mathstat.dal.ca>: > Arnaud Quette wrote: > > > > 2006/9/29, Peter Selinger <selinger@mathstat.dal.ca>: > > > > > I don't really understand the purpose of the "Testing" branch. It has > > > not been touched since July, as far as I can see. I also don't > > > understand NUT's release

Hi, I have installed in suse 9.3 and ellipse premium 500 usb a psp 3.0 with yast2 and versions: nut-2.0.2-4 mgeups-psp-3.0.0-3 the first time that I launch psp it seems to contact the UPS and you can make changes to the parameters and all seems ok. If you make a reboot the psp hangs up and if you try /etc/init.d/ups it fails: Starting service NUT: -> Starting UPS driver: Network UPS Tools -

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: