search for: usb_set_altinterfac

If you have a USB UPS, and can rebuild NUT from source (tarball or Git), please read on. I was trying to fix a problem specific to OS X and Tripp Lite UPSes, but it turns out that the redundant call to usb_set_altinterface(0) is right in the middle of the common NUT USB driver code, affecting pretty much any USB UPS that we support. So I would like to get a little additional testing before merging this. (Thanks to Steve Ballantyne for testing this on a different Tripp Lite model.) Basically, this call to usb_set_al...

If you have a USB UPS, and can rebuild NUT from source (tarball or Git), please read on. I was trying to fix a problem specific to OS X and Tripp Lite UPSes, but it turns out that the redundant call to usb_set_altinterface(0) is right in the middle of the common NUT USB driver code, affecting pretty much any USB UPS that we support. So I would like to get a little additional testing before merging this. (Thanks to Steve Ballantyne for testing this on a different Tripp Lite model.) Basically, this call to usb_set_al...

...On Aug 16, 2014, at 5:25 PM, Charles Lepple <clepple at gmail.com> wrote: > If you have a USB UPS, and can rebuild NUT from source (tarball or Git), please read on. > > I was trying to fix a problem specific to OS X and Tripp Lite UPSes, but it turns out that the redundant call to usb_set_altinterface(0) is right in the middle of the common NUT USB driver code, affecting pretty much any USB UPS that we support. So I would like to get a little additional testing before merging this. (Thanks to Steve Ballantyne for testing this on a different Tripp Lite model.) > > Basically, this call to...

...f libtool and autoconf are not compatible. (On Fink, I am currently using autoconf-2.69 and libtool-2.4.6) > - building against libusb 0.1 does not change in any way the situation, I still get the same error related to lack of ability to claim the interface At some point, we took out a call to usb_set_altinterface() - the kernel is supposed to activate bAlternateSetting=0 automatically, and re-selecting it caused problems on other platforms. Maybe it was required with Linux kernel 2.6.x. With libusb-0.1 linked in, does "-x usb_set_altinterface=0" change anything?

...? ? 0.278835? ? - ProductID: 3016 >? ? 0.278843? ? - Manufacturer: unknown >? ? 0.278852? ? - Product: unknown >? ? 0.278859? ? - Serial Number: unknown >? ? 0.278867? ? - Bus: /dev/usb >? ? 0.278876? ? Trying to match device >? ? 0.278925? ? Device matches >? ? 0.278937? ? nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) Just for grins, can you try adding "usb_set_altinterface" to the ups.conf section for your UPS, and see if that changes this part of the log? (That is, after "[upstl1300]"). >? ? 0.306126? ? HID descriptor, method 1: (9 bytes) => 0...

So when the UPS is communicating with the driver... it seems to work.? Problem is now that it keeps disconnecting.? Any recommendation on how to keep the drivers from disconnecting using the usb_set_altinterface?? (PS.? Is there a specific value to use?)? Or this confirms there is an issue with the usbhid-ups driver with the FreeBSD 10.2 kernel? upsc upstl1300 battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.runtime: 709 battery.type: PbAC battery.voltage: 0.0 battery.voltage....

>Just for grins, can you try adding "usb_set_altinterface" to the ups.conf section for your UPS, and see if that changes this part of the log? (That is, after "[upstl1300]"). Here is the output with the usb_set_altinterface?added to ups.conf or at least partially output because it keeps going in a loop. ? 46.820206???? Checking device (09A...

...278818???? - VendorID: 09ae ?? 0.278835???? - ProductID: 3016 ?? 0.278843???? - Manufacturer: unknown ?? 0.278852???? - Product: unknown ?? 0.278859???? - Serial Number: unknown ?? 0.278867???? - Bus: /dev/usb ?? 0.278876???? Trying to match device ?? 0.278925???? Device matches ?? 0.278937???? nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) ?? 0.306126???? HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22 6e 03 ?? 0.306148???? HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 6e 03 ?? 0.306156???? HID descriptor length 878 ?? 5.279939???? Unable to get Report descriptor...

...: unknown 2.024090 - Serial Number: unknown 2.024093 - Bus: 002 2.024096 - Device release number: 0001 2.024099 Trying to match device 2.024122 Device matches 2.024134 failed to claim USB device: Device or resource busy 4.898305 detached kernel driver from USB device... 4.898344 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 9.901010 Unable to get HID descriptor (Connection timed out) 9.901031 HID descriptor length (method 1) -1 9.901037 i=0, extra[i]=09, extra[i+1]=21 9.901044 HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 25 02 9.901048 HID descriptor...

> You could also try adding "-x usb_set_altinterface" to the command line > (or adding it to ups.conf). The lsusb output implies that the only valid > setting is 0 (bAlternateSetting), but it might need to be set explicitly. I checked with -x usb_set_altinterface and it says nut_usb_set_altinterface: usb_set_altinterface() should not...

...Manufacturer: MEC - Product: MEC0002 - Serial Number: unknown - - Bus: 008 + - Bus: 006 - Device release number: 0100 Trying to match device Device matches + failed to claim USB device: could not claim interface 0: Device or resource busy + detached kernel driver from USB device... nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) HID descriptor, method 1: (9 bytes) => 09 21 00 01 00 01 22 70 02 **** device or resource busy? 11) retrying as root #/lib/nut/usbhid-ups -DDD -u root -x explore -a turbo-x 2>&1 | tee delme.root 12) stripping, diffing -- no diffs Here is th...

On Sep 8, 2016, at 9:25 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > + failed to claim USB device: could not claim interface 0: Device or > resource busy > + detached kernel driver from USB device... > nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) > HID descriptor, method 1: (9 bytes) => 09 21 00 01 00 01 22 70 02 > > **** device or resource busy? This happens the first time you run a NUT driver after the USB cable is plugged in, or the system reboots. The old Linux kernel HID driver was...

...s should already done by the OS when the device is enumerated. If that is the case, then there is no reason why we should hardcode the alternate interface to 0. If I remove the following code, tripplite_usb seems to work*: /* set default interface */ usb_set_altinterface(udev, 0); Any objections to removing this? Can I get some volunteers to try this out on their non-OS X systems? I am using libusb-0.1.12 on Mac OS X 10.5.8. * I did have to monkey with a codeless kext in order to allow libusb to claim the device. However, it doesn't seem like OS X allows yo...

...e descriptor, which should be available regardless. The version number of your driver says "2.7.2.6_RTD". Which Git revision does that correspond to in the NUT repository (aside from your changes)? I'm curious because somewhere (af5f84c5) between 2.7.2 and 2.7.3, I removed a spurious usb_set_altinterface() call, and I'm wondering if that changes the claim/detach error messages. -- Charles Lepple clepple at gmail

...8835 - ProductID: 3016 > 0.278843 - Manufacturer: unknown > 0.278852 - Product: unknown > 0.278859 - Serial Number: unknown > 0.278867 - Bus: /dev/usb > 0.278876 Trying to match device > 0.278925 Device matches > 0.278937 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) Just for grins, can you try adding "usb_set_altinterface" to the ups.conf section for your UPS, and see if that changes this part of the log? (That is, after "[upstl1300]"). > 0.306126 HID descriptor, method 1: (9 bytes) =>...

...   2.024096 - Device release number: 0001 > >    2.024099 Trying to match device > >    2.024122 Device matches > >    2.024134 failed to claim USB device: Device or resource busy > >    4.898305 detached kernel driver from USB device... > >    4.898344 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) > >    9.901010 Unable to get HID descriptor (Connection timed out) > >    9.901031 HID descriptor length (method 1) -1 > >    9.901037 i=0, extra[i]=09, extra[i+1]=21 > >    9.901044 HID descriptor, method 2: (9 bytes) => 0...

...' -> after the SET INTERFACE Request that succeed, all subsequent GET DESCRIPTOR responses are malformed. ?- after usb cable plugin, issue an 'usbhid-dump' -> the device proudly survive These observations would need more insight. But as a workaround, I've commented the "usb_set_altinterface(udev, 0);" call at line 225 of the drivers/libusb.c source file. Thanks to this hack, the driver can dialog with the device. # upsdrvctl -u nut start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Generic HID driver 0.38 (2.7.2.5) USB communication driver 0.32 Using subd...

...1 - Bus : 001 5.019859 Matched expected vendor='ATCL FOR UPS'. 5.020208 USB device [0001:0000] opened I have also tried with blazer_usb and nutdrv_qx. With the former I get: 0.012149 Trying to match device 0.012194 Device matches 0.012224 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 0.012242 Trying megatec protocol... 0.012255 send: Q1 0.013044 read: Broken pipe 0.013543 Stall condition cleared 0.013564 blazer_status: short reply 0.013574 Status read 1 failed 0.013581 send: Q1 0.014632...

...ProductID: 3016 0.034097 - Manufacturer: unknown 0.034100 - Product: unknown 0.034102 - Serial Number: unknown 0.034105 - Bus: /dev/usb 0.034108 - Device release number: 0002 0.034111 Trying to match device 0.034128 Device matches 0.034135 nut_usb_set_altinterface: calling usb_set_altinterface(udev, 0) 0.034148 nut_usb_set_altinterface: usb_set_altinterface() should not be necessary - please email the nut-upsdev list with information about your UPS. 0.045127 Unable to get HID descriptor (Unknown error) Could you help please? Thanks and regar...

...s it possible that there is another copy of the driver running in the background? There is apparently an issue where we only write a PID file when the driver goes into the background, and "-D" prevents that. > Any recommendation on how to keep the drivers from disconnecting using the usb_set_altinterface? (PS. Is there a specific value to use?) >From the earlier usbconfig output, I only see "bAlternateSetting = 0x0000". Adding that option (as you did just now) defaults to a parameter of zero. I will look into this. FYI, some history is here: https://github.com/networkupstools/nut/...