similar to: Can't get latest version for Raspberry Pi

On Jan 25, 2016, at 2:16 PM, paul at smithp.co.uk wrote: > > I now see that the directory containing 2.6.4 in the repository at http://archive.raspbian.org/raspbian/pool/main/n/nut/ appears to have a build version also available of 2.7.2 ? but no matter what I do with apt-get remove, purge, update, upgrade, install, (all the options!) it always seems to suggest that the only available

Hello, I am attempting to run tinc on a raspberry pi (version 1 B HW, 512mb ram). Tinc starts, but then the tinc daemon crashes. # cat /etc/issue Raspbian GNU/Linux 7 \n \l # cat /etc/debian_version 7.8 $ apt-cache showpkg tinc Package: tinc Versions: 1.0.19-3 (/var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages) Description Language:

i have a OMNIVS1500XL i have used nut for several years on a full sized pc with no problems i am trying to get nut working with this ups on a raspberry pi i tried with a pi 3b running raspbian stretch i tried with a pi 3b running raspbian buster i tried plugging the usb cable straight into the pi i tried using a powered usb hub i tried rebuilding nut from the source package all caused the pi to

On Jul 13, 2014, at 9:46 AM, pere at riusnebot.com wrote: > Dear Charles Lepple, > Sorry for my email intrusion. for next time: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > I have an UPS called Ovislink 1000VA and it use a UPSMART2000R (with ?ATCL FOR UPS?). > I?m a beginner Linux user and I ?will install your new driver <nutdrv_atcl_usb > to work

Everything runs fine for several hours, then communication is lost and nut doesn't reestablish communication on its own. Running sudo upsdrvctl stop then sudo upsdrvctl start reestablishes communication. OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux Nut Version: 2.7.2-4 Nut Installation Method: apt Device: CyberPower PR1500LCD Uses ? ? Generic

Hello Guus, thank you for your fast reply. Indeed the upgrade to a newer Raspbian image did solve my problem with tinc, I was not aware that there was a new Jessie based version. The current Jessie based Raspbian has tinc 1.0.24 version included, which runs fine, so I did not run tinc with debug messages enabled, since the issue that had caused my tinc crashes in 1.0.19 had probably been fixed.

Dear Charles, Thanks for your quick reply, but I can't install nut_2.7.2 in my raspberry. 1) I create a [nut] directory and use wget to download three files: [nut_2.7.2-1.dsc] [nut_2.7.2.orig.tar.gz] [nut_2.7.2-1.debian.tar.xz] 2)I unpack: dpkg-source -x nut_2.7.2-1.dsc 3) I use command root at pi1:/nut/nut-2.7.2# debuild -us -uc . .. And I have the following error code:

Hi, I have a Liebert UPS which I have connected to a FreeNAS Box. I had all sorts of issues making FreeNAS (FreeBSD based) talk to the UPS over USB. My solution seemed to be to buy a Raspberry Pi then connect it to the UPS (works fine), then make my NAS read the UPS status from the Pi over a TCP/IP connection. Convoluted I know, but it works well...for about a month, then it just loses

I think I may be of some help in this matter. Since I am running a bunch of Raspberry Pi's with NUT and it took a lot of hacking to make it possible. You could probably copy and paste this right into a shell script and just run it ... # Do an rpi-update FIRST to prevent USB strangeness #some depencies from repo sudo apt-get -y install m4 libtool libudev-dev automake #fixing autoconf for

In R 3.3.2 detectCores() in package parallel reports 2 rather than 1 on Raspberry Pi B+ running Raspbian. (This report is just 'for the record'. The model is superseded and I think no longer produced.) The problem seems to be caused by grep processor /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) (On Raspberry Pi 2 and 3 there is no error because

Hi Steve. Thanks for your tutorial. I was following on my raspberry pi with raspbian os. i have an error, when i run " sudo ln -s /usr/bin/autom4te /usr/local/bin/autom4te " i have this error messagge " ln: failed to create symbolic link `/usr/local/bin/autom4te': File exists ". Sorry but i'm not an expert as you.... How can i fix it? It's important? Thanks!

On Aug 12, 2017, at 12:00 PM, Rory Jaffe <rsjaffe at gmail.com> wrote: > > OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux > Nut Version: 2.7.2-4 > Nut Installation Method: apt > Device: CyberPower PR1500LCD > Uses? ?Generic HID driver 0.38 (2.7.2) Is this stock Raspbian or another variant? If it is Raspbian, I think it might

Jean-Marc, I can try both of the things you suggested. Maybe this coming weekend. I installed the Raspbian libopus-dev package instead of building it myself and that's been working great. Do I use --disable-intrinsics on ./configure, or on make? On Thu, May 25, 2017 at 9:28 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Hi Samuel, > > Can you see if this commit fixes

Hello, I'm following the directions that 'make check' gave me: to e-mail you log files. I'm attempting to build opus on a raspberry pi zero w, which I think has more or less the original hardware as an original raspberry pi + WiFi. I'm running a clean install of the latest version of raspbian lite. Note that lite has no gui, but also has less packages in general, so it

I have a Powercom SPD-850U UPS. I try to connect this UPS with my Raspberry PI 3B + via NUT, I came to the conclusion - all works nice with Raspbian (2018-03-13), the first one that supports 3B +, but does not work with the latest version of Raspbian (2019-04-08). I think, the algorithm for working with the USB bus has changed in the latest versions of the kernel. And this is bad, because it

I have a Powercom SPD-850U UPS. I try to connect this UPS with my Raspberry PI 3B + via NUT, I came to the conclusion - all works nice with Raspbian (2018-03-13), the first one that supports 3B +, but does not work with the latest version of Raspbian (2019-04-08). I think, the algorithm for working with the USB bus has changed in the latest versions of the kernel. And this is bad, because it

On Sep 10, 2019, at 10:40 AM, grumpy at mailfence.com wrote: > > i have a OMNIVS1500XL > i have used nut for several years on a full sized pc with no problems > i am trying to get nut working with this ups on a raspberry pi > i tried with a pi 3b running raspbian stretch > i tried with a pi 3b running raspbian buster The “unable to handle kernel paging request” points to a

Dear list, since some days I own an APC Back-UPS BX1400U. Now I try to connect my Raspberry Pi to it using NUT, but ... ;) The UPS is connected via an USB-cable, and "lsusb" shows an APC device. NUT is installed via "sudo apt-get install nut". My goal: a Synology DiskStation DS1515+ should "read" UPS-data provided from the Raspberry an shut-down itselt at 30%

I have just started trying Opus with a view to using it in a project. I am interested in embedded hardware and tried it on the Raspberry Pi using the raspbian distro. The version of libopus in the repos is 0.9.14. I installed this and tried encoding 2 minutes of speech from a librevox recording. It managed this at a respectable pace for complexity 10: Skipping chunk of type "LIST",

On Fri, Jan 22, 2016 at 12:50:39PM +0100, Maximilian H. wrote: > I am attempting to run tinc on a raspberry pi (version 1 B HW, 512mb > ram). Tinc starts, but then the tinc daemon crashes. What do you mean by "crashes"? Were there any error messages logged? In doubt, run tinc in the foreground with debugging messages enabled: tincd -n <netname> -d5 -D > # cat