Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Alright, I'm geting some where! Found out that the mac terminal does some weird things with tabs and you cannot tab in it. I switched to linux and all is well. This is what I receive when I try to start the driver with tripplite_usb: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. Error: UPS [Tripp-Lite] is for driver usbhid-ups, but I'm tripplite_usb! This is what I receive when I try to start the usbhid-ups driver: Checking device (09AE/0001) (001/002) - VendorID: 09ae - ProductID: 0001 - Manufacturer: TRIPP LITE - Product: TRIPP LITE UPS - Serial Number: unknown - Bus: 001 Trying to match device This Tripp Lite device (09ae/0001) is not supported by usbhid-ups. Please use the tripplite_usb driver instead. This is what I receive when I am trying to start upsdrvctl with tripplite_usb Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. No matching USB/HID UPS found Driver failed to start (exit status=1 And this is what I receive when I try to start upsdrvctl with usbhid-ups: Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 This Tripp Lite device (09ae/0001) is not supported by usbhid-ups. Please use the tripplite_usb driver instead. No matching HID UPS found Driver failed to start (exit status=1) Thanks for all the help guys. Now maybe I can help. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Citeren Chris Abel ca...@wildwood.edu: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. Error: UPS [Tripp-Lite] is for driver usbhid-ups, but I'm tripplite_usb! You failed to update the 'ups.conf' file. You *must* set driver = tripplite_usb in order for this to work. This is needed for starting multiple drivers by upsdrvctl later on. This is what I receive when I try to start the usbhid-ups driver: Checking device (09AE/0001) (001/002) - VendorID: 09ae - ProductID: 0001 - Manufacturer: TRIPP LITE - Product: TRIPP LITE UPS - Serial Number: unknown - Bus: 001 Trying to match device This Tripp Lite device (09ae/0001) is not supported by usbhid-ups. Please use the tripplite_usb driver instead. We told you a couple of times already, this device is not supported by usbhid-ups (and never will either). Don't waste our time by repeatedly posting attempts to use this driver. Do as I told you before and run this driver with /path/to/tripplite_usb -D -u root -a upsname Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Citeren Chris Abel ca...@wildwood.edu: When using the tripplite_usb driver I get the same thing: Checking device (09AE/0001) (001/002) - VendorID: 09ae - ProductID: 0001 - Manufacturer: TRIPP LITE - Product: TRIPP LITE UPS - Serial Number: unknown - Bus: 001 Trying to match device Device does not match - skipping This is weird, it should be supported. So it appears that this ups is not supported, correct? Please post your 'ups.conf' file. It should be supported. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
interesting, I was thinking that tripplite_usb was for older units, not HID compliant. the newer runs usbhid-ups, but I'm now wondering if these are HID compliant. but looking at the lsusb output, the report size seems too short for this. anyway, just thinking out loudly. I tried usbhid-ups as well and it told me to use the tripplite_usb drivers. That was my experience, as well, when installing one of these UPS units on a Debian Lenny system 9 months ago. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
2009/9/8 Chris Abel ca...@wildwood.edu Arnaud Quette aquette@gmail.com writes: ok, now you can recompile 2.4.1 with the flags mentioned before, and do only a make (not install) then fire drivers/tripplite_usb -D -a upsname defined in /etc/nut/ups.conf # drivers/tripplite_usb -D -a Tripp-Lite bash: drivers/tripplite_usb: No such file or directory # tripplite_usb -D -a Tripp-Lite bash: tripplite_usb: command not found seems you don't have libusb-dev installed on your system (needed to compile the USB drivers). you can see it in the configure report, ie: ... build USB drivers: yes ... so sudo apt-get install libusb-dev and send us back the output. last question: have you bought this unit recently? Yes It was bought just a couple of weeks ago. interesting, I was thinking that tripplite_usb was for older units, not HID compliant. the newer runs usbhid-ups, but I'm now wondering if these are HID compliant. but looking at the lsusb output, the report size seems too short for this. anyway, just thinking out loudly. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arnaud Quette aquette@gmail.com writes: are you sure that you have re executed configure, and that you have the above build USB drivers: yes message? don't forget to call make too. I see no reason for not having tripplite_usb if the above are met. please, fix that point first. I suspect it is because of my limited knowledge of compiling from source. Basically I have the source directory in my home directory. I login as root and run this: ./configure --with-user=ups --with-group=nut --prefix=/usr --exec-prefix=/ --sysconfdir=/etc/nut --mandir=/usr/share/man --libdir=/lib --includedir=/usr/include --without-ssl --with-hal --with-cgi --with-dev --enable-static --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut --datadir==/usr/share/nut --with-pkgconfig-dir=/usr/lib/pkgconfig That seems to configure correctly, but when I run make I do get a lot of errors; all from snmp-ups.c. Not sure if that is normal or not. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Citeren Chris Abel ca...@wildwood.edu: Although I do have that tag in my ./configure, I do not have the directory /lib/nut after running make install. I have a lot of errors after running make and make install. All related to snmp-ups.c In that case, try if adding --without-snmp to the configure command line helps. It shouldn't (since the prerequisites for building the snmp-ups driver should be checked automatically), but chances are this is failing for you. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arjen de Korte nut+us...@de-korte.org writes: In that case, try if adding --without-snmp to the configure command line helps. It shouldn't (since the prerequisites for building the snmp-ups driver should be checked automatically), but chances are this is failing for you. I think I'm getting some where. I installed smnp-dev and the make and make install went through with no errors, but I cannot find the directory it put nut. The only thing I can find is the directory: /lib/nut --with-cgipath=/usr/lib/cgi-bin/nut There is no /lib/nut directory. Maybe the ./configure is wrong? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arjen de Korte nut+us...@de-korte.org writes: If you followed the instructions Arnaud send before, you told the configuration script --with-drvpath=/lib/nut So when you ran 'make install' the drivers were probably installed there, so you may need to try /lib/nut/tripplite_usb -D -u root -a Tripp-Lite Although I do have that tag in my ./configure, I do not have the directory /lib/nut after running make install. I have a lot of errors after running make and make install. All related to snmp-ups.c ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
I did manage to get tripplite_usb and upsdrvctl working with different tags in ./configure, but I still do not think it is correct. This is my output for tripplite_usb -D -a ups1: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. send_to_all: SETINFO driver.parameter.port auto debug level is '5' Can't chdir to /var/run/nut --with-altpidpath=/var/run/nut: No such file or directory This is my output for upsdrvctl start: Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1) Warning: This is an experimental driver. Some features may not function correctly. Can't chdir to /var/run/nut --with-altpidpath=/var/run/nut: No such file or directory Driver failed to start (exit status=1) It seems that whenever I specify a different directory in a ./confgure tag it does not get applied right. Thanks for helping thus far. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
When I simply copy and replace the following I get this at the end of ./configure: checking user to run as... ups--with-group=nut--sysconfdir=/etc/nut/--mandir=/usr/share/man--libdir=/lib/cludedir=/usr/include/--without-ssl--without-hal--with-cgi--with-dev--enable-static--with-statepath=/var/run/nut/--with-altpidpath=/var/run/nut checking group membership of user to run as... nobody configure: error: If you specify --with-user, you also must specify --with-group The output in ssh when I paste your directions looks like this: ./configure --with-user=ups\ --with-group=nut\ --sysconfdir=/etc/nut/\ --mandir=/usr/share/man man/man-db/ --mandir=/usr/share/man\ --libdir=/lib/ Display all 161 possibilities? (y or n) --libdir=/lib/cludedir=/usr/include/\ --without-ssl\ --without-hal\ --with-cgi\ --with-dev\ --enable-static\ --with-statepath=/var/run/nut/\ --with-altpidpath=/var/run/nut Am I the only one that has trouble compiling this with Ubuntu? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Citeren Chris Abel ca...@wildwood.edu: Am I the only one that has trouble compiling this with Ubuntu? You clearly have a problem with control characters that are being added somehow. Maybe it's the mail reader your using or some obscure character set, I don't know. The attached shell script might work for you. If it doesn't, just type in the contents (replace whitespace by TAB character). Best regards, Arjen -- Please keep list traffic on the list conf.sh Description: application/shellscript ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Citeren Chris Abel ca...@wildwood.edu: I have attached my config.log. You have some strange characters in the ./configure line. Please try again with the following: ./configure --with-user=ups \ --with-group=nut\ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-ssl \ --without-hal \ --with-cgi \ --with-dev \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut Make sure that when you copy the above, you don't accidentally add control characters. You should be able to copy-and-paste the above. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Yes, This is my config summary: enable SSL development code: yes enable libwrap (tcp-wrappers) support: no enable IPv6 support: yes build CGI programs: no build and install the development files: no build serial drivers: yes build SNMP drivers: yes build USB drivers: yes enable HAL support: no build neon based XML driver: no build Powerman PDU client driver: no Is there another way to update to 2.4 other than building from source? I can't seem to get this to work and it is probably because I am relatively new to linux. After configuring it with those tags I still do not have upsdrvctl. When doing this upsdrvctl start I get this bash: /sbin/upsdrvctl: No such file or directory. There is now nothing in /usr/local/ups/bin or /usr/local/ups/sbin. Arnaud Quette aquette@gmail.com writes: have you done the make uninstall, then used the configure directives above, then make ; make install? ___ Chris Abel Systems and Network Administrator Wildwood Programs 2995 Curry Road Extension Schenectady, NY 12303 518-836-2341 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
2009/9/4 Chris Abel ca...@wildwood.edu Yes, This is my config summary: enable SSL development code: yes enable libwrap (tcp-wrappers) support: no enable IPv6 support: yes build CGI programs: no build and install the development files: no build serial drivers: yes build SNMP drivers: yes build USB drivers: yes enable HAL support: no build neon based XML driver: no build Powerman PDU client driver: no Is there another way to update to 2.4 other than building from source? I can't seem to get this to work and it is probably because I am relatively new to linux. ok, before going to deep on this and wasting too much time on compilation, I'd like to have: - the output of lsusb -vv -d09ae:0001. - your USB topology (ie is the UPS plugged on a root hub, are there other devices on the same bus, ...) - the result of ls -l /dev/bus/usb/XXX/YYY where XXX is the Bus number and YYY the Device number as shown by lsubs) once this part is ok, we'll check again to test 2.4.1 from the source tree. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
Arnaud Quette aquette@gmail.com writes: ok, before going to deep on this and wasting too much time on compilation, I'd like to have: - the output of lsusb -vv -d09ae:0001. Bus 001 Device 002: ID 09ae:0001 Tripp Lite Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x0001 bcdDevice0.01 iManufacturer 1 TRIPP LITE iProduct2 TRIPP LITE UPS iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 60mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 52 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x (Bus Powered) - your USB topology (ie is the UPS plugged on a root hub, are there other devices on the same bus, ...) Bus 002 Device 001: ID : Bus 001 Device 005: ID 05ac:0302 Apple Computer, Inc. Apple Optical Mouse [Fujitsu] Bus 001 Device 004: ID 05ac:0204 Apple Computer, Inc. Bus 001 Device 003: ID 05ac:1002 Apple Computer, Inc. Apple Extended Keyboard Hub [Mitsumi] Bus 001 Device 002: ID 09ae:0001 Tripp Lite Bus 001 Device 001: ID : Yes there are other devices on the same bus. - the result of ls -l /dev/bus/usb/XXX/YYY where XXX is the Bus number and YYY the Device number as shown by lsubs) crw-rw-r-- 1 root nut 189, 1 2009-09-04 12:50 /dev/bus/usb/001/002 once this part is ok, we'll check again to test 2.4.1 from the source tree. Hope that helps. ___ Chris Abel Systems and Network Administrator Wildwood Programs 2995 Curry Road Extension Schenectady, NY 12303 518-836-2341 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
2009/9/4 Chris Abel ca...@wildwood.edu Arnaud Quette aquette@gmail.com writes: ok, before going to deep on this and wasting too much time on compilation, I'd like to have: - the output of lsusb -vv -d09ae:0001. Bus 001 Device 002: ID 09ae:0001 Tripp Lite Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x0001 bcdDevice0.01 iManufacturer 1 TRIPP LITE iProduct2 TRIPP LITE UPS iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 60mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 52 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x (Bus Powered) - your USB topology (ie is the UPS plugged on a root hub, are there other devices on the same bus, ...) Bus 002 Device 001: ID : Bus 001 Device 005: ID 05ac:0302 Apple Computer, Inc. Apple Optical Mouse [Fujitsu] Bus 001 Device 004: ID 05ac:0204 Apple Computer, Inc. Bus 001 Device 003: ID 05ac:1002 Apple Computer, Inc. Apple Extended Keyboard Hub [Mitsumi] Bus 001 Device 002: ID 09ae:0001 Tripp Lite Bus 001 Device 001: ID : Yes there are other devices on the same bus. - the result of ls -l /dev/bus/usb/XXX/YYY where XXX is the Bus number and YYY the Device number as shown by lsubs) crw-rw-r-- 1 root nut 189, 1 2009-09-04 12:50 /dev/bus/usb/001/002 once this part is ok, we'll check again to test 2.4.1 from the source tree. Hope that helps. ok, now you can recompile 2.4.1 with the flags mentioned before, and do only a make (not install) then fire drivers/tripplite_usb -D -a upsname defined in /etc/nut/ups.conf and send us back the output. last question: have you bought this unit recently? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
2009/9/2 Chris Abel ca...@wildwood.edu Arnaud Quette aquette@gmail.com writes: do a make uninstall first, and then use: ./configure --prefix=/usr --exec-prefix=/ --sysconfdir=/etc/nut --mandir=/usr/share/man --libdir=/lib --includedir=/usr/include --without-ssl --with-hal --with-cgi --with-dev --enable-static --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/pkgconfig --with-user=nut --with-group=nut After configuring it with those tags I still do not have upsdrvctl. When doing this upsdrvctl start I get this bash: /sbin/upsdrvctl: No such file or directory. There is now nothing in /usr/local/ups/bin or /usr/local/ups/sbin. have you done the make uninstall, then used the configure directives above, then make ; make install? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
2009/9/2 Chris Abel NUT user list Nut-upsuser@lists.alioth.debian.org writes: What does 'lsusb' return for this device? Bus 002 Device 002: ID 09ae:0001 Tripp Lite We will also need some basic information: * What OS? * Which distribution? * Did you install from source? Linux, Ubuntu Server 9.04. I did not install it from source, but I can try that as well. there is something strange here: the previous output you sent reports nut 2.2.1, while jaunty provides 2.4.1 (2.4.1-2ubuntu4 to be precise)! can you check for upgrading nut, and play back your tests? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
please keep the list posted Chris 2009/9/2 Chris Abel ca...@wildwood.edu My bad. I thought for sure we have Ubuntu 9.04. After double checking I see that we are using Ubuntu 8.04. I will compile and install from source and get back to you. 2009/9/2 Chris Abel ca...@wildwood.edu My bad. I thought for sure we have Ubuntu 9.04. After double checking I see that we are using Ubuntu 8.04. I will compile and install from source and get back to you. (...) After a ./configure --with-user=ups --with-group=nut --with-all make and make install, upsdrvctl does not seem to be available. It does not exists in /usr/local/ups/bin. The only ones I have are upsc upscmd upslog upsrw upssched-cmd . Am I doing something wrong? do a make uninstall first, and then use: ./configure --prefix=/usr --exec-prefix=/ --sysconfdir=/etc/nut --mandir=/usr/share/man --libdir=/lib --includedir=/usr/include --without-ssl --with-hal --with-cgi --with-dev --enable-static --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/pkgconfig --with-user=nut --with-group=nut Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
On Wed, Sep 2, 2009 at 12:48 PM, Arnaud Quetteaquette@gmail.com wrote: do a make uninstall first, and then use: ./configure --prefix=/usr --exec-prefix=/ --sysconfdir=/etc/nut --mandir=/usr/share/man --libdir=/lib --includedir=/usr/include --without-ssl --with-hal --with-cgi --with-dev --enable-static --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/pkgconfig --with-user=nut --with-group=nut Arnaud, be sure to check on the udev rules - the original driver error message appears to have been the result of no permissions (cf. Model: unknown) -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500
On Sep 1, 2009, at 3:33 PM, Chris Abel wrote: Model: Tripp-lite OMNIVS1500 What does 'lsusb' return for this device? Error: Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: unknown/unknown libusb_set_report() returned -1 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing list libusb_set_report() returned -1 instead of 8 Error reading protocol Driver failed to start (exit status=1) We will also need some basic information: * What OS? * Which distribution? * Did you install from source? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
