<br><br><div><span class="gmail_quote">2005/12/13, Peter Selinger <<a href="mailto:selinger@mathstat.dal.ca" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">selinger@mathstat.dal.ca</a>>:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
=?windows-1252?Q?Kri=9Atof_Petr?= wrote:<br>><br>> Peter Selinger wrote:<br>> > I am forwarding the below message. Does anybody on this list know<br>> > anything about this problem?<br>> ><br>> > Petr - perhaps you should switch from the "hidups" to the "newhidups"
<br>> > driver. I believe it supported the APC Back UPS even in NUT 2.0.2, and<br>> > it certainly does so in the Development version that you can get from<br>> > CVS (see the NUT download page).<br>>
<br>> No, the result is the same:<br>> # service ups start<br>> Starting newhidups: Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2)<br>><br>> No USB/HID UPS found<br><br>Yes, but you should start the driver with debugging enabled. Try this
<br>(as root):<br><br>drivers/newhidups -u root -DD auto<br><br>At the very least, it should give you some more useful debugging info.<br><br>> > Also, could you post the output of "ls -l /dev/usb"? Perhaps this is
<br>> > not a kernel problem at all, but a problem of a missing device node.<br>><br>> # ls -al /dev/usb<br>> total 0<br>> drwxr-xr-x 2 root root 60 Dec 8 11:33 .<br>> drwxr-xr-x 9 root root 3740 Dec 8 11:35 ..
<br>> crw-rw---- 1 root nut 189, 1 Dec 8 11:33 ups0<br><br>Hm. Newhidups actually does not use /dev/usb, it uses /proc/bus/usb.</blockquote><div><br>
false: the /proc/bus/usb path is libusb dependant. And a libusb
compiled on a 2.6.14 machine use ... /dev/bus/usb! The problem I'm now
facing is that the hotplug scripts used by udev still report the new
device as /proc/bus/usb/X/Y and not /dev/bus/usb/X/Y. Still
investigating.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I believe the kernel change only affected hotplugging, i.e.,<br>permissions, and not the actual USB interface. If this is true, then
<br>with "-u root", it should work anyway.<br><br></blockquote></div><br>
that's right. The only aim of this "feature" is to set the proper
permissions on the device at plug time. So trying as root for debug
purpose is fine.<br><br>
Note that this point is one of the 2 remaining for the 2.0.3 release
(the other one is a regression on mge-utalk, along with some docs
update)<br>
<br clear="all">Arnaud<br>-- <br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://people.debian.org/%7Eaquette/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://people.debian.org/~aquette/</a><br>OpenSource Developer -
<a href="http://arnaud.quette.free.fr/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://arnaud.quette.free.fr/
</a>