similar to: NUT and Raspberry pi 3b+

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 was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 15 Player. But my Raspberry Pi 3b + (with raspbian last version) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at

I was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 15 Player. But my Raspberry Pi 3b + (with raspbian) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at raspberrypi:~

I installed the NUT under the latest Ubuntu Mate for Raspberry. The driver immediately earned with my UPS (Powercom SPD-850U). But my happiness was not long. After the first restart of Raspberry, the NUT did not start. It is treated by reconnecting the USB connector. Reconnection has to be performed after each reboot of Raspberry. The USB permissions for the "nut" group and priority

On May 2, 2019, at 6:22 PM, Vladimir Zaitchikov wrote: > > pi at raspberrypi:~ $ lsusb -v > > Bus 001 Device 004: ID 0d9f:0004 Powercom Co., Ltd What are the permissions on /dev/bus/usb/001/004? If the group is not "nut", and you installed NUT after plugging in the UPS USB cable, you may need to run udevadm as mentioned here:

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

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

Sorry, I forgot this: torsten at raspberrypi:/ $ sudo /lib/nut/usbhid-ups -a UPS -x vendorid=051d -DD Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.004718 upsdrv_initups... 0.007534 Checking device (051D/0002) (001/004) 0.008910 - VendorID: 051d 0.010030 - ProductID: 0002 0.011196

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%

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 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.

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:

Hi all, Someone should be able to help me - I think this is an easy one. I have a Raspberry Pi successfully running nut-server talking via USB to a Liebert UPS. It is running Version 2.6.4 which was installed ages ago following instructions freely available on the internet by A. Bakalidis I now see that the directory containing 2.6.4 in the repository at

Hi Steve thanks for your answer. I follow your tutorial untill this instruction: wget "http://downloads.sourceforge.net/project/libusb/libusb-1.0/libusb- 1.0.18/libusb-1.0.18.tar.bz2? r=http%3A%2F%2Fwww.libusb.org%2F&ts=1404210716&use_mirror=softlayer-ams" -O libusb-1.0.18.tar.bz2 in my opiniono there are 2 " that are not needed and i when -O libusb- 1.0.18.tar.bz2 is not

I've searched the listserv archive, to no avail, so I hope I'm not duplicating a previous problem. I am anxious to get this working, so I'm open to uninstalling what I have and starting over. One note which may not be meaningful is that this UPS pre-dates the Raspberry Pi I've got connected to it, and I used to use it with the CyberPower software, which requires logging in with a

Hi all, I'll try either, as my last tries (1 year ago) to make an RPI4 a Samba AD-DC have all failed because of missing dependencies. Thanks Electronico NEW-CALEDONIA (South Pacific) Le 09/08/2023 ? 15:54, Dirk Laurenz via samba a ?crit?: > Hi, > > that sounds nice.... i will try this... > > -----Urspr?ngliche Nachricht----- > Von: samba <samba-bounces at

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

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

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!

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