similar to: NUT Quit Working

On 9/6/2014 12:47 PM, Charles Lepple wrote: > On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > >> I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), > > Can you be more specific about the changes? Well, I did an automated upgrade (apt-get upgrade), I changed

On Sep 6, 2014, at 4:16 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > Oh, hey! That seems to have worked. I'm sure the UPS got plugged into a different port one of the (many) times the server was removed from the relay rack, and it was on a USB 3.0 port. I moved it to a 1.0 port and everything seems to be working just fine. The specifics of the motherboard and its USB

On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), Can you be more specific about the changes? Key variables: * USB controller information (old and new hardware) * Kernel versions, for both working and non-working setups

Hi All, I bought a USB Bluetooth dongle. However, it's not working for me. Please help, how to debug and get more information as I can not see any error or warning message from system log message. I checked http://thread.gmane.org/gmane.linux.bluez.kernel/22183/focus=22211, however, also find another page

Hello list, ? ?Cannot make Evolution 850 to be recognized, maybe the problem is "Warning: incomplete endpoint descriptor" in lsusb? Details are as follows. NUT installed by download of debian package. Any ideas/suggestions are highly welcome, thanks in advance! --ValenteM = ? ?= ? ? = ? ? = Ubuntu server 12.04.1 LTS (GNU/Linux 3.2.0-35-generic x86_64) sudo dpkg -i

Hi, just try the Unitek Self Protek Mistral 1000ipF with nut and I doesn't work. How can I correctly configure it (if the driver support it). Best regards, In my dmesg: [42953293.620000] usb 1-2: new low speed USB device using uhci_hcd and address 7 [42953293.760000] usb 1-2: no configurations [42953293.760000] usb 1-2: can't read configurations, error -22 [42953293.880000] usb 1-2: new

Hi, I have a powermust with a usb connector. I searched the archive and found this post: http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-April/000816.html Must I abandon hope of controlling this UPS via USB with NUT? Added this line to /etc/udev/rules.d/70-nut-usbups.rules: # OMRON - usbhid-ups SYSFS{idVendor}=="06da", SYSFS{idProduct}=="0003",

Some of my messages never went through since I hit a message size limit. I'm resending them in the hopes they are under the limit. Charles, The lsusb command did not trigger a disconnect. The output of that command is below. I ran "usbhid-ups -a upsunit -DDD &> output.log" and I have attached the /var/log/messages and output.log to this email. Before running this test

Hello I have two completely different UPS that turn out to use the same driver. Both work with blazer_usb my LSUSB says: Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial my lsusb -vd 0665: says: pi at elektra:~ $ lsusb -vd 0665: Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial

Has anyone gotten this model of tripp-lite to work? sudo /usr/local/bin/upsdrvctl -DDDDD -u root start Network UPS Tools - UPS driver controller 2.0.5 Starting UPS: tripplite exec: /usr/local/bin/tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.7 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP

folks, the following is lsusb -v for my 250gb usb hard drive. I note the Protocol line mentions zip: ie bInterfaceProtocol 80 Bulk (Zip) does that mean its one of those USB-ZIP devices ? If so, to the parameters below say anything about the CHS settings needed ? tia, PS - HPA, you were correct wrt what I missed :-} Bus 001 Device 002: ID 1058:0401 Western Digital Technologies,

Hi all! FYI, after some research in your list I think that blazer_usb is the best driver for my Soyntec Sekury A600 UPS (which is not in the hardware supported lists). I connected it with my system using USB port (it also has serial RS-232) This is the report I have: battery.voltage: 13.60 battery.voltage.nominal: 12.0 beeper.status: enabled device.type: ups driver.name: blazer_usb

On 9/22/2020 10:01 AM, David Zomaya wrote: > Can you send me the serial number (at least 1st 12 characters, see: https://www.tripplite.com/support/identify-products) and lsusb -v output for the UPS? > > Thank you, > David Zomaya > Tripp Lite > Oh cool, someone from Tripplite. Serial number 3021EYOSM886901200. lsusb -v for just the Tripplite: Bus 003 Device 057: ID 09ae:2012

I just did a fresh installation of Debian Jessie on one of my servers, but NUT won't configure and install. When I try to install, I get the following: Setting up nut-client (2.7.2-1+b2) ... Job for nut-monitor.service failed. See 'systemctl status nut-monitor.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nut-client, action "start" failed.

Hi everybody, In a christmas sequel I've been offered one of the units mentioned above. I've tried to connect it to my Fedora 8 workstation but rapidly concluded it's not yet supported by NUT. So far, I've decompiled the Java classes of the manufacturer's application and noticed that it's most probably yet another kind of serial protocol through the USB. Since

Hello, I (now) own an Emerson Liebert GXT3 6000VA conected via USB. I've searched the web trying to configure nut (nut-2.6.5-1.el6.x86_64 epel rpm on CentOS 6.3) to monitor the UPS, but couldn't find a successful configuration. I'm running kernel 2.6.32-279.14.1.el6.x86_64. The UPS is connected with an USB cable: Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive

Hi, we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20 lsusb -v: Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor

Hi Leslie, 2014-09-29 17:14 GMT+02:00 Leslie Rhorer <lrhorer at mygrande.net>: > > I just did a fresh installation of Debian Jessie on one of my > servers, but NUT won't configure and install. When I try to install, I get > the following: > > Setting up nut-client (2.7.2-1+b2) ... > Job for nut-monitor.service failed. See 'systemctl status >

Hi Rok, I retired from working on NUT a few months ago, so I don't have the most up-to-date info. But the guys on the nut-upsdev mailing list (cc'd above) are very helpful. Both of your devices (or nearly identical ones) have been seen on the mailing lists before. The Sweex was first mentioned in a message by Eli Wapniarski on 14 Jun 2006 on nut-upsuser, and was most recently discussed

Hi, we bought two Smart-UPS X 1500 FW:UPS 09.1 / ID=20 lsusb -v: Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor