Hi Arnaud, > Arnaud Quette <[email protected]> wrote: > > Hi Greg > > first, a thank to Kjell too... > > 2009/7/12 Greg Vickers <[email protected]> > > > Hi Kjell, > > > > > > Kjell Claesson wrote: > > > >> Hi all, > >>> > >> Hi Greg, > >> > >> I've got a Powerware 5110 UPS that I'm trying to set up with nut in > >>> Ubuntu. I've installed nut and configured the first two files: > >>> > >>> $ cat /etc/nut/nut.conf > >>> MODE=standalone > >>> $ cat /etc/nut/ups.conf > >>> [pw5110] > >>> driver = bcmxcp_usb > >>> port = auto > >>> # port = /dev/bus/usb/002/002 > >>> > >> Yes the port should be auto. > >> And if you use the latest libusb you should have a device > >> at /dev/bus/usb/002/002 that you have found. > >> > >> > >>> When I try to test this configuration with the following command: > >>> $ sudo upsdrvctl start pw5110 > >>> Network UPS Tools - UPS driver controller 2.4.1 > >>> Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) > >>> USB communication subdriver 0.17 > >>> Can't set POWERWARE USB configuration > >>> Unable to find POWERWARE UPS device on USB bus > >>> > >>> > >> To make a real test that it read the usb you can do the following. > >> Set libusb debug to 3. > >> sudo export LIBUSB_DEBUG=3 > >> > >> Then run the driver in debug (not by upsdrvctl). > >> sudo /path/to/bcmxcp_usb -DD -u -a pw5110 > >> > >> Now it should spit out some info. You end it by ctrl-c. > >> > >> Report back and we can have a look. > >> > >> We may have a bug here, but it is not confirmed as our tests > >> does not reveal it. > >> > > > > After leaving my Ubuntu host overnight, I've turned it on and the nut > > daemon was running when I tried the above check. I stopped that > daemon and > > the above test worked just fine! I didn't change anything and now > it's > > working just fine. > > > > Thank you for the information about the debug test! All OK now! :) > > well, ok now, but there is still something under the hood! > my guess is that the udev update change introduced by Scott James > doesn't fully refresh the udev rights. > I've not taken the time to validate it though, so mea culpa. > the result is basically that if you don't unplug/replug your device or > reboot your system after nut installation, the udev rule is not applied.
I did try unplugging and replugging the USB cable the UPS was attached by, and still couldn't contact the UPS correctly. I have also had trouble on this system with the IR receiver on my TV tuner card not reappearing on a reboot, I have to do a shutdown and turn the host back on to get the IR receiver device to reappear. I didn't diagnose this IR receiver problem until after that night, so I suspect that this may have impacted the UPS communication as well. However, now when I do a reboot, the UPS is detected just fine - go figure. At one point I was suspicious that the udev rule wasn't being run, and tried copying it into /etc/udev/rules.d, and un/re-plugging the UPS, but to no avail. > I'll try to check that tomorrow, and make some more progress on 2.4.1-4, > which will be a major Debian update. Thanks, Greg _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
