Ok, thanks. I also read a bunch of other posts on this.
However, I can't figure out the right parameters to the
add_drv or update_drv command:
$ pfexec /usr/sbin/add_drv -m '* 0660 nut ups' -i 'usb5/2' ugen
("usb5/2") already in use as a driver or alias.
$ pfexec /usr/sbin/update_drv -m '* 0660 nut ups' -i
'usb5/2' ugen
devfsadm: driver failed to attach: ugen
Warning: Driver (ugen) successfully added to system but
failed to attach
$
The "usb5/2" I'm using comes from
$ /usr/sbin/cfgadm -lv usb5/2
Ap_Id Receptacle Occupant
Condition Information
When Type Busy Phys_Id
usb5/2 connected configured ok
Mfg: Tripp Lite Product: TRIPP LITE UPS
NConfigs: 1 Config: 0 <no cfg str descr>
unavailable usb-input n
/devices/pci@0,0/pci103c,2a6c@2:2
$
On 08/26/11 09:47 AM, Arnaud Quette wrote:
2011/8/26 Charles Lepple <clep...@gmail.com
<mailto:clep...@gmail.com>>
On Aug 25, 2011, at 7:08 PM, Kostas Oikonomou wrote:
I don't pretend to understand the output, but here
it is:
wiley$ testlibusb -v
Dev #0: Generic - Mass Storage Device
It's a disk drive of some sort. The key is that no UPS
is currently visible to libusb (and hence, to NUT).
Did some digging, and maybe the following information
will help?
http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-March/002444.html
I was going to point that or similar things.
Note that libusb use the "ugen" generic usb driver.
and this requires the "add_drv" commands...
cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader -
http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
