similar to: New sub-driver submission process timeframe?

On Mar 6, 2015, at 4:40 PM, Rob Groner <rgroner at RTD.com> wrote: > So, if I write my own subdriver for our UPS?how quickly can I expect that it will be incorporated in some downloadable version of nut that a user can then use? I'm struggling a bit to provide a useful answer that doesn't sound dismissive ("sometime soon") but explains what we're up against. At the

I don't have any problem with pointing customers to a branch they can clone via git and compile. But until that's available, I will do what you suggested (and what my boss has been suggesting for a while) which is to take 2.7.2 and put our driver in it nice and happy and then package that up for our customer to use. That will be a more than sufficient means to get our UPS working until

Is there a specific file with the version number in it that I would modify, or do you just mean the file names? Sincerely, Rob Groner From: Charles Lepple [mailto:clepple at gmail.com] Sent: Monday, March 09, 2015 9:23 AM To: Rob Groner Cc: nut-upsdev at lists.alioth.debian.org Subject: Re: [Nut-upsdev] New sub-driver submission process timeframe? On Mar 9, 2015, at 9:09 AM, Rob Groner

On Mar 9, 2015, at 9:09 AM, Rob Groner <rgroner at RTD.com> wrote: > I don?t have any problem with pointing customers to a branch they can clone via git and compile. I know this sounds pedantic, but while the snapshots correspond to specific branches and commits in git, they are simpler for end users to build than the git branches, since they include the ./configure script and a few

Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c

On Mar 9, 2015, at 9:55 AM, Rob Groner <rgroner at RTD.com> wrote: > Is there a specific file with the version number in it that I would modify, or do you just mean the file names? The canonical place is in configure.ac, and everything else gets regenerated if you rerun autogren.sh That script, by the way, calls "autoreconf -i" which includes the --add-missing flag that I

Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid driver, I'll revisit writing our own. Thanks for the helps. Sincerely,

On Mar 2, 2015, at 12:49 PM, Rob Groner <rgroner at RTD.com> wrote: > Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid

This doesn't seem to be my day for getting things to work right.... The most obvious place I could find to change the version number was near the top: AC_INIT(nut, 2.7.2) I changed to AC_INIT(nut, 2.7.2_RTD) However, I cannot find "autogren.sh" anywhere, whether in the nut dir or as a system executable. I also tried "autogen.sh" in case that was a typo...no luck.

Ok, so please correct me if I?m wrong?. The quickest way to get my UPS running with nut (as the current release exists) is to either: 1) Add my vendor and device ID to the openups_usb_device_table OR 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list And then recompile/install. Obviously #1 will be easier at this point, but I understand that it

On Feb 25, 2015, at 11:35 AM, Rob Groner <rgroner at RTD.com> wrote: > The quickest way to get my UPS running with nut (as the current release exists) is to either: > > 1) Add my vendor and device ID to the openups_usb_device_table OR > 2) Create my own driver file, and then add that driver to the usbhid-ups subdriver_list > > And then recompile/install.

> On Sep 9, 2015, at 10:12 AM, Rob Groner <rgroner at RTD.com> wrote: > > linux-5048:/home/rtd # ldd /usr/local/ups/bin/usbhid-ups > linux-vdso.so.1 (0x00007fff403fc000) > libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f7c34b56000) The last line seems to indicate that it is the real libusb-0.1, not -compat. What kernel version on openSUSE? --

Sorry for the bad formatting of the previous message...I tried to use plus signs as bullet points, and that caused a problem somehow. Ok...I discovered that if I do the autoreconf after the first failed make (and the autoreconf still gives that error message), and then do make again...it builds. Conclusions: 1) Autoreconf *must* be run, and not ./configure? I had thought that putting in my *.c

On Feb 20, 2015, at 3:15 PM, Rob Groner <rgroner at RTD.com> wrote: > Instead, it seems that the usbhid-ups driver will search through its own list of known devices with vid/pid, and won't "match" my device unless that device exists as an entry in its device table. Is that correct? More or less, yes. It turns out that UPS vendors all have somewhat different

On Sep 10, 2015, at 8:49 AM, Rob Groner <rgroner at RTD.com> wrote: > > Charles, > > 3.16.6.-2-desktop I think that corresponds to this file: http://lxr.free-electrons.com/source/drivers/usb/core/devio.c?v=3.16 (but I don't see anything obvious there) What does "lsusb -vvv -d 2a37:" return? Usually I'd say run that as root when the driver isn't running,

I think I had a misconception about something.. My goal was that someone could use our UPS with the "default" UPS driver in NUT right out of the box, so they wouldn't have to alter any NUT code to get it working. NUT config files, yes, but not NUT code. I thought that if I put in the ups.conf file that I wanted to use the usbhid-ups driver, and then put our vendor and product ID,

For fun, if you want to see where the system thinks it is linking a library from, you can use "ldconfig -p" and it will give you a path to all known libraries that it can find. If you have one loaded, and it can't find it (odd directory, etc.) you can always amend "LD_LIBRARY_PATH" the same way as PKG_CONFIG_PATH I mentioned earlier . . . . PKG . . . is for the build

Rob - Just stepping in from the sidelines . . . with a few tidbits. Nut uses pkgconfig to find and identify stuff as part of it's build . . . So, depending on where your libusb install went, if it wasn't in the default "PKG_CONFIG_PATH" setting, it won't be found. Much like other shell variables, you can adjust that setting to find anything you like . . . IE

On Sep 9, 2015, at 9:40 AM, Rob Groner <rgroner at RTD.com> wrote: > > I'm not sure which USB lib it compiled against. What does this return? ldd /path/to/driver -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150909/ba08f4c0/attachment.html>

I am running tests on my system and UPS, making sure that it is reliably able to come up, detect power loss, shutdown safely, and then come back up when the power returns. It does that MOST of the time. However, a significant part of the time, the system comes up, and then doesn't respond to loss of power. Doing some checking, I find that the reason is because upsd never started. Capturing