On Aug 21, 2015, at 9:19 AM, Mario Lobo <ml...@digiart.art.br> wrote: > > On Aug 20, 2015, at 10:26 PM, Charles Lepple <clep...@gmail.com> wrote: >> >> On Aug 20, 2015, at 6:33 PM, Mario Lobo <ml...@digiart.art.br> wrote: >>> >>> ** cuaU0 >>> >>> [>]/usr/local/libexec/nut/solis -D -a lobos -u root >>> Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3) >>> 0.000000 debug level is '1' >>> 21.065536 Solis not detected! aborting ... >> >> It looks like /dev/cuaU0 is the port that was suggested for a >> similarly-named model last year: >> >> http://article.gmane.org/gmane.comp.monitoring.nut.user/8554 >> >> The binary patches mentioned in that thread have been superseded by source >> code chances that are part of NUT 2.7.3. >> >> Unfortunately, as you have seen, the solis driver does not have much debug >> output. What happens when you run it under ktrace? > Man ... the output of ktrace is really big! it produced an output file > of 200 k, attached to this e-mail (solis.txt). > > I don't even know what to look for! > > Do you have any ideas?
It's fairly large, but it compresses well. (Please keep the list CC'd - this is how people can find this information in the future.) Not sure what to look for yet. It might be easier to add in the debug calls to the source code-- can you try building NUT from source? If you installed via the ports tree (as opposed to binary packages), you should have most of the dependencies installed. You might also need libtool and autoconf, as mentioned in the second link below: http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management and http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building -- Charles Lepple clepple@gmail
solis.txt.gz
Description: GNU Zip compressed data
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
