similar to: new mobo, ups doesn't connect

Displaying 20 results from an estimated 5000 matches similar to: "new mobo, ups doesn't connect"

2019 Dec 09
2
new mobo, ups doesn't connect
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 > >
2019 Dec 09
0
new mobo, ups doesn't connect
On Sunday 08 December 2019 22:17:39 Gene Heskett wrote: > 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) > > >
2019 Sep 14
2
Changing UPS to a bigger APC 1500 1000WA, what driver?
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:
2020 Jan 08
1
unexpected UPS status
On Wed, 8 Jan 2020, Gene Heskett wrote: > On Wednesday 08 January 2020 06:44:03 Roger Price wrote: >> I am surprised that there is no ups.delay.start for this UPS. > My new APC Smart-UPS_1500 doesn't have it either. Hello Gene, The NUT 2.7.2 "device dump library" entry for the APC Smart-UPS 1500 at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html shows an entry
2009 Dec 27
2
Old thread on belkin
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
2019 Dec 08
1
new mobo, ups doesn't connect
On Sunday 08 December 2019 09:25:29 Roger Price wrote: ls -lF /var/run/nut/ total 8 -rw-r--r-- 1 nut nut 5 Dec 7 18:49 upsd.pid -rw-r--r-- 1 root root 5 Dec 7 18:52 upsmon.pid No permission if I look as gene(me) Now, I do have a /home/nut ls -l /home root at coyote:Daily$ ls -l /home total 16 drwx------ 53 amanda backup 4096 Jul 8 12:22 amanda drwxr-xr-x 72 gene gene 4096 Dec 8 12:17
2019 Dec 09
1
new mobo, ups doesn't connect
On Dec 8, 2019, at 10:26 PM, Gene Heskett <gheskett at shentel.net> wrote: > I put it back to original and restarted the nut-server. And its now > working. Go figure... >> [myups] >> #driver=hidraw >> driver=usbhid-ups >> #driver=belkin >> #driver=belkinunv >> #driver=genericups >> port=auto >> offdelay=120 >> ondelay=0 >
2014 Oct 18
3
config file locations
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
2015 Mar 01
2
New batteries and another attempt to get nut running
Hi Charles; I hope this finds you well. 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 [Belkin Belkin UPS] on usb-0000:00:02.0-3/input I have configured it to use this generic-usb, and probably made it less
2023 Jun 20
1
had to reinstall on new drive, lost all nut related .conf's
On 6/19/23 18:57, gene heskett wrote: > Greetings Jim & friends; > > Just installed nut 2.7.4 on a debian bullseye system.? ups is: > Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS > Device Descriptor: > ? bLength??????????????? 18 > ? bDescriptorType???????? 1 > ? bcdUSB?????????????? 2.00 > ? bDeviceClass??????????? 0 > ?
2019 May 31
4
odd msg at top of upsc output
Greetings all; gene at coyote:~$ upsc myups Init SSL without certificate database battery.charge: 100 battery.charge.low: 30 [yadda yadda] Is there a certificate package I should install? Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page
2023 Jun 19
1
had to reinstall on new drive, lost all nut related .conf's
Greetings Jim & friends; Just installed nut 2.7.4 on a debian bullseye system. ups is: Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor
2014 Oct 20
0
config file locations
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
2019 May 12
2
nut vs ups fail
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
2015 Mar 02
0
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
2019 May 07
3
nut vs ups fail
On Tuesday 07 May 2019 09:49:47 am Charles Lepple wrote: > On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > 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,
2019 May 07
2
nut vs ups fail
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
2023 Jun 20
1
had to reinstall on new drive, lost all nut related .conf's
On 6/19/23 20:29, gene heskett wrote: Some speeling korrections > On 6/19/23 18:57, gene heskett wrote: >> Greetings Jim & friends; >> >> Just installed nut 2.7.4 on a debian bullseye system.? ups is: >> Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS >> Device Descriptor: >> ?? bLength??????????????? 18 >> ?? bDescriptorType????????
2018 Aug 11
1
After years, upsmon says I've no perms
But /etc/nut/upsmon.conf has the correct username and password. returns: gene at coyote:/usr/share/doc/nut-doc/pdf$ upsmon myups at localhost Network UPS Tools upsmon 2.6.4 kill: Operation not permitted /etc/nut/upsmon.conf line 75: invalid directive [*****] /etc/nut/upsmon.conf line 76: invalid directive password = ************** /etc/nut/upsmon.conf line 77: invalid directive upsmon master UPS:
2020 Jun 23
1
Low Battery Problems
On Monday 22 June 2020 18:50:25 Gene Heskett wrote: > On Monday 22 June 2020 18:03:16 Charles Lepple wrote: > > On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > >> So I just edited /etc/nut/upsd.users to add both the commands it > > >> claims to have but get this response to either: > >