similar to: TrippLite OMNI1000LCD hiddev

Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker:

Greetings all, Anyone done any work on these products? I have several (a couple of different models) that are rebranded Ultra in the US. Using explore with usbhid returns some significant quantities of data and I've done some captures with usbsnoop. I've also asked Ultra to get me the HID definition that was used for them, in the hopes I don't have to usbsniff all the setting

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

Hello everyone, Charles suggested (about a week ago) that I repost to this list. I took a moment to run some additional tests ... The basics: -- UPS: Liebert PowerSure PSA 500 (from the 230 VAC / 50 Hz line) -- Kernel: 2.6.11.5 (from sources), USB support (down to and including CONFIG_USB_HIDDEV) compiled in statically (not as a module) -- Rest of OS: Basically still from the original SuSE

Hi! I've (finally) decided to try and make my PowerWalker work with megatec_usb. So far it seems the agiler subdriver is the way to go, but it doesn't work. The initial detection process sometimes succeeds in 1 out of 5 "Q1" commands, but that's about it (which is better than what the krauler subdriver can do... absolutely nothing). So, what needs to be done to obtain more

tags 354429 + upstream thank 2006/2/26, suicune@eml.cc <suicune@eml.cc>: > Package: nut > Version: 2.0.1-3 > > > This is the spam message: > drivers/usb/input/hid-core.c: ctrl urb status -32 received > > I never once saw this message until after I installed and configured > nut. > > Spam begins during boot and continues infinitely until reboot or nut is >

Package: logcheck-database Version: 1.2.32 Severity: wishlist Ignore rules to supress messages generated from pugging in, and then removing, a USB headset (one speaker). ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: drivers\/usb\/class\/audio\.c: v1.0.0:USB Audio Class driver$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: usbaudio: assuming that a stereo channel connected directly to a mixer is

> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only >write a PID file when the driver goes into the background, and "-D" prevents that. I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... /var/run/devd.pid

Hi, I have been trying to figure out why the S100U is not performing very well on RH9.. Here is my thinking..( may be totally wide of the mark but here goes anyway) I remember reading somwhere that the sound system used by RH has changed... Does the S100U not depend on the sound subsystem?? So what I think is that the sound subsystem in RH9 and the S100U are not happy working together.. Does

Hello, I have a UPS unit with a USB Interface that appears to work with the blazer_usb and nutdrv_qx drivers. I have tried all combinations of subdriver and protocol and the result is always the same. The values returned are all zero's. The issue seems to be the same as https://github.com/networkupstools/nut/issues/307 Attempts to send a command to silence the beeper or trigger a battery

Hello, Sorry if any of this is obvious - I'm new to NUT. NUT via upsc is displaying (edited for length): device.model: Eaton 5P 2200 device.type: ups driver.name: usbhid-ups ups.alarm: Fatal EEPROM fault! ups.status: ALARM OL CHRG ups.test.interval: 604800 ups.test.result: Done and passed driver.version: 2.7.2 driver.version.data: MGE HID 1.33 driver.version.internal: 0.38 Is this possibly

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 All, I've finally found solutions for my previous problems. But since this includes changes in the shared files, I'd like to discuss them here. 1. Driver restart problem. When I start the driver for the first time, everything is ok. But when I want to restart it, problems begin. The driver fails to read Report descriptor for the second time (libusb_open is used to open the device).

Hi, I've been trying (unsuccessfully) to interact with the above UPS using its USB/HID interface and have come to the conclusion that it's not going to be as "easy" as I'd first thought :( My attempts have all been on FreeBSD-5 (kernel as of today) using NUT v2.0.2 and fiddling with newhidups -- I tried the simple approach of adding the IDs and "seeing what

Hello everybody, After succeeded in "tuning" nut-2.0.0's hidups and 2.0.3's newhidups on customized Linux kernels, we are now facing a new challenge : trying to install nut-2.0.5 on a RedHat ES4 which is based on a 2.6.9 kernel. I picked up the 2.0.5 source package and follow the INSTALL doc until step 6. So far so good. RH ES4 is managed by udev, therefore I presume we

Hi all: I am trying to get a TrippLito OMNI1000LCD working with nut. Even with the development branch, I get the following.... upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: HID UPS driver 0.13 (2.1.0) Warning: This is an experimental driver. Some features may not function correctly. Detected Tripp Lite TRIPP LITE UPS on port /dev/usb/hiddev0

-> ups at p34 POWER ALERT on Sat Aug 25 07:40:01 EDT 2007 -> UPS belkin at localhost battery is low The last good version is 2.0.4, someone e-mailed me from this list before exactly why this happened it was about ignoring bad events from the usb-dev subsystem/kernel but I guess my question is this going to get fixed or should I stick with 2.0.4 as long as I can? Thanks. # ./usbhid-ups

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

> I have a UPS unit with a USB Interface that appears to work with the blazer_usb and nutdrv_qx drivers. I have tried all combinations of subdriver and protocol and the result is always the same. The values returned are all zero's. > > The issue seems to be the same as https://github.com/networkupstools/nut/issues/307 > > Attempts to send a command to silence the beeper or