Hi Charles, I´ve try get_descriptor. Here are the results:
# lsusb -v Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 005: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The first run as root # ./get_descriptor 003 005 1 0 0 128 0x22 0 Warning: could not set config 1: Device or resource busy Warning: could not set alt intf 0/0: Connection timed out Can't get endpoint 128 descriptor 0x22 index 0: error sending control message: Protocol error The second run as root # ./get_descriptor 003 005 1 0 0 128 0x22 0 Warning: could not set config 1: Protocol error Warning: could not set alt intf 0/0: Protocol error Can't get endpoint 128 descriptor 0x22 index 0: error sending control message: Protocol error I could try again anything! Juan Pablo 2011/6/11 Charles Lepple <[email protected]> > On Wed, Jun 8, 2011 at 9:00 AM, Charles Lepple <[email protected]> wrote: > > On Wed, Jun 8, 2011 at 8:39 AM, Arnaud Quette <[email protected]> > wrote: > >> > >> 2011/6/8 Don Gould <[email protected]> > >>> > >>> On 8/06/2011 11:04 p.m., Charles Lepple wrote: > >>>> > >>>> On Jun 8, 2011, at 6:29 AM, Don Gould wrote: > >>>> > >>>>> it was suggested to me that nut might support my new ups. > >>>>> > >>>>> I have a headless debian box that it will be powering. > >>>>> > >>>>> Can someone tell me what packages I need to install? > >>>> > >>>> The base package for NUT in Debian is just called "nut" (currently at > >>>> version 2.4.3): > >>>> > >>>> http://packages.debian.org/squeeze/nut > >>>> > >>>> However, I don't think any of the NUT developers currently own a GXT3, > >>> > >>> Well I have one and I'm more than willing to provide system access to > the > >>> devs if they want to help figure this out. > >>> > >>> I've been though a number of weeks bouncing messages at the manufacture > of > >>> the UPS to end up with a less than satisfactory answer and I'd just > love to > >>> see this puppy with some functional FLOSS driving it. > > > > Don, > > > > There's a simple program that Peter Selinger wrote a few years ago to > > grab some of the information from the UPS's USB interface - I'll dig > > that up and we can try to figure out what's going on. As a minimum, > > you'll need the Debian build-essentials package, as well as > > libusb-dev. > > Here's the program: > > > http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-November/001292.html > > You should be able to build it with the following command: > > $ gcc -o get_descriptor get_descriptor.c -lusb > > (after installing the packages listed above) > > Assuming that 'lsusb -v' (run as root) returns the same information as > Juan Pablo Valles posted on 5/30/2011, I think you'll need to run it > as follows: > > # ./get_descriptor <bus> <device> 1 0 0 128 0x22 0 > > <bus> and <device> are from the line of lsusb output which matches your > UPS. > > Juan, if you would like to try the same program, that would also be > useful to compare results. > > -- > - Charles Lepple >
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
