search for: 5161

...6r PIPE 0xcb0006c0 16384 ->0xcc08b2d0 dovecot-a 22627 root 7w PIPE 0xcc08b2d0 0 ->0xcb0006c0 dovecot-a 22627 root 12r VCHR 46,1 0t1024 45571 /dev/urandom ---------- COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 5161 root cwd VDIR 0,6 512 405514 /var/run/dovecot dovecot 5161 root txt VREG 0,5 119872 1109297 /usr (/dev/wd0f) dovecot 5161 root txt VREG 0,0 866469 67587 /lib/libc.so.12.125 dovecot 5161 root txt VREG 0,0 56172 101377 /libexec/ld.elf_so...

...PowerShield Defender 1200VA UPS working and it appears to be supported by the blazer_usb driver, although it did not have the correct permissions within udev to load the driver as the non-root user after an RPM install on Fedora Core 16. [root at localhost ~]# lsusb ... Bus 006 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial [root at localhost ~]# dmesg | grep usb [1034160.810062] usb 6-3: new low speed USB device number 5 using ohci_hcd [1034160.963157] usb 6-3: New USB device found, idVendor=0665, idProduct=5161 [1034160.963166] usb 6-3: New USB device strings: Mfr=1, Product=2,...

...ntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status > > The product information PDF for the device in quesetion is http://www.powerwalker.com/datasheet/Line-Interactive/PowerWalker%20VI%201500%20LCD.pdf > [...] > > $ lsusb > [...] > > Bus 004 Device 006: ID 0665:5161 Cypress Semiconductor USB to Serial > > ^ This is most likely your UPS. Yea, I disconnected the cable to check and there are also no other USB devices on that computer. I also tried to plug it in some other port, just in case that would help. > Josu Lazkano just emailed this list last m...

...ss/input/input4 input: USB HID v1.00 Gamepad [WayTech Development(S) WayTech USB-RS232 Interface (V1.0) Baud rate 2400bps] on usb-0000:00:1d.1-2 So, apparently, it has an USB-HID interface. Output from lsusb: chopito:/home/jordi# lsusb Bus 005 Device 001: ID 0000:0000 Bus 002 Device 004: ID 0665:5161 Bus 002 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 chopito:/home/jordi# lsusb -vvv -d 0665:5161 Bus 002 Device 004: ID 0665:5161 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB...

.... What is the exact NUT package version (including the Ubuntu-specific version number)? > The product information PDF for the device in quesetion is http://www.powerwalker.com/datasheet/Line-Interactive/PowerWalker%20VI%201500%20LCD.pdf [...] > $ lsusb [...] > Bus 004 Device 006: ID 0665:5161 Cypress Semiconductor USB to Serial ^ This is most likely your UPS. Josu Lazkano just emailed this list last month with a similar problem (NUT 2.6.4 on Debian): http://thread.gmane.org/gmane.comp.monitoring.nut.user/8180 There should be an entry in /lib/udev/rules.d/52-nut-usbups.rules for 066...

...matching HID UPS found Driver failed to start (exit status=1) I followed a thread with the same title, more or less, having permission problems. I applied that solution. My problem seems different. # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 002 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business Bus 002 Device 002: ID 1c4f:0065 SiGma Micro Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub When I unplug the USB cable from my Easton 5L 600VA USB # lsusb Bus 001 Devic...

...: usbfs: process 10804 (blazer_usb) did not claim interface 0 before use ups.conf: maxstartdelay = 70 norating novendor subdriver = cypress [eaton_1] driver = blazer_usb port = "002" desc = "Eaton NV 2000H" vendorid = 0665 productid = 5161 bus = "003" [eaton_2] driver = blazer_usb port = "002" desc = "Eaton NV 2000H" vendorid = 0665 productid = 5161 bus = "004" [eaton_3] driver = blazer_usb port = "003&qu...

...thing: cidsignalling=v23 cidstart=polarity If I comment them out, no problem. It works, but not CID. I get the following log entries: *CLI> == Starting post polarity CID detection on channel 5 -- Starting simple switch on 'Zap/5-1' Sep 30 19:04:29 NOTICE[1111234112]: chan_zap.c:5161 ss_thread: Got event 2 (Ring/Answered)... Sep 30 19:04:32 NOTICE[1111234112]: chan_zap.c:5161 ss_thread: Got event 2 (Ring/Answered)... Sep 30 19:04:35 NOTICE[1111234112]: chan_zap.c:5161 ss_thread: Got event 2 (Ring/Answered)... Sep 30 19:04:38 NOTICE[1111234112]: chan_zap.c:5161 ss_thread: Got ev...

..., try running the driver with at least 'subdriver', 'vendorid' and 'productid' options specified. Please refer to the man page for details about these options (man 8 blazer). $ lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 006: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Thanks for any help or guidance you can give me, Shinhan --------------...

...ze the algorithm of the filter function, solution #2 below, for the case of the rep(1/k,k) kernel? Thanks, Vadim [R] Survey of "moving window" statistical functions - still looking f or fast mad function * This message: [ Message body <http://tolstoy.newcastle.edu.au/R/help/04/10/5161.html#start> ] [ More options <http://tolstoy.newcastle.edu.au/R/help/04/10/5161.html#options2> ] * Related messages: [ Next message <http://tolstoy.newcastle.edu.au/R/help/04/10/5162.html> ] [ Previous message <http://tolstoy.newcastle.edu.au/R/help/04/10/5160.html> ] [ Ne...

...t for drivers megatec_usb and blazer_usb: =========================================================== gate# /usr/local/libexec/nut/megatec_usb -DDDD -a IPPON Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) Serial-over-USB transport layer 0.10 debug level is '4' Checking device (0665/5161) (/dev/usb1//dev/ugen0) - VendorID: 0665 - ProductID: 5161 - Manufacturer: Cypress Semiconductor - Product: USB to Serial - Serial Number: unknown - Bus: /dev/usb1 Trying to match device Device matches DTR=1, RTS=0 Starting UPS detection process... Asking for UPS information [I]... I => FAILED [...

Hello, i try to setup NUT service to read/control my UPS but without success. Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: /Network UPS Tools - UPS driver controller 2.6.2/ / 0.000000/ /If you're not a NUT core developer, chances are that you're told to enable debugging/ /to see why a driver

On Jan 2, 2012, at 10:51 AM, Vladimir Micovic wrote: >> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > Unfortunately, this device ID is used by several different vendors. What does "lsusb -vvv -d 0665:5161" show? > Also, what OS and kernel are you using? (I thought certain kernels had USB-to-serial drivers for that chip.) > -- > Charles...

...e CD :) >>> http://www.power-software-download.com/viewpower.html >>> >>> But I was wondering if NUT can work with the UPS. >>> And it seems ?POWEREX VI 1000 LED? can work with ?blazer_usb? driver (see >>> below) >>> >>> # lsusb -d 0665:5161 >>> Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial >>> >> >> well, though it won't be as good as an Eaton (standard disclaimer ;-), >> this one should indeed be supported by the blazer drivers. >> >> Not fully sure if it'...

Hi Sven, 2008/1/25, Sven Koch <haegar at sdinet.de>: > Package: nut > Version: 2.2.1-1 > Severity: normal > > I am using a Mustec PowerMust 1000 USB, connected with a USB cable to > the PC. > > With nut 2.2.0-2.1 everything works without problems - but since the > 2.2.1-1 update the "upsdrvctl start" from the init script just fails, > executing the

...ked and all of the rules have MODE=664. I had concerns that the MODE parameter might need an explicit leading "0" for octal, but at least in the latest code, it is being parsed with strtol(..., 8). > Also, I don't know how to check which rules could match it. Maybe 'grep -r 5161 /etc/udev/rules.d /lib/udev/rules.d'? That might produce a few false positives. -- Charles Lepple clepple at gmail

Hello i need your help regarding the following issue : i have a hero touch ups from infosec. it is connected via USB to a raspberry pi 3. i?ve configure ups.conf file as below [HERO] driver = blazer_usb vendorid = 0665 productid = 5161 either with port = auto or port = /dev/hidraw0 or port = /dev/ttySo the connection never works i get the following log from command line : sudo /lib/nut/blazer_usb -a HERO -DDD -u root Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) 0.000000 debug level...

...and megatec_usb. I've tried both the 2.0.5 version in apt for Ubuntu fesity and compiling my own 2.2. All report not being able to find the driver. Relevant bit of /proc/bus/usb/devices included below and the result of usbhid-ups -DDDD -a belkin -u root -x explore -x vendorid=0665 -x productid=5161 (/dev/hiddev0 seems to disappear after I run this). Regards, Cian Davis /proc/bus/usb/devices T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0665 ProdID=5161 Rev= 0.02 S: Manufacturer=Cypress Semiconduc...

...100 /var/lib/dpkg/status debian version: root at raspberrypi:/home/pi/deb# cat /etc/debian_version 8.0 my /etc/nut/ups.conf looks like this: [PW1500LCD] driver = blazer_usb port = auto desc = "PowerWalker VI 1500 LCD" running lsusb gives: Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and /lib/udev/rules.d/52-nut-usbups.rules...

...P EP 850 with usb connection (http://www.fsplifestyle.com/product.php?LID=1&PSN=74) NUT installed from official repository, version: nut-2.6.3-2.fc16.x86_64. ups.conf: [EP850] driver = blazer_usb port = auto desc = "FSP EP 850" vendorid = 0665 productid = 5161 Output of command lsusb -v -d 0665:5161: Bus 004 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass...