search for: groner

...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 system, and LD. . . is for the runtime dynamic linker. - Tim On 09/22/2015 03:48 PM, Rob Groner wrote: > Tim, > > Thanks for the help! No, I didn't already know that... I swear, the more time I spend at this, the less I seem to be understanding. > > I know that it had to be finding the libusb-compat I had just installed, because configure hadn't worked before that, and...

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 <rgroner at RTD.com<mailto:rgroner...

...S...it is still not setting it to nut group permissions. I am looking at the file in /dev/usb/hid/hiddev0 (which goes away when I unplug the UPS). Either way, upsdrvctrl still won't start unless I add "-u root". So I think my udev rule is simply not taking somehow. Sincerely, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Wednesday, February 18, 2015 8:11 PM > To: Rob Groner > Cc: nut-upsuser List > Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut > 2.7.2 > > On Feb 18, 2015,...

On Mar 9, 2015, at 12:00 PM, Rob Groner <rgroner at RTD.com> wrote: > 1) Autoreconf *must* be run, and not ./configure? I had thought that putting in my *.c and *.h files and making the makefile changes and then executing ./configure for the first time would be enough. Each tool serves a different purpose. autoreconf (and N...

...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, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Wednesday, February 25, 2015 8:10 PM > To: Rob Groner > Cc: nut-upsuser List > Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut > 2.7.2 > > On Feb 25, 2015,...

...udedir=${prefix}/include Name: libusb Description: USB access library Version: 0.1.12 Libs: -L${libdir} -lusb Cflags: -I${includedir} This may help make sense of what version report, and how stuff gets found. Then again, if you already know this, sorry . . . - Tim On 09/22/2015 02:47 PM, Rob Groner wrote: > Thanks Charles, you were right about that. > > Here is what I tried...I installed openSUSE 13.1 from scratch (which means no libusb). I then took libusb-1.0 from the sourceforge site and built and installed it. Still it got the "cannot find libusb" error. So, looking...

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

...ked that upsd wasn't getting started from anywhere else, and I looked in the NUT code to see if I could figure out why it thought upsd was already started, but nothing was obvious. Does anyone have any other suggestions for tracking down why upsd errors out like that sometimes? Sincerely, Rob Groner Software Engineer RTD Embedded Technologies, Inc. ISO 9001 and AS9100 Certified Ph: 814-234-8087 www.rtd.com<http://www.rtd.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150707/1ee...

...r at this point, but I understand that it will only get me the functionality that currently exists in the openups driver (which is ok, I structured my USB reports around what that driver makes available). If I want full functionality I?ll need to eventually make my own driver file. Sincerely, Rob Groner From: Charles Lepple [mailto:clepple at gmail.com] Sent: Friday, February 20, 2015 7:50 PM To: Rob Groner Cc: nut-upsuser List Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut 2.7.2 On Feb 20, 2015, at 3:15 PM, Rob Groner <rgroner at RTD.com<mailto:rgroner at RTD.com...

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

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

...I had this working fine earlier this year and now it doesn't, and a changing version of libusb would explain that. Plus, if I install openSUSE 13.1 AND install libusb* from the ISO, then it works. It's just getting libusb from some other source that seems to be causing the problem. Rob Groner Software Engineer Level II RTD Embedded Technologies, Inc. ISO 9001 and AS9100 Certified Ph: +1 814-234-8087 www.rtd.com -----Original Message----- From: Tim Dawson [mailto:tadawson at tpcsvc.com] Sent: Tuesday, September 22, 2015 4:52 PM To: Rob Groner <rgroner at RTD.com>; nut-upsuser at...

...sts as an entry in its device table. Is that correct? In other words, instead of the ups.conf file saying "Use usbhid-ups with USB device of vid/pid", it is saying "Use usbhid-ups with USB device of vid/pid *if* they are in the list of devices for usbhid-ups"? Sincerely, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Thursday, February 19, 2015 10:09 PM > To: Rob Groner > Cc: nut-upsuser List > Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut > 2.7.2 > > On Feb 19, 2015,...

...ho knew? Thank you all for the patient help. I'm now putting the system through some systematic shutdown testing to make sure it's good, and then I'll start again from scratch and make sure I can repeat it, and then I'll finally be able to move on with wrapping this thing up. Rob Groner Software Engineer Level II RTD Embedded Technologies, Inc. ISO 9001 and AS9100 Certified Ph: +1 814-234-8087 www.rtd.com > -----Original Message----- > From: Nut-upsuser [mailto:nut-upsuser- > bounces+rgroner=rtd.com at lists.alioth.debian.org] On Behalf Of Rob Groner > Sent: Wednesda...

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

...created by "make install" would have "nut" as their group, but they don't....they have only root:root. Does the group permissions not get set in these directories upon install? I thought that was the point of creating the user and group in the beginning. Thank you, Rob Groner

...That gave me an error message that I do not believe is related to my driver: Parallel-tests: error: required file './test-driver' not found Parallel-tests: 'automake --add-missing' can install 'test-driver' Autoreconf: automake failed with exit status 1 Sincerely, Rob Groner > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Monday, March 02, 2015 8:27 PM > To: Rob Groner > Cc: nut-upsuser List > Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut > 2.7.2 > > On Mar 2, 2015, at 12...

On Sep 21, 2015, at 9:39 AM, Rob Groner <rgroner at RTD.com> wrote: > > I didn't think to look for a log (attached), but now looking in it, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. > > It does reference the line in the configure where the test for USB...

On Sep 18, 2015, at 2:45 PM, Rob Groner <rgroner at RTD.com> wrote: > > Well, I've spent a couple hours on this, unable to figure it out. I removed the libusb-compat-devel package using zypper. And I've downloaded, built, and installed libusb from sourceforge. But trying to configure nut now I get "USB driver...

https://bugs.freedesktop.org/show_bug.cgi?id=61611 Priority: medium Bug ID: 61611 Assignee: nouveau at lists.freedesktop.org Summary: Crash of X on a notification popup Severity: major Classification: Unclassified OS: Linux (All) Reporter: raphgro at web.de Hardware: x86-64 (AMD64) Status: NEW