similar to: ambiguous USB IDs (was: [nut-commits] svn commit r1589 - in trunk: . drivers)

On Mon, Dec 1, 2008 at 7:43 PM, Alexander Gordeev <agordeev-guest at alioth.debian.org> wrote: > Author: agordeev-guest > Date: Tue Dec 2 00:43:04 2008 > New Revision: 1589 > > Log: > * added lakeview_usb driver. Could we possibly rename this driver before it gets into 2.4? As I mentioned in another thread, Lakeview Research is probably not the manufacturer. Note that

Citeren Charles Lepple <clepple at gmail.com>: >> Another thing, loosely related to this, is how we are going to deal with the >> 'generic' VID:PID combinations in some of the USB drivers, for example the >> megatec_usb and (new) blazer_usb drivers. At present, in the megatec_usb >> driver we have several VID:PID combinations for USB-to-serial converters

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

On Thu, Dec 4, 2008 at 4:51 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Thu Dec 4 21:51:28 2008 > New Revision: 1596 > > Log: > Added new richcomm_usb driver based on the lakeview_usb driver (using libusb). Sorry if I wasn't clear - I was advocating *renaming* the lakeview_usb driver to richcomm_usb. Is there another

Alexander Gordeev wrote: > Author: agordeev-guest > Date: Mon Aug 13 13:09:43 2007 > New Revision: 1049 > > Log: > drivers/megatec_usb.c: added credits to the banner message. Is this really needed/desirable? I think this kind of information needs to be put in the AUTHORS document. There are many more people on this list that put a lot of effort in NUT, without claiming credit

Hello, all. Some time ago I bought myself a UPS which was advertised as USB-HID. It was a surprise to learn that while it definitely is recognized as USB device, the HID descriptor has no UPS pages at all. The only software it came with was a windows program written in visual basic. Trying to research this topic I found a reference to energizer USB ups driver and learned about variety of

Does this require a new entry in scripts/hotplug/* and scripts/udev/*? -- Peter Alexander Gordeev wrote: > > Author: agordeev-guest > Date: Sat May 26 12:04:26 2007 > New Revision: 924 > > Log: > data/driver.list: added SVEN Power Smart RM 2000 to the list. > > Modified: > trunk/ChangeLog > trunk/data/driver.list > > Modified: trunk/ChangeLog >

Hi Jon, your patches are malformed because (presumably) your email client wrapped this lines. Could you please send these as a unified diff ("diff -u"), and send them in attachments, rather than as a copy-and-paste? Thanks, -- Peter Jon Gough wrote: > > Peter, > Here are the files I have worked on. I hope I have diff'd them > correctly. I have not touched the

Arnaud, should we move tools/ up to the beginning of the subdirectory list? It seems that it is writing some *.in files during 'make dist', which should undergo variable substitution. (There will probably be other dependency issues to resolve, but that would be the first step.) On a related note, I would like to add some code to nut-usbinfo.pl to blacklist bogus vendor IDs (e.g. 0x0000,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good day to all. In one of the offices I'm administering there are about 15 UPS marked with the brand "Ippon BackPro". This brand is widely popular in Russian Federation, while by itself is a 'Made in PRC' megatec clone. Depending on the model this UPSes have got either one standard serial RS-232C interface (cheaper models like

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

On 1/23/07, Henning Brauer <hb-nut@bsws.de> wrote: > good new first: the megatec driverin 2.0.5 now works with the Online > Xanto S3000R here - well, for the very basics. > > the UPS has NO way ofidentifying itself. It also does not respond to > the power ratings query ("F"). I previously used a hacked up fentonups > driver. This means the driver cannot figure out

Hi, Sorry for the forwarding. I sent this with the wrong "from" address and got rejected by the list. ---------- Forwarded message ---------- From: Carlos Rodrigues <cefrodrigues at mail.telepac.pt> Date: Jun 18, 2007 9:34 PM Subject: Re: Megatec - modem control lines [impact to megatec_usb] To: Arjen de Korte <nut+devel at de-korte.org> Cc: ups-dev-list <nut-upsdev at

Hi. I'm from Russia. I try to use NUT with PowerWalker vi 400 se (usb). I use FreeBSD 7.0 (amd64) and megatec_usb driver. Settingup the NUT with FreeBSD installation procedure (Thierry Thomas, from FreeBSD). PowerWalker connect to the computer by usb cable on port usb0 (uhib0). NUT don't starting, and talk to me that supporting device not found. Please, help me. Thank's! With best

I have an UPS, that claims to be IPPon Back Power Pro 700. I'm trying to connect it using USB. lsusb -v says: Bus 1 Device 3: ID 06da:0003 Phoenixtec Power Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0

Hi Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the

hi, i've bought a 750VA orvaldi ups http://en.orvaldi.com/index.php/en/product_catalog/product_view/11/162 which holds my hardware (wifi router, cable modem, quad-core with raid and lcd monitor) for ~15 minutes. pretty nice result for a cheap (~57 euro) home ups. in fact, the vendor software for linux is very old (e.g. requires ancient redhat with qt2), requires db9 port while shipped

----- Forwarded Message ---- From: Terry Powling <terrypowling at yahoo.co.uk> To: nut-upsuser at lists.alioth.debian.org Sent: Sat, 27 February, 2010 22:30:05 Subject: trouble setting up kebo-1000d ups (usb) Trying to setup Kebo ups-1000D with usb port. lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0925:1234 Lakeview Research Bus 002 Device

On Nov 26, 2007 6:38 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Mon Nov 26 18:38:18 2007 > New Revision: 1164 > > Log: > Allow longer commands in the 'phoenix' subdriver. > > Modified: > trunk/ChangeLog > trunk/drivers/megatec_usb.c FYI, the shutdown still doesn't work. -- Carlos Rodrigues