search for: lakeview

Hi all, i've read a thread about this UPS from Peter van Valderen. He tried to develop a driver for this specific type of UPS. I've downloaded nut-2.2.2 and tried to apply the patches (lakeview.patch & lakeview.v2.patch) but both resulted in rejected chunks. I've tried to ./configure with type lakeview and then a make, but the make command fails. Does anybody has any experience with getting this type of UPS working with nut? In the latest version of nut I don't find any r...

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

...thentication process to run as the user requesting to login? Should that be allowed? Another thought is to backport some of the patches proposed for 2.2 that remove krb5_kuserok from the loop. Thank you for any insight. This server is not in production use so I can experiment. May 9 10:54:49 lakeview.ligo-wa.caltech.edu dovecot: auth: Debug: gssapi(jonathan.hanks at SOME.REALM,198.129.xxx.xxx,<qYAkv0zc9wDGgdAT>): Negotiated security layer May 9 10:54:49 lakeview.ligo-wa.caltech.edu dovecot: auth: Debug: gssapi(jonathan.hanks at SOME.REALM,198.129.xxx.xxx,<qYAkv0zc9wDGgdAT>): Negoti...

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 this is the same VID/PID as on this example on the Lakeview Research home page: http://www.lvr.com/usb_on_a_budget.htm We...

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 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSiz...

Hallo all. I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. i tried the blazer_usb <http://www.networkupstools.org/docs/man/blazer_usb.html> driver and others but i didn't succeed. My lsusb says Bus 002 Device 005: ID 0925:1234 Lakeview Research Bus 004 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 004 Device 004: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card Reader Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1...

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 reason to keep both in the tree? I'm pretty sure that this device with the Lakeview Research VID is actually made by Richcomm, as the earlier links po...

...me *.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, or the Lakeview Research VID) from the HAL files. I guess we can leave them in the udev/hotplug files, but eventually we will want to separate them out as well (as discussed previously) -- - Charles Lepple

On Wed, Dec 3, 2008 at 4:05 PM, Arjen de Korte <nut+devel at de-korte.org> wrote: > Citeren Charles Lepple <clepple at gmail.com>: > >> Note that this is the same VID/PID as on this example on the Lakeview >> Research home page: >> >> http://www.lvr.com/usb_on_a_budget.htm >> >> We can include the name "Lakeview Research" in the documentation, but >> we shouldn't lead people astray here. > > Another thing, loosely related to this, is how we are...

I have a Gentoo linux (OpenRC) desktop connected to a UPS, the brand is Vultech, but lsusb gives me this: Bus 003 Device 006: ID 0925:1234 Lakeview Research and I found an article about this hardware here, someone had it working with the richcomm_usb driver: http://verahill.blogspot.it/2012/12/kstar-australia-1500-va-ups-on-debian.html So, I installed nut and configured my UPS to work with the richcomm_usb driver, and everything seems to wor...

...nnel.c:1597 __ast_request_and_dial: Unable to request channel h323/101014037402962@65.17.207.253 Aug 19 09:18:30 NOTICE[-1273607248]: pbx_spool.c:235 attempt_thread: Call failed to go through, reason 0 Callfile: MaxRetries: 2 extension: 9999 Channel: h323/101014037402962@65.17.207.253 CallerID: LAKEVIEW 4037422000 This is my h323.conf file: ; The NuFone Network's ; Open H.323 driver configuration ; [general] port = 1720 bindaddr = 0.0.0.0 disallow=all allow=g723.1 ; Hm... Proprietary, don't use it... allow=g729 dtmfmode=rfc2833 gatekeeper = 65.17.207.253 context=incoming [h323] t...

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

...bit about driver development > but never did any work for NUT or USB devices, so > any advice is very welcomed. > > ===================================================== > Sweex PP100 is reported as: > ================= > # cat lsusb > > Bus 001 Device 004: ID 0925:1234 Lakeview Research > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 >...

...t;2" "Power Pro+ series" "USB" "blazer_usb" "SVEN" "ups" "2" "Power Smart RM 2000" "USB" "blazer_usb" 2. lsusb output Bus 002 Device 001: ID 0000:0000 Bus 002 Device 002: ID 0925:1234 Lakeview Research Bus 001 Device 001: ID 0000:0000 3. My ups.conf [sven] driver = blazer_usb subdriver = krauler #phoenix vendorid = 0925 productid = 1234 port = auto desc = "Power Pro+ 500" 4. I tried both subdrivers: krauler and phoenix TRACE: a) s...

...com> > wrote: > > > > I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. > > > > i tried the blazer_usb driver and others but i didn't succeed. > > > > > > My lsusb says > > > > Bus 002 Device 005: ID 0925:1234 Lakeview Research > > > > It might work with richcomm_usb: > https://lists.alioth.debian.org/pipermail/nut-upsuser/2012-April/007551.html > > but that USB ID on a production device isn't very useful (the equivalent > of the 555-1212 phone number). > > Also, richcomm_usb doe...

...Andreas Cattelan <ilmondodiwit at gmail.com> wrote: > > I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. > > i tried the blazer_usb driver and others but i didn't succeed. > > > My lsusb says > > Bus 002 Device 005: ID 0925:1234 Lakeview Research > It might work with richcomm_usb: https://lists.alioth.debian.org/pipermail/nut-upsuser/2012-April/007551.html but that USB ID on a production device isn't very useful (the equivalent of the 555-1212 phone number). Also, richcomm_usb does not provide much information - it is s...

On Wed, Dec 3, 2008 at 10:19 PM, <clepple+buildbot at ghz.cc> wrote: > The Buildbot has detected a new failure of FreeBSD-6.2-i686. > Full details are available at: > http://buildbot.ghz.cc/public/nut/FreeBSD-6.2-i686/builds/123 Looks like this was the error: ../../drivers/lakeview_usb.c:58: warning: implicit declaration of function `usb_comm_fail' ../../drivers/lakeview_usb.c: At top level: ../../drivers/lakeview_usb.c:86: error: conflicting types for 'usb_comm_fail' ../../drivers/lakeview_usb.c:58: error: previous implicit declaration of 'usb_comm_fail'...

...t;> > I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. >> > >> > i tried the blazer_usb driver and others but i didn't succeed. >> > >> > >> > My lsusb says >> > >> > Bus 002 Device 005: ID 0925:1234 Lakeview Research >> > >> >> It might work with richcomm_usb: >> https://lists.alioth.debian.org/pipermail/nut-upsuser/2012-April/007551.html >> >> but that USB ID on a production device isn't very useful (the equivalent >> of the 555-1212 phone number). >...

...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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth Bus 004 Device 003: ID 10d...