similar to: Belkin usp startup

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 ]

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

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

Hi Gene, On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > 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. We have an open ticket about that[*]; basically, the official NUT documentation needs to be a bit more explicit

On Sunday 19 October 2014 22:03:23 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > 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

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

Hi Charles; I had nut working from before, but managed to lock up something and had to reboot. Nut is in the stuff to start at boot time, but is not now capable to being restarted with the nut script in /etc/init.d, claiming it is disabled: gene at coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a

On Sunday 19 October 2014 22:03:23 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > 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

On Thursday 01 January 2015 08:36:40 Robert Blayzor did opine And Gene did reply: > On Jan 1, 2015, at 8:10 AM, Stephan Bosch <stephan at rename-it.nl> wrote: > > Could you enable mail_debug? That should show why it is trying to > > recompile the Sieve script. > > Well, that it does! And it's saying the script is "not up to date" and > tries to

On Tuesday 21 October 2014 22:06:48 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 21, 2014, at 9:12 PM, Gene Heskett <gheskett at wdtv.com> wrote: > >> configure: error: libgd not found, required for CGI build > >> > >> And gdlib does not appear to be available from the repo's. > > Sorry, I must have missed that message.

On Sunday 19 October 2014 23:28:38 Gene Heskett did opine And Gene did reply: Ping? > On Sunday 19 October 2014 22:03:23 Charles Lepple did opine > > And Gene did reply: > > Hi Gene, > > > > On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > > Greetings; > > > > > > I found pdf user manual which explains a

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 Tuesday 21 October 2014 22:06:48 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 21, 2014, at 9:12 PM, Gene Heskett <gheskett at wdtv.com> wrote: > >> configure: error: libgd not found, required for CGI build > >> > >> And gdlib does not appear to be available from the repo's. > > Sorry, I must have missed that message.

hi i have a belkin ups here some setting chmod 0600 /dev/hiddev0 chown nut:root /dev/hiddev0 linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No matching USB/HID UPS found Driver failed to start (exit status=1) linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl -u root start

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

# /lib/nut/megatec_usb -a myups Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with

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

I have a new Belkin F6C900-UNV. I see that it's not listed in belkin-hid.c The VendorID is 0x050d like all the Belkin UPSes, and the ProductID is 0x0900. I haven't had a chance to actually test the development version of nut yet, since I'm running Fedora Core 6, which still has nut 2.0.3. `newhidups -DD -a myups` gives the error of: Checking device (050D/0900) (001/002) - VendorID:

Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 : Normal: ups.status: OL No wall power: ups.status: OB Runtime calibration (started from AP9630 web interface): ups.status: OB CAL So at this stage there is a difference! I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power

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