thr3ads.net - Nut upsuser - [Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups KSTAR BM3150 1500VA "Line Interactive" High Frequency UPS [Sep 2014]

If this information is useful, please help other people find it:
Share via:

Barry Skrypnyk

2014-Sep-04 17:29 UTC

[Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups

I talked to Tripp Lite Technical support.

Their policy is that they only support Fedora and SUSE.  There is no one
there that could help with Ubuntu or NUT issues.  The only answer they could
give me was to port the rpm files to Ubuntu and use them.  This is way
beyond my experience level.

I will go to the local electronics store and buy a cheap USB 2 hub to see if
that works.  I will post the result.

In the meantime, I am also going to start looking for a different UPS that
is better supported by Ubuntu and NUT.  Any recommendations for a 1500VA
UPS?

Barry
> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: Friday, August 29, 2014 3:59 PM
> To: barry at skrypnyks.com
> Cc: nut-upsuser at lists.alioth.debian.org
> Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups
> 
> 
> On Aug 29, 2014, at 2:02 PM, Barry Skrypnyk <barry at skrypnyks.com>
wrote:
> 
> > See comments below.
> >
> >> -----Original Message-----
> >> From: Charles Lepple [mailto:clepple at gmail.com]
> >> Sent: Friday, August 29, 2014 5:35 AM
> >> To: barry at skrypnyks.com
> >> Cc: nut-upsuser at lists.alioth.debian.org
> >> Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with
> >> usbhid-ups
> >>
> >> On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at
skrypnyks.com>
> wrote:
> >>
> >>> I have searched the archives and googled this problem with
usbhid-ups.
> > I
> >> would really appreciate any help anyone could offer to solve the
problem.> >>>
> >>> System: Ubuntu 14.04.1 Trusty Tahr
> >>
> >> Which kernel version are you using?
> > 3.13.0-35-generic
> > I just updated this late last night.
> >>
> >>> Installed nut from Ubuntu repositories - nut 2.7.1
> >>>
> >>> Ups.conf file
> >>>
> >>> maxretry = 3
> >>>
> >>> # user = nut
> >>>
> >>> [TrippLite]
> >>>
> >>>        driver = usbhid-ups
> >>>
> >>>        port = auto
> >>>
> >>>        productid = 3016
> >>>
> >>>        desc = "Tripp Lite UPS, USB Interface"
> >>
> >> Configuration looks good.
> >>
> >>>
> >>> Data from the usbhid-ups command
> >>>
> >>> <<...>>
> >>
> >> This part confuses me:
> >>
> >>  68.487087     Checking device (09AE/3016) (004/008)
> >>  68.564137     - VendorID: 09ae
> >>  68.564168     - ProductID: 3016
> >>  68.564174     - Manufacturer: Tripp Lite
> >>  68.564220     - Product: TRIPP LITE UPS
> >>  68.564225     - Serial Number: 2406CVLSM871900494
> >>  68.564231     - Bus: 004
> >>  68.564235     Trying to match device
> >>  68.564255     Device does not match - skipping
> >>
> >> Judging from the time, did the driver connect initially, or is it
> >> still trying to reconnect? (I haven't used
"maxretry" before.)
> > Tries to reconnect forever.  It never initially connected.  Maxretry
> > was in the configuration file as a default of the new installation.  I
> > added from the user = nut to the end.
> >>
> >>> Data from lsusb command
> >>>
> >>> fs00pc:~$ lsusb
> >>> Bus 003 Device 002: ID 0bda:0111 Realtek Semiconductor Corp.
RTS5111
> >>> Card Reader Controller Bus 003 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 004 Device 008: ID 09ae:3016 Tripp
Lite
> >>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus
> >>> 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus
008
> >>> Device
> >>> 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> >>
> >> After the errors from usbhid-ups, does "lsusb -vvv -d
09ae:" return
> >> valid information, or do you also get timeouts in syslog as well?
> > I included the result of the command and the syslog in the attached
> > gzip file.  It looks like it worked but there is also a complaint
> > about not being able to open the device properly.
> 
> That error is okay - the rest of the descriptors came in.
> 
> >  Since I installed the new kernel, I
> > re-ran the tests from before.  I still get an error but it is not in
> > an infinite loop looking to connect with the Tripp Lite on the usb
> > port as it was before.
> >>
> >> If lsusb doesn't work, it points to a problem between the UPS
> >> firmware and your Linux kernel version. (Well, technically, lsusb
> >> could be at fault, but it doesn't change as much as the kernel
USB
> >> HCI drivers.)
> >>
> >> In that case, you may want to check with Tripp Lite; they were
kind
> >> enough to post results of testing their hardware against NUT and
> >> Linux. They should be able to repeat that test with Ubuntu 14.04.
> > I will try to contact Tripp Lite support to see if they can be of some
help.> 
> One thing you can also try is adding a USB 1.1 or 2.0 hub between the UPS
> and the PC. If it works, that might rule out any USB 3.0-related xHCI
issues.> 
> >>
> >> --
> >> Charles Lepple
> >> clepple at gmail
> >>
> >
> > <usb.txt.gz>
> 
> This part also points to a potential kernel/UPS incompatibility:
> 
> Aug 29 10:26:46 fs00pc kernel: [ 9558.209427] usbhid: USB HID core driver
> Aug 29 10:26:46 fs00pc kernel: [ 9558.268826] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.269805] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.270828] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.298820] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.299808] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.300835] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.608907] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.609905] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.610914] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.611899] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.612898] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.613898] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.614891] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.615890] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.616882] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.618621] hid-generic
> 0003:09AE:3016.0001: hiddev0,hidraw0: USB HID v1.11 Device [Tripp Lite
> TRIPP LITE UPS] on usb-0000:00:12.0-5/input0
> 
> The kernel is getting timeouts even before NUT has a chance to attach to
the> device.
>

oVirtNut

2014-Sep-05 12:23 UTC

head link

[Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups KSTAR BM3150 1500VA "Line Interactive" High Frequency UPS

Barry,

I have had success with NUT on Debian and an EATON 5E2000IUSB-AU 5E
2000VA/1200W UPS With 3 x OUTLETS which I believe is good value.

I would believe the the EATON ?5E 1500VA/900W UPS With 3 x OUTLETS
would work just as well. 

The 1500VA also uses the same batteries as the 2000VA so I would
believe it would run its raited load longer than 2000VA. My eight
drive RAID driver uses less that 400W so I would expect that the
device would easily run two small servers, and one monitor and/or ADSL
modem for about 30 minutes, plenty of time to allow? a 5 minute wait
time before a shutdown process. 

I like to wait 5 minutes to give people an opportunity to restore
power if the issue was a tripped circuit breaker, the only issue is
the UPS alarm for 5 minutes can be annoying for staff. I have yet to
try turning off the alarm via NUT.

I found this device's cooling fan a bit noisy for the first seven or
so hours whenever you turn it on, but after that it is silent.? This
was my first concern as smaller UPS and small business servers are
often located with the client, and not in a server room, thus noise
can detract from the staff's experience.

I have yet to have time to fully implement shutdown on power fail due
to time constraints.? I am running KVM and Virt-Manager and want to
ensure that the VMs are shutdown before unmounting the local Debian
server's drives and shutting down the UPS.
http://www.msy.com.au/act/fyshwick/pc-accessories/13153-eaton-5e2000iusb-au-5e-2000va1200w-ups-with-3-x-outlets.html

Another alternative that I have, but have yet to test with NUT, is
the? KSTAR BM3150 1500VA "Line Interactive" High Frequency UPS.? I
have tested a single? server running on this UPS for up to 1 hour.?
If I remember it was a lot quieter that the Eaton. I placed this UPS
into the centre of an office area and was concerned about its fan
noise, but no one complained. And the fan of course only runs when the
UPS is initially charging, after which it is completely silent.

http://www.msy.com.au/act/fyshwick/pc-accessories/10333-kstar-bm3150-1500va-line-interactive-high-frequency-ups.html

To anyone running a Linux server, I really recommend setting up UPS
and NUT to do a graceful shutdown.? The cost is not that much.

I would like to have a 'two power supply' server so I could test a
single server with two UPS, each supporting one of the two power
supplies. This would mean if one UPS failed to switch over, the other
most likely would. I have read that people who really don't want the
server to loose power set up such a configuration. However for my
needs I would not go this far. At least having one UPS will do me.

I hope some of the above information may be of help to you.

Thanks,

George.

At Friday, 05-09-2014 on 03:29 Barry Skrypnyk wrote:

I talked to Tripp Lite Technical support.

Their policy is that they only support Fedora and SUSE.??There is no
one
there that could help with Ubuntu or NUT issues.??The only answer
they could
give me was to port the rpm files to Ubuntu and use them.??This is
way
beyond my experience level.

I will go to the local electronics store and buy a cheap USB 2 hub to
see if
that works.??I will post the result.

In the meantime, I am also going to start looking for a different UPS
that
is better supported by Ubuntu and NUT.??Any recommendations for a
1500VA
UPS?

Barry
> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: Friday, August 29, 2014 3:59 PM
> To: barry at skrypnyks.com
> Cc: nut-upsuser at lists.alioth.debian.org
> Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with
usbhid-ups> 
> 
> On Aug 29, 2014, at 2:02 PM, Barry Skrypnyk  wrote:
> 
> > See comments below.
> >
> >> -----Original Message-----
> >> From: Charles Lepple [mailto:clepple at gmail.com]
> >> Sent: Friday, August 29, 2014 5:35 AM
> >> To: barry at skrypnyks.com
> >> Cc: nut-upsuser at lists.alioth.debian.org
> >> Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with
> >> usbhid-ups
> >>
> >> On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk 
> wrote:
> >>
> >>> I have searched the archives and googled this problem with
usbhid-ups.> > I
> >> would really appreciate any help anyone could offer to solve the
problem.> >>>
> >>> System: Ubuntu 14.04.1 Trusty Tahr
> >>
> >> Which kernel version are you using?
> > 3.13.0-35-generic
> > I just updated this late last night.
> >>
> >>> Installed nut from Ubuntu repositories - nut 2.7.1
> >>>
> >>> Ups.conf file
> >>>
> >>> maxretry = 3
> >>>
> >>> # user = nut
> >>>
> >>> [TrippLite]
> >>>
> >>>????????driver = usbhid-ups
> >>>
> >>>????????port = auto
> >>>
> >>>????????productid = 3016
> >>>
> >>>????????desc = "Tripp Lite UPS, USB Interface"
> >>
> >> Configuration looks good.
> >>
> >>>
> >>> Data from the usbhid-ups command
> >>>
> >>> 
> >>
> >> This part confuses me:
> >>
> >>??68.487087???? Checking device (09AE/3016) (004/008)
> >>??68.564137???? - VendorID: 09ae
> >>??68.564168???? - ProductID: 3016
> >>??68.564174???? - Manufacturer: Tripp Lite
> >>??68.564220???? - Product: TRIPP LITE UPS
> >>??68.564225???? - Serial Number: 2406CVLSM871900494
> >>??68.564231???? - Bus: 004
> >>??68.564235???? Trying to match device
> >>??68.564255???? Device does not match - skipping
> >>
> >> Judging from the time, did the driver connect initially, or is it
> >> still trying to reconnect? (I haven't used
"maxretry" before.)
> > Tries to reconnect forever.??It never initially
connected.??Maxretry> > was in the configuration file as a default of the new
installation.??I> > added from the user = nut to the end.
> >>
> >>> Data from lsusb command
> >>>
> >>> fs00pc:~$ lsusb
> >>> Bus 003 Device 002: ID 0bda:0111 Realtek Semiconductor Corp.
RTS5111> >>> Card Reader Controller Bus 003 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 004 Device 008: ID 09ae:3016 Tripp
Lite> >>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus> >>> 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus
008> >>> Device
> >>> 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> >>
> >> After the errors from usbhid-ups, does "lsusb -vvv -d
09ae:"
return> >> valid information, or do you also get timeouts in syslog as well?
> > I included the result of the command and the syslog in the
attached> > gzip file.??It looks like it worked but there is also a
complaint> > about not being able to open the device properly.
> 
> That error is okay - the rest of the descriptors came in.
> 
> >??Since I installed the new kernel, I
> > re-ran the tests from before.??I still get an error but it is
not in> > an infinite loop looking to connect with the Tripp Lite on the usb
> > port as it was before.
> >>
> >> If lsusb doesn't work, it points to a problem between the UPS
> >> firmware and your Linux kernel version. (Well, technically, lsusb
> >> could be at fault, but it doesn't change as much as the kernel
USB> >> HCI drivers.)
> >>
> >> In that case, you may want to check with Tripp Lite; they were
kind> >> enough to post results of testing their hardware against NUT and
> >> Linux. They should be able to repeat that test with Ubuntu 14.04.
> > I will try to contact Tripp Lite support to see if they can be ofsome
help.> 
> One thing you can also try is adding a USB 1.1 or 2.0 hub between
the UPS> and the PC. If it works, that might rule out any USB 3.0-relatedxHCI
issues.> 
> >>
> >> --
> >> Charles Lepple
> >> clepple at gmail
> >>
> >
> > 
> 
> This part also points to a potential kernel/UPS incompatibility:
> 
> Aug 29 10:26:46 fs00pc kernel: [ 9558.209427] usbhid: USB HID core
driver> Aug 29 10:26:46 fs00pc kernel: [ 9558.268826] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.269805] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.270828] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.298820] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.299808] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.300835] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.608907] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.609905] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.610914] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.611899] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.612898] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.613898] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.614891] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.615890] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.616882] usb 4-5: ctrl urb
status -62> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.618621] hid-generic
> 0003:09AE:3016.0001: hiddev0,hidraw0: USB HID v1.11 Device [Tripp
Lite> TRIPP LITE UPS] on usb-0000:00:12.0-5/input0
> 
> The kernel is getting timeouts even before NUT has a chance toattach to
the> device.
> 

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140905/6d36acf7/attachment.html>

Barry Skrypnyk

2014-Sep-08 22:45 UTC

head link

[Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups KSTAR BM3150 1500VA "Line Interactive" High Frequency UPS

Update:

Tried using a USB 2.0 Hub.  The UPS is communicating and connected.  There are
hiccups occasionally.

From: oVirtNut [mailto:oVirtNut at goproject.info] 
Sent: Friday, September 05, 2014 5:23 AM
To: barry at skrypnyks.com; nut-upsuser at lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups KSTAR
BM3150 1500VA "Line Interactive" High Frequency UPS

Barry,

I have had success with NUT on Debian and an EATON 5E2000IUSB-AU 5E 2000VA/1200W
UPS With 3 x OUTLETS which I believe is good value.

I would believe the the EATON  5E 1500VA/900W UPS With 3 x OUTLETS would work
just as well.

The 1500VA also uses the same batteries as the 2000VA so I would believe it
would run its raited load longer than 2000VA. My eight drive RAID driver uses
less that 400W so I would expect that the device would easily run two small
servers, and one monitor and/or ADSL modem for about 30 minutes, plenty of time
to allow  a 5 minute wait time before a shutdown process.

I like to wait 5 minutes to give people an opportunity to restore power if the
issue was a tripped circuit breaker, the only issue is the UPS alarm for 5
minutes can be annoying for staff. I have yet to try turning off the alarm via
NUT.

I found this device's cooling fan a bit noisy for the first seven or so
hours whenever you turn it on, but after that it is silent.  This was my first
concern as smaller UPS and small business servers are often located with the
client, and not in a server room, thus noise can detract from the staff's
experience.

I have yet to have time to fully implement shutdown on power fail due to time
constraints.  I am running KVM and Virt-Manager and want to ensure that the VMs
are shutdown before unmounting the local Debian server's drives and shutting
down the UPS.

http://www.msy.com.au/act/fyshwick/pc-accessories/13153-eaton-5e2000iusb-au-5e-2000va1200w-ups-with-3-x-outlets.html

Another alternative that I have, but have yet to test with NUT, is the  KSTAR
BM3150 1500VA "Line Interactive" High Frequency UPS.  I have tested a
single  server running on this UPS for up to 1 hour.  If I remember it was a lot
quieter that the Eaton. I placed this UPS into the centre of an office area and
was concerned about its fan noise, but no one complained. And the fan of course
only runs when the UPS is initially charging, after which it is completely
silent.

http://www.msy.com.au/act/fyshwick/pc-accessories/10333-kstar-bm3150-1500va-line-interactive-high-frequency-ups.html

To anyone running a Linux server, I really recommend setting up UPS and NUT to
do a graceful shutdown.  The cost is not that much.

I would like to have a 'two power supply' server so I could test a
single server with two UPS, each supporting one of the two power supplies. This
would mean if one UPS failed to switch over, the other most likely would. I have
read that people who really don't want the server to loose power set up such
a configuration. However for my needs I would not go this far. At least having
one UPS will do me.

I hope some of the above information may be of help to you.

Thanks,

George.

At Friday, 05-09-2014 on 03:29 Barry Skrypnyk wrote:

I talked to Tripp Lite Technical support.

Their policy is that they only support Fedora and SUSE.  There is no one
there that could help with Ubuntu or NUT issues.  The only answer they could
give me was to port the rpm files to Ubuntu and use them.  This is way
beyond my experience level.

I will go to the local electronics store and buy a cheap USB 2 hub to see if
that works.  I will post the result.

In the meantime, I am also going to start looking for a different UPS that
is better supported by Ubuntu and NUT.  Any recommendations for a 1500VA
UPS?

Barry
> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: Friday, August 29, 2014 3:59 PM
> To: barry at skrypnyks.com
> Cc: nut-upsuser at lists.alioth.debian.org
> Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups
> 
> 
> On Aug 29, 2014, at 2:02 PM, Barry Skrypnyk <barry at skrypnyks.com>
wrote:
> 
> > See comments below.
> >
> >> -----Original Message-----
> >> From: Charles Lepple [mailto:clepple at gmail.com]
> >> Sent: Friday, August 29, 2014 5:35 AM
> >> To: barry at skrypnyks.com
> >> Cc: nut-upsuser at lists.alioth.debian.org
> >> Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with
> >> usbhid-ups
> >>
> >> On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at
skrypnyks.com>
> wrote:
> >>
> >>> I have searched the archives and googled this problem with
usbhid-ups.
> > I
> >> would really appreciate any help anyone could offer to solve the
problem.> >>>
> >>> System: Ubuntu 14.04.1 Trusty Tahr
> >>
> >> Which kernel version are you using?
> > 3.13.0-35-generic
> > I just updated this late last night.
> >>
> >>> Installed nut from Ubuntu repositories - nut 2.7.1
> >>>
> >>> Ups.conf file
> >>>
> >>> maxretry = 3
> >>>
> >>> # user = nut
> >>>
> >>> [TrippLite]
> >>>
> >>>        driver = usbhid-ups
> >>>
> >>>        port = auto
> >>>
> >>>        productid = 3016
> >>>
> >>>        desc = "Tripp Lite UPS, USB Interface"
> >>
> >> Configuration looks good.
> >>
> >>>
> >>> Data from the usbhid-ups command
> >>>
> >>> <<...>>
> >>
> >> This part confuses me:
> >>
> >>  68.487087     Checking device (09AE/3016) (004/008)
> >>  68.564137     - VendorID: 09ae
> >>  68.564168     - ProductID: 3016
> >>  68.564174     - Manufacturer: Tripp Lite
> >>  68.564220     - Product: TRIPP LITE UPS
> >>  68.564225     - Serial Number: 2406CVLSM871900494
> >>  68.564231     - Bus: 004
> >>  68.564235     Trying to match device
> >>  68.564255     Device does not match - skipping
> >>
> >> Judging from the time, did the driver connect initially, or is it
> >> still trying to reconnect? (I haven't used
"maxretry" before.)
> > Tries to reconnect forever.  It never initially connected.  Maxretry
> > was in the configuration file as a default of the new installation.  I
> > added from the user = nut to the end.
> >>
> >>> Data from lsusb command
> >>>
> >>> fs00pc:~$ lsusb
> >>> Bus 003 Device 002: ID 0bda:0111 Realtek Semiconductor Corp.
RTS5111
> >>> Card Reader Controller Bus 003 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux
> >>> Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux
> >>> Foundation 2.0 root hub Bus 004 Device 008: ID 09ae:3016 Tripp
Lite
> >>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus
> >>> 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus
008
> >>> Device
> >>> 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> >>
> >> After the errors from usbhid-ups, does "lsusb -vvv -d
09ae:" return
> >> valid information, or do you also get timeouts in syslog as well?
> > I included the result of the command and the syslog in the attached
> > gzip file.  It looks like it worked but there is also a complaint
> > about not being able to open the device properly.
> 
> That error is okay - the rest of the descriptors came in.
> 
> >  Since I installed the new kernel, I
> > re-ran the tests from before.  I still get an error but it is not in
> > an infinite loop looking to connect with the Tripp Lite on the usb
> > port as it was before.
> >>
> >> If lsusb doesn't work, it points to a problem between the UPS
> >> firmware and your Linux kernel version. (Well, technically, lsusb
> >> could be at fault, but it doesn't change as much as the kernel
USB
> >> HCI drivers.)
> >>
> >> In that case, you may want to check with Tripp Lite; they were
kind
> >> enough to post results of testing their hardware against NUT and
> >> Linux. They should be able to repeat that test with Ubuntu 14.04.
> > I will try to contact Tripp Lite support to see if they can be of some
help.> 
> One thing you can also try is adding a USB 1.1 or 2.0 hub between the UPS
> and the PC. If it works, that might rule out any USB 3.0-related xHCI
issues.> 
> >>
> >> --
> >> Charles Lepple
> >> clepple at gmail
> >>
> >
> > <usb.txt.gz>
> 
> This part also points to a potential kernel/UPS incompatibility:
> 
> Aug 29 10:26:46 fs00pc kernel: [ 9558.209427] usbhid: USB HID core driver
> Aug 29 10:26:46 fs00pc kernel: [ 9558.268826] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.269805] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.270828] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.298820] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.299808] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:46 fs00pc kernel: [ 9558.300835] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.608907] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.609905] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.610914] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.611899] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.612898] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.613898] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.614891] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.615890] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.616882] usb 4-5: ctrl urb status -62
> received
> Aug 29 10:26:47 fs00pc kernel: [ 9558.618621] hid-generic
> 0003:09AE:3016.0001: hiddev0,hidraw0: USB HID v1.11 Device [Tripp Lite
> TRIPP LITE UPS] on usb-0000:00:12.0-5/input0
> 
> The kernel is getting timeouts even before NUT has a chance to attach to
the> device.
> 

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140908/b25b5264/attachment-0001.html>

Possibly Parallel Threads

Search for more reasonably related threads

Nut upsuser - Sep 2014 - Smart1500lcdt will not connect with usbhid-ups KSTAR BM3150 1500VA "Line Interactive" High Frequency UPS

[Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups

[Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups KSTAR BM3150 1500VA "Line Interactive" High Frequency UPS

[Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups KSTAR BM3150 1500VA "Line Interactive" High Frequency UPS

Possibly Parallel Threads