Displaying 20 results from an estimated 400 matches similar to: "CyberPower usbhid-ups continuously disconnects/reconnect"
2013 Sep 01
0
System Shutting Down Shortly After Boot, COMMBAD, "Writing Error", "Data Receiving Error"
I've been having a problem with my system during boot, which results in a
upsd/upsmon COMMBAD event shutting the system down shortly after it is
started. The shutdown is dependent upon the number of processes started at
boot time, and their load. Fewer processes and lighter load, and there is
no shutdown. More processes and heavy load cause upsd/upsmon to shut the
system down shortly after
2007 Feb 25
2
Success with newhidups - Dynex DX-800U
Just wanted to report that I have successfully got a Dynex DX-800U UPS
functioning with the newhidups driver. This UPS appears to be made by
CyberPower Systems and I believe is the same as the CPS 800AVR.
---------
# upsc dynex@localhost
battery.charge: 66
battery.charge.low: 10
battery.charge.warning: 20
battery.runtime: 399
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 19.7
2006 Nov 11
1
Help with newhidups subdriver for Dynex UPS
Hello everyone!
If this message was posted twice, my apologies. I'm having issues with my webmail today...
I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to
2014 Aug 08
2
Cyberpower Value1200E might not need 0.667 battery scaling
On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote:
> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote:
>
>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:
2014 Aug 09
0
Cyberpower Value1200E might not need 0.667 battery scaling
On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote:
> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote:
>
>> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote:
>>
>>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage
2014 Aug 11
1
Cyberpower Value1200E might not need 0.667 battery scaling
Attached is the first 32 seconds of the driver output after applying the
patch which fixes the battery scaling problem for this UPS.
Matthew Stapleton
Email: matthew4196 at gmail.com
On 10/08/14 01:27, Charles Lepple wrote:
> On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote:
>
>> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com>
2010 May 10
2
USB problems
I was getting:
"Can't claim USB device [0764:0501]: could not detach kernel driver from
interface 0: Operation not permitted"
so I manually installed the udev rules the source (I installed the
Gentoo ebuild).
I am now getting:
# upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
Using
2011 Jun 07
2
CyberPower usbhid-ups continuously disconnects/reconnects
Hello,
I've had this same model CyberPower connected to a linux server and a
freebsd server.
[root at sensor003 menon]# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus
2019 Dec 11
1
[EXTERNAL] Re: Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting
Thought I'd follow up in case someone else runs into this issue. In the end
what worked for me was tweaking the udev rules. I have had no USB
disconnects or stale data warnings so far. I only used one rule for my UPS:
# /etc/udev/rules.d/62-nut-usbups.rules
SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end"
# TrippLite
# e.g. TrippLite SMART1500LCD - usbhid-ups
2013 Apr 15
1
Bug#705490: Uses deprecated RUN+="socket:"
Source: xen
Version: 4.1.4-2
Severity: important
Hi,
using RUN+="socket:" in udev rules files has been deprecated for a
while. In udev 183 support for that has been removed [1]
>From the NEWS file:
* udev: RUN+="socket:..." and udev_monitor_new_from_socket() is
no longer supported. udev_monitor_new_from_netlink()
needs to be used to subscribe to events.
2019 Dec 10
0
[EXTERNAL] Re: Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting
Charles, thank you for that link to David's earlier message. I tried adding
those udev rules and changing the pollinterval. I need to do some tinkering
but I don't think the part RUN+="/sbin/upsdrvctl stop; /sbin/upsdrvctl
start" is working right. If I manually run the commands then the USB
disconnects stop and there are no kernel messages. Running "sudo
/lib/nut/usbhid-ups
2014 Aug 08
0
Cyberpower Value1200E might not need 0.667 battery scaling
On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote:
> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id: 0764:0501, UPS.PowerSummary.Voltage reports 26.6 for the 24V batteries so when the 0.667
2019 Dec 09
4
[EXTERNAL] Re: Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting
I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite information I can help with, let me know.
David Zomaya
Tripp Lite
________________________________
From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Charles Lepple <clepple at gmail.com>
Sent: Sunday, December 8, 2019 8:36 PM
To: Layne Fowler
2013 Feb 21
3
[PATCH] virtio-blk: emit udev event when device is resized
When virtio-blk device is resized from host (using block_resize from QEMU) emit
KOBJ_CHANGE uevent to notify guest about such change. This allows user to have
custom udev rules which would take whatever action if such event occurs. As a
proof of concept I've created simple udev rule that automatically resize
filesystem on virtio-blk device.
ACTION=="change", KERNEL=="vd*",
2013 Feb 21
3
[PATCH] virtio-blk: emit udev event when device is resized
When virtio-blk device is resized from host (using block_resize from QEMU) emit
KOBJ_CHANGE uevent to notify guest about such change. This allows user to have
custom udev rules which would take whatever action if such event occurs. As a
proof of concept I've created simple udev rule that automatically resize
filesystem on virtio-blk device.
ACTION=="change", KERNEL=="vd*",
2020 Feb 03
4
USB devices with same vendor:product id
Hi,
We have a VM with several USB devices attached. Everything works well, but sometimes, after a reboot of the host, some usb device get a different bus/device number and that prevent the reboot of the VM :
-------
error: Failed to start domain xxx
error: internal error: Did not find USB device 04b9:0300 bus:1 device:5
-------
I guess this is because we have multiple usb devices with the same
2014 Aug 08
2
Cyberpower Value1200E might not need 0.667 battery scaling
I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut
2.7.2, it appears to report battery voltage too low due to the battery
scaling function (In drivers/cps-hid.c). Even though the ups has usb
id: 0764:0501, UPS.PowerSummary.Voltage reports 26.6 for the 24V
batteries so when the 0.667 battery scale is applied that goes down to
17.7V.
upsc output:
battery.charge: 100
2020 Feb 03
0
Re: USB devices with same vendor:product id
Hi Maxime,
Quoting Maxime Accadia (2020-02-03 14:20:47)
> Hi,
>
> We have a VM with several USB devices attached. Everything works well,
> but sometimes, after a reboot of the host, some usb device get a
> different bus/device number and that prevent the reboot of the VM :
> ...
> Any idea on how to handle this case ?
>
> We were thinking about using udev, but it
2008 Apr 14
1
Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi,
I got this error when starting a domU on Centos 5.1 i386,
Device 0 (vif) could not be connected. Hotplug scripts not working.
Why is this happening ? I should restart the machine to see if this
still happends after a fresh network bridge. But it's somehow a
production server, I would like not to restart it, if possible. No domU
is currently running. I could start domUs a week ago.
2012 Aug 19
5
fail to mount after first reboot
I created a 1TB RAID1. So far it is just for testing, no important data
on there.
After a reboot, I tried to mount it again
# mount /dev/mapper/vg00-btrfsvol0_0 /mnt/btrfs0
mount: wrong fs type, bad option, bad superblock on
/dev/mapper/vg00-btrfsvol0_0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or