similar to: NUT + devd + FreeBSD

On Mon, Oct 29, 2007 at 9:45 PM, Daniel O'Connor <doconnor at gsoft.com.au> wrote: > I made the following devd script.. > > sh > cd /tmp > fetch > mkdir /usr/local/etc/devd > sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ > device-name "ugen[0-9]+";\ > match

On Aug 13, 2014, at 11:46 PM, O'Connor, Daniel <darius at dons.net.au> wrote: > I did some fiddling and came up with.. > notify 100 { > match "system" "USB"; > match "subsystem" ?DEVICE"; > match "type" "ATTACH"; > match "vendor"

I'm trying to make devd run an stty command whenever a USB serial device is attached. Unfortunately, $device-name is ucom[0-9] and the device names are /dev/cuaU[0-9] - how do I get the correct name in the device action? I haven't found a way to extract the number by itself, so I'm stuck with specifying a separate rule for each number, like so: attach 100 { device-name

I'm sure I'm missing something, but I can't seem to get NUT working on FreeBSD. bryce at tahiti[/usr/local/etc/nut]>cat ups.conf [belkin] driver = usbhid-ups port = auto vendorid = 050d #productid = 0751 bryce at tahiti[/usr/local/etc/nut]>s /usr/local/libexec/nut/usbhid-ups -DDDDD -a belkin Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31

# usbconfig -d ugen0.2 dump_device_desc ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (60mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x09ae idProduct = 0x0001

On Jan 31, 2014, at 3:14 PM, Chris Duffy wrote: > The current one I am looking is support for: > > Upsonic Commercial UPS CXR 2000 - 2000VA/1200W - Rack/Tower > > What seems to be supported in Freebsd is: Small clarification: the hardware compatibility list isn't broken down by operating system (theoretically, the drivers should work on any POSIX system, with additional

Hi, I have an MGE Ellipse 1000 connected to a FreeBSD 7.1 system and it works well except that if I yank the cable it doesn't detect a problem.. It seems to quite merrily read the old data (upsc reports the same values). There is nothing logged by NUT to indicate comms is lost (usbhid-ups is still running). In the attached log I yanked the able at the 28 second mark and plugged it back

I am working with a number of our customers to ensure that NUT works with different UPS's on Freebsd 9.1. The current one I am looking is support for: *Upsonic Commercial UPS CXR 2000 - 2000VA/1200W - Rack/Tower* What seems to be supported in Freebsd is: CXR1000 blazer_ser LAN Saver 600 genericups upstype=0 Power Guardian genericups upstype=7 PrOffice 650 USB blazer_usb DS-800 USB

Hello everyone, I have a Tripp-Lite UPS (smart1500rmxl2ua) I'm trying to get working with nut. This is a FreeBSD 10.3 box. I've tried using the usbhid-ups<http://networkupstools.org/docs/man/usbhid-ups.html> driver but everytime I try to start up nut, I get this: # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4)

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

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

Hello, I have FreeBSD guest running with KVM+libvirt, when I send shutdown through virsh for ex. $ virsh shutdown freebsd There is not any reaction from FreeBSD. Linux guests works together with acpid daemon well. devd in freebsd is running, and should work correct. Is there any way to fix this dumpxml config http://pastebin.com/UGGgG894 devd config is out of box -- Nikita A Menkovich JID:

Hi, Reference: lists.vn1 at gishpuppy.com wrote: > OS: Debian Wheezy > Nut: 2.6.4-2.3 > Installation method: Synaptic > Device: CDP B-UPR505 > Traces, debugs, etc.: Not available or irrelevant > > Description: > > Where I currently live (Honduras), buying a UPS with monitoring capability means spending at least twice as much as a "plain-Jane" model - usually

Thx for the info Charles. Here is what I am seeing from 'usbconfig list' ugen0.1: <EHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: <EHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: <product 0x0024 vendor 0x8087> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: <product 0x0024 vendor

On 6/2/2014 6:28 AM, Charles Lepple wrote: > On Jun 2, 2014, at 7:27 AM, elliot smith wrote: > >> For example I am using FreeNAS. Rather than supporting my unorthodox UPS >> signaling scheme by installing it as a script in FreeNAS, (and me probably >> messing something up in the process) this scheme could be supported >> instead by NUT. > > Bear in mind that

On Jun 2, 2014, at 7:27 AM, elliot smith wrote: > For example I am using FreeNAS. Rather than supporting my unorthodox UPS > signaling scheme by installing it as a script in FreeNAS, (and me probably > messing something up in the process) this scheme could be supported > instead by NUT. Bear in mind that all of the NUT drivers have authors who are expected to be maintainers of that

Alright. Sorry to bother you guys. Apparently after I rebooted the box, it started working now on the tripplite-usb driver. One correct also. I didn't have it installed from ports but from binary pkg. (pkg install nut) I doubt this did anything but I did create nut.conf because it wasn't there before. I set it to standalone. Again, sorry to bother you guys. I'm retarded. Nick

Hi; I'm having some trouble to comunicate with my just bought (08/17/15) Ups. According to SOLIS(8): SUPPORTED HARDWARE This driver has been tested with : Solis 1000 VA Solis 1500 VA Solis 2000 VA Solis 3000 VA Back-UPS BZ1200-BR Back-UPS BZ2200BI-BR So solis is the one to go for. Here is my scenario: SW: nut-2.7.3 (compiled from ports) OS: FreeBSD

> On Oct 11, 2016, at 1:35 PM, Nick Teague <nick.teague at smartfox.us> wrote: > > ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (60mA) To determine the proper driver, would you please run the following usbconfig command as root? Here's an example from my UPS: # usbconfig -d ugen0.2 dump_device_desc ugen0.2:

On Dec 17, 2014, at 6:58 AM, ??????? ??????? <freemgm at gmail.com> wrote: > OS version: FreeBSD 8.4-RELEASE-p19 > NUT version: nut-2.7.2_6 > NUT installation method: from freebsd pkg system > Device info: EATON 9SX 5000i, manufacturing date: 05.09.2014 > ups.firmware: 9SX5Ki ... > there're lot of data in output, if it needed i can attach in file... Not sure why it