[Nut-upsuser] upsd problem with NUT 2.6.1

[Kostas Oikonomou]

I'm pretty sure that it has not. I've rebooted the machine a 
couple of times, though.

W.r.t. to Arnaud's suggestion, yes, I did that in order to 
get the UPS working in the first place:

pfexec /usr/sbin/add_drv -i '"usb9ae,1008.10"' -m '* 0660 
nut ups' ugen

I verified that this is still valid by doing "prtconf -v" 
which yields (sorry for long output)

....

input, instance #0
                 Driver properties:
                     name='pm-components' type=string 
items=3 dev=none
                         value='NAME= ugen0 Power' + '0=USB 
D3 State' + '3=USB D0 State'
                 Hardware properties:
                     name='configuration#' type=int items=1
                         value=00000001
                     name='driver-minor' type=int items=1
                         value=00000000
                     name='driver-major' type=int items=1
                         value=00000002
                     name='low-speed' type=boolean
                     name='usb-product-name' type=string items=1
                         value='TRIPP LITE UPS '
                     name='usb-vendor-name' type=string items=1
                         value='Tripp Lite '
                     name='usb-serialno' type=string items=1
                         value='FW-2408 B '
                     name='usb-raw-cfg-descriptors' 
type=byte items=34
 
value=09.02.22.00.01.01.00.a0.32.09.04.00.00.01.03.00.00.00.09.21.10.01.00.01.22.c9.01.07.05.81.03.08.00.28
                     name='usb-dev-descriptor' type=byte 
items=18
 
value=12.01.10.01.00.00.00.08.ae.09.08.10.10.00.03.01.02.01
                     name='usb-release' type=int items=1
                         value=00000110
                     name='usb-num-configs' type=int items=1
                         value=00000001
                     name='usb-revision-id' type=int items=1
                         value=00000010
                     name='usb-product-id' type=int items=1
                         value=00001008
                     name='usb-vendor-id' type=int items=1
                         value=000009ae
                     name='compatible' type=string items=9
                         value='usb9ae,1008.10' + 
'usb9ae,1008' + 'usbif9ae,class3.0.0' + 'usbif9ae,class3.0' 
+ 'usbif9ae,class3' + 'usbif,class3.0.0' + 'usbif,class3.0' 
+ 'usbif,class3' + 'usb,device'
                     name='reg' type=int items=1
                         value=00000002
                     name='assigned-address' type=int items=1
                         value=00000002


The important thing is the 'compatible' entry above, which 
includes 'usb9ae,1008.10'.

Anyhow, doesn't the fact that

pfexec /opt/nut/2.6.1/bin/usbhid-ups -DD -a eco550 -u root

works fine indicate that the ugen driver is ok?





On 09/ 1/11 07:49 PM, Charles Lepple wrote:
> On Sep 1, 2011, at 2:05 PM, Kostas Oikonomou wrote:
>
>> The driver is not running. In fact, it appears I'm back to
>> a problem I had solved before:
>>
>> wiley$ pfexec /opt/nut/bin/upsdrvctl start
>> Network UPS Tools - UPS driver controller 2.6.1
>> Network UPS Tools - Generic HID driver 0.35 (2.6.1)
>> USB communication driver 0.31
>> No matching HID UPS found
>> Driver failed to start (exit status=1)
>> wiley$
>>
>> This was a permissions issue, but I now forgot exactly what.
>>
>> pfexec /opt/nut/2.6.1/bin/usbhid-ups -DD -a eco550 -u root
>>
>> works fine, which supports the permissions theory.
>
>
> Has the UPS USB cable been unplugged since the permissions
> were first set?
>
> If so, Arnaud's suggestion to make the add_drv rule more
> general might be the ticket:
>
> http://article.gmane.org/gmane.comp.monitoring.nut.user/6572
>