Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arjen de Korte
Citeren Chris Abel : 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

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Chris Abel
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/nu

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arjen de Korte
Citeren Chris Abel : 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=

Re: [Nut-upsuser] blazer_ser driver / (brand)Inform (series)Informer Compact

2009-09-08 Thread Mutlu T.
Dear Arnaud and crew on list, Please find the verbose output of `/sbin/blazer_ser -D -a inform` command in the attached file. It spans on battery and online boost stages of UPS operation. Information about test environment is also attached. Sorry for the late feedback. Best wishes, Mu

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arnaud Quette
2009/9/8 Chris Abel > 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

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arjen de Korte
Citeren Chris Abel : It seems that whenever I specify a different directory in a ./confgure tag it does not get applied right. Please post the contents of your 'config.log' file here. Best regards, Arjen -- Please keep list traffic on the list ___

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Chris Abel
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

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Chris Abel
Arjen de Korte 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

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Kjell Claesson
Hi Chris, > Arnaud Quette 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 s

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arjen de Korte
Citeren Chris Abel : 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 l

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Chris Abel
Arjen de Korte 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

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arjen de Korte
Citeren Chris Abel : then fire drivers/tripplite_usb -D -a # 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 If you followed the instructions Arnaud send before,

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Chris Abel
Arnaud Quette 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

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arnaud Quette
2009/9/8 Chris Abel > Arnaud Quette writes: > >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" > > I had already don

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Chris Abel
Arnaud Quette writes: >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" I had already done this. To double check I did this again: R

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Arnaud Quette
2009/9/8 Chris Abel > Arnaud Quette 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 >/etc/nut/ups.conf> > # drivers/tripplite_usb -D -a Tripp-Lite > bash: drivers/tripplite_usb:

Re: [Nut-upsuser] Tripplite_usb Driver fail on OMNIVS1500

2009-09-08 Thread Chris Abel
Arnaud Quette 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 /etc/nut/ups.conf> # drivers/tripplite_usb -D -a Tripp-Lite bash: drivers/tripplite_usb: No such file or directory # tripplite_

Re: [Nut-upsuser] usbhid-ups driver can't be killed...

2009-09-08 Thread Frédéric Marchal
Thanks ! Unfortunately, this server is too old to have IPMI (no comment). I will post on my linux distro forums to resolve this kernel issue ! Charles Lepple a écrit : On Sep 8, 2009, at 6:14 AM, Frédéric Marchal wrote: Hello I'm encountering a big problem with usbhid-ups driver : the drive

Re: [Nut-upsuser] usbhid-ups driver can't be killed...

2009-09-08 Thread Charles Lepple
On Sep 8, 2009, at 6:14 AM, Frédéric Marchal wrote: Hello I'm encountering a big problem with usbhid-ups driver : the driver hangs after loading some other modules (stale data message) ! And we can't restart it. We load : i2c-piix4 adm1021 adm9240 lm75 The unloading of the modules doesn't

[Nut-upsuser] usbhid-ups driver can't be killed...

2009-09-08 Thread Frédéric Marchal
Hello I'm encountering a big problem with usbhid-ups driver : the driver hangs after loading some other modules (stale data message) ! And we can't restart it. We load : i2c-piix4 adm1021 adm9240 lm75 The unloading of the modules doesn't solve the problem. # ps -eaf | grep usb /root 18

Re: [Nut-upsuser] No battery.charge

2009-09-08 Thread Arjen de Korte
Citeren vk : I have a nut 2.4.1 on FreeBSD 7.1 i386. UPS model is IPPON smart smart power pro 2000. When i try to see battery charge, in output it have not such variable, and i can't control other servers (Win2k3 + WinNUT) because they not knows about current battery charge. How i can solve

[Nut-upsuser] No battery.charge

2009-09-08 Thread vk
Hi all! I have a nut 2.4.1 on FreeBSD 7.1 i386. UPS model is IPPON smart smart power pro 2000. When i try to see battery charge, in output it have not such variable, and i can't control other servers (Win2k3 + WinNUT) because they not knows about current battery charge. How i can solve that pr