Nut upsdev - Nov 2008 - Looks like the Tripplite SMART1500SLT support borked?

Back in July I succeeded in getting my SMART1500SLT to work with help 
from folks on the list and changes someone made in subversion. I just 
checked out the latest code from subversion and it stopped working after 
a reboot. It looks like usbhid-ups won't load now:

# usbhid-ups -a tripplite

Network UPS Tools: 0.29 USB communication driver - core 0.34 (2.3.0-1555)

No matching HID UPS found


This was only put in in July. What happened?
The vendorid which worked then was:  vendorid = 09ae

What can I do to get this working again?
--Jeff

PS: I've read the FAQ - queequeq and all that - I'm asking for
specifics.

Citeren Jeff Cunningham <jeffrey at cunningham.net>:
> Back in July I succeeded in getting my SMART1500SLT to work with help
> from folks on the list and changes someone made in subversion. I just
> checked out the latest code from subversion and it stopped working after
> a reboot.
If you're running the latest, bleeding edge version from the trunk,  
expect things to break any time. If you don't want that, the answer is  
easy, stick with a version that works (but read on).
> It looks like usbhid-ups won't load now:
>
> # usbhid-ups -a tripplite
>
> Network UPS Tools: 0.29 USB communication driver - core 0.34 (2.3.0-1555)
>
> No matching HID UPS found
The all important question now is, what is the driver reporting if you  
run it in debug mode (-DD).
> This was only put in in July. What happened?
No pun intended, but apparently something changed between the version  
you where running at the time and what you have now... :-)

If you want to help finding what went wrong, downgrade until you've  
reached a version that works again (as far as I can see, there where  
only a couple of changes, so this shouldn't take too long). Please  
make sure you rebuild (and install) the whole NUT package and not just  
the driver.
> The vendorid which worked then was:  vendorid = 09ae
You shouldn't have to specify a vendorid (that never helps), you  
probably specified productid = 0x3012 at the time to make the driver  
recognise the UPS. This should no longer be needed (and you should  
remove it now).
> What can I do to get this working again?
See above. Checkout which commit broke the driver and report back here.

Best regards, Arjen
-- 
Please keep list traffic on the list

On Tue, Nov 18, 2008 at 12:43 AM, Jeff Cunningham
<jeffrey at cunningham.net> wrote:
> Back in July I succeeded in getting my SMART1500SLT to work with help
> from folks on the list and changes someone made in subversion. I just
> checked out the latest code from subversion and it stopped working after
> a reboot. It looks like usbhid-ups won't load now:
>
> # usbhid-ups -a tripplite
>
> Network UPS Tools: 0.29 USB communication driver - core 0.34 (2.3.0-1555)
>
> No matching HID UPS found
Is this installed on a different machine than where you originally tested this?

If so, it is possible that the permissions have not been set on the
device. The drivers drop root permissions before they access the
hardware.

A quick workaround is to add "-u root" to the command line, but
depending on your OS and distribution, there are ways to set this
automatically, e.g. through hotplug or udev.

-- 
- Charles Lepple

Now this is odd... I unplugged the USB cable again, plugged it back in, 
then reloaded the driver and this time it worked fine -  _without_ the 
-u root permissions defeat.

I just don't understand the whole udev system. It seems like mysterions 
at work and not something you can consistently count on. Arghh! Has 
anyone else noticed problems like this when USB cables are disconnected 
and reconnected?

By the way, I suspect I hit reply to on my last post and it went to 
Arjen de Korte rather than the list. If so, sorry about that, Arjen. 
Most lists I subscribe to are set up so the "Reply-To" address is the 
list address. I'll probably get chewed out over that again. For the sake 
of continuity, that post follows my signature.


Regards,
Jeff


08:09 PM

Well, that worked. And I could have sworn I tried that already once. Oh 
well.
Anyway, I'm running Linux - Debian 2.6.25.11 #5 SMP PREEMPT x86_64 on 
this box. There's only one thing I did before this stopped working that 
I haven't mentioned: I unplugged the usb cord briefly. After it stopped 
working, and after I had tried killing all the daemons and reloading 
them, I thought of the usb not being recognized properly (although 
usbview showed it alright), so I rebooted the machine just to be sure. 
Its never worked right since. Since I had also just updated the svn 
trunk I assumed it had to do with that. Now I don't know what to do. I 
don't exactly want to have it mounted with root privileges all the time.

Regards,
--Jeff

Citeren Jeff Cunningham <jeffrey at cunningham.net>:
> Well, that worked. And I could have sworn I tried that already once. Oh
well.
> Anyway, I'm running Linux - Debian 2.6.25.11 #5 SMP PREEMPT x86_64  
> on this box. There's only one thing I did before this stopped  
> working that I haven't mentioned: I unplugged the usb cord briefly.  
> After it stopped working, and after I had tried killing all the  
> daemons and reloading them, I thought of the usb not being  
> recognized properly (although usbview showed it alright), so I  
> rebooted the machine just to be sure. Its never worked right since.  
> Since I had also just updated the svn trunk I assumed it had to do  
> with that. Now I don't know what to do. I don't exactly want to
have
> it mounted with root privileges all the time.
Find someone who has nut-2.2.2 Debian packages available compiled for  
x86_64 and install those. In all likelihood, you failed to install the  
udev rules properly (if at all). I don't know how to do that on  
Debian, but after doing that things should work running as  
non-privileged nut user. Unlike the serial interface (where it is  
sufficient to set permissions once), USB requires either hotplug or  
udev rules to set these permissions once a device is plugged in and  
enumerated.

Best regards, Arjen

PS  Please honor the line below.
-- 
Please keep list traffic on the list