Re: [Nut-upsuser] Cannot get Tripplite su2200xla working on freebsd 7.1 nut 2.4.1
I did recompile the kernel, per advice, but I still don't see any drivers (I removed usbhid from my kernel)...the device now looks like: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, self powered, config 1, TRIPP LITE UPS(0x4003), Tripp Lite(0x09ae), rev 0.00 My ups.conf: [tripplite] driver=usbhid-ups port=auto desc=igor vendorid=09ae So any other ideas welcome. I invoke usbhid-ups with the following: ./usbhid-ups -a tripplite -x explore -u root I added -x vendorid=09ae and changed the vendorid to 4003 as well. No luck. Any ideas? Thomas On Wed, Aug 12, 2009 at 1:17 AM, Daniel O'Connor docon...@gsoft.com.auwrote: On Wed, 12 Aug 2009, Thomas Munn wrote: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2 on uhub0 I would bet the problem is that uhid is picking it up and the NUT driver uses libusb which requires ugen to attach to it (except in 8.0 where libusb is part of base and can attach to any device). A quick test would be to not load uhid and plug the UPS in, you should then see ugen grab it. After that NUT should work (you will need to chown the device node for it though as NUT runs as non-root by default). If that does work then do a send-pr with your usbdevs -v output and ask for the UPS to be blacklisted from uhid. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -- --- Two Wheels Good, Four Wheels Bad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cannot get Tripplite su2200xla working on freebsd 7.1 nut 2.4.1
I finally solved it, if anyone else has a tripplite: use the following method on freebsd: First, you have to recompile the kernel to NOT use usbhid. http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html Install the kernel, reboot the system. Create the following config files: /usr/local/etc/nut/ups.conf [tripplite] driver = usbhid-ups port = auto vendorid = 09ae desc Igor copy the upsd.conf.sample to upsd.conf file, change the 'listen' address to appropriate values chown the file to uucp (the default user that upsd becomes) edit the /usr/local/etc/rc.d/nut configuration file to start the driver thingy as root (to get around the problem of driver permissions) change the nut_prestart to have -u root edit the /etc/rc.conf file to start nut: nut_enable=yes On Wed, Aug 12, 2009 at 3:37 AM, Thomas Munn symgr...@gmail.com wrote: I did recompile the kernel, per advice, but I still don't see any drivers (I removed usbhid from my kernel)...the device now looks like: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, self powered, config 1, TRIPP LITE UPS(0x4003), Tripp Lite(0x09ae), rev 0.00 My ups.conf: [tripplite] driver=usbhid-ups port=auto desc=igor vendorid=09ae So any other ideas welcome. I invoke usbhid-ups with the following: ./usbhid-ups -a tripplite -x explore -u root I added -x vendorid=09ae and changed the vendorid to 4003 as well. No luck. Any ideas? Thomas On Wed, Aug 12, 2009 at 1:17 AM, Daniel O'Connor docon...@gsoft.com.auwrote: On Wed, 12 Aug 2009, Thomas Munn wrote: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2 on uhub0 I would bet the problem is that uhid is picking it up and the NUT driver uses libusb which requires ugen to attach to it (except in 8.0 where libusb is part of base and can attach to any device). A quick test would be to not load uhid and plug the UPS in, you should then see ugen grab it. After that NUT should work (you will need to chown the device node for it though as NUT runs as non-root by default). If that does work then do a send-pr with your usbdevs -v output and ask for the UPS to be blacklisted from uhid. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -- --- Two Wheels Good, Four Wheels Bad -- --- Two Wheels Good, Four Wheels Bad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cannot get Tripplite su2200xla working on freebsd 7.1 nut 2.4.1
2009/8/12 Thomas Munn symgr...@gmail.com I did recompile the kernel, per advice, but I still don't see any drivers (I removed usbhid from my kernel)...the device now looks like: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, self powered, config 1, TRIPP LITE UPS(0x4003), Tripp Lite(0x09ae), rev 0.00 My ups.conf: [tripplite] driver=usbhid-ups port=auto desc=igor vendorid=09ae So any other ideas welcome. I invoke usbhid-ups with the following: ./usbhid-ups -a tripplite -x explore -u root I added -x vendorid=09ae and changed the vendorid to 4003 as well. No luck. Any ideas? this device (09ae:4003) is supported in 2.4.1 by usbhid-ups. now, I'd like to see a driver debug output, ie /path/to/usbhid-ups -D -a tripplite using your above tripplite entry in ups.conf On Wed, Aug 12, 2009 at 1:17 AM, Daniel O'Connor docon...@gsoft.com.auwrote: On Wed, 12 Aug 2009, Thomas Munn wrote: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2 on uhub0 I would bet the problem is that uhid is picking it up and the NUT driver uses libusb which requires ugen to attach to it (except in 8.0 where libusb is part of base and can attach to any device). A quick test would be to not load uhid and plug the UPS in, you should then see ugen grab it. After that NUT should work (you will need to chown the device node for it though as NUT runs as non-root by default). If that does work then do a send-pr with your usbdevs -v output and ask for the UPS to be blacklisted from uhid. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -- --- Two Wheels Good, Four Wheels Bad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cannot get Tripplite su2200xla working on freebsd 7.1 nut 2.4.1
On Aug 12, 2009, at 3:37 AM, Thomas Munn wrote: I added -x vendorid=09ae and changed the vendorid to 4003 as well. No luck. Any ideas? I saw your later email where you got it working, but out of curiosity, what was the error message when it didn't work? Regards, -- Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Usbhip-ups going wild
On Aug 11, 2009, at 4:37 AM, Antoine Gatineau wrote: On the machine connected to a MGE Evolutipn 1250, I got this message during the night : Aug 10 23:44:17 localhost kernel: hub 3-0:1.0: port 2 disabled by hub (EMI?), re-enabling... Aug 10 23:44:17 localhost kernel: usb 3-2: USB disconnect, address 14 Aug 10 23:44:26 localhost kernel: usb 3-2: new low speed USB device using address 16 It doesn't really bother me because it is reconnected in 10 seconds but isn't there some issue here? It is the kernel that disconnects the device but I wonder why... The kernel is disconnecting it, but that is based on a signal from the root hub hardware (probably on your motherboard). The EMI is likely caused by insufficient isolation between the USB hardware and the power switching circuitry in the UPS. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Usbhip-ups going wild
So this is hardware related. The hardware is in a big lab with AC and a lot of other servers and electronic cards so the EM must be quite big there. I think everything is fine for me now. Thanks a lot for your time and help. I will update with url for RHEL4 and RHEL5 packages as soon as it is accepted by Fedora/EPEL people :) Antoine -Message d'origine- De : Charles Lepple [mailto:clep...@gmail.com] Envoyé : mercredi 12 août 2009 13:31 À : Antoine Gatineau Cc : nut-upsuser List Objet : Re: [Nut-upsuser] Usbhip-ups going wild On Aug 11, 2009, at 4:37 AM, Antoine Gatineau wrote: On the machine connected to a MGE Evolutipn 1250, I got this message during the night : Aug 10 23:44:17 localhost kernel: hub 3-0:1.0: port 2 disabled by hub (EMI?), re-enabling... Aug 10 23:44:17 localhost kernel: usb 3-2: USB disconnect, address 14 Aug 10 23:44:26 localhost kernel: usb 3-2: new low speed USB device using address 16 It doesn't really bother me because it is reconnected in 10 seconds but isn't there some issue here? It is the kernel that disconnects the device but I wonder why... The kernel is disconnecting it, but that is based on a signal from the root hub hardware (probably on your motherboard). The EMI is likely caused by insufficient isolation between the USB hardware and the power switching circuitry in the UPS. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] blazer_ser driver / (brand)Inform (series)Informer Compact
2009/8/9 Mutlu T. cmt...@gmail.com
Hi Arnaud,
Hi Mutlu,
first, please keep the list cc'ed. other people might be interested
(including Arjen when he will get back from vacation)...
I checked out development branch (2.5) from SVN [/] [trunk/] [drivers/]
[blazer_ser.c] - Rev 1804 and driver version turned out as below;
#define DRIVER_NAME Megatec/Q1 protocol serial driver
#define DRIVER_VERSION 1.51
Since same version of the driver was already installed, I quickly switched
driver to blazer_ser and performed same tests as before and voila, works
like a charm. You can find the results in the attached txt file, I will
perform further tests and give development version a go as soon as a
maintanence downtime is scheduled for this server and let you know all about
it.
I hope this helps, unfortunately there was no USB port on UPS, so I only
returned data on blazer_ser.
Best wishes,
Mutlu
--
Attachment 1: nut_blz_ser.txt[2711B]
On Sun, 09 Aug 2009 21:34:56 +0300, Arnaud Quette aquette@gmail.com
wrote:
Hi Mutlu,
2009/8/7 Mutlu T. cmt...@gmail.com
Redirecting to debian.org domain due to being rejected as spam by
free.fr
--- Forwarded message ---
From: Mutlu T. cmt...@gmail.com
To: arnaud.que...@free.fr
Cc:
Subject: New NUT HCL entry / (brand)Inform (series)Informer Compact
Date: Fri, 07 Aug 2009 15:31:04 +0300
Dear Arnaud,
First of all thank you for all the efforts you have put into NUT and OS
software development. I am using NUT with megatec driver to take control
of my compact UPS, namely Inform :: Informer Compact :: 1000VA on a
Fedora
[9,11] server and it gets the job perfectly done. Not all reported
instant
commands (listed below) work but basic functionality is there;
[r...@saboteur ~]# upscmd -u admin -p [verysecretpasswd] -l
inf...@saboteur
Instant commands supported on UPS [inform]:
beeper.toggle - Toggle the UPS beepernot working
load.off - Turn off the load immediately not tested
load.on - Turn on the load immediately not tested
reset.input.minmax - Reset minimum and maximum input voltage status
not
working
reset.watchdog - Reset watchdog timernot working
shutdown.return - Turn off the load and return when power is back
not
tested
shutdown.stayoff - Turn off the load and remain off not
tested
shutdown.stop - Stop a shutdown in progress not tested
test.battery.start - Start a battery testnot working
test.battery.start.deep - Start a deep battery test not working
test.battery.stop - Stop the battery testnot working
UPS succesfully returns OnBoost/OnBuck/OnBattery/OnLine information to
megatec driver, as well as LowBattery/BatteryCritical alerts. This is a
line interactive unit with sinus wave AC output at all times. More
information regarding this cheap unit can be retrieved via
http://www.informups.com/informer_compact.html (EN, user guide,
pictures).
Data returned by upsc command is as below;
[r...@saboteur ~]# upsc inf...@saboteur
battery.charge: 95.0
battery.voltage: 27.00
battery.voltage.nominal: 24.0
driver.name: megatec
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS1
driver.version: 2.4.1
driver.version.internal: 1.6
input.frequency: 50.0
input.frequency.nominal: 50.0
input.voltage: 214.0
input.voltage.fault: 140.0
input.voltage.maximum: 238.5
input.voltage.minimum: 206.5
input.voltage.nominal: 230.0
output.voltage: 248.0
ups.beeper.status: disabled
ups.delay.shutdown: 0
ups.delay.start: 2
ups.load: 30.0
ups.mfr:
ups.model: IN01064B
ups.serial: unknown
ups.status: OL BOOST
ups.temperature: 25.0not polled, always @ 25.0
ups.type: standby
Hope this helps, I would be glad to return any further information you
might need.
Best regards,
Mutlu Tunç
Sys Admin, Turkey.
--
PS. I'm not affiliated with any UPS manufacturer but Tunçmatik and Inform
are two well known UPS manufacturers in Turkey and they export goods to
EC
and ME. I would gladly help with communication and other needs concerning
these parties on behalf of NUT project, if that's the least I can do for
support.
thanks a lot for this verbose feedback. it's much appreciated.
I've added an entry to the compatibility list.
Arjen is currently on holidays, but he would ask for testing the blazer
support.
this blazer drivers will soon replace the megatec ones.
so please, if you can, do some testing of the development version.
if you also have a USB port, try the *_usb equivalent too.
thanks for your contrib,
Arnaud
ok, thanks for these info.
I've updated the driver.list entry to mention blazer_ser too
note that, according to your attached file, Arjen will probably be
interested in a debug output.
ie
/path/to/blazer_ser -D -a inform
this will help in fixing the empty ups.{mfr,model} and some more.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Re: [Nut-upsuser] Cannot get Tripplite su2200xla working on freebsd 7.1 nut 2.4.1
The system simply didn't see the ups. I ran the upsdevctl and the machine simply didn't see the ups 'no ups found' is the nearest approximation. I also finally located this wonderful freebsd howto: (on the nut documention of all places!) http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt Thanks for everyone who helped. Getting rid of usbhid fixed it. Thomas On Wed, Aug 12, 2009 at 7:23 AM, Charles Lepple clep...@gmail.com wrote: On Aug 12, 2009, at 3:37 AM, Thomas Munn wrote: I added -x vendorid=09ae and changed the vendorid to 4003 as well. No luck. Any ideas? I saw your later email where you got it working, but out of curiosity, what was the error message when it didn't work? Regards, -- Charles Lepple -- --- Two Wheels Good, Four Wheels Bad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
