similar to: Trouble getting Roline/Powercom UPS recognized

On Jul 16, 2019, at 3:52 AM, Patrick M. Hausen wrote: > The OS is FreeBSD: > > FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64 > > This is the device: > > ugen0.6: <POWERCOM Co.,LTD HID UPS

Hi all, > Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at gmail.com>: > There may be an issue with the uhid driver binding to the device. I can't remember which versions of FreeBSD this affects, though. Unloaded the kmod - did not change anything. But I will configure devd not to load uhid.ko ever, just to be sure. You are implying Ithe uhid driver should not be

Hi! > Am 16.07.2019 um 15:50 schrieb Patrick M. Hausen <pmh at hausen.com>: >> Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at gmail.com>:We have another branch that uses the libusb-1.0 API: https://github.com/networkupstools/nut/issues/300 > > I will compile and try this one and report back. OK … so which one? libusb-1.0 libusb-1.0+0.1 libusb-compat-1.0

Hello, My Samba has been working well until I recently run Windows update for DC. I got the error message below on my client (Windows 8.1 Enterprise Evaluation OS) when accessing the Samba shares. " *\\pinnacle** is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.* " I can

On Jul 18, 2019, at 5:09 AM, Patrick M. Hausen wrote: > > Hi! > >> Am 18.07.2019 um 05:02 schrieb Charles Lepple <clepple at gmail.com>: >> @zykh recommends libusb-compat-1.0. I have not tested it recently, but when I last did, I had to run the driver as root on FreeBSD (probably 11.1?): > > I’ll check, thanks. > > Just FYI: the FreeBSD ports maintainer

My guess Samba 3.6 (smb v1) Windows 8.1 after update, disabled smb v1 probely. ( wannacry crypto leak) Dont know for sure but that was ms its advice also. I think its time to update your samba. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > albert samba via samba > Verzonden: woensdag 24 mei 2017 20:13 >

Hi, colleagues! Something strange happens with a server. I am attempting to connect management interface of UPS with server via USB. In console I see a lot of errors: Mar? 7 13:42:04 xxx kernel: ugen2.2: <POWERCOM Co.,LTD HID UPS Battery> at usbus2 Mar? 7 13:42:05 xxx kernel: uhid0 on uhub6 Mar? 7 13:42:05 xxx kernel: uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.02,

I wrote a small app that monitors a Back-UPS ES500 UPS via the uhid0 interface. I want to run the daemon with as little privs as possible. gastest# ls -l /dev/uhid0 crw-rw---- 1 root operator 122, 0 Nov 12 05:26 /dev/uhid0 gastest# Is it safe to chmod o+r /dev/uhid0 ? Or is there a better way to drop privs of the daemon yet still be able to read from the device ? All I am doing is

Hello, Help me please with *newhidups* setup. Does it work for someone on *BSD ? Here is the data. --------------------------------------------------------------- *** FreeBSD root.srv# uname -a FreeBSD xxxxxx.dyndns.info 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Tue Feb 8 07:38:22 UTC 2005 admin@temp.botka.homeunix.org:/usr/src/sys/i386/compile/SRV i386 *** NUT ver.2.0.3 root.srv# ll /var/db/pkg/

Hi, Have anybody tried Cyberpower Value 600E (USB) under FreeBSD? usbhid-ups from nut 2.4.1 does not recognize (find) the device on my machine. [root at substance /usr/local/libexec/nut]# uname -a FreeBSD substance.dyndns.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root at walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root at substance

Hi Vladimir, I have got 2.0.3 working on netBSD 3.0. To get it operational I needed to do the following (most of this is from memory...). 1). Recompile kernel with uhid removed. If uhid ataches to the device then libusb is not able to. Have to allow generic usb driver ugen to claim port. >From dmesg usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class

On 2/5/14, 9:55 PM, Charles Lepple wrote: > On Feb 5, 2014, at 9:03 PM, Chris Duffy wrote: > >>> Please run this: >>> >>> /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D >>> >>> and send the output back to the list. >>> >> Output from the above command: >> >> 0.000000 debug level is '1' >>

On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > 0.016485 Trying megatec protocol... > 0.017411 send: Q1 > 0.252545 read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001 > 0.252589 Status read in 1 tries > 0.252602 Supported UPS detected with megatec protocol > 1.288032 send: Unknown error > 1.288085 Permissions problem: Input/output error

Hi all. I'm trying to get a CyberPower OR700LCDRM1U UPS working with NUT (via USB). I assumed this would be compatible since the OR2200LCDRM2U is. Clearly I'm wrong or missing something vital. I'm on FreeBSD, using the version of NUT from the ports tree (2.6.1). FWIW, I tried compiling from source with similar results. Here's my UPS in ups.conf: [ssups] driver=usbhid-ups

Hi! I'm having problems connecting Ippon Smart power pro 1000 UPS to nut via usb under FreeBSD 7-stable The UPS uses megatec protocol and works fine via RS232 (UPS has RS232 and USB connectors) When I connect USB /dev/uhid0 is created. Tried port=/dev/uhid0 - doesn't work. Kernel rebuild w/o option uhid. On connect I get 2 devices /dev/ugen1, /dev/ugen1.1. Tried both of them.

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent three last days trying to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. # dmesg|grep -i powercom ugen0.3: <POWERCOM Co.,LTD> at usbus0 uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01, addr 3> on usbus0 uhid0: <POWERCOM

On April 28, 2017 9:11:59 AM GMT+03:00, "????????? ?????????" <vtk-alexb at mail.ru> wrote: >Hello all! > >Some days ago we received new UPS?Powercom BNT-2000AP with USB >interface to replace an old staff and I've spent four last days trying >to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. > ># dmesg|grep -i powercom >ugen0.3:

Hello! I can't get my UPS to get detected. I have tried to search the internet for several hours. I have a Mustek Powermust 1400 USB that has both a USB and serial port. OS: openSUSE 20151209 (x86_64) VERSION = 20151209 CODENAME = Tumbleweed Kernel: 4.2.1-1-desktop Nut: nut-2.7.3-1.5.x86_64 installed with zypper dmesg |grep usb [94414.680765] usb 1-1.1: new low-speed USB device number 4

OS = NAS4Free (FreeBSD Revision: 199506) NUT Version = 2.7.3 for other parts of NUT version is listed below NUT is part of the NAS4Free distribution Device = Tripp Lite SMART1300LCDT URL http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/ PROBLEM: NUT is ABLE to see the UPS BUT it is not getting the right(?) descriptor? I am using

Hello, I'm new to the list, new to NUT, but not new to Unix-likes. I could use some help getting NUT to talk to my Tripp Lite G1000U. Searching Google for "Tripp Lite G1000U" returns exactly two hits at this writing, so that may not be a good sign. ;-) It may just be rebranded for sale through this source (Costco). Externally, the G1000U looks much like the SMART1000LCD: an amber