<br><br><div class="gmail_quote">2008/6/16 Jan Bakuwel <<a href="mailto:jan.bakuwel@gmail.com">jan.bakuwel@gmail.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Arnaud,<br>
<div class="Ih2E3d"><br>
> possibly due to the NUT version difference.<br>
> You should be running a patched 2.2.1 on HH and a 2.0.4 on Etch.<br>
> iirc, there was a fix for your problem. So your best chance is to get<br>
> a backport for Etch...<br>
<br>
</div>I have compiled the version of megatec_usb (1.5.9) that comes with the<br>
source of nut 2.2.1 from Debian Testing on Etch... (driver only;<br>
backporting nut 2.2.1 looked a bit daunting not knowing the code (it<br>
didn't compile)). The megatec_usb driver did compile & run OK though on<br>
Etch (apart from timing out rather quickly on USB messages). Ubuntu<br>
Hardy also uses the same version driver (1.5.9)... the driver works fine<br>
on Hardy.<br>
<br>
I have a feeling might be USB subsystem related? Guess the USB subsystem<br>
from Etch is different from the one on Hardy... would appreciate some<br>
help in further debugging the issue.<br>
</blockquote><div><br>our USB drivers are based upon libusb, which in turn is based upon the usbdevfs.<br>so, you should also compare the version of these.<br>otherwise, "export USB_DEBUG=3" will help in debugging the libusb side.<br>
</div></div><br>Arnaud<br>-- <br>Linux / Unix Expert R&D - MGE Office Protection Systems - <a href="http://www.mgeops.com">http://www.mgeops.com</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://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>