similar to: Cannot connect to Kstar UPS

Hello, Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. 1. I tried blazer_usb and usbhid-ups. Any other suggestions? 2. What would be needed to get it supported by NUT? ======== HW ======== HP Microserver Gen 8 ======== UPS ======== Working:Kstar Micropower Micro

Barry, I have had success with NUT on Debian and an EATON 5E2000IUSB-AU 5E 2000VA/1200W UPS With 3 x OUTLETS which I believe is good value. I would believe the the EATON ?5E 1500VA/900W UPS With 3 x OUTLETS would work just as well. The 1500VA also uses the same batteries as the 2000VA so I would believe it would run its raited load longer than 2000VA. My eight drive RAID driver uses less that

On Sep 27, 2019, at 9:19 AM, Dragos Leahu wrote: > > Hello, > > Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. > > 1. I tried blazer_usb and usbhid-ups. Any other suggestions? blazer_usb is no longer maintained - try nutdrv_qx instead. You may need some additional

Hi list! Currently I use Asterisk 1.8.30.0 on an OpenWRT-Switch. Now I want to change to Asterisk 13.14.1 on a Banana PI (with Armbian/Debian 9). Well, I copied the configuration and changed what needed, so basically, it works, at least with my tests. But when Asterisk will be started, in the message log I get this error: [Feb 15 08:40:15] ERROR[3971] chan_oss.c: Unable to register channel

Another Update: I had to reboot my server today. After the reboot, I had the exact same problem as before without the usb hub. Since I already had the ups connected and communicating, I decided to try to figure out how to fix it. Here is what worked for me using the usb 2.0 hub sudo upsd ?c stop sudo upsdrvctl stop sudo upsdrvctl start sudo upsd Everything connected up and was

Zitat von Tzafrir Cohen <tzafrir.cohen at xorcom.com>: Hi, > Off-topic: any reason you don't use chan_alsa? This was the "Armbian installation", I didn't configured it extra... > Are you sure you quote the error message right? Copy+Paste... ;) But I searched a little bit and I really don't think, I need this module... As I undestand, I just need it, if I

Hi, I have an OEM of KStar UDC9101S which is Megatec protocol rs232 capable unit. So I use blazer_ser protocol=megatec /dev/ttyUSB0 with no issue to get NUT running. Please direct me what command should I issue to collect the data in order to include the UPS to device database? P.S. tryed /lib/nut/blazer_ser -DD... but no difference from a regular output has being added by the driver.

I was able to install the kdeedu RPM, from the Fedora Core 3 Install DVD, without any problem, on my CentOS 4.4 box and KStars is up and running and has been updated. :-) The bad news is that I didn't learn anything, by doing it this quick and simple way, so now I'm going to begin reading about creating my own RPMs. When I get the CentOS 5.0 install DVD, that will be another issue for

Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.service●

On Tue, 7 Jul 2020, Alexander Karenin wrote: > Hi, I have an OEM of KStar UDC9101S which is Megatec protocol rs232 capable unit.So I use blazer_ser protocol=megatec /dev/ttyUSB0 with no issue to get > NUT running. > > Please direct me what command should I issue to collect the data in order to include the UPS to device database? It would be interesting to see the output of upsc

Hello, I have been able to restore a backup, disabled samba initially, changed hostname, and then joined as a DC. It looks as if that was successful and some data was replicated. I had to manually update some DNS data to get it operational however. As a test whether user data (my major concern) was replicated, I disabled the old DCs and ran samba-tool user list, and the result was as expected.

I have a Gentoo linux (OpenRC) desktop connected to a UPS, the brand is Vultech, but lsusb gives me this: Bus 003 Device 006: ID 0925:1234 Lakeview Research and I found an article about this hardware here, someone had it working with the richcomm_usb driver: http://verahill.blogspot.it/2012/12/kstar-australia-1500-va-ups-on-debian.html So, I installed nut and configured my UPS to work with the

Hi again! I tried to attach two VoIP-phones to my new Asterisk 13.14.1 on a Banana PI with Armbian/Debian 9. First test was to call a test service that say the time. Works! Second test was to record my voice and play it again. Works! Third test was to call the other VoIP-phone. It does NOT work... :( Then I noticed that, by starting, Asterisk says the following messages: [Feb 15 18:42:54]

Hi all I have a problem when I use `virsh attach` to attach a qcow2 disk to vm without argument --subdirver=qcow2 and this makes the qcow2 disk become a raw format disk, and the data in this disk is missing in guest os and also I have used guestmout to confirm this, the same result. Is there any way to let me find back the data in this disk ? the version of libvirt and kvm is : Compiled

On 12/09/2013 09:03 PM, lyz_pro@163.com wrote: > Hi all > > I have a problem when I use `virsh attach` to attach a qcow2 disk to vm without argument --subdirver=qcow2 > and this makes the qcow2 disk become a raw format disk, and the data in this disk is missing in guest os > and also I have used guestmout to confirm this, the same result. The format of a file is important. By

Is there an RPM for this? I think it's in the kdeedu package on the FC6 DVD. My wife is an amateur astronomer and she uses this excellent program. If upstream isn't including it, can I get it and not break my CentOS 4.4 system? (Also, I'd like to migrate her and my daughter to CentOS). TIA, Lanny

On 27 July 2007, Scott Silva wrote: >You can get Fedora 3 src rpms for Centos 4 and Fedora 6 srpms for >Centos 5. Then it can be as simple as rpmbuild --rebuild bla- >bla-.src.rpm. It can also be difficult if other dependencies creep in. >But the rpmbuild process should warn you. Scott: Thank you again! I think I have the SRC RPMS for FC3 and FC6. I will do some reading, about

-------------------------------------------------- From: <hyouko at gmail.com> Sent: Tuesday, July 08, 2014 12:16 AM To: "Hill" <hill at fermot.com.pl> Cc: "Charles Lepple" <clepple at gmail.com>; <nut-upsuser at lists.alioth.debian.org> Subject: Re: [Nut-upsuser] Lupus 500 MEC0003 Problems >> Everything looks fine apart from ups.beeper.status

> Everything looks fine apart from ups.beeper.status always shows enabled > even if the status bit fom the ups has changed state. Probably because the driver updates the beeper status only every 'pollfreq' (default 30) seconds, so it may have missed the change. > After more testing the indexes work as follows > > 0x0a = load.on / cancel.shutdown.stayoff /

gene heskett <gheskett at shentel.net> writes: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 It is likely that you have built new nut but old nut is still on your system. I do a 'sudo make install' to write over the distribution nut (on NetBSD/pkgsrc, surely not what you are using).