similar to: Have any FreeBSD users tried the new libusb-1.0 branch?

Displaying 20 results from an estimated 400 matches similar to: "Have any FreeBSD users tried the new libusb-1.0 branch?"

2017 Nov 26
2
Have any FreeBSD users tried the new libusb-1.0 branch?
Charles Lepple writes: > still looking for volunteers to test the libusb-1.0 code on FreeBSD and > other systems. On Fedora 27, running commit 2999c95f0: # nut-scanner Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. There's also a bug in the configure script on 64 bit
2017 Nov 26
1
Have any FreeBSD users tried the new libusb-1.0 branch?
> >> # nut-scanner >> Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. > > Although I suspect that the USB portion of nut-scanner could probably be replaced with a small shell script that parses the output of lsusb, this shouldn't be too hard to fix. Logged, in case it
2017 Nov 26
0
Have any FreeBSD users tried the new libusb-1.0 branch?
On Nov 26, 2017, at 3:15 PM, Sam Varshavchik wrote: > > Charles Lepple writes: > >> still looking for volunteers to test the libusb-1.0 code on FreeBSD and other systems. > > On Fedora 27, running commit 2999c95f0: Thanks for checking this. I should have been more clear in the second email in the thread, but commit 2999c95f0 is on the original "libusb-1.0"
2017 Nov 26
0
Have any FreeBSD users tried the new libusb-1.0 branch?
On Nov 22, 2017, at 7:39 PM, Charles Lepple <clepple at gmail.com> wrote: > > The new branch will only attach to the device if I pass the '-u root' flag to usbhid-ups. fixed: https://github.com/networkupstools/nut/compare/dfd514e...80bc452 still looking for volunteers to test the libusb-1.0 code on FreeBSD and other systems.
2017 Nov 12
5
Cyberpower model numbers in the HCL
Anyone familiar with Cyberpower's model numbers? I finally got sick of my Tripplite's USB port going south, all the time, so I'm looking to replace it. The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is the CP1500PFCLCD model, a newer, premium version of the unit; but the HCL does have an entry for the CP1000PFCLCD model. Pretty sure that the CP1500PFCLCD
2016 Dec 03
2
Problem installing NUT on 16.04
> On Dec 3, 2016, at 12:31 PM, Jack McGee <jack at greendesk.net> wrote: >> so this is progress. Thanks! Anything else to check to know it is working as it should? http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns The "FSD" test is more for the NUT logic, which isn't too complicated with only one UPS and one server. If you want to
2017 Nov 12
1
Cyberpower model numbers in the HCL
Charles Lepple writes: > On Nov 12, 2017, at 10:08 AM, Sam Varshavchik wrote: > > > > The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is > the CP1500PFCLCD model, a newer, premium version of the unit; but the HCL > does have an entry for the CP1000PFCLCD model. > > > > Pretty sure that the CP1500PFCLCD will work; but figure I ask if anyone
2016 Dec 09
2
Problem installing NUT on 16.04
I rebooted machine and nut cannot connect to the UPS. mythuser at amethi:/etc$ sudo /lib/nut/usbhid-ups -DD -a CyberUPS1 Network UPS Tools - Generic HID driver 0.42 (2.7.4.1) USB communication driver (libusb 1.0) 0.02 0.000000 debug level is '2' 0.000499 upsdrv_initups... 0.005722 Checking device (8087/8000) 0.005753 Failed to open device, skipping. (Access
2013 Jan 31
1
CyberPower on OpenIndiana
Hello, I have a CyberPower CP1500PFCLCD and I'm trying to get nut to see it under OpenIndiana. All search online suggested that it basically can't happen, but I decided to ask again, maybe things have changed since then. The UPS can be seen by the system: # /usr/sbin/cfgadm -lv usb9/1.1 Ap_Id Receptacle Occupant Condition Information When Type
2016 Oct 25
2
setting up CYBERPOWER CP1500PFCLCD
Hi, Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during power outage. I configured QNAP properly (like this: http://geekbeat.tv/qnap-adding-external-devices-qnap), but I don't know what to do next. I work
2020 Aug 16
1
UPS Reboots when Pi Reboots!
OS: Raspbian Lite 4.19 (Linux 5.4.51-v7l+ armv7l) NUT version: 2.7.4 Install Method: Package (apt-get) Device Name: CyberPower CP1500PFCLCD, connected via USB Problem: This is a brand-new installation; the only step I've taken is my initial edit of /etc/nut/ups.conf (which I'll post below). I started the driver and after doing so issued a reboot command to my Raspberry Pi (sudo reboot).
2014 Apr 15
3
CyberPower CP1500PFCLCD and NUT upsset.cgi
Since there is apparently no immediate solution to upsstats.cgi not reading the output voltage correctly, I have moved on to trying to use upsset.cgi. To recap the UPS is a CyberPower CyberPower CP1500PFCLCD UPS running on a headless server running Slackware 14.1 with the 3.10.7 kernel. The version of NUT is 2.71 and I am using usbhid-ups for communication with the UPS The problem is that when
2020 Jun 18
3
Low Battery Problems
Hello, I am having a heck of a time with false low battery alarms right now.  It has been going on for the last couple of months.  I originally started getting them with a UPS that was 1-2 years old so I thought it was time to change it out and buy a new one.  I'm still getting the false alarms with the brand new one.  The status is "OL LB" which is strange to me. I have a
2014 Mar 26
0
Incorrect Values From usbhid-ups
On Mar 23, 2014, at 11:12 PM, Bill S wrote: > The output of the driver is below. The incorrect voltage of 136 is > shown at 0.265256. It should match input voltage of 119 as shown at > 0.265219 but it doesn't. The voltages displayed on the UPS LCD panel > information however are equal and match the input voltage provided by > the driver. There might be other incorrect
2018 Mar 10
2
UPS CYBERPOWER CP1300EPFCLCD MISSING FROMCOMPATIBILITY LIST
Hi I have just purchased a Cyberpower CP1300EPFCLCD UPS. It is not listed in your Compatibility List http://networkupstools.org/stable-hcl.html I am very new to all this but do have a background in IT. I have been retired for 18 years so am a bit out of touch so please excuse if I am a bit fuzzy. I will try my best to explain my issue below. When I plug my UPS into my Synology NAS
2020 Oct 26
2
Can't get CyberPower UPS to work with Raspberry Pi 4
On Oct 26, 2020, at 9:01 AM, I wrote: > >> battery.voltage.nominal: 24 > > I don't have the citation handy, but I think another user reported that the battery.voltage returned by the UPS is a constant 24.0 V, regardless of the actual battery voltage. Here's what I was thinking of:
2011 Aug 24
3
UPS issues with PFC PSU
Just noticed that our new server has a newer 80+ efficiency 865W PSU with PFC. So apparenty our existing 1500VA (865W) APC Back-UPS is not safe to use anymore. We apparently need a pure sine wave UPS. http://nam-en.apc.com/app/answers/detail/a_id/8883 I found an affordable 1500VA UPS by CyberPower, model CP1500PFCLCD, which has a pure sine wave output. Wondering if anyone has experience with
2024 Jun 10
3
Permissions error
https://youtu.be/vyBP7wpN72c?si=SQFhJQ7bhUAUNCIW I watched a youtube video to get this installed. I have standalone nut installation on Ubuntu 22.04.? UPS is a CP1500PFCLCD.? I have gotten as far as eliminating the no connection error that I was being broadcast.? I have the web view viewable at http://192.168.1.105/cgi-bin/nut/upsstats.cgi The problem I have I believe is permissions.
2020 Jun 23
1
Low Battery Problems
> *From:* Charles Lepple [mailto:clepple at gmail.com] > *To:* Mike Dillinger <miked at softtalker.com> > *Cc:* nut-upsuser at alioth-lists.debian.net > *Date:* Monday, June 22, 2020, 5:19 AM PDT > *Subject:* [Nut-upsuser] Low Battery Problems > > I’d recommend a battery test. Starting the test via the front panel should be sufficient, or you might be able to do it with
2016 Dec 03
2
Problem installing NUT on 16.04
This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD.