On Apr 6, 2015, at 1:58 PM, Eric Cobb <[email protected]> wrote:
> That worked out just fine. What I am currently running into are conditions > where I am getting the following error that I figured I would share. > > Error: > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 4d b2 0d 00 > 00 00 00 '.M......' > > > Conditions: upsdrvctl start via Init Script at Boottime. If I run the init > script after boot, I do not receive this error. That is odd. Running the init script later should pass the same parameters to the driver. The only thing I can think of: other processes are interfering at boot time? Does the driver eventually start, or does that error continue? -- Charles Lepple clepple@gmail
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
