Displaying 5 results from an estimated 5 matches for "1.127030".
Did you mean:
1.127036
2014 Sep 12
2
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On 09/11/14 22:34, Charles Lepple wrote:
> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote:
>
>> I see a libusb_get_interrupt message in the log. Could that be the problem?
> Yes, it seems related.
>
> 1.126896 upsdrv_initinfo...
> 1.126906 upsdrv_updateinfo...
> 1.127023 libusb_get_interrupt: Function not implemented
>
2014 Sep 18
0
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote:
> On 09/11/14 22:34, Charles Lepple wrote:
>> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote:
>>
>>> I see a libusb_get_interrupt message in the log. Could that be the problem?
>> Yes, it seems related.
>>
>> 1.126896 upsdrv_initinfo...
2014 Sep 12
0
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote:
> I see a libusb_get_interrupt message in the log. Could that be the problem?
Yes, it seems related.
1.126896 upsdrv_initinfo...
1.126906 upsdrv_updateinfo...
1.127023 libusb_get_interrupt: Function not implemented
1.127030 Got 0 HID objects...
1.127036 Quick update...
Come to think of it, this
2014 Sep 12
2
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On 09/11/14 21:43, Charles Lepple wrote:
> On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote:
>
>> I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had
2014 Sep 19
2
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On 09/17/14 22:31, Charles Lepple wrote:
> On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote:
>
>> On 09/11/14 22:34, Charles Lepple wrote:
>>> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote:
>>>
>>>> I see a libusb_get_interrupt message in the log. Could that be the problem?
>>> Yes, it