[Nut-upsuser] UPS/NUT with openSUSE 13.1

[Rob Groner]

Nope, not the same directory.  The code has moved about quite a lot since then.  git show couldn't find anything.

I haven't updated the code since that first pull, which was around March 14, 2014 (year and a half ago), so no change in nut would explain why I suddenly can't do what I was able to do earlier this year.

The firmware has certainly changed since then, however.  Is it possible some aspect of how the device responds in USB is causing the error?  I might try an older version of the firmware just to see. 

It's strange that Porteus works fine, though.  And that openSUSE 13.2 works *sometimes*.  I might try Ubuntu....

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: Charles Lepple [mailto:clepple at gmail.com] 
Sent: Thursday, September 10, 2015 10:05 PM
To: Rob Groner <rgroner at RTD.com>
Cc: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org>
Subject: Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

On Sep 10, 2015, at 10:28 AM, Rob Groner <rgroner at RTD.com> wrote:
> [...]
> I noticed the "can't open device" at the top of the listing before, but I also saw that every other entry in the results from "lsusb -vvv" (including the mouse) had the same string, so I didn't think it was unusual.  I did notice that my USB stick didn't have that message.

Not a big deal, in this case. I was just looking for the device/configuration descriptors, and things look reasonable.

> Unfortunately, I don't recall much about the git pull, except when you told me how to do it however many months back it was.  I pulled it and then went on my merry way modifying it.  Is there some way to look in the code/data to see it?

If it is still the same directory (with the .git metadata directory at the top level), you can say "git show".

-- 
Charles Lepple
clepple at gmail