similar to: FreeBSD installation procedure (updated)

Hi, Have anybody tried Cyberpower Value 600E (USB) under FreeBSD? usbhid-ups from nut 2.4.1 does not recognize (find) the device on my machine. [root at substance /usr/local/libexec/nut]# uname -a FreeBSD substance.dyndns.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root at walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root at substance

Hello all, I've got an MGE Pulsar Ellipse Premium 800 powering a couple of FreeBSD systems. Driver used is mge-shut, I don't know what the new mge-shut driver offers, but I follow the "if it works, don't fix it" dogma here. :) I also had a nut server installed on the master, with the /usr/local/etc/rc.d/nut script slightly modified to include a couple of upsrw commands

Hello all, I just wanted to dump some info here for the archives. Here's the original thread for reference: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-March/002403.html Charles Lepple did a tremendous amount of work to get my TrippLite USB working on FreeBSD 6.2. I'm running an svn version (nut-2.1.0-r879) to pick up his changes to tripplite_usb. So far, it is

Hi, I wrote a small utility to stay in Windows tray and indicate NUT UPS device status and some properties. The tray icon shows UPS battery status (from green for 100% to red for 0% and red-crossed for unconnected state). The tooltip shows UPS manufacturer and model names, date of production, UPS status, battery status and voltage, time left when running on batteries. Archive containing compiled

Hi all. I'm trying to get a CyberPower OR700LCDRM1U UPS working with NUT (via USB). I assumed this would be compatible since the OR2200LCDRM2U is. Clearly I'm wrong or missing something vital. I'm on FreeBSD, using the version of NUT from the ports tree (2.6.1). FWIW, I tried compiling from source with similar results. Here's my UPS in ups.conf: [ssups] driver=usbhid-ups

Hi all, > Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at gmail.com>: > There may be an issue with the uhid driver binding to the device. I can't remember which versions of FreeBSD this affects, though. Unloaded the kmod - did not change anything. But I will configure devd not to load uhid.ko ever, just to be sure. You are implying Ithe uhid driver should not be

Hi all, I just bought a Trust 1000VA PW-4105 UPS. I installed the UPS on FreeBSD 6.1, and installed NUT 2.0.3 via the FreeBSD port. I had no problems installing and configuring nut and the UPS to run with the PowerMust driver. My problem however is when I test the powerdown function by issuing the command: 'upsmon -c fsd' The UPS is cutting the power before the shutdown procedure

Hello, I'm new to the list, new to NUT, but not new to Unix-likes. I could use some help getting NUT to talk to my Tripp Lite G1000U. Searching Google for "Tripp Lite G1000U" returns exactly two hits at this writing, so that may not be a good sign. ;-) It may just be rebranded for sale through this source (Costco). Externally, the G1000U looks much like the SMART1000LCD: an amber

2007/3/8, Charles Lepple <clepple-guest@alioth.debian.org>: > Author: clepple-guest > Date: Thu Mar 8 04:15:51 2007 > New Revision: 848 > > Modified: > branches/tl_usb_fbsd/drivers/Makefile.am > branches/tl_usb_fbsd/drivers/libhid-uhid.c > Log: > Work-in-progress... maybe I need to look at how the SHUT subdriver works. > ... simply use the same interface

My UPS has a usb interface with USB-to-Serial chip. But ucycom driver doesn't recognize it. uhid driver does, but it doesn't help me, I need a virtual com port. (output below is without uhid loaded) What can I do to get it working? udi = '/org/freedesktop/Hal/devices/usb_device_665_5161_noserial' freebsd.device_file = '/dev/ugen1' (string) freebsd.driver =

On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > 0.016485 Trying megatec protocol... > 0.017411 send: Q1 > 0.252545 read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001 > 0.252589 Status read in 1 tries > 0.252602 Supported UPS detected with megatec protocol > 1.288032 send: Unknown error > 1.288085 Permissions problem: Input/output error

Hi. I'm from Russia. I try to use NUT with PowerWalker vi 400 se (usb). I use FreeBSD 7.0 (amd64) and megatec_usb driver. Settingup the NUT with FreeBSD installation procedure (Thierry Thomas, from FreeBSD). PowerWalker connect to the computer by usb cable on port usb0 (uhib0). NUT don't starting, and talk to me that supporting device not found. Please, help me. Thank's! With best

Thx Charles, So since this is a new type of UPSonic UPS, do you think the vendor screwed up or is it just some quirk on Freebsd? Yes, if you can look into this I would appreciate it. I do not see anyone else on the Web attempting to use this new device yet.....but....... Regards chris On 2/6/14, 8:24 AM, Charles Lepple wrote: > On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > >>

Hello ! Anybody have expirience with Powercom Imperial 1500 VAC (USB interface) ? Under FreeBSD 6.2 it's shown as uhid device: uhid0: POWERCOM CO., LTD. USB to Serial, rev 1.00/0.00, addr 2, iclass 3/0 usbhid-ups doesn't recognize it, and powercom driver doesn't work with uhid device. It seems for me that FreeBSD doesn't support it, so it doesn't create serial device for

Hi Shane, please try the instructions at http://www.mathstat.dal.ca/~selinger/ups/backups.html (with appropriate modifications for FreeBSD). If you can't get it to work, please get help from the nut-upsuser mailing list (cc'd above), as I am no longer actively involved in NUT development. Good luck, -- Peter Shane Roberts wrote: > > Hi Peter, > > I am running the NUT

On Tue, 13 Oct 2015, Davide Baldini wrote: > Guess I can assume that my OnePower A03-S1001 just doesn't support the > shutdown command. Might this be the case? If the UPS does shut down, then it will have to do so after a delay and not immediately on receiving the shutdown command. Does upsc <ups_name> report anything like ups.delay.shutdown: 30 ups.delay.start: 40

Hello Arno, FreeNAS doesn't come with a compiler and I had to compile with the patch on FreebBSD-9.3 and then copy the produced mge-shut. Unfortunately it didn't work out. For every try I was getting "Connection Refused" and when I tried /usr/local/libexec/nut/mge-shut -D -a <ups_name> I was always getting 'No matching HID UPS found'. I returned back to the

Hi Vladimir, I have got 2.0.3 working on netBSD 3.0. To get it operational I needed to do the following (most of this is from memory...). 1). Recompile kernel with uhid removed. If uhid ataches to the device then libusb is not able to. Have to allow generic usb driver ugen to claim port. >From dmesg usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class

On 10/08/2012 21:58, nut-upsuser-request at lists.alioth.debian.org wrote: >>> Arnaud Quette<aquette.dev<at> gmail.com> writes: >>>> 2012/6/3 Chris Rees<crees<at> freebsd.org>: >>>>> Hi all, >>>> Hi Chris, >>>> >>>>> After some research I've found that this device should run with the

Arjen, All, I need help unwrapping my head from around the problem of getting nut running on the same machine it runs fine with on another drive!! Sound easy -- not here :) I have network-ups-tools 2.4.1-2 on two servers. On one server I had a raid drive fail (which I'm still booting from and running nut on just fine). I bought a second pair of drives to establish a new array in the