similar to: Some FreeBSD tips (was: OMNIVS1500XL and FreeBSD)

I'm running FreeBSD 6.2 with Nut 2.0.5 installed from ports... I have a TrippLite OmniVS1500XL plugged in, but I'm having little luck with the tripplite_usb module. I have already built and booted a new kernel with UHID disabled so that libusb can grab /dev/ugen0. At first I was able to get the following out of the driver: # USB_DEBUG=5 /usr/local/libexec/nut/tripplite_usb -u root

Howdy, I had this working with lots of help for a developer before (Charles Lepple), but after upgrading to a somewhat more current version of FreeBSD the patched-up version stopped working. Seeing as this was more than a few years ago, I thought I'd give a new libusb and NUT a try to see if it might work out of the box. So far, no luck. Some info: FreeBSD 6.3 libusb 0.1.12 NUT 2.4.1

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

Hello, I wanted to see if there's any chance that NUT will support a few new TrippLite UPSes that we just bought: Sep 9 01:42:25 miko /kernel: uhid0: TRIPP LITE TRIPP LITE OMNIVS1500XL, rev 1.1 I grabbed the devel sources via cvs, but am having trouble building it when I enable the "newhidups" driver: gmake[1]: Leaving directory `/usr/local/src/nut/common' drivers/

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

Hello again! Thanks to the precious help from Henning Brauer, I managed to solve an issue with my UPS (a rebranded UPS speaking in Ablerex-ese over USB). Under OpenBSD 4.3, the UPS was claimed by HID. Now that I recompiled the kernel, adding a USB_quirk, this is what I get when I insert the USB cable: ugen0 at uhub0 port 2 "UIS_ABLER USB to Serial" rev 1.00/1.00 addr 2 So far, so

Hello, We recently moved from courier to dovecot, and I'm seeing a handful of errors that prevent people from retrieving email. Below is a snippet of the log sequence I see when this happens: Oct 10 13:44:24 mbox dovecot: imap(xxx at bway.net): Error: Cached message size smaller than expected (1759 < 1830) Oct 10 13:44:24 mbox dovecot: imap(xxx at bway.net): Error: Maildir filename has

The purpose of this posting is to summarize the FreeBSD installation procedure from the beginning till the very end. 1. Follow the instructions provided in the How-To prepared by Thierry Thomas (http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt). Please note the following: a) if you are using an USB device, as of NUT 2.2 usbhid-ups completely replaces the legacy hidups driver and provides

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

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 =

Good afternoon, I'm trying without much success to monitor a Tripp Lite OMNIVS1500XL using NUT. I checked the compatibility list and saw that this UPS is supported by tripplite_usb. The system is running Debian Stable, but I've downloaded NUT 2.0.3 and compiled from source since the packaged 2.0.1 doesn't include tripplite_usb. I compiled --with-user=nut. My first attempt at

Hi all, I gave up on a Tripplite OMNIVS1500XL due to it failing to work on the version of Nut in FreeNAS (and having experienced numerous issues on Debian Jessie as well due to incomplete/unknown protocol elements causing USB problems and Debian Wheezy doesn't even recognize the device). Since the issue is likely lack of information (i.e. unknown protocol) I'm not sure my offer of device

[It seems the last time this came up was in march, under the heading of "Sony Cybershot should be in hardware notes". This message is intended mainly to document what I've managed to track down.] The m500s still will not sync with pilot-link 0.11.7 in -STABLE. An easily triggerable panic is another issue [1]. The pilot-link code first opens /dev/ugenX and then switches to

All, I recently purchased a Tripp-Lite OmniVS1500XL and am running NUT on a Centos-based system. Based on the compatibility list I specified the tripplite_usb driver. When I query the unit I get: [root@chryxus ~]# upsc UPS@localhost battery.voltage.nominal: 24 driver.name: tripplite_usb driver.version: 2.0.3-pre2 driver.version.internal: 0.6 input.voltage.nominal: 120

Arnaud: I just wanted to chime in here to say that getting these TrippLite USB UPS's supported under a NUT driver would be fantastic! They are simple, inexpensive UPS's (under $100 for 1000VA at Costco) and it would be quite the "deal of the year" to be able to buy these units so cheaply and monitor them directly via Linux. I already have 5 of these units and have

Hi, I'm working with svn trunk rev 815, testing tripplite_usb with this model. I haven't gotten far in my testing, but thought I'd notify the list of this error message. Is this message of any consequence, and is it worthwhile for me to continue testing prior to resolving this? I am happy to help debug any driver issues, so please let me know if I can be of assistance. My platform

I am running Debian Etch, with the nut 2.0.4 packages, and I get a segmentation fault from tripplite_usb. # /lib/nut/tripplite_usb -u root -DDDDD auto Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.4) Warning: This is an experimental driver. Some features may not function correctly. debug level is '5' Checking device (09AE/0001) (002/004) - VendorID: 09ae -

i just purchased a tripp lite OMNIVS1500XL and have been attempting to get it working with the usb drivers since it doesn't have a serial port. it hasn't been anywhere near successful and i was hoping someone might be able to point me in the right direction. i run gentoo and this is what i currenlty have installed: nut 2.0.2 libusb 0.1.10a (gentoo modified) usbutils 0.11-r5

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: > >>

Hallo, Following the tips found at https://calomel.org/nut_ups.html I was trying to make NUT operate "APC Back UPS CS-350". The device introduces itself as: #v+ ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I USB FW:q7" rev 1.10/0.06 addr 2 #v- My config: #v+ [apc] driver = usbhid-ups port = /dev/ugen0.00 pollfreq =