Kjell,<br><br><div class="gmail_quote">2009/5/26 Kjell Claesson <span dir="ltr"><<a href="mailto:kjell.claesson@epost.tidanet.se">kjell.claesson@epost.tidanet.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Greg and Arnaud<br>
<div class="im">><br>
> I missed to add that I'm also interested in this one: "unset USB_DEBUG &&<br>
> lsusb -d06da:0002 -v" on your 9.04. I can't find it back in the thread.<br>
><br>
> @Kjell: do you see anything that could lead to that kind of "regression"?<br>
> I'm not sure that it's on our side though.<br>
><br>
</div>I can not set the finger on what it is. My PW3105 is running fine on<br>
nut-2.4.1.<br>
</blockquote><div><br>so does the 5115 I have underhand. tested with both 2.4.1 (ubuntu vanilla) and the trunk!<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I know that there have been changes to the nut_usb.c file, and I<br>
made a comment to Arjen about it. Because it was breaking the<br>
switch between Powerware and Phoenixtec. But that is fixed.<br>
</blockquote><div><br>yup, I've checked the code 2 times, since many things have moved around.<br>but I don't see any possible break here.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And the problem on my side is that I don't have any ups with the<br>
Phoenixtec Power Co usb interface.</blockquote><div><br>I've cc'ed Tatu. Maybe he can arrange a remote access to such a device.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If I get some time I can put<br>
ubuntu on a computer and test if the nut package is working on<br>
the pw3105.<br>
<br>
Arnaud, do you have any problems running PW5115 with nut-2.4.1 ?<font color="#888888"><br>
</font></blockquote></div><br>yes, as stated above.<br>that's why I'm interested in the verbose lsusb (check if bConfigurationValue == 1) and the kernel version (some 2.6.28 have broken USB, irrc -3 and another one).<br>
<br>as told previously, I'm more inclined in thinking that this issue comes from outside of NUT.<br>something between libusb and the kernel, since the device is working otherwise, and particularly with an older NUT release. testing 2.2.2 on Greg's jaunty would confirm that (if it doesn't work!).<br>
<br>cheers,<br clear="all">Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br>