Displaying 20 results from an estimated 1000 matches similar to: "[nut-commits] svn commit r1589 - in trunk: . drivers"
2008 Dec 04
2
ambiguous USB IDs (was: [nut-commits] svn commit r1589 - in trunk: . drivers)
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
2008 Dec 05
1
[nut-commits] svn commit r1596 - in trunk: drivers man tools
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
2007 Nov 20
2
Mustek Powermust 600VA
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
2007 May 20
1
Sweex 1000VA UPS (was: powermust usb)
--- 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
2007 May 20
1
Sweex 1000VA UPS (was: powermust usb)
--- 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
2008 Dec 04
0
[nut-commits] buildbot failure in FreeBSD-6.2-i686
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'
2008 Nov 30
4
Sweex 1000VA UPS (Lakeview Research)
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
2007 Aug 13
2
[nut-commits] svn commit r1049 - in trunk: . drivers
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
2007 May 26
3
[nut-commits] svn commit r924 - in trunk: . data
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
>
2007 Feb 08
3
Re: [nut-commits] svn commit r801 - in branches/megatec-usb: . drivers
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
2007 Oct 03
2
[nut-commits] svn commit r1136 - in trunk: . drivers
> Author: agordeev-guest
> Date: Wed Oct 3 00:09:21 2007
> New Revision: 1136
>
> Log:
> - drivers/megatec_usb.c: added ability to do subdriver-specific
> initialization, and moved some shared code to agiler init function
> since krauler doesn't need it.
[...]
I'm not very thrilled about this patch:
1) Down at the subdriver level, one shouldn't use
2007 Sep 24
2
Debugging DCOM for Future Pinball
With current wine version, Future Pinball (a free pinball simulation)
needs native DCOM98.EXE to run.
What are the necessary debug channel that could help to debug DCOM ?
LvR
2012 Apr 19
1
Trust UPS Oxxtron 1300VA (17679)
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
2008 Dec 14
1
order of subdirectories and nut-usbinfo.pl
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,
2010 Oct 12
2
Factors in an regression using lm()
Hi,
I am trying to do a multiple regression on the dataset "Hdma", available in
the Ecdat package.
The data looks like this:
> str(Hdma)
'data.frame': 2381 obs. of 13 variables:
$ dir : num 0.221 0.265 0.372 0.32 0.36 ...
$ hir : num 0.221 0.265 0.248 0.25 0.35 ...
$ lvr : num 0.8 0.922 0.92 0.86 0.6 ...
$ ccs : num 5 2 1 1 1 1 1 2 2 2
2016 Jan 22
2
UPS Trust OXXTRON 1300VA not working
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
2013 May 09
1
Crossrealm Kerberos problems
I am running dovecot 2.1.7 on Debian Squeeze 64 bit, config information
at the end of the email.
I am working on a Kerberos/GSSAPI based setup that requires cross-realm
authentication. I have regular GSSAPI working, I can log in using
pam_krb5 with password based logins or with the GSSAPI support when
using a kerberos ticket in the default realm.
However when I attempt to authenticate using
2017 Sep 02
3
Problem with upsmon?
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
2004 Aug 23
1
H323 outgoing calls
Does asterisk support using an H.323 provider for outgoing calls? From
everything I have found, it looks like it does. However, I have had no
success in getting it to work. I would really appreciate if somebody
could give me a hand. I am using the channel that comes with asterisk.
I have also tried using the channel from inaccessnetoworks but have not
had any more success. My provider
2008 Dec 04
1
ambiguous USB IDs
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