<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Zarafa WebAccess v7.0.6-32752">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: [Nut-upsuser] Re Powercom Vanguard driver for nut</title>
<style type="text/css">
body
{
font-family: Arial, Verdana, Sans-Serif ! important;
font-size: 12px;
padding: 5px 5px 5px 5px;
margin: 0px;
border-style: none;
background-color: #ffffff;
}
p, ul, li
{
margin-top: 0px;
margin-bottom: 0px;
}
</style>
</head>
<body>
<p>Compiled 2.6.4 with what I believe to be the right options and can now load the driver usbhid-ups for the powercom 0d9f:0004.</p><p>But just get a rolling screen of</p><p> </p><p> 156.702195 Quick update...<br /> 158.690980 upsdrv_updateinfo...<br /> 158.750008 Got 1 HID objects...<br /> 158.750030 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x0e, Offset: 0, Size: 8, Value: 100<br /> 158.750038 Full update...<br /> 160.691067 upsdrv_updateinfo...<br /> 160.734022 file_report_buffer: expected 0 bytes, but got 2 instead<br /> 160.734039 HIDGetEvents: unexpected input report (ignored)<br /> 160.734046 Got 0 HID objects...<br /> 160.734053 Quick update...<br /> </p><p>with some</p><p> 94.938441 libusb_get_interrupt: Connection timed out</p><p> </p><p>and some data</p><p> 142.943604 Quick update...<br /> 144.690952 upsdrv_updateinfo...<br /> 144.733790 Got 13 HID objects...<br /> 144.733818 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0a, Offset: 0, Size: 1, Value: 0<br /> 144.733837 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0a, Offset: 1, Size: 1, Value: 0<br /> 144.733853 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 1<br /> 144.733869 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x0a, Offset: 3, Size: 1, Value: 1<br /> 144.733883 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0a, Offset: 4, Size: 1, Value: 0<br /> 144.733899 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0a, Offset: 5, Size: 1, Value: 0<br /> 144.733911 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a, Offset: 6, Size: 1, Value: 0<br /> 144.733922 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x0a, Offset: 7, Size: 1, Value: 0<br /> 144.733933 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x0a, Offset: 8, Size: 1, Value: 0<br /> 144.733944 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x0a, Offset: 9, Size: 1, Value: 0<br /> 144.733956 Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, ReportID: 0x0a, Offset: 10, Size: 1, Value: 0<br /> 144.733967 Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, ReportID: 0x0a, Offset: 11, Size: 1, Value: 0<br /> 144.733978 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x0a, Offset: 15, Size: 1, Value: 0<br /> </p><p>But when trying to get other components to run keep getting a refusal</p><p>upsc VGD@localhost<br />Error: Connection failure: Connection refused<br /> </p><p>Is there something I am missing? Should it run under the powercom driver or the usbhid-ups?</p><br /><p> </p><p>Powercom returns</p><p>Network UPS Tools - PowerCom protocol UPS driver 0.13 (2.6.4)<br /> 0.000000 debug level is '2'<br /><br />Unable to open /var/lib/ups/hiddev0: No such device<br /><br /> Current user id: root (0)<br />Serial port owner: nut (57)<br />Serial port group: nut (57)<br /> Mode of port: 0750<br /><br />Things to try:<br /><br /> - Use another port (with the right permissions)<br /><br /> - Fix the port owner/group or permissions on this port<br /><br /> - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf).<br /> See upsdrvctl(8) and ups.conf(5).<br /><br /> 0.000610 Fatal error: unusable configuration<br /> </p><p>TIA</p><p> </p><p> </p><p> </p><p><br /> </p><blockquote style="border-left: 2px solid #325FBA; padding-left: 5px;margin-left:5px;">-----Original message-----<br /><strong>From:</strong> Charles Lepple <clepple@gmail.com><br /><strong>Sent:</strong> Sun 22-07-2012 08:56<br /><strong>Subject:</strong> Re: [Nut-upsuser] Re Powercom Vanguard driver for nut<br /><strong>To:</strong> Gordon Longland <gordon@compsos.com.au>; <br /><strong>CC:</strong> nut-upsuser@lists.alioth.debian.org Users <nut-upsuser@lists.alioth.debian.org>; <br />[please keep the list CC'd, most likely with reply-all]<br /><br />On Jul 21, 2012, at 6:46 PM, Gordon Longland wrote:<br /><br />> Thank you for the reply Charles<br />> <br />> https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=806567<br />> <br />> The above bug reflects the issues I had with trying to compile nut on RHEL5 i686 system. Has anyone managed to get nut 2.6.3 working on RHEL5?<br /><br />I don't currently use any RPM-based systems myself, but I wonder why they are calling autoreconf when using the nut-2.6.3 tarball (usually autoreconf is only needed when building from a SVN checkout). Omitting that line from the spec file should help.<br /><br />-- <br />Charles Lepple<br />clepple@gmail<br /><br /><br /><br /></blockquote>
</body>
</html>