similar to: Device not found--newhidups, FreeBSD 4.10, CyperPower 685AVR

I've been a NUT user for a while, on Linux, and I've been very pleased with the performance of it. I have a new machine here, that runs NetBSD, and I've been having fits with that. First, NetBSD has NUT 2.0.5 in the pkgsrc collection, and I don't really want to mess with that, since it's so far out of date. So, I built NUT 2.4.1, from source. All is well there, but I

i can't seem to get newhidups to detect my UPS.. i'm using nut-2.0.3 (tried both the rpm from fc5-updates and compiling my own) here is the entry for the UPS in /proc/bus/usb/devices T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0764 ProdID=0501 Rev= 0.01 S: Manufacturer=CPS S: Product=UPS

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

Have recently purchased a MGE Nova 1100 UPS and am trying to get running on netBSD. Configuration netBSD 3.0 amd64 libusb 0.1.10a nut 2.0.3 Built & installed libusb Built kernel with ugen device and uhid removed Build & install nut-2.0.3 with usb Chmod /dev/ugen1 etc to allow access by nut user. Ups.conf [MGENova] driver = newhidups port = auto

Hi Scott, Scott Alfter wrote: > I had a UPS go bad recently (shuts off all by itself for no good reason, >AFAICT), so I bought a CyberPower 685AVR this afternoon. The two CyberPower >drivers in NUT 2.0.2 don't know how to talk to it, but the hidups driver >appears to work properly. This means you have to use USB instead of RS-232 (it >supports both), but at least it works. >

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

Hello, Help me please with *newhidups* setup. Does it work for someone on *BSD ? Here is the data. --------------------------------------------------------------- *** FreeBSD root.srv# uname -a FreeBSD xxxxxx.dyndns.info 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Tue Feb 8 07:38:22 UTC 2005 admin@temp.botka.homeunix.org:/usr/src/sys/i386/compile/SRV i386 *** NUT ver.2.0.3 root.srv# ll /var/db/pkg/

All: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2> on uhub0 using the usbdevs -v command: Controller /dev/usb0: addr 1:

On 2/5/14, 9:55 PM, Charles Lepple wrote: > On Feb 5, 2014, at 9:03 PM, Chris Duffy wrote: > >>> Please run this: >>> >>> /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D >>> >>> and send the output back to the list. >>> >> Output from the above command: >> >> 0.000000 debug level is '1' >>

Hi, folks! There is FreeBSD 7.1, NUT 2.4.1, UPS APC Smart 2200 XL. NUT is compiled from ports with following options: --------------------------------------- _OPTIONS_READ=nut-2.4.1_5 WITH_SERIAL=true WITH_USB=true WITH_SNMP=true WITHOUT_NEON=true WITHOUT_PDU=true WITHOUT_HAL=true WITHOUT_IPV6=true WITHOUT_CGI=true --------------------------------------- UPS is successfully recognized by OS

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

Short version: Different clients need different socket options to perform well. Can I point to a different smb.conf file as a function of the client name or OS? Long version follows for the masochists! At home I run a mixed-client network, and I am having problems configuring my smb.conf to support them all equally well. I am able to create shares, and I can browse them, but file transfers

Hello, 1) On OpenIndiana 151, I configured nut 2.6.1 as configure --prefix=/opt/nut/2.6.1 --with-cgi --with-hal --with-user=ups --with-group=nut CC=cc The result is -e Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes build Powerman PDU client driver: no enable SSL development code: yes

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 =

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

Folks, while I've got the above combination to compile and run under Solaris 10, it seems that there are still problems in the libusb/ugen driver stack from Sun and or the APC Smart UPS 1500, so things aren't actually working. It seems that the APC Smart UPS 1500RM doesn't return the HID descriptor length information in 0x21 as noted in a previous thread, but in my case, it also

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

On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote: > We have upd(4) attaching to these devices now. Either nut needs a > driver getting status from upd (trivial, will show up in the > hw.sensors sysctl tree) or we need some way for nut still being able > to talk to the ups directly, without upd and nut interfering with each > other. While a upd(4) driver

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

* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]: > * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > Looks like this patch fixed the problem. I see the status change now. > > Good to hear. > > I'm not familiar with the OpenBSD release process. Is