similar to: Re: how to apply the shutdown scripts

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 Peter, I've fwded your info to the list, as other people might be interested in. I've also logged a patch tracker so that you can follow its inclusion: https://alioth.debian.org/tracker/index.php?func=detail&aid=302882&group_id=30602&atid=411544 As a side note, there is a work underway to merge the similar driver (mustek, powermust, ...) into one named megatec. This one

Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker:

2006/3/27, devzero@web.de <devzero@web.de>: > ... > ps: > Furthermore, there seems some inconsistency between driver.list and website: > > # Network UPS Tools driver.list > # > # This file is used to build the compat.html on the web server. Any line > # with exactly 4 arguments will be turned into an entry on there. > # Naturally, it is read by parseconf, so the

I have an APC Back-UPS XS1500 powering my computer. It may be overkill for a single computer but it makes me feel secure. Gnome power management will not install on CentOS 4.4 because of dependency problems. I have installed the acpupsd daemon and this will protect me against power failure but the GUI interface to it, gapcmon, will not install due to dependency problems. I know that some

Markus Layr wrote: >Hi, > >thanks for the mustek driver for the nut packages. >It works nearly perfect for my Mustek PowerMust USV 2000VA. > >There is only a little problem concering the battery.charge, perhaps you >can help me to solve it. > >I always get 100.0 as value for the battery.charge, it never changes. > >Regards, >Markus Layr > >

NUT recently stopped working on my debian. I'm not sure which upgrade broke it. ups.conf: [mustek] driver = megatec port = /dev/ttyS0 desc = "mustek ups" # upsd -DDDD Network UPS Tools upsd 2.4.1 listen_add: added ::1:3493 listen_add: added 127.0.0.1:3493 setuptcp: try to bind to 127.0.0.1 port 3493 listening on 127.0.0.1 port 3493 setuptcp: try to bind

Dears, I have centos 5.5 with kernel 2.6.18 UPS: Mustek PowerMust 2000VA USB I trying to setup monitoring for this ups, I connect ups with server via COM port and USB. But here is the problem (with megatec_usb): [root at optimus ups]# /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos

And sorry, I forgot to put log from messages, I always got this: Oct 30 21:06:25 optimus kernel: usb 5-1: usbfs: process 9808 (megatec_usb) did not claim interface 0 before use From: nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org [mailto:nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org] On Behalf Of Vladimir Micovic Sent: Saturday, October 30, 2010 8:00

Hello ! first off, thank you all for making this piece of software. from what i have seen so far this seems to be a really mature and advanced tool for all sorts of UPS models ! I`d like to tell that I own a UPS which isn`t listed on the compatibility list, but seems to be compatible. It is a PowerWalker - see this at

Hello ! first off, thank you all for making this piece of software. from what i have seen so far this seems to be a really mature and advanced tool for all sorts of UPS models ! I`d like to tell that I own a UPS which isn`t listed on the compatibility list, but seems to be compatible. It is a PowerWalker - see this at

Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less

Disclaimer: I've setup APC UPS monitoring and it works... ... but when it comes to mustek powermust 600usb (connected via com-port), I can't make it work. Got NUT installed via aptitude in ubuntu feisty and a basic setup, exactly the same as for the apc, except for the name of the ups and the corresponding section of ups.conf -- [mustek] driver = megatec port = /dev/ttyS1

Does anyone here have any "feel" for the "Battery disconnected" and "Battery reattached" log entries? The rebooting came as a result of me turning off modems, router, external drives, monitor, cordless phone and finally, the computer, trying to locate a quiet but annoying "chirp". The "chirps" stopped when I tilted the UPS to look at the front

On Jan 2, 2012, at 10:51 AM, Vladimir Micovic wrote: >> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > Unfortunately, this device ID is used by several different vendors. What does "lsusb -vvv -d 0665:5161" show? > Also, what OS and kernel are you using? (I thought certain kernels had USB-to-serial drivers for that chip.) > -- > Charles

I need a little help on this problem, please? I include my /etc/apcupsd/apcupsd.conf file is attached. port 3551 udp/tcp has been added to the (running) firewall. My APC is recognized as: APC Back-UPS 450 FW:844.Kld.D USB FW:Kld This from the hardware browser. PS says: root 2419 0.0 0.0 4196 584 ? Ss Mar23 0:09 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf Is group 2419 the

Hello;I just came across NUT, testing FreeNAS/FreeBSD. I?m running at home a APC UPS connected to another computer, running apcupsd. I found out that NUT didn't talk by default to apcupsd, and there was a driver created relatively recently (apcupsd-ups), which filled in that gap. The version I found on my FreeBSD/FreeNAS system seems to imply that there is more to come to that driver (0.04)

Hello, I had to increase slightly the maxstartdelay value to 60 instead of 45 as a work around, otherwise upsdrv and upsdrvctl are unable to start megatec_usb daemon at all. The strange thing is /lib64/nut/megatec_usb -DDDDDD -u nut -a mgeups runs without any problem and will recognize the value coming from the ups faster. Anyway, I don't understand why upsdrvctl does take so long to

Hi, I'm trying to setup my Mustek 600 with USB (no serial ports on my computer) on Gentoo. The configuration I use is: [Mustek] driver = megatec_usb port = auto desc = "Power Mustek 600 USB" The NUT I use on my x86_64 machine is: sys-power/nut-2.4.3-r2 USE="bash-completion ssl usb xml -cgi -hal -snmp" When I start upsdrv I get: weasel ~ # /etc/init.d/upsdrv start

> Am 17.11.2017 um 17:36 schrieb m.roth at 5-cent.us: > > wwp wrote: >> On Fri, 17 Nov 2017 10:34:53 -0500 Digimer <lists at alteeve.ca> wrote: >> >>> On 2017-11-17 10:16 AM, m.roth at 5-cent.us wrote: >>>> I can't seem to find apcupsd for C 6. Just went to epel's website, and >>> not >>>> visible. Anyone have a clue?