similar to: Tripp-Lite OMNI650LCD

I have a Tripp Lite OMNI900LCD. It has a usb connector and claims to be USB/HID. I haven't been able to get it to work with newusbhid or tripplite_usb. Here's lsusb -v output: Bus 001 Device 013: ID 09ae:2005 Tripp Lite Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level)

This is a USB only ups. I could not make it work with nut. So I put this daemon together. Get it from http://www.vsys.org/sventura/dev/ at the bottom of the page. Init scripts are gentoo based but I think it should be easy to adjust them to any distro. I am planning to integrate it with nut if I can find the time and there is enough interest on it to justify the project. This is a very entry

I wrote a while back about the inability to kill the following command with anything but "kill -9" and the apparent high speed polling rate. # /lib/nut/usbhid-ups -u root -DDD -a trippy The setup I have worked on a previous version of nut, but I have forgotten at what point it stopped working. (I believe it was around Nov, 2007 that I noticed things were not working correctly.) I

Hi Patrick, in February, you tried to post the below message to the nut-upsuser list, but the post was rejected because you were not subscribed to the list. Unfortunately, you did not subscribe and re-post it. Anyway, I have been working on Tripp-Lite support for newhidups recently, and I wonder if you have any feedback. Did you ever get this device to work? >From the information you sent,

James, thanks, this is useful info. Comments below. -- Peter James Pooton wrote: > > > I saw on the list that you were looking for some details. Sorry I'm not > part of the list, but here are my results: > > > [root@blackhole bin]# ./newhidups -DDD -u root ups@127.0.0.1 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) > > debug

Hi Patrick, Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on vacation, so I finally got a chance to take a > look at this. > > Peter Selinger wrote: > ... > > In case you feel like experimenting with this, I am attaching a patch > > that *might* enable this device to be supported by the

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

Hello all, About a month ago Peter and Charles were kind enough to try to help me with getting a Tripp Lite USB UPS to work with NUT. I reported quite a bit of initial success, and then other things here fell apart. Between work, fence building and a week-long out of town business trip, I have had to drop this from my list of things to do lately. I am back at it, and I believe I will have

Hi James, thanks for the feedback. The output you get seems generally fine, except for battery.voltage: 0.0 and output.voltage: 164.0; these values are consistent with what Phil DeBoest reported. Upsmon normally executes the shutdown command when you reach the "low battery" threshold, as decided by the UPS and/or driver. It does so by looking at ups.status, not battery.charge. --

Greetings, Any suggestions? I think I'm close but I can't quite get tripplite_usb to talk to my OMNI1000LCD. I'm new to NUT and couldn't find an answer using Google. With any luck, I've simply missed the obvious. The system I'm using, kaylee, is a debian stable system with some debian testing installed and a 2.6.15.4 kernel. I downloaded NUT 2.0.3 and built it from

I'm happy to have had a quick look at this thread... 2007/5/17, Peter Selinger <selinger at mathstat.dal.ca>: > ... > as you know, I haven't had much time to work on NUT. Now my wife is > expecting our first baby in 1 week, so I don't think I will get back > to it in the foreseeable future. I didn't knew before! what a good news: all my congratulations to you

I've having trouble understanding the NUT compatibility page. Is it compatible with the OMNISMART300? Or the OMNI900LCD? The compatibility page said for instance SMART550 -- tripplite_usb SmartUPS -- tripplite OMNI650LCD -- usbhid_ups so I'm not sure if an OMNISMART300 is like a Smart, or a SMART, or an OMNI, or even if it's supported at all. Thanks in advance for any help!

Dear all, since it could be of interest for the list, here I post a link to compiled kernel for XEN 3.1 on a DELL PowerEdge 1950 compiled with gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) on a Debian4 distribution. This is provided AS IS AND WITHOUT ANY SUPPORT AND/OR ANY RESPONSIBILITY :-) The first link (7 MB) pack all the files you should have in /boot. The second link (12 MB)

Does the following error message have a specific meaning: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -75 I get two of these messages every time I run the following: /lib/nut/usbhid-ups -u root -DDD -a trippy The following is the output from the above command: debug level is '3' Checking device (0000/0000) (004/001) - VendorID: 0000 - ProductID:

Hi Patrick, I didn't get further bug reports from you, so I have now listed your device as "supported" by newhidups. Last I saw as of your below message, the driver was working as expected. If there are any future problems, let me know! -- Peter Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on

Dear George, Thanks for the input and ideas. Unfortunately bootscrub=false dos not work, not does setting nothing for vga, still get the 'Little white squares'! I am asking the xen-users as you suggest Regards, Francis From: "George Dunlap" <dunlapg at umich.edu> To: "Francis Greaves" <francis at choughs.net>, "centos-virt" <centos-virt

Yes I usually work headless, but I have been setting it up from new, so need to see what is going on. Regards Francis From: "Scot P. Floess" <sfloess at nc.rr.com> To: "Francis Greaves" <francis at choughs.net> Cc: "centos-virt" <centos-virt at centos.org> Sent: Monday, 22 February, 2016 17:02:12 Subject: Re: [CentOS-virt] Garbled screen

Thanks Kjell for the help with the build problem. Thanks for your input, too, Charles. Now I have a new problem that I think has already been solved. I have Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver to communicate correctly. I found a thread on the development list from last December where Jonathan Freedman described had a problem with this UPS in a thread

Dear All I am using Centos 7 with Xen 4.6 on a Dell Poweredge T430 When the machine boots, after the 'Scrubbing Free RAM' message, I get a screen filled with little white squares until the login prompt, so I cannot see what is happening as the machine boots. Also there is nothing on the screen when I reboot. My /etc/default/grub is GRUB_DISTRIBUTOR="$(sed 's, release

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does