similar to: New batteries and another attempt to get nut running

On Sun, Mar 1, 2015 at 2:23 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hi Charles; I hope this finds you well. Hi Gene, > Here is dmesg output: > gene at coyote:~$ dmesg |grep Belkin > [ 3.315667] usb 2-3: Product: Belkin UPS > [ 3.315669] usb 2-3: Manufacturer: Belkin > [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device

Greetings all; Back to a thread I started back in May of 2008 I think. I never did get this belkin and nut to talking, so I thought I'd make another run at it. Trying to run the driver as the user gene, I'm getting this: --------------------------- [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups" Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2) debug

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

Greetings; Its unk because whats plugged in seems to be blocking the rear name plate. About all I can recall is that its big, 3 battery unit, rated somewhere north ob 1250 VA. Its an 050D:0751 Belkin. What driver should I use, and what file is that set in? The nut version presently and freshly installed is from the Ubuntu 10.04.4 LTS repo's. Probably old, but IIRC it also worked with

On Nov 11, 2014, at 9:41 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Can't claim USB device [050d:0751]: could not detach kernel driver from > interface 0: Operation not permitted > Driver failed to start (exit status=1) > > In /dev/ttyUSB0 is owned by root. /dev/usb/hiddev3, the last one, has a > slow data marching out of it if I sudo cat /etc/dev/usb/hiddev3

Greetings Charles; Following the chapter 6, configuration notes, and having configured everything I had done previously in the repo built /etc/nut directory without any success previously, I found when trying: /usr/local/ups/upsdvrctl start, It reported it couldn't open /usr/local/ups/etc/ups.conf So I copied what I had done before to that path by mv'ing them with mc. Then I checked

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

On Oct 12, 2014, at 8:28 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Its unk because whats plugged in seems to be blocking the rear name plate. > About all I can recall is that its big, 3 battery unit, rated somewhere > north ob 1250 VA. > > Its an 050D:0751 Belkin. > > What driver should I use, and what file is that set in? Looks like it is in usbhid-ups. If

On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote: > /lib/nut/usbhid-ups -a myups -DD gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission denied lemme see who owns that. huh? amandabackup:nut what the h? Who is supposed to own

On Tuesday 14 October 2014 08:19:02 Charles Lepple did opine And Gene did reply: > usbhid-ups Added that, but only get this at "sudo service nut start" gene at coyote:/etc/init.d$ sudo service nut start * Starting Network UPS Tools [ OK ]

On Thursday, February 19, 2015 10:16:41 PM Charles Lepple wrote: > On Feb 19, 2015, at 8:55 AM, Gene Heskett <gheskett at wdtv.com> wrote: > > On Wednesday, February 18, 2015 08:11:13 PM Charles Lepple wrote: > > [...] > > > >> On recent Debian and Ubuntu with 2.7.2 and > >> earlier, there was an issue where the udev rules file needed to be >

Greetings; Nut pull & build from about two weeks ago, 2.4.3 I believe. Belkin UPS. I have everything working but a proper shutdown of upsd when I reboot, it hangs there and needs the hdwe reset button to reset it. That may be related to my finding more than 1 K##upsd and more than one K##upsmon, in /etc/rc5.d and which I have now nuked. However, while its working well enough to monitor,

On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > > New testing install(stretch) > > pulled in nut stuff from repo. > > copied old wheezy configs to /etc/nut, overwriting the resident > > files can't talk to ups, missing usbhid-ups file > > Gene, > > What do you have in /etc/nut/ups.conf? (There

Hi Charles; Had a fire on the mobo of my old server, replaced it all with about 10x the hardware. dmesg now says this: 71068.842780] usb 1-9: new full-speed USB device number 10 using xhci_hcd [71069.012577] usb 1-9: New USB device found, idVendor=051d, idProduct=0003 [71069.012579] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [71069.012579] usb 1-9: Product:

On Feb 19, 2015, at 11:23 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Almost $800 dollars and worthless > on wheezy. I am asking a few ?? over that on their mailing list as it > worked perfectly on ubuntu-10.04.4 LTS. If you still have a backup of /etc from the Ubuntu install, there might be some clues in /etc/cups about the duplex settings (or which drivers support duplex,

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >

Greetings; I found pdf user manual which explains a few things that might help. However, for a ubuntu flavor, the various .conf etc files seem to be in /etc/nut. But this pdf says they are in /usr/local/ups/etc, and yes indeed there are some there, with the .sample files being owned by root, and the rest are user 503, whoever he may be. Are these just a sample storage in case one needs to

Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value:

I've drug it as far under the table as I can get it on a 30% heart. Yeah, I'm getting on, I'll be 85 in about 2 weeks. Heart surgury will be scheduled in the next few days to replace a worn out, leaky aortic valve. Piece if cake if my veins are big enough. So what driver do I use with a Smart-UPS_1500??? Never mind it was found and accessed by the bootup! upsc my usp reports:

Mr. Selinger, I'm CCing you directly since it appears (insofar as I can tell) that you are one of the delelopers for the newhidups driver. This is the third time I've submitted this (hence the CC this time). Hopefully mailman takes it. I've tweaked my SPF records, and I'm hoping that was the problem. My sincere apologies if this has gone through and I just haven't seen it