search for: dump_curr_config_desc

...was also not as big as you made it out to be. > > Well, I didn't expect the driver to fail *that* badly :-) > > Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) > > usbconfig -u 4 -a 2 dump_curr_config_desc Here is output of the command. Thank you for your help with this. ugen4.2: <product 0x0601 CyberPower Systems> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0029 bNumInterface...

...bMaxPacketSize0 = 0x0008 ? idVendor = 0x09ae ? idProduct = 0x3016 ? bcdDevice = 0x0002 ? iManufacturer = 0x0003? <retrieving string failed> ? iProduct = 0x0001? <TRIPP LITE UPS> ? iSerialNumber = 0x0005? <retrieving string failed> ? bNumConfigurations = 0x0001 usbconfig -u 0 -a 5 dump_curr_config_desc ?datanas: ~# usbconfig -u 0 -a 5 dump_curr_config_desc ugen0.5: <TRIPP LITE UPS Tripp Lite> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) ?Configuration index 0??? bLength = 0x0009 ??? bDescriptorType = 0x0002 ??? wTotalLength = 0x0022 ??? bNumInterfaces = 0x0001 ??? bConfiguratio...

Here is what I get: # usbconfig -u 1 -a 3 dump_curr_config_desc ugen1.3: <Tripp Lite TRIPP LITE UPS> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <no...

----- On Sep 23, 2015, at 9:26 AM, Charles Lepple clepple at gmail.com wrote: > On Sep 23, 2015, at 9:22 AM, Louis G. <louis at frentzgzesh.info> wrote: >> >> >Can you open up a root shell, kill the old `usbhid-ups` process, and run it from >> >the command line? >> > >> > /usr/local/libexec/nut/usbhid-ups -a ups -DDD >> > >>

> >> usbconfig -u 4 -a 2 dump_curr_config_desc > > Here is output of the command. Thank you for your help with this. > > ugen4.2: <product 0x0601 CyberPower Systems> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA) > [...] > bLength = 0x09 > bDescriptorType = 0x21 > bDescriptorSubType = 0x10 >&...

Hi Everyone, I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD 11.2, nut 2.7.4 installed from FreeBSD port. The debug output is rather big when I'm starting usbhid-ups initially, Please find that attached (gzipped to comply with message size limit). Subsequently, until I unplug and replug the USB cable, I'm geting a shorter debug output, like this: Network UPS

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

...bMaxPacketSize0 = 0x0008 ? idVendor = 0x09ae ? idProduct = 0x3016 ? bcdDevice = 0x0002 ? iManufacturer = 0x0003? <retrieving string failed> ? iProduct = 0x0001? <TRIPP LITE UPS> ? iSerialNumber = 0x0005? <retrieving string failed> ? bNumConfigurations = 0x0001 usbconfig -u 0 -a 5 dump_curr_config_desc ?datanas: ~# usbconfig -u 0 -a 5 dump_curr_config_desc ugen0.5: <TRIPP LITE UPS Tripp Lite> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) ?Configuration index 0??? bLength = 0x0009 ??? bDescriptorType = 0x0002 ??? wTotalLength = 0x0022 ??? bNumInterfaces = 0x0001 ??? bConfiguratio...

...r Power CP900AVR laying around that I can test with. Joe Gzesh Sent from Zimbra Open Source Mail Server. Hosted at my House. Ask me how to set up your own Zimbra server. ----- On Sep 25, 2015, at 7:34 AM, Joseph Gzesh louis at frentzgzesh.info wrote: >> >>> usbconfig -u 4 -a 2 dump_curr_config_desc >> >> Here is output of the command. Thank you for your help with this. >> >> ugen4.2: <product 0x0601 CyberPower Systems> at usbus4, cfg=0 md=HOST spd=LOW >> (1.5Mbps) pwr=ON (50mA) >> > [...] >> bLength = 0x09 >> bDescriptorType = 0x21 &...

...te: > > The output was also not as big as you made it out to be. Well, I didn't expect the driver to fail *that* badly :-) Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) usbconfig -u 4 -a 2 dump_curr_config_desc -- Charles Lepple clepple at gmail

On Sep 24, 2015, at 10:28 AM, Louis G. <louis at frentzgzesh.info> wrote: > >> usbconfig -u 4 -a 2 dump_curr_config_desc > > Here is output of the command. Thank you for your help with this. > > ugen4.2: <product 0x0601 CyberPower Systems> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA) > [...] > bLength = 0x09 > bDescriptorType = 0x21 > bDescriptorSubType = 0...

...ort of thing you would want to rely on. You may have better luck using a different system running the NUT driver, such as a Raspberry Pi or Beaglebone Black, as ARM boards seem less affected (but not 100% reliable) with 3016 devices. Can you try the following commands as root? usbconfig -u 1 -a 3 dump_curr_config_desc usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 (The "-u" and "-a" options are based on the /dev/ugen1.3 line above - adjust the numbers as appropriate after unplugging and re-plugging the USB cable.) Since usbconfig is part of the base FreeBSD distribution, and not p...

On Aug 19, 2018, at 3:03 PM, Valentin Merkulov <schnobel at ickis.net> wrote: > > Here is what I get: > > # usbconfig -u 1 -a 3 dump_curr_config_desc > ugen1.3: <Tripp Lite TRIPP LITE UPS> at usbus1, cfg=0 md=HOST spd=LOW > (1.5Mbps) pwr=ON (100mA) > [...] Hmm, that may be an issue on the NUT side, then. (You might see issues if you run those commands repeatedly, though.) We are working on another branch that uses the newer lib...

...5.279939 Unable to get Report descriptor: Input/output error My other concern is that FreeBSD might not allow the method that we use to retrieve the Report Descriptor. What do the following commands return (need to run them as root)? usbconfig -u 0 -a 5 dump_device_desc usbconfig -u 0 -a 5 dump_curr_config_desc usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 (I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that might change if the UPS USB cable is unplugged and re-inserted.) > cat /var/etc/ups.conf > [upstl1300] > driver = usbhid-ups > port = aut...

...error). 0.033456 [D1] upsdrv_cleanup... On Mon, Aug 20, 2018 at 4:33 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 19, 2018, at 3:03 PM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> Here is what I get: >> >> # usbconfig -u 1 -a 3 dump_curr_config_desc >> ugen1.3: <Tripp Lite TRIPP LITE UPS> at usbus1, cfg=0 md=HOST spd=LOW >> (1.5Mbps) pwr=ON (100mA) >> > [...] > > Hmm, that may be an issue on the NUT side, then. (You might see issues if you run those commands repeatedly, though.) > > We are working on anot...

...ptor. 0.043731 [D2] nut_libusb_open: unable to retrieve any HID descriptor. 0.043762 [D2] nut_libusb_open: no appropriate HID device found. 0.043768 No matching HID UPS found 0.043782 [D1] upsdrv_cleanup... usbconfig commands return the following: # usbconfig -u 1 -a 3 dump_curr_config_desc ugen1.3: <Tripp Lite TRIPP LITE UPS> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <n...

...? 5.279939? ? Unable to get Report descriptor: Input/output error My other concern is that FreeBSD might not allow the method that we use to retrieve the Report Descriptor. What do the following commands return (need to run them as root)? usbconfig -u 0 -a 5 dump_device_desc usbconfig -u 0 -a 5 dump_curr_config_desc usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 (I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that might change if the UPS USB cable is unplugged and re-inserted.) > cat /var/etc/ups.conf > [upstl1300] >? ? ? ? driver = usbhid-ups >? ? ? ? port = auto...

Attached are config.log and usbhid-ups output with -u root (gzipped). Now driver output looks a lot like the one from port build. On Mon, Aug 20, 2018 at 1:42 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 20, 2018, at 1:03 AM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> 0.033412 [D3] nut_usb_claim_interface: failed to claim USB >>