similar to: Poweroff USP on upsmon FSD

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",

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

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

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 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

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

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, 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

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

rtd at linux-5048:~> lsusb -vvv -d 2a37: Bus 001 Device 005: ID 2a37:5110 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor

Bonjour, Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous) DaneZ _____ From: DaneZ [mailto:david.guillotte@danez.no-ip.org] To: arnaud.quette@mgeups.com Sent: Sat, 08 Jul 2006 23:24:06 +0200 Subject: Fw: INFOSEC 500 XP en USB _____ Bonjour Arnaud, Je me

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)

I just purchased a Newpoint 200894 UPS and I'm interested in getting it going. It seems to use a USB to serial conversion that I'm not sure how to get running. Here's the lsusb -vvv Bus 002 Device 005: ID 0665:5161 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level)

Hi, I have a UPS device that seems to work fine with the blazer_usb driver. (I have guessed the driver by googling up the "Product" usb string 010937). However, it does not appear in the supported list, and I had to manually add a udev rule for granting access to the 'nut' user. Would be nice if the info I provide below could be used to help the project/future users to

Hi, are this UPS supported by any other driver than "richcomm_usb". The device works with richcomm_usb, but only signals online, offline etc. Not voltage, batterylevels etc. Bus 006 Device 009: ID 0925:1234 Lakeview Research Bus 006 Device 009: ID 0925:1234 Lakeview Research Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10

Hi everyone, I'm trying to run a software that relies on an USB protection dongle. Windows sees the dongle as a HID device, and my Debian detects it correctly. Here's the dump from lsusb for that device: Code: Bus 002 Device 002: ID 0e50:0002 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at