similar to: NUT-2.0.5: newhidups on RedHat ES4

Hi everybody, If we let the feature running, it appears that the driver gets unbound after a while ( variable from quarter of hour to 6 hours ) and cannot reconnect. This behavior appear with both MGE Ellipse ASR and non-ASR models with connection to an UHCI and OHCI controllers. The USB core is from 2.4.28 kernel. We use nut-2.0.3. Start, powerfail and recovery detections, UPS shutdown work

Hi Arnaud, hi all I wish you all the best for 2006. Enjoying of some less stressed time, I follow your advice, Arnaud, to switch our UPS management on the newhidups driver. ( Enfin ! ;) Our goal is to support (soon) the new MGE ASR ELLIPSE ( and of course also the old ELLIPSE and EXTREME models ). I rebuild the libusb-0.1.10a packages to conform to our installation process. I perform the same

please tell me how i can use the hyperterminal to calibiration of my ups sua 1000VA. nut-upsdev-request@lists.alioth.debian.org wrote: Send Nut-upsdev mailing list submissions to nut-upsdev@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev or, via email, send a message with subject or body

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, I'm using NUT to manage a MGE Ellipse ASR UPS, with the newhidups driver. It works fine, except that after a few hours, I get a few errors from the kernel and the driver dies. Here's the output from the syslog: Apr 26 02:00:41 ezquiel kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Apr 26 02:00:43 ezquiel last message repeated 2 times

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

Hi, I bought an Ellipse MAX 1100 a few months ago. First I attached it to my desktop and installed mge's personal solution pac. (a graphical interface which uses nut). It works. But I want to attach the ups to my server which runs without an x-server. I followed http://opensource.mgeups.com/install/debian.htm. Didn't work. Then I copied over the configuration files which the personal

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB

- UPS MGE Premium Ellipse Premium 1200 - SuSE Linux 10.0 OSS, kernel 2.6.13 smp - gcc version 4.0.2 20050901 (prerelease), glibc-2.3.5-40 - mgeups-psp-3.0.0-3, nut-2.0.2-4 - Dell Dimension 8400 with dual core Intel Xeon. 3.0GHz. lsusb shows: Bus 002 Device 003: ID 0463:ffff MGE UPS Systems UPS less /proc/bus/usb/devices shows for bus 2 device 3: T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=

Hi all Arnaud, Some newly purchased Ellipse ASR-model UPS find their way to my office for a first evaluation test. It concerns the Ellipse 1500 and Ellipse 1000 models. As you know we are still working with hidups. Peripheral recognition, start of NUT, mains short interruptions management, all that work fine... as expected ;-) But changes occured on the delayed shutdown procedure after the

*********************** Your mail has been scanned by InterScan MSS. *********************** Has anyone managed to get this UPS to work? I am using the laster development nuts. My /proc/bus/usb/devices content: ==== cut ==== T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=ffff ProdID=0000 Rev= 1.00 S:

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=

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

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:

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

This took a long time because I had problems with my system. After I reloaded my operating system several times I found I had a bad memory module. Here is the output from newhidups for my Geek Squad GS1285U. It just kept repeating until I hit ctl-z. I think that this means nut will work for this ups. My computer is not powered by the ups yet. I did not want it to be powered down by accident.

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:

Hello We have successfully set up Red Hat Enterprise Linux ES4 and we are now trying to connect remote clients to connect to it. The problems we are having are as follows: a) If we set connect with telnet, we get the login prompt. If we use any valid login name & password combination (including root), we get the response "Login incorrect" and then the login prompt comes back. How

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"