similar to: FreeBSD 6.1, MGE Ellipse ASR600USBS, newhidups & upsd

Hi, (please let me know if there is a better place to submit bugs) I run a FreeBSD box with stack-protector enabled, which raises a problem in the upsdrv_initups() function of the newhidups.c module; the regex_array variable is sized one item too small. Regards, Herve Masson <<<< void upsdrv_initups(void) { int i; #ifndef SHUT_MODE /*! * SHUT is only supported by

Hello. So as my english is not so good, i'll try to write my story in bash commands :o) miwa@zork3$ uname -mrs FreeBSD 5.5-STABLE i386 miwa@zork3$ su root@zork3# cd /usr/ports/sysutils/nat root@zork3# make && make install root@zork3# cd ../nut-usb root@zork3# make && make install root@zork3# cd /usr/local/etc/nut root@zork3# cat ups.conf user=root [MGE-Ellipse]

Fellows, back for 4 days, the baby and the mother are now at home, and the father is... hem, well not so fresh ;-) For those interested in some pictures: http://benjamin.quette.free.fr/ 2006/11/16, Peter Selinger <selinger@mathstat.dal.ca>: > ... > Arnaud: could you please amend the instructions on the NUT download > website http://www.networkupstools.org/source.html (Development

Hello, I am having trouble getting upsd to start. I am using the Debian NUT packages version 2.0.3 (current in Debian/sid). I am using the newhidups driver with an APC Back-UPS BR 800. The init.d script wasn't functioning, so I backtracked to running upsd manually and I get: foxstar:/etc/nut# upsd -u root Network UPS Tools upsd 2.0.3 Can't connect to UPS [foxstarups] (newhidups-auto):

I'm using an APC Back-UPS XS with nut 2.0.3. I've recompiled/reinstalled the source, and switched over to the newhidups driver (instead of the old hidups driver). I modified by ups.conf to use newhidups. The hotplug files were not automatically installed, I had to copy those from the scripts directory to my hotplug/usb directory. The newhidups driver loads find and then works for a

Mr. Selinger, I'm CCing you directly since it appears (insofar as I can tell) that you are one of the delelopers for the newhidups driver. This is the third time I've submitted this (hence the CC this time). Hopefully mailman takes it. I've tweaked my SPF records, and I'm hoping that was the problem. My sincere apologies if this has gone through and I just haven't seen it

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

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

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

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

I have an MGE Ellipse Premium 1200 that I connected to my server using its USB cable. Nut seems to be working fine. I've done a power down test and it worked and came back up when the UPS had power again. I'm using the newhidups driver and the USB cable. The problem I'm having is that if I boot with the cable connected newhidups says it can't find the UPS. If I unplug and plug in

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 -

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

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 there, been using NUT for ages and recently upgraded to a new server; while I'm waiting for a USB->Serial adapter for Solaris to arrive, I thought I'd play with the newhidups, as the APC UPS I have has a USB port and the new server doesn't have a serial port.... I've got Solaris 10 & newhidups working with the ugen driver up to a point, and that is a read

I've recently bought an MGE 650 that has both cables : USB and Serial. Since it's used on a server, I'd prefer not to load usb drivers just for nut. The problem is, either with newhidups or with mge-shut, the driver instantanly report that the communication with my MGE is lost, and shotly after that my ups is unavailable. It never show up again, and nut constantly says that the

Hi there, I'm trying to track down a problem with said combination. Broadcast message from nut (Thu Jan 26 13:22:06 2006): Communications with UPS UPS@localhost lost Broadcast message from nut (Thu Jan 26 13:22:11 2006): UPS UPS@localhost is unavailable "newhidups -DDD hiddev0" seems happy enough, as does "upsd -DDD -f" - at least until I start upsmon. Then I

hi i have a belkin ups here some setting chmod 0600 /dev/hiddev0 chown nut:root /dev/hiddev0 linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No matching USB/HID UPS found Driver failed to start (exit status=1) linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl -u root start

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

Hi all, First of all thanks for the great work on nut ! (despite it's not fully functional yet overhere). Everything seemed to go fine until the final test : shutdown the UPS ! The system is running FreeBSD 5.3, the UPS is MGE Ellipse 800 USBS both linked with the MGE serial cable. The system is a remote server, only running some file services and large disks. The porting,