similar to: nut and megatec_usb

I recently purchased a Tripp Lite OmniSV1500XL and I've had no luck getting nut to work. # lsusb Bus 001 Device 001: ID 0000:0000 Bus 006 Device 002: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter Bus 006 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000 Bus 004 Device 009: ID 09ae:0001 Tripp Lite Bus 004 Device

One small comment: When the driver has no permission to access the device, it exits with a segmentation fault, it would be nice to have a more informative error. I'm not really sure if the issue is speciffic to this driver or is it general. I attached the output of an strace with the driver crashing. Best regards. -------------- next part --------------

after I starting battery test on my laptop I see in my logs some error and ups (IPPON Smart Power Pro 1400. usb interface) isn't monitoring now [ippon] driver = megatec_usb port = auto desc = "local" Feb 16 23:22:09 f37 upsd[17150]: Instant command: stlk at 127.0.0.1 did test.battery.start on ippon Feb 16 23:22:12 f37 megatec_usb[17249]: ser_get_line: Device detached? (error

Hello, I am having a problem with Samba 3.0.4 and DOS clients. The MSDOS COPY command will not work on mapped directories. When I try to run the COPY command I get an "File not found" error message. This only happens on DOS, all other OS's work fine. I have noticed that someone else on this list has also run into this problem, but no answer/work-around is posted. Here is my

Hi, In btrfs, inode number is increased each time a new file or directory is made. Therefore, if the making deletion of the file is repeated, value of ''i_ino'' increases rapidly. For example, inode number changes as follows. $ touch foo $ ls -i foo 266 foo $ rm foo $ touch bar $ ls -i bar 267 bar $ And then, length of ''i_ino'' and

I just did a bit of testing on OpenBSD and there the above setup seems to work and I can remove the files just fine over sftp. So this thing should work but there's still something causing it to fail on CentOS's side. One difference between our CentOS and OpenBSD is that OpenBSD uses newer openssh server. I looked through the release notes and didn't see any changes related to

On Jan 12, 2014, at 11:07 AM, Ariel Wainer wrote: > On 11/01/14 15:27, Charles Lepple wrote: >> On Jan 10, 2014, at 4:46 PM, Ariel Wainer wrote: >> >>> On 10/01/14 01:53, Charles Lepple wrote: >>>> I am curious about why the Interrupt Out packet is sent by the Windows software if it isn't to turn off the UPS. Is it possible to do some more testing with

Hi. While debugging some encfs errors in the logs, I realized they are being generated because rsync (chrooted inside a encfs file system, --reverse) is trying to access files like: /root/.popt, /etc/localtime etc. This doesn't seem to be related to ID-name mapping as I already have numeric ids enabled in config. Here is the relevant strace output: [pid 25549] chroot("/chroot")

Hi Alexey, Please post the output of 'lsusb' and 'megatec_usb -a sven_625 -u nut -DDDDD'. On Monday 15 June 2009 14:32:16 you wrote: > Package: nut > Version: 2.4.1-3 > Severity: normal > > I have a SVEN Pro+ 625 ups that uses megatec_usb driver. > In ups.conf I describe it like: > [sven_625] > driver = megatec_usb > port = auto > desc =

2010/10/18 Michael Eitelwein > Hi Arnaud > Hi Michael, > Yes, did test it without success. > can you please post the first 20 seconds running blazer_usb in debug mode, ie: $ sudo /lib/nut/blazer_usb -DDD -a cyberpower aside from fixing the megatec situation, ensuring that you'll be able to run the replacement is also to be considered ;-) now, for the megatec issue, we need

Hello again! Thanks to the precious help from Henning Brauer, I managed to solve an issue with my UPS (a rebranded UPS speaking in Ablerex-ese over USB). Under OpenBSD 4.3, the UPS was claimed by HID. Now that I recompiled the kernel, adding a USB_quirk, this is what I get when I insert the USB cable: ugen0 at uhub0 port 2 "UIS_ABLER USB to Serial" rev 1.00/1.00 addr 2 So far, so

Hey all, thanks for your work on nut. I recently got myself a new cheap UPS, and have thus far determined very little about it. I can run whatever you like to help identify and work with it. So far I've played around with various settings and have had some limited success with the megatec_usb driver (Debian testing version): ----ups.conf---- [plexus] driver=megatec_usb model=500VA mfr=Plexus

Hi, Just purchashed this UPS. The megatec_usb driver appears to be communicating with the UPS - however, the ups.status field always states "off" /usr/local/ups/bin/megatec_usb -a plexus -DD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c)

Hi, Just purchashed this UPS. The megatec_usb driver appears to be communicating with the UPS - however, the ups.status field always states "off" /usr/local/ups/bin/megatec_usb -a plexus -DD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c)

Citeren Roman Mamedov <roman at rm.pp.ru>: >> Another useful thing would be to run the bundled driver on a Windows >> box while running 'usbsnoop' so that we can get an idea what it is >> doing. Maybe we're missing something here. I still would like to see that. > Keep in mind that the patched megatec_usb driver (which I use since > yesterday) can

Hi everyone, I have a belkin ups that was bought around 2 months ago. It seems like the driver doesn't like the UPS, although on the website it's listed as supported. This is on a gentoo system with nut 2.2.1 . megatec_usb output: ---------SNIP---------- digamma nut # ./megatec_usb -a belkinm -DDDDDD Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb] Carlos Rodrigues

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Trying to use it with Sven Smart RM2000 (seems to be an OEM clone of Sysgration Smart RM UPS: http://www.sysgration.com/product.asp?KID=7). I have just compiled the latest svn trunk. Unfortunately it does not work with that UPS: dbely at vserver1:~/nut-svn$ sudo /usr/local/ups/bin/megatec_usb -u root -a myups Network UPS Tools 2.1.0 - Megatec protocol driver 1.5.3 [megatec_usb] Carlos Rodrigues

Hi Bj?rn, 2009/10/9 Bj?rn Torkelsson > Public bug reported: > > Binary package hint: nut > > I have recently upgraded from hardy to intrepid to jaunty. After > upgrading to Intrepid the megatec_usb stopped recognizing my Trust PW- > 4130M ups, it still does not work on Jaunty. It worked without any > problems in hardy. > > I tried the megatec_usb driver from hardy