On Sep 22, 2014, at 11:14 AM, Shade Alabsa <[email protected]> wrote:
> As mentioned earlier I have tried another USB port and cable. Below are the > /var/log/messages - I also got a new behavior this time. What is the new behavior? Your latest excerpt from /var/log/messages does not show that the driver is running at all, so the upsd and upsmon messages are to be expected. Also, in your first email in this thread, you mentioned that you saw problems only when NUT is configured. Can you elaborate on that? With upsd, upsmon and usbhid-ups stopped, you should be able to plug in the UPS, and only see one message like this: Sep 19 17:49:41 localhost kernel: usb 8-1: new low speed USB device number 119 using uhci_hcd Sep 19 17:49:41 localhost kernel: usb 8-1: New USB device found, idVendor=09ae, idProduct=3015 Sep 19 17:49:41 localhost kernel: usb 8-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4 Sep 19 17:49:41 localhost kernel: usb 8-1: Product: TRIPP LITE SMART1500RM2UN Sep 19 17:49:41 localhost kernel: usb 8-1: Manufacturer: Tripp Lite Sep 19 17:49:41 localhost kernel: usb 8-1: SerialNumber: 2424AY0SM882300229 Sep 19 17:49:41 localhost kernel: usb 8-1: configuration #1 chosen from 1 choice You should also be able to run "lsusb -v -d 09ae:" and get results from the UPS, also without anything disconnecting. If that doesn't trigger a disconnection, we will want to see the output of running the usbhid-ups driver in debug mode (probably at the "-DDD" level) as well as the corresponding /var/log/messages output. -- Charles Lepple clepple@gmail
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
