[Nut-upsuser] tripplite_usb/nut-2.2.1: Driver not connected.
forest at alittletooquiet.net
Thu May 29 18:52:21 UTC 2008
On Thu, May 29, 2008 at 02:45:09PM -0400, Charles Lepple wrote:
> On Thu, May 29, 2008 at 2:05 PM, Forest Bond <forest at alittletooquiet.net> wrote:
> > On Thu, May 29, 2008 at 02:01:39PM -0400, Charles Lepple wrote:
> >> Arjen pointed out what is the most likely cause of the segfault (our
> >> reconnection code has changed a bit since the driver was first
> >> written), but the problem is that I won't have time to work on that
> >> for a week or so.
> > Would it behoove me to downgrade nut?
> Hi Forest,
> I'm not sure that downgrading would help - the reconnection changes
> were made a long time ago, and just haven't been well-tested.
> Can you send the output of upsc when the driver is working, or does it
> not get that far? (You may omit unit-specific things such as the
> serial number if you prefer.) The two important things I am looking
> for are the protocol number and the model.
# upsc tripplite
ups.debug.V: 31 30 34 30 58 58 0d '1040XX.'
ups.firmware.aux: protocol 2001
ups.mfr: Tripp Lite
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080529/4e842b8b/attachment.pgp
More information about the Nut-upsuser