Displaying 20 results from an estimated 1000 matches similar to: "2.6.31.4: Any other suggestions regarding a UPS/USB (APC1500VA) on (Intel P55KG) stale issue?"
2009 Oct 13
6
USB/UPS connectivity issue on Intel DP55KG Motherboard
Hello,
I use the following in my ups.conf:
# USB:
[apc]
driver = usbhid-ups
port = auto
desc = "APC 1500VA"
pollfreq = 5
On my new motherboard (an Intel DP55KG), every once and awhile I get this:
Broadcast Message from nut at box.com
(somewhere) at 17:48 ...
Communications with UPS apc at localhost lost
Broadcast Message from nut at box.com
2007 Apr 11
1
Programming Problem (for loop, random # control, 3 dimentional graph)
Dear List,
This is just a programming problem which i cannot seem
to figure out. I am trying to get a set of power from
a test (say, kolmogorov smirnov) out of a distribution
(say, G-K distribution) as follows. I am trying to
reduce to pain of writing the whole set of data points
(p# below) using "for" loop. However, I seem to have
some problem in it as the output "M" does not
2006 Nov 15
1
Tripp Lite OMNI900LCD
I am having an issue running NUT and using an TrippLite OMNI900LCD.
When I run ./upsdrvctl start I get :
[player@V0002-S002 bin]$./upsdrvctl start
Network UPS Tools - UPS driver controller 2.1.0
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0)
Detected a UPS: Tripp Lite /TRIPP LITE UPS
Using subdriver: TrippLite HID 0.1 (experimental)
dstate_setflags: base variable
2008 Aug 20
1
FreeBSD usbhid-ups problem
Hi,
I have an MGE Ellipse UPS connected to a FreeBSD 7.0 system and it works
OK
to begin with but after an hour or so it dies, eg..
Starts out OK..
debug level is '2'
upsdrv_initups...
Checking device (0463/FFFF) (/dev/usb2//dev/ugen0)
- VendorID: 0463
- ProductID: ffff
- Manufacturer: MGE UPS SYSTEMS
- Product: ELLIPSE
- Serial Number: 000000000
- Bus: /dev/usb2
Trying to match device
2011 Apr 21
0
2.6.38.3 w/nut: libusb_get_string: error sending control message: Broken pipe
Hello,
Dist: Debian Testing
Kernel: 2.6.38.3
Software: nut 2.6.0-1
I believe this is a chipset bug, are there any plans for a workaround?
The messages have changed over the kernel versions for this problem, but
the problem itself still exists:
Apr 21 09:17:25 p34 usbhid-ups[3737]: libusb_get_string: error sending control
message: Broken pipe
Apr 21 09:44:20 p34 usbhid-ups[3737]:
2023 May 24
1
Synthesize low batt (LB) fron SNMP UPS which does not support this?
Hi again,
On 5/22/23 18:31, Willcox David via Nut-upsuser wrote:
> Hmm. Is there maybe something there already that will do this? Maybe
> kind of back-handed.
>
> In drivers/dstate.c, I see:
>
> 1. In status_init(), if ?driver.flag.ignorelb? is set in the driver
> state, the ?ignorelb? flag is set.
> 2. In status_set(), if ignorelb is set, and the status being set
2011 Jun 28
1
Windows 2.6.0-1 usbhid-ups driver infinite loop on USB disconnect
I was doing some testing with the 2.6.0-1 beta Windows installer and a
Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the
usbhid-ups driver if the UPS is lost on the UPS bus. This is on a
Windows XP SP3 system. USB device access is via libusb 1.2.4.0
(driver mode, not filter) in case that matters.
Everything seems to work just fine so far while the UPS is connected
(so kudos,
2008 Feb 04
2
nut with Belkin "Active Battery Backup" UPS (BU30 series)
Hi,
I bought a Belkin Active Battery Backup UPS
(http://www.belkin.com/uk/activebattery/) yesterday with a USB port and
hoped it would work with nut.
The device will show up in /proc/bus/usb/devices as a Cypress
Semiconductor USB to Serial. It creates /dev/hiddev0 (and this
disappears when the UPS is unplugged). I've tried using belkin,
belkinunv, usbhid-ups and megatec_usb. I've tried
2017 Jan 19
1
PowerWalker VFI 2000 RT LCD
Hi all,
I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB
(didn't try serial yet).
UPS should work via HID driver but ups.status is not rendered properly.
Specification of UPS says USB HID compatible.
HID driver is the only one which talks with UPS as i try a few from
/lib/nut.
I use driver usbhid-ups (which communicate with ups), but subdriver
resolving is
2016 Oct 15
2
Data Stale at random intervals
Hi Charles,
Thanks for the tip. I reran the debug again until communication stopped. Backtrace is below. Thanks!
441.204990 upsdrv_updateinfo... (Driver stopped communicating)
Broadcast message from nut at golgotha.tklapp.com (somewhere) (Sat Oct 15 03:36:57
UPS nailbunny at localhost is unavailable
^C
Program received signal SIGINT, Interrupt.
0x00007ffff76ec1c7 in ioctl
2016 Sep 08
2
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X)
Hi again,
Thanks for the prompt reply.
Just for the record i am running debian unstable/sid with nut 2.7.4-3
# dpkg -l 'nut*' | grep ^ii
ii nut 2.7.4-3 all network UPS tools
- metapackage
ii nut-client 2.7.4-3 amd64 network UPS tools
- clients
ii nut-server 2.7.4-3 amd64 network UPS tools
- core
2007 Jun 21
2
[nut-commits] svn commit r971 - in trunk: . drivers
> Author: aquette
> Date: Thu Jun 21 07:43:46 2007
> New Revision: 971
>
> Log:
> fix communication lost status handling
>
> Modified:
> trunk/ChangeLog
> trunk/drivers/usbhid-ups.c
>
> Modified: trunk/ChangeLog
> ==============================================================================
> --- trunk/ChangeLog (original)
> +++ trunk/ChangeLog
2007 Jan 26
1
newhidups output for Geek Squad GS1285U
This took a long time because I had problems with my system. After I
reloaded my operating system several times I found I had a bad memory
module.
Here is the output from newhidups for my Geek Squad GS1285U. It just
kept repeating until I hit ctl-z. I think that this means nut will work
for this ups. My computer is not powered by the ups yet. I did not want
it to be powered down by accident.
2014 Dec 11
2
06da:0002 Phoenixtec Power Co., Ltd UPS
Hi! Charles.
This is the output with 'explore'
# ./usbhid-ups -DDDD -u root -x explore -x vendorid=06da -a CENER_LA900_usb
Network UPS Tools - Generic HID driver 0.37 (2.6.4)
USB communication driver 0.32
0.000000 debug level is '4'
0.000676 upsdrv_initups...
0.288980 Checking device (06DA/0002) (008/004)
0.316956 - VendorID: 06da
0.317057 - ProductID: 0002
2011 Jun 28
1
[nut-commits] svn commit r3104 - branches/apcsmart-dev/drivers
Citeren Michal Soltys <msoltyspl-guest at alioth.debian.org>:
> @@ -417,10 +414,12 @@
> if (flags & SER_CC) {
> iset = IGN_CCCHARS;
> aset = "";
> + sec = 6; usec = 0;
> }
> if (flags & SER_CS) {
> iset = IGN_CSCHARS;
> aset = "";
> + sec = 6; usec = 0;
> }
>
> memset(buf, '\0', buflen);
2006 Jul 06
1
tracing a problem with newhidups
Hi. I'm having trouble with nut-2.0.3 on a linux kernel 2.4.32 machine and a
MGE Evolution 3000. The problem is that I'm getting the following message,
repeatidly, on dmesg:
usbdevfs: usb_submit_urb returned -22
(-22 means -EINVAL)
I traced the problem with newhidups -DDDDDD auto and found out that the -22
error appears in a line "none (-22)" of the output as:
----------
2017 Mar 02
1
Copeland Engineering Dockmaster
On 3/2/17 10:02 AM, Charles Lepple wrote:
> Can you provide a pointer to details on the usbhid-dump tool? Not
> familiar with that one.
I'm using Ubuntu 14.04 Server on an i686 Dell/Wyse CX0 thin-client -
usbhid-dump was available as part of usbhid-utils, if I am not mistaken.
https://github.com/DIGImend/usbhid-dump
> Depending on how much of the Power Device Class (PDC) HID
2006 Feb 27
1
MGE Nova 1100 using newhidups on netBSD 3.0
Have recently purchased a MGE Nova 1100 UPS and am trying to get running on
netBSD.
Configuration
netBSD 3.0 amd64
libusb 0.1.10a
nut 2.0.3
Built & installed libusb
Built kernel with ugen device and uhid removed
Build & install nut-2.0.3 with usb
Chmod /dev/ugen1 etc to allow access by nut user.
Ups.conf
[MGENova]
driver = newhidups
port = auto
2006 May 02
5
Newhidups gets unbound after a while
Hi everybody,
If we let the feature running, it appears that the driver gets unbound
after a while ( variable from quarter of hour to 6 hours ) and cannot
reconnect.
This behavior appear with both MGE Ellipse ASR and non-ASR models with
connection to an UHCI and OHCI controllers.
The USB core is from 2.4.28 kernel.
We use nut-2.0.3.
Start, powerfail and recovery detections, UPS shutdown work
2015 Apr 05
2
nutdrv_qx hangs after send: QS
Thank you for the rapid response. I will try and investigate getting
answers to some of your points but I'm a little new to Solaris so I'll need
some time. Glancing at the configure output, it looks like it built against
v0.1.7 of libusb (yes i think that is derived from the one you mention),
checking for libusb version via pkg-config... 0.1.7 found
checking for libusb cflags...
checking