search for: vasvir

> You could also try adding "-x usb_set_altinterface" to the command line > (or adding it to ups.conf). The lsusb output implies that the only valid > setting is 0 (bAlternateSetting), but it might need to be set explicitly. I checked with -x usb_set_altinterface and it says nut_usb_set_altinterface: usb_set_altinterface() should not be necessary - please email the

...* mod_libc_wrapper - wrapping of functions missing in a specific libc + * or not working in a statically compiled binary + * + * Copyright (C) 2003 Greg Kroah-Hartman <greg@kroah.com> + * Copyright (C) 2005 Kay Sievers <kay@vrfy.org> + * Copyright (C) 2005 Vassilis Virvilis <vasvir@yahoo.gr> + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of the GNU General Public License as published by the + * Free Software Foundation version 2 of the License. + * + * This program is distributed in the hope that it will be useful, but...

On Sep 8, 2016, at 4:26 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) > doesn't. > From the lsusb descriptor output, the 1500 seems to implement the HID Power Device Class (PDC) spec - so it might be possible to adapt usbhid-ups to work wit...

On Sep 8, 2016, at 8:14 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > Hi again, > > Thanks for the prompt reply. > > Just for the record i am running debian unstable/sid with nut 2.7.4-3 > Thanks, that is useful. > 0.447725 refresh_report_buffer: expected 13 bytes, but got 8 instead This is the first...

On Sep 8, 2016, at 9:25 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > + failed to claim USB device: could not claim interface 0: Device or > resource busy > + detached kernel driver from USB device... > nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) > HID descriptor, method 1: (9 bytes) => 0...

On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > Now that's a problem. I am not sure that I can find > > 1) the original software > 2) a (physical) windows machine in the vicinity of the UPS > > I will give it a try but for now looks like a dead end. I have 3 of these > UPS. Two of them...

Hi again, > On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> > wrote: >> Now that's a problem. I am not sure that I can find >> >> 1) the original software >> 2) a (physical) windows machine in the vicinity of the UPS >> Ha! I jumped several hooks but I think I got it. 01. I contacted the store...

...b1.com/~lkcl"> Samba Consultancy and Support </a> ---------- Forwarded message ---------- Date: 31 Dec 1997 11:53:00 GMT From: Mark Evans <mark@leasion.demon.co.uk> Newsgroups: comp.protocols.smb Subject: Re: User profiles (was Re: "domain groups") Vassilis Virvilis (vasvir@iit.nrcps.ariadne-t.gr) wrote: : Bruce Cook wrote: : > : > --snip! : > : > What you want is server based user profiles. : > Weel why didn't you say so :) : > : > This is an extract from a news item that occured a while ago. : > : > --snip! : > : : I have setu...

[snip hex dump analysis] > > It is possible that the blazer_usb driver initialization has put the UPS > into a bad state. If you can schedule some downtime, you might want to try > usbhid-ups again after powering the UPS down completely and unplugging it > for a little while. (Often, a few seconds after the output is off and the > AC has been removed, you will hear relays

Hi again, Thanks for the prompt reply. Just for the record i am running debian unstable/sid with nut 2.7.4-3 # dpkg -l 'nut*' | grep ^ii ii nut 2.7.4-3 all network UPS tools - metapackage ii nut-client 2.7.4-3 amd64 network UPS tools - clients ii nut-server 2.7.4-3 amd64 network UPS tools - core

Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output

Hi again Looks like the ups always replies 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 The software sends 1) The first time 80 06 0303 4095 0064 100 < 2) The second time with 80 06 030c 4095 0064 100 < 3) The third time with 80 06 030d 4095 0064 100 < 4) repeats step 1) 8 times 5) go to step 2) Regards Vassilis Virvilis

Halo, I think the following patch is correct. I just downloaded 1.0.9 and has the same problem namely it doesn't respect INSTALLROOT when installs the shared library -------------- next part -------------- diff -ur orig/klibc-1.0.8/klcc.in klibc-1.0.8/klcc.in --- orig/klibc-1.0.8/klcc.in 2005-03-07 23:44:49.000000000 +0200 diff -ur orig/klibc-1.0.8/klibc/Makefile klibc-1.0.8/klibc/Makefile

Halo, fnmatch() and getopt_long are necessary to compile module-init-tools with klibc out of the box. Would you consider accepting patches to implement those 2 functions? Can we use the bsd libc functions? is the lisence acceptable to you? .bill

This is tiny and has no impact in klib size other that it is polluting the namespace. .bill -------------- next part -------------- A non-text attachment was scrubbed... Name: patch-index-strchr.txt Type: text/x-diff Size: 355 bytes Desc: not available Url : http://www.vas.nu/pipermail/klibc/attachments/20050530/b7c96936/patch-index-strchr.bin

Halo, I was wondering to no avail how to to use the klcc wrapper in order to build udev and module-init-tools. Does klibc has an install target when is embedded in the kernel tree? Is klcc available? .bill

A little deciphering > Looks like the ups always replies > 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 That is length = 0x16 = 22 type = 0x3 = string Message = "UPS No Ack" Very fun... Regards Vassilis Virvilis

> that string shows up here, among other places: > > https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.c#L764 > > but if the upsilon screen isn't showing many values, I'm not sure if that > version is going to help. Are there any other settings to select a > different model or protocol? Here is the output of #/etc/upsilon/upsilon config hope