[Nut-upsuser] blazer_ser problem on windows NUT 2.6.5-3780M
tinuva at ipv6.za.org
Sun May 12 12:26:10 UTC 2013
Thank you, interesting to know. Currently have my serial-usb-cable plugged
into a USB2 port, trying to save the USB3 ports for devices that can
actually make use of the speed, but won't hurt to try it I guess.
On Sat, May 11, 2013 at 9:05 PM, Kris Jordan
<nut.kj at sagebrushnetworks.com>wrote:
> David Bezuidenhout wrote, On 5/11/2013 10:26 AM:
>> I have a bunch of UPSs, most connected to pcs with Linux working 100%
>> with NUT.
>> The only one I have a problem with, is connected to Windows 7 64bit, and
>> I used the straight MSI installed from the website named
>> Took me a while to find a way to get it to work, but it is ugly for now.
>> Just starting up the service results in a NUT not working at all, and I
>> tracked it down to the blazer_ser driver not finding the UPS. Debugging
>> shows some problem with the communication on my serial-usb port. What I
>> have found is, that it doesn't work until I add 4x debug flags. eg: -DDDD
> I had a similar issue with usbhid-ups on a USB 3.0 port until I moved it
> to a USB 2.0 port. Maybe it's timing related, I'd expect adding debugging
> would slow it down a tad.
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.**debian.org<Nut-upsuser at lists.alioth.debian.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser