search for: nutdr_qx

Displaying 7 results from an estimated 7 matches for "nutdr_qx".

Did you mean: nutdrv_qx
2015 Jan 02
0
Data stale error after short while
On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > Not sure what other logs I can provide to try to troubleshoot this? > Two things: - the output of 'lsusb -d 0665:' before and after the 'stale data' warning - the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 | tee /tmp/nutdrv_qx.log' (Please gzip nutdrv_qx.log before
2015 Jan 02
0
Data stale error after short while
...inux Foundation 2.0 root hub -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150102/6861088f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: nutdr_qx-txt.tar.gz Type: application/x-gzip Size: 10948 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150102/6861088f/attachment.bin>
2015 Jan 02
2
Data stale error after short while
Hi Charles, and thanks for your suggestion. I tried the nutdrv_qx and moved the rules file like you said, and re-attached the USB. It picked up to begin with, but within 10 minutes it lost the device again. $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.1 Network UPS Tools - Generic Q* USB/Serial driver 0.01 (2.7.1) USB communication driver 0.32 Using protocol: Megatec
2015 Jan 02
2
Data stale error after short while
...at gmail > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150102/1e19f712/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: nutdr_qx-log.tar.gz Type: application/x-gzip Size: 1893 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150102/1e19f712/attachment.bin>
2015 Jan 05
0
Fwd: Data stale error after short while
...9 Device not supported! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150105/b9282709/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: nutdr_qx-txt.tar.gz Type: application/x-gzip Size: 53857 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150105/b9282709/attachment-0001.bin>
2015 Jan 02
3
Data stale error after short while
On Jan 2, 2015, at 3:33 PM, Mike Raath <raathm at gmail.com> wrote: > Sorry, I messed up my reply a bit. > > The output of the lsusb command is the same before and after the data goes stale. > > $ lsusb -d 0665: > Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial > OK. That usually means that the VM kernel doesn't see that the device is
2015 Jan 03
4
Data stale error after short while
On Jan 2, 2015, at 4:27 PM, Mike Raath <raathm at gmail.com> wrote: > Maybe usbpassthrough is something I should look at? I'll do some reading. You may have found this already, but this (plus the followup KB item #1021345) seems to imply that you can bind the USB-to-serial adapter to the NUT VM: