similar to: Confusing Generic USB UPS cannot be matched

I have a Belkin F6H500ukUNV ups that I am attempting to get working under nut, however it does not appear to be detected by nut, I'm assuming that I need to feed some information back to you guys to get it included in the database somwhere. I've included (what I can think might be) the relivant outputs. Please let me know if you require anything else. dmesg output /sbin/newhidsups

Hi Folks, I'm trying to use a ZIGOR Danubio 2000 ups with NUT on Debian squeeze (AMD64). OS/NUT are all the latest official release (as of last week) with NUT installed from packages. As the usb descriptor presents MEC (and the Fry's electronics) I chose to use the blazer_usb driver. All appears to work well excepting that the UPS does not appear to accept the shutdown instcmd to turn

Hello I am using Freenas 11.3 (freebsd like) with a GREENCELL usb ups. with nut 2.7.4_13 pre installed But, this ups is not detected as "blazer_usb" on port "auto" neither "ugen0.4"! Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4) No supported devices found. detail below. Another info : This

Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output

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

Regards I am installing NUT for the UPS Skate UPS-2200D, the UPS have conection with USB to PC and i have problems to configure nut the ups is conected and Linux report this config Aug 19 23:34:56 dakota kernel: [22393.099595] usb 2-2: new low speed USB device using uhci_hcd and address 7 Aug 19 23:35:06 dakota kernel: [22403.186326] usb 2-2: Product: MEC0002 Aug 19 23:35:06 dakota kernel:

Hello, I am trying to get a "no-brand" (LMS DATA, model no LMSP1200RI) UPS to work with NUT. I now realise I should have checked compatibility with NUT before purchase. My other UPS (APC) works perfectly..... Anyway, I have spent a good day trying to get this thing working. #lsusb Bus 001 Device 003: ID 0001:0000 Fry's ElectronicsDevice Descriptor: bLength 18

Hi, Has anyone had success with the Dynamix 650VA, that uses the USB cable? I can't get megatec_usb to recognize it, I have tried both stable and development versions. Regards Glen Ogilvie

Hi, This is my first post ever on a technical forum, so please forgive any poor etiquette etc. Also I'm totally new to Linux all of my experience has been trying to get this UPS to work. So please bear this in mind. I'm running OpenSuse 13.1 and I have a Lupus 500 USB (Fideltronik) After quite a bit of playing around I managed to get the status of the UPS using the blazer_usb driver and

On Sep 8, 2016, at 8:14 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > Hi again, > > Thanks for the prompt reply. > > Just for the record i am running debian unstable/sid with nut 2.7.4-3 > Thanks, that is useful. > 0.447725 refresh_report_buffer: expected 13 bytes, but got 8 instead This is the first sign of trouble. > 0.447736

I just received my dev kit and installed the hardware. I followed the directions Digium sends out to the letter and when I ran modprobe tor2 I got the following error: /lib/modules/2.4.18-19.7.x/misc/tor2.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the

Hello to all list members, I'm trying to make my UPS work with nut-2.2.2 (using Debian Testing, but compiled from source code) for a week ago, with not success. It's a Unitek Alpha 1000Ps, and I supossed it would work with megatec_usb driver, as other Unitek models. It has an USB interface, and when I plug it into my system I've got this message: chopito:/home/jordi# dmesg | tail

[snip hex dump analysis] > > It is possible that the blazer_usb driver initialization has put the UPS > into a bad state. If you can schedule some downtime, you might want to try > usbhid-ups again after powering the UPS down completely and unplugging it > for a little while. (Often, a few seconds after the output is off and the > AC has been removed, you will hear relays

Hello guys! I hope you bare with yet another newbie on the list! :-) I am trying to setup an asterisk installation in between a Siemens HiPath 3800 and my local carrier (Telefonica/Brazil). Both running R2. ISDN is not an option on the carrier. :-( I could apparently setup both E1s just fine according to zttool (both OK with no alarms) but, and this is where it starts to get

The following two patches allow the parallel use of memsharing, xenpaging and xen-access by using an independent ring buffer for each feature. Please review. v2: - update mem_event_check_ring arguments, check domain rather than domain_id - check ring_full first because its value was just evaluated - check if ring buffer is initialized before calling mem_access_domctl/mem_paging_domctl

Followed the "instructions" on voip-info.org regardinging fedora FC2, making Zaptel seems to work fine, however when I modprobe I get this. It looks like a version mismatch somehow. Ideas? If this ooc, sorry first post here :-) modprobe tor2 WARNING: Error inserting zaptel (/lib/modules/2.6.5-1.358smp/misc/zaptel.ko): Invalid module format WARNING: Error inserting zaptel

Hi list, I have a asterisk box with an E400P that was running ok until last week. The machine just stop responding and after a reboot, the module (tor2) doesn't load anymore. anyone could help? regards Eduardo modprobe returns this: asterix:~# modprobe tor2 Zapata Telephony Interface Registered on major 196 Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xfe121800/0xfe121000 irq 7

Hello, I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601. I have seen that people had some success using megatec driver. But now megatec is replaced by blazer-usb and I am not able to use my upses under nut. Can you help me? Thanks! Mario

Hi all... I did some Google searches and didn't find any info on this so I'm posting it here... if this was recently discussed, I apologize for the duplication -- please point me to the appropriate thread. System Description: Supermicro SuperServer 5015M-MF w/ PDSMi Motherboard Intel Pentium 4 2.8 Ghz CPU 2 GB DDR2 Memory Digium T400P 4 Port T1 Card CentOS 5.1 (Final) Kernel:

Hey all, ? I'm trying to get an E400P and 2 X100Ps working together in the one box and don't seem to be having much luck. ? I can get the two different types of boards working separately, but not together.? I've made calls on both the X100P and have seen sync and correct signalling on the E400P.? But when I try to enable to configs together I get the following: ? modprobe wcfxo