Guys,<br> How can I get my system to boot up and load the driver correctly? I rebooted it when I got home this evening and the UPS device moved to this spot: /dev/bus/usb/002/002 which wouldn't be a big deal, except the permissions changed back to root:plugdev. When I load upsdrvctl it can't connect because of the permissions.
<br><br>Anyway, how can I go about finding the correct ups usb device in /dev and changing the permissions of it during boot (before upsdrvctl gets issued)??<br><br>Any suggestions?<br><br><div><span class="gmail_quote">On 2/7/07,
<b class="gmail_sendername">Peter Selinger</b> <<a href="mailto:selinger@mathstat.dal.ca">selinger@mathstat.dal.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Greg,<br><br>the battery runtime is computed by the device firmware. 80 minutes<br>sounds like a lot, but there's no guarantee that it's accurate.<br><br>-- Peter<br><br>Greg Grotsky wrote:<br>><br>> Thanks Peter, Charles Lepple repsonded this morning and I got it all sorted
<br>> out. I believe it's working now, I can execute "upsc myups" and it spits out<br>> all sorts of cool info. I have a question though: Does "battery.runtime" get<br>> calculated based on the current load or is it just something that the
<br>> manufacturer sets in the firmware for the model? I ask because the value I<br>> currently have for battery.runtime is 4800 and from what I read that is in<br>> seconds. I'm basically running just a computer (no monitor) from the ports
<br>> on this thing, does 80 minutes of runtime sound right?<br>><br>> Thanks,<br>> -Greg<br>><br>><br>> On 2/7/07, Peter Selinger <<a href="mailto:selinger@mathstat.dal.ca">selinger@mathstat.dal.ca
</a>> wrote:<br>> ><br>> > From the file INSTALL:<br>> ><br>> > The setup for USB ports is slightly more complicated. Device files<br>> > for USB devices, such as /proc/bus/usb/002/001, are usually
<br>> > created "on the fly" when a device is plugged in, and disappear<br>> > when the device is disconnected. Moreover, the names of these<br>> > device files can change randomly. To set up the correct
<br>> > permissions for the USB device, you may need to set up (operating<br>> > system dependent) hotplugging scripts. Sample scripts and<br>> > information are provided in the scripts/hotplug and
<br>> > scripts/udev directories. (If you want to try if a driver<br>> > works without setting up hotplugging, you can add the "-u root"<br>> > option to upsd, upsmon, and drivers; this should allow you to
<br>> > follow the below instructions. However, don't forget to set up the<br>> > correct permissions later!).<br>> ><br>> > -- Peter<br>> ><br>> > Greg Grotsky wrote:<br>> > >
<br>> > > So I just bought one of these fabulous CyberPower UPS devices from<br>> > BestBuy<br>> > > hoping I could control it with my machine. Luckily, I found NUT! I've<br>> > got<br>
> > > the SVN sources and compiled and installed them but I haven't been able<br>> > to<br>> > > get it to recognize the usb AE550.<br>> > ><br>> > > When I plug the usb cable in I see this in syslog:
<br>> > > Feb 6 22:36:56 mythbox kernel: usb 1-1: new low speed USB device using<br>> > > ohci_hcd and address 4<br>> > > Feb 6 22:36:56 mythbox kernel: usb 1-1: configuration #1 chosen from 1
<br>> > > choice<br>> > > Feb 6 22:36:56 mythbox kernel: hiddev96: USB HID v1.10 Device [CPS UPS<br>> > > AE550] on usb-0000:00:02.0-1<br>> > ><br>> > > I run lsusb and I see this:
<br>> > > $ lsusb<br>> > > Bus 003 Device 001: ID 0000:0000<br>> > > Bus 001 Device 004: ID 0764:0501 Cyber Power System, Inc.<br>> > > Bus 001 Device 001: ID 0000:0000<br>> > > Bus 002 Device 002: ID 15c2:ffda SoundGraph Inc.
<br>> > > Bus 002 Device 001: ID 0000:0000<br>> > ><br>> > > My /usr/local/ups/etc/ups.conf file contains<br>> > > [CyberPower]<br>> > > driver = usbhid-ups<br>> > > port = auto
<br>> > > # vendor = "Cyber Power Systems"<br>> > > # product = "AE550"<br>> > > # vendorid = 0764<br>> > > # productid = 0501<br>> > > desc = "MythBox"
<br>> > ><br>> > > When I run upsdrvctl start I get this:<br>> > > $ ./upsdrvctl start<br>> > > Network UPS Tools - UPS driver controller 2.1.0<br>> > > Network UPS Tools: 0.28
USB communication driver 0.28 - core 0.30 (2.1.0<br>> > )<br>> > ><br>> > > No matching HID UPS found<br>> > > Driver failed to start (exit status=1)<br>> > ><br>> > ><br>
> > > I have tried everything in attempt to get this recognized. As you can<br>> > see<br>> > > in my conf file I tried supplying the values I recieved in lsusb and the<br>> > > vendor and product names. I've tried doing that at the command line as
<br>> > well<br>> > > running usbhid-ups -x vendor=CyberPower. I've also tried supplying<br>> > > usbhid-ups with the device name /dev/usb/hiddev0 or /dev/usbdev1.4_ep00<br>> > or<br>> > > /dev/usbdev1.4_ep81 (not sure what these are but I think they all
<br>> > represent<br>> > > the ups). I've created a user for the software to use and set the<br>> > > permissions correctly. What am I missing??<br>> > ><br>> > > BTW: I'm running 64bit version of Debian. I didn't have any problems
<br>> > with<br>> > > the compile or install.<br>> > ><br>> > > Thanks,<br>> > > -Greg<br></blockquote></div><br>