Justin Piszcz wrote:
>> Beats me, I'm not the author of this driver. But now that nut-2.2.0 has
>> been released, you should first check if the problem still exists in
>> that version. We've had quite some changes since nut-2.0.5 came out, so
>> chances are the problem no longer exists.
In the me
On Mon, 30 Jul 2007, Arjen de Korte wrote:
> Justin Piszcz wrote:
>
>>> Beats me, I'm not the author of this driver. But now that nut-2.2.0 has
>>> been released, you should first check if the problem still exists in
>>> that version. We've had quite some changes since nut-2.0.5 came out, so
>>>
On 7/30/07, Justin Piszcz <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, 28 Jul 2007, Arjen de Korte wrote:
>
> > Justin Piszcz wrote:
> >
> >> Thanks, any idea what is causing the low battery alarm for 2.0.5 but
> >> before that no alarms?
> >
> > Beats me, I'm not the author of this driver. But now tha
On Sat, 28 Jul 2007, Arjen de Korte wrote:
> Justin Piszcz wrote:
>
>> Thanks, any idea what is causing the low battery alarm for 2.0.5 but
>> before that no alarms?
>
> Beats me, I'm not the author of this driver. But now that nut-2.2.0 has
> been released, you should first check if the problem
On Sat, 28 Jul 2007, Arjen de Korte wrote:
> Arjen de Korte wrote:
>
>> I will add the productid 1100 to the development version.
>
> Hmmm, could you post the Belkin part# for this device? I suspect it
> might be the F6C1200-UNV, but I'm not sure.
>
> Best regards, Arjen
>
Just checked out the
Arjen de Korte wrote:
> I will add the productid 1100 to the development version.
Hmmm, could you post the Belkin part# for this device? I suspect it
might be the F6C1200-UNV, but I'm not sure.
Best regards, Arjen
___
Nut-upsuser mailing list
Nut-upsu
Justin Piszcz wrote:
> Thanks, any idea what is causing the low battery alarm for 2.0.5 but
> before that no alarms?
Beats me, I'm not the author of this driver. But now that nut-2.2.0 has
been released, you should first check if the problem still exists in
that version. We've had quite some cha
On Sat, 28 Jul 2007, Arjen de Korte wrote:
> [...]
>
>> That works, question is, why do I have to specify a productid with the new
>> version when the previous previous never had this problem?
>
> The previous version (< nut-2.0.5) would only check if the vendorid
> (Belkin, 050d) matched and di
[...]
> That works, question is, why do I have to specify a productid with the new
> version when the previous previous never had this problem?
The previous version (< nut-2.0.5) would only check if the vendorid
(Belkin, 050d) matched and didn't look at all at the productid. So if you
would have
On Sat, 28 Jul 2007, Justin Piszcz wrote:
>
>
> On Sat, 28 Jul 2007, Justin Piszcz wrote:
>
>>
>>
>> On Sat, 28 Jul 2007, Arjen de Korte wrote:
>>
>>> Justin Piszcz wrote:
>>>
# /lib/nut/newhidups -u nut - auto -x productid=1100
>>>
>>> [...]
>>>
Checking device (050D/1100) (00
On Sat, 28 Jul 2007, Justin Piszcz wrote:
>
>
> On Sat, 28 Jul 2007, Arjen de Korte wrote:
>
>> Justin Piszcz wrote:
>>
>>> # /lib/nut/newhidups -u nut - auto -x productid=1100
>>
>> [...]
>>
>>> Checking device (050D/1100) (003/002)
>>> - VendorID: 050d
>>> - ProductID: 1100
>>> - Manuf
On Sat, 28 Jul 2007, Arjen de Korte wrote:
> Justin Piszcz wrote:
>
>> # /lib/nut/newhidups -u nut - auto -x productid=1100
>
> [...]
>
>> Checking device (050D/1100) (003/002)
>> - VendorID: 050d
>> - ProductID: 1100
>> - Manufacturer: Belkin
>> - Product: Belkin UPS
>> - Serial Number:
Justin Piszcz wrote:
> # /lib/nut/newhidups -u nut - auto -x productid=1100
[...]
> Checking device (050D/1100) (003/002)
> - VendorID: 050d
> - ProductID: 1100
> - Manufacturer: Belkin
> - Product: Belkin UPS
> - Serial Number: unknown
> - Bus: 003
> Trying to match device
> This partic
# /lib/nut/newhidups -u nut - auto -x productid=1100
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
debug level is '8'
Checking device (/) (001/001)
- VendorID:
- ProductID:
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- B
Have had no issue until I ran apt-get dist-upgrade this morning:
# /lib/nut/newhidups -u nut -DD auto
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
debug level is '6'
Checking device (/) (001/001)
- VendorID:
- ProductID:
- Manufacturer: unknown
-
15 matches
Mail list logo
