search for: hiddev

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

...h 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 Unhandled event: 0x8400d0 (1) Unhandled event: 0x840044 (1) Unhandled event: 0x840045 (0) Unhandled event: 0x84004b (0) upsc myups@localhost battery.charge: 28 battery.chemistry: Unknown driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.1.0 ups.delay.shutdown: 0 ups.mf...

...= "bla bla ..." > > Yesterday it took me about 10 minutes to configure an APC Smart UPS 1500 > on another Sarge box (using apcupsd), but the combination of nut, USB > and this Powerware 5115 UPS seems to be really tricky. Is it obligatory > to use something like /dev/usb/hiddev0 in the port statement in ups.conf? > (The apcupsd on the other machine is configured with a simple "usb" > statement and automagically finds the correct UPS. Does something like > this exist for nut?) What kind of "port" statement is needed in ups.conf? > I don'...

[moved to nut-upsdev while we figure out the protocol] > On Mar 9, 2017, at 11:22 AM, Drew from Zhrodague <drewzhrodague at zhrodague.net> wrote: > > I'm able to cat /dev/usb/hiddev0 and /dev/hidraw0 - I pipe this through hexdump and I get different types of data from each: > > > hiddev: > > 0002420 00a7 ffa0 00ff 0000 00a7 ffa0 00ff 0000 > 0002430 00a7 ffa0 00a3 0000 00a7 ffa0 0001 0000 > 0002440 00a6 ffa0 0080 0000 00a7 ffa0 0011 0000 > 0002450 00a...

...trunk/configure.in > Log: > Undoing changeset [608]. It fails with this error: > > configure: error: conditional "HAVE_LIBUSB" was never defined. > Usually this means the macro was only invoked conditionally. > > if --with-usb is not passed. Not sure why; the HIDDEV macro is defined > conditionally, and I definitely don't have hiddev on OS X. I will revisit this > when I am more awake. This just means that the following two lines: AM_CONDITIONAL(HAVE_LIBUSB, test "${nut_have_libusb}" = "yes") AM_CONDITIONAL(HAVE_HIDDEV, test -n...

...need any help here. > no, but some details for those who will read it, maybe ;-) I have SUSE 10.0 and an MGE Ellipse. I installed the NUT package from MGE. > > 1) The generated ups.conf pointed to a bad location: > /dev//dev/input/event0 > who generated that ? it seems like an old hiddev / hidups detection that failed 2) The hidups driver will not work with SUSE 10 out of the box. To make it > work (which was academic because I prefer newhidups), I had to: > a) Customize the kernel to exclude CONFIG_USB_HIDINPUT > b) Add a udev rule: KERNEL=="hiddev*", NAME=...

...nufacturer=MGE UPS SYSTEMS S: Product=Evolution S: SerialNumber=AF3G03062 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 40mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=20ms So the kernel correctly identifies the device as a HID class, but the hiddev dev refuses to "claim" the device. What's happening here? How can I fix this? Cheers, Rodrigo Ventura -- *** Rodrigo Martins de Matos Ventura <yoda@isr.ist.utl.pt> *** Web page: http://www.isr.ist.utl.pt/~yoda *** Teaching Assistant and PhD Student at ISR: *** Instit...

...nd this is what i currenlty have installed: nut 2.0.2 libusb 0.1.10a (gentoo modified) usbutils 0.11-r5 (gentoo modified) kernel 2.6.12.3-r7 (gentoo modified) and i built nut with these configure options: ./configure --with-user=nut --prefix=/usr/local/nut-2.0.2 --with-linux-hiddev=/usr/src/linux/include/linux/hiddev.h lsmod shows that i do have the usbhid in (i have to double check this all the time <g>): Module Size Used by usbhid 32992 0 usblp 12032 0 ehci_hcd 38344 0 ohci_hcd...

Hello, I've already written to the list before about my non-standard hid Unitek UPS. I've tried to use hiddev to access my UPS as its USB HID interface is the same as the energizerups. Nevertheless, the protocols are different and I didn't manage to communicate with my UPS through hiddev. Moreover, the problem described in this page http://www.vttoth.com/ER-OF800.htm about the Linux kernel not register...

...tel.com> Reviewed-by: Jason Gunthorpe <jgg at mellanox.com> Signed-off-by: Arnd Bergmann <arnd at arndb.de> --- drivers/char/ppdev.c | 12 +--------- drivers/char/tpm/tpm_vtpm_proxy.c | 12 +--------- drivers/firewire/core-cdev.c | 12 +--------- drivers/hid/usbhid/hiddev.c | 11 +-------- drivers/hwtracing/stm/core.c | 12 +--------- drivers/misc/mei/main.c | 22 +---------------- drivers/mtd/ubi/cdev.c | 36 +++------------------------- drivers/net/tap.c | 12 +--------- drivers/staging/pi433/pi433_if.c | 12 +------...

...tel.com> Reviewed-by: Jason Gunthorpe <jgg at mellanox.com> Signed-off-by: Arnd Bergmann <arnd at arndb.de> --- drivers/char/ppdev.c | 12 +--------- drivers/char/tpm/tpm_vtpm_proxy.c | 12 +--------- drivers/firewire/core-cdev.c | 12 +--------- drivers/hid/usbhid/hiddev.c | 11 +-------- drivers/hwtracing/stm/core.c | 12 +--------- drivers/misc/mei/main.c | 22 +---------------- drivers/mtd/ubi/cdev.c | 36 +++------------------------- drivers/net/tap.c | 12 +--------- drivers/staging/pi433/pi433_if.c | 12 +------...

I am having problems building usb on mac os x. First, mac os x doesn't seem to have asm/types.h, just sys/types.h. I can't find hiddev.h on mac os x either. Also, it doesn't have usb.h but instead IOKIT/usb/USB.h. I am using mac os x (10.4), and the latest cvs of nut. Is the new usb support going to work on mac os x? Is anyone working on it? It seems that libusb is available on mac os x via Fink, although Fink is not in...

Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-ssl \ --with-dev \ --enable-static \ --with-statepath=/...

...that still use it will be warned why it doesn't work anymore by the time we release nut-2.4? Looking at the comments in the driver about the problems with 2.6.x kernels I wouldn't be too heartbroken if we would drop it from the stable tree by the way. Being the only driver that uses hiddev and the aforementioned comment (and how this problem was 'fixed' in the driver) lead me to believe that this won't be a great loss to NUT. Best regards, Arjen -- Please keep list traffic on the list

Hi, is there a way to use my Belkin F6H650 on the USB port? I already installed usbhid-support, but neither the hidups worked (reports "/dev/usb/hiddev0 is not a UPS") nor genericups with upstype=7 and the hiddev set as device ("ioctl TIOCMSET: Invalid argument") worked. I have installed the debian sarge package of nut 2.0.1 (2.0.1-4) Regards, Philipp

...;s for an RBC 43, which takes 8, and weighs a ton), and put it in, and let it charge. Idiot "change battery" led stays on. So I hit the test button, it discharges very rapidly (a good number of servers on this), and the led stays on. For some reason, apcupsd's USB test fails, with an HIDDEV i/o error. So I got rid of the weird APC usb cable, and put in one of their serial cables, and run the "smart" test (the USB does more), and get results showing everything's fine. But the idiot light's still on. So, looking at all the values that the "apcsmart" choice...

...r, > &apc_subdriver, > &belkin_subdriver, Ah, sorry, I had forgotten these. Good catch. > That made this work with ... > > user=root > [myups] > driver=newhidups > vendorid=09AE > #tripplite=1 > port=/dev/usb/hiddev0 > > And returned.... > > /usr/local/ups/bin/upsc myups@localhost > driver.name: newhidups > driver.parameter.port: /dev/usb/hiddev0 > driver.parameter.vendorid: 09AE > driver.version: 2.1.0 > UPS.BatterySystem.Battery.PresentStatus.Charging: 1 > UPS.BatterySystem.Ba...

...GNU/Linux When i try to start the driver an i use hidups i get this failure massage: aigner:/lib/nut# upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: HID UPS driver 0.13 (2.0.4) Warning: This is an experimental driver. Some features may not function correctly. hiddev path open auto: No such file or directory Driver failed to start (exit status=1) When i use the newhidups driver, he tells me this: aigner:/lib/nut# upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No matching USB/HID UPS foun...

...cation driver 0.31 Using subdriver: TrippLite HID 0.4 libusb_get_report: could not claim interface 0: Device or resource busy Got disconnected by another driver: Device or resource busy Can't initialize data from HID UPS Driver failed to start (exit status=1) I did an 'fuser -m -v /dev/usb/hiddev0' just prior, and the file was unused by any other process, so the error report is a little odd. (Another oddity is that the file _was_ earlier claimed by encfs, when I had an encrypted file system mounted, where no USB was involved at all. Don't understand that. I unmounted that before r...

...red as connecting in /var/log/messages eg usb 3-1: USB disconnect, address 3 usb 3-2: new low speed USB device using uhci_hcd and address 4 But I don't know how to progress from here. I have used the following commands: mkdir /dev/usb mkdir /dev/usb/hid mknod /dev/usb/hid/hiddev0 c 180 96 mknod /dev/usb/hid/hiddev1 c 180 97 mknod /dev/usb/hid/hiddev2 c 180 98 mknod /dev/usb/hid/hiddev3 c 180 99 However, I'm not sure how to check that there is a link between hiddev0 and the USB device that's registering above. - In a fit of woeful optimism I have configured ups.co...