similar to: CyberPower SX650G no driver.

I went to the link to test the power off if the battery gets to low. Here is what I got on the command line. root at odroid-u2:/etc/nut# /usr/local/ups/bin/upsdrvctl -t shutdown -bash: /usr/local/ups/bin/upsdrvctl: No such file or directory root at odroid-u2:/etc/nut# find / -name upsdrvctl /sbin/upsdrvctl ^C root at odroid-u2:/etc/nut# /sbin/upsdrvctl -t shutdown Network UPS Tools - UPS driver

28 ??????? 2016??. 4:18:06 CEST, Raymond Day <raymondday at hotmail.com> ?????: >I forgot how I ask this. But I just found out. It's a list here: > >http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-October/007229.html > >Thanks again. Seems like it's working real good. > >Is there a way to test if it will turn off my server when the battery >power

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

Wow thanks for all your help. I unplug the power to the UPS and did the command "upsc serverups" to see if the "battery.charge: 100" would go down. I watched some videos so it's hard drive would spin up to use more power. After about a hour it did go down to "battery.charge: 90" So it is working. Not sure if it will turn off at 20% of battery that's what

I did just copy and paste on the command line like this: root at odroid-u2:/etc/nut# Shutdown UPS: serverups -bash: Shutdown: command not found root at odroid-u2:/etc/nut# /lib/nut/usbhid-ups -a serverups -k Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 Initiating UPS shutdown root at odroid-u2:/etc/nut# Don't know why

(please use Reply-All to keep the list CC'd, thanks) > On Oct 18, 2016, at 8:53 AM, Raymond Day <raymondday at hotmail.com> wrote: > > Wow that was fast thank you Charles. > > Put "upsc" in the /etc/nut/ups.conf and then went to start it with > "upsdrvctl start" but I get this then: No, sorry, I didn't mean to change ups.conf - I meant that

sending to the list for posterity. > On Oct 27, 2016, at 6:43 AM, Raymond Day wrote: > > Thank you. > > Looked like that worked. > > I put your code in /etc/nut/nut.conf just at the end of that file. > > Then did. > > upsdrvctl start > > upsc serverups > > Got this date back: > > battery.charge: 100 > battery.charge.low: 10 >

On Saturday 26 November 2016 19:25:41 Peter Stuge wrote: > Gene Heskett wrote: > > the inside of the door .. two SBC's: > > .. > > > I have tried running X on the raspi, but it hasn't enough memory or > > iron to do it well. > > A GHz system with GB of RAM is certainly capable of running a > well-written GUI effortlessly. > > > Running htop

On 14 November 2013 02:13, Sean Silva <chisophugis at gmail.com> wrote: > I love Arch, but it is probably a bit too unstable for a long-term > buildbot. CC'ing Renato who might have some suggestions. > Mikael, Sean, I think having an Arch buildbot is a great idea. At Linaro, we normally test on Debian-derived distros, and having something else entirely is a good stress test

On Oct 18, 2016, at 9:35 AM, Raymond Day <raymondday at hotmail.com> wrote: > > How do I run the git one? I guess it's up to date. Don't, for now. There have been a few posts on the mailing list explaining what to pass to ./configure (or ./autogen.sh, which calls configure) to get the Git version to install over the Debian one, but I would recommend getting the .deb version

I forgot how I ask this. But I just found out. It's a list here: http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-October/007229.html Thanks again. Seems like it's working real good. Is there a way to test if it will turn off my server when the battery power goes to low? -Raymond Day On 10/27/2016 8:37 AM, Charles Lepple wrote: >> On Oct 27, 2016, at 6:43 AM, Raymond

Greetings everybody; I have 2 questions today, but to put them in context, I'll describe the setup first. I am in the process of cnc'ing an old Sheldon metal lathe. These can make large amounts of flying metal chips & stringers when doing what they do, so its paramount that the electronics to run them are either far enough away, or put in a box thats well sealed, with fans in

Thanks Marco, I may try this if I can't get David's udev rules to work. On Mon, Dec 9, 2019 at 12:58 AM Marco Walther <marco at sonic.net> wrote: > On 12/8/19 8:18 PM, David Zomaya wrote: > > I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite > information I can help with, let me know. > > We had that discussion about the

Renato, thanks for your elaborate walk-through of the issues with ARM boards. I'm trying to add some of this to the "How to Build on ARM" document and will submit a patch later on. I already ran into the problem of cores disappearing, but on Arch Linux (which uses a fairly recent kernel), the missing cores come back as soon as the load falls to zero. Unfortunately, my personal

On Wed, Nov 13, 2013 at 8:28 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Dmitri, > > I am not using any kind of cache (didn't even know of ccache). I have now > installed ccache. Perhaps ccache should be mentioned in the buildbot > document so that every buildbot owner knows about it? > > It is currently running Arch Linux ARM. if there are good

Hi, We are making the move from legacy JIT (llvm-3.5.x) to ORC JIT and I am looking to recompile (and re-link) functions at runtime for an ARM platform (Odroid XU3) . I looked at OrcLazyJIT.cpp as a starting point. However, after going through the code, it appears that the createCompileCallbackMgr (llvm-3.8.0) / createLocalCompileCallbackManager (llvm-git) do not support an ARM triple yet.

2 years ago at one Meetup in Paris, Marc Girondot, professor at University Paris-Saclay, presented his cluster built with 12 Odroid (equivalent to Rapsberry Pi). The stack was almost the same size than your picture as there was no fan and a narrower distance between each PCB card. There were many more cables. For a total cost of less than 1000 ? and an electrical consumption reduced by a

On 17 November 2013 05:15, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I finally got it to work - and my ODROID-XU is now a passive member of the > LLVM builder society for the next week or so, until it has proven itself > (it monitors changes to the SVN repository and builds in my end without > bothering anyone at LLVM.org about its findings). I did write up a

I finally got it to work - and my ODROID-XU is now a passive member of the LLVM builder society for the next week or so, until it has proven itself (it monitors changes to the SVN repository and builds in my end without bothering anyone at LLVM.org about its findings). I did write up a "short" treatise on how to do it, in case anybody needs to do this sometime in the future. I expect

On Wed, Nov 20, 2013 at 6:11 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Renato, > > My XU is on build 141 and there hasn't been a single problem yet. No > reboots, no crashes, and as far as I have observed no core dropouts (after > I did the cpu-freq trick you sent me). Perhaps I have a stable board or > perhaps it is because of its revision (rev. 0.3)?