Greetings; I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) installed and this ups (from lsusb -vv): Bus 001 Device 006: ID 050d:0751 Belkin Components Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x050d Belkin Components idProduct 0x0751 bcdDevice 0.01 iManufacturer 4 iProduct 20 Belkin UPS -------------------------------------- As nut comes totally non-configured, is there an instructional web page?, or can someone please tell me how to make this combo work with linux? Thank you -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. <https://www.nrahq.org/nrabonus/accept-membership.asp> Of course power tools and alcohol don't mix. Everyone knows power tools aren't soluble in alcohol... -- Crazy Nigel
On Sun, May 31, 2009 at 19:26, Gene Heskett <gene.heskett at gmail.com> wrote:> Greetings; > > I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) installed > and this ups (from lsusb -vv):Note that 2.2.2 is over a year old. 2.4.1 is the latest version. If you run into any problems expect to be advised to upgrade.> As nut comes totally non-configured, is there an instructional web page?, or > can someone please tell me how to make this combo work with linux?http://www.networkupstools.org/, and the man pages ;) -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
On 05/31/2009 09:26 PM, Gene Heskett wrote:> Greetings; > > I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) installed > and this ups (from lsusb -vv): > > Bus 001 Device 006: ID 050d:0751 Belkin Components > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x050d Belkin Components > idProduct 0x0751 > bcdDevice 0.01 > iManufacturer 4 > iProduct 20 Belkin UPS > -------------------------------------- > As nut comes totally non-configured, is there an instructional web page?, or > > can someone please tell me how to make this combo work with linux? >you'll need to tweak the files existing in /etc/ups
On May 31, 2009, at 2:26 PM, Gene Heskett wrote:> I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) > installed > and this ups (from lsusb -vv): > > Bus 001 Device 006: ID 050d:0751 Belkin ComponentsHi Gene, This device should be supported by the usbhid-ups driver. Usually you would look this up in the data/drivers.list file, but it doesn't look like the lsusb output is terribly helpful for that (Belkin seems to change the underlying hardware while keeping the model name the same). Which model do you have? The NUT "README" file, while not specific to Fedora, should have the rest of the info needed to set this up. (Perhaps someone with Fedora 10 experience can suggest whether the "classic" driver or the HAL driver would be better.) If I had to guess, I'd say the README is in / usr/share/doc/nut. - Charles
On Sunday 31 May 2009, Rob MacGregor wrote:>On Sun, May 31, 2009 at 19:26, Gene Heskett <gene.heskett at gmail.com> wrote: >> Greetings; >> >> I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) >> installed and this ups (from lsusb -vv): > >Note that 2.2.2 is over a year old. 2.4.1 is the latest version. If >you run into any problems expect to be advised to upgrade.I'll take that up with Rahul. If that's the case, I am not allergic to building from the tarball, some of the stuff I run here straight from the tarball, like the kernel is 2.6.30-rc7, and amanda is from yesterdays snapshot of what will become amanda-2.6.2 in a few months. However, I have no clue if I have a problem because I can't get it to run at all. [root at coyote amanda]# service ups start Starting UPS driver controller: [FAILED] Starting upsd: [ OK ] Starting UPS monitor (master): [FAILED] So I need help from square one. Would a tarball build be preferable in this case?>> As nut comes totally non-configured, is there an instructional web page?, >> or can someone please tell me how to make this combo work with linux? > >http://www.networkupstools.org/, and the man pages ;)Those I have been looking at, intermittently. Too many trees, can't see the forest. :) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. <https://www.nrahq.org/nrabonus/accept-membership.asp> I got this powdered water -- now I don't know what to add. -- Steven Wright
On May 31, 2009, at 10:17 PM, Gene Heskett wrote:> On Sunday 31 May 2009, Charles Lepple wrote: >> On May 31, 2009, at 2:26 PM, Gene Heskett wrote: >>> I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) >>> installed >>> and this ups (from lsusb -vv): >>> >>> Bus 001 Device 006: ID 050d:0751 Belkin Components >> >> Hi Gene, >> >> This device should be supported by the usbhid-ups driver. > > That seems not to be part of the 2.6.30-rcX kernels. > The current .config has: > > CONFIG_USB_HID=y > CONFIG_USB_HIDDEV=y > CONFIG_HID_BELKIN=yI should have been more specific - usbhid-ups is a user-mode driver in NUT. It uses libusb to kick the kernel's USB HID driver off of the device, and it uses /dev/bus/usb (I forget the kernel driver name) to speak the HID protocol.> I can probably dig out anything else that might be helpful. > >> Usually you >> would look this up in the data/drivers.list file, but it doesn't look >> like the lsusb output is terribly helpful for that (Belkin seems to >> change the underlying hardware while keeping the model name the >> same). >> Which model do you have? >> >> The NUT "README" file, while not specific to Fedora, should have the >> rest of the info needed to set this up. (Perhaps someone with Fedora >> 10 experience can suggest whether the "classic" driver or the HAL >> driver would be better.) If I had to guess, I'd say the README is >> in / >> usr/share/doc/nut. >> >> - Charles > > It might help, if it was there: > [root at coyote ~]# locate 'nut/README' > [root at coyote ~]# > [root at coyote ~]# cd `locate 'nut/'` > [root at coyote cur]# ls > 1243795177.4479.gANVC:2,RS 1243799859.4479.0TdwL > 1243813905.4479.2izhm > [root at coyote cur]# pwd > /root/Mail/nut/cur > [root at coyote cur]# > > I don't believe it exists in the rpms. Next?Sounds to me like a bug in the package. We're trying to overhaul the documentation, so the website is a little behind. But this should apply: http://www.networkupstools.org/doc/2.2.0/README.html (please keep the list CC'd via reply-all - thanks!)
On May 31, 2009, at 10:36 PM, Gene Heskett wrote:> [myups] > driver = mydriver > port = /dev/ttyS1 > cable = 1234 > desc = "A POS Belkin" > # > # To find out if your driver supports any extra settings, start it > with > # the -h option and/or read the driver's documentation. > ----------------- > I now see the port is wrong, and should probably be /dev/ttyUSB1, as > zero is > busy here, with heyu. However, fixing that makes zero difference.Actually, for the usbhid-ups driver (with only one UPS on a machine), / etc/nut/boils down to: ########### [myups] driver = usbhid-ups port = auto desc = "Whatever floats your boat" ########### "port" does not matter here, it just has to be something (the Linux / dev/bus/usb addresses change based on what order things are plugged in, as well as the kernel version and phase of the moon). The key to your setup is specifying "usbhid-ups" as the driver name. Out of curiosity, do you get any more detail from 'lsusb -vv' if you run it as root?