Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 14, 2013, at 2:02 PM, Matus UHLAR - fantomas wrote: But that is still an issue of libusb,not NUT, correct? I can upgrade openwrt on my router ... On 14.04.13 15:57, Charles Lepple wrote: It does seem that it is a libusb-1.0 issue, yes. They may not be aware of it, though (since it probably only comes up when dealing with broken USB descriptors like on your UPS). Before bothering to upgrade, check to see if they have a newer libusb-1.0, and then we can see if they might have fixed this. Are there any test tools that come with libusb-1.0? The libusb-0.1 source tree had a tool that was like a miniature lsusb: it would print some descriptor information, but not much else. I don't know if many distributions packaged that. If there is such a tool for 1.0, that would make a great test case to confirm that the problem is in libusb-1.0. after further checking, it seems that the issue lies in libusb_compat - 0.1.4-1 present in current OpenWRT trunk. After moving to OpenWRT 12.09 containing libusb - 0.1.12-3 the UPS is detected just fine. Detected a UPS: EATON/Protection Station 800 I'm getting other error: libusb_get_interrupt: Connection timed out but this may be standard process, is it? now I wonder if nut could support libusb-1.0 (does it?) -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Windows found: (R)emove, (E)rase, (D)elete ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On 13.04.13 14:58, Matus UHLAR - fantomas wrote: as seen on my home PC: http://test.fantomas.sk/pc_lsusb-vvv-d_0463: I will try to get output on my home NAS (ARM architecture) here it is: http://test.fantomas.sk/nas_lsusb-vvv-d_0463 While it seems that the USB data are broken, both QNAP NAS firmware and debian squeeze can handle it. But that is still an issue of libusb,not NUT, correct? I can upgrade openwrt on my router ... -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Linux IS user friendly, it's just selective who its friends are... ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 14, 2013, at 2:02 PM, Matus UHLAR - fantomas wrote: On 13.04.13 14:58, Matus UHLAR - fantomas wrote: as seen on my home PC: http://test.fantomas.sk/pc_lsusb-vvv-d_0463: I will try to get output on my home NAS (ARM architecture) here it is: http://test.fantomas.sk/nas_lsusb-vvv-d_0463 While it seems that the USB data are broken, both QNAP NAS firmware and debian squeeze can handle it. But that is still an issue of libusb,not NUT, correct? I can upgrade openwrt on my router ... It does seem that it is a libusb-1.0 issue, yes. They may not be aware of it, though (since it probably only comes up when dealing with broken USB descriptors like on your UPS). Before bothering to upgrade, check to see if they have a newer libusb-1.0, and then we can see if they might have fixed this. Are there any test tools that come with libusb-1.0? The libusb-0.1 source tree had a tool that was like a miniature lsusb: it would print some descriptor information, but not much else. I don't know if many distributions packaged that. If there is such a tool for 1.0, that would make a great test case to confirm that the problem is in libusb-1.0. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 14, 2013, at 2:02 PM, Matus UHLAR - fantomas wrote: here it is: http://test.fantomas.sk/nas_lsusb-vvv-d_0463 BTW, looks like that URL got truncated: http://test.fantomas.sk/nas_lsusb-vvv-d_0463: -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote: libusb: 0.00 error [get_config_descriptor] short output read 0/8 On 05.04.13 20:39, Charles Lepple wrote: Reading the config descriptor is a pretty basic operation. What does lsusb -vvv -d 0463: return? On Apr 6, 2013, at 10:08 AM, Matus UHLAR - fantomas wrote: http://test.fantomas.sk/tplink2543nd_lsusb-vvv-d_0463: On 06.04.13 10:20, Charles Lepple wrote: Hmm, perhaps Arnaud can ask someone what the other five configurations are: idVendor 0x0463 MGE UPS Systems idProduct 0x UPS bcdDevice1.00 iManufacturer 1 EATON iProduct2 Protection Station iSerial 4 AN2E49008 bNumConfigurations 6 Is there any way you can build against the real libusb-0.1, versus the compatibility layer from 1.0? They may have different error checking strategies when reading descriptors. as seen on my home PC: http://test.fantomas.sk/pc_lsusb-vvv-d_0463: I will try to get output on my home NAS (ARM architecture) -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote: libusb: 0.00 error [get_config_descriptor] short output read 0/8 On 05.04.13 20:39, Charles Lepple wrote: Reading the config descriptor is a pretty basic operation. What does lsusb -vvv -d 0463: return? On Apr 6, 2013, at 10:08 AM, Matus UHLAR - fantomas wrote: too much of output to send here: http://test.fantomas.sk/tplink2543nd_lsusb-vvv-d_0463: On 06.04.13 10:20, Charles Lepple wrote: Hmm, perhaps Arnaud can ask someone what the other five configurations are: idVendor 0x0463 MGE UPS Systems idProduct 0x UPS bcdDevice1.00 iManufacturer 1 EATON iProduct2 Protection Station iSerial 4 AN2E49008 bNumConfigurations 6 Is there any way you can build against the real libusb-0.1, versus the compatibility layer from 1.0? They may have different error checking strategies when reading descriptors. I don't think I can build it anywhere now (no experience with cross-compiling on different architecture), but I can try looking at it on my QNAP NAS and linux PC. ...it seems that openwrt uses libusbx fork, version 1.0.9 and there's 1.0.12 available with some changes to related code... -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. On the other hand, you have different fingers. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote: libusb: 0.00 error [get_config_descriptor] short output read 0/8 On 05.04.13 20:39, Charles Lepple wrote: Reading the config descriptor is a pretty basic operation. What does lsusb -vvv -d 0463: return? too much of output to send here: http://test.fantomas.sk/tplink2543nd_lsusb-vvv-d_0463: -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Fighting for peace is like fucking for virginity... ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 6, 2013, at 10:08 AM, Matus UHLAR - fantomas wrote: On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote: libusb: 0.00 error [get_config_descriptor] short output read 0/8 On 05.04.13 20:39, Charles Lepple wrote: Reading the config descriptor is a pretty basic operation. What does lsusb -vvv -d 0463: return? too much of output to send here: http://test.fantomas.sk/tplink2543nd_lsusb-vvv-d_0463: Hmm, perhaps Arnaud can ask someone what the other five configurations are: idVendor 0x0463 MGE UPS Systems idProduct 0x UPS bcdDevice1.00 iManufacturer 1 EATON iProduct2 Protection Station iSerial 4 AN2E49008 bNumConfigurations 6 Is there any way you can build against the real libusb-0.1, versus the compatibility layer from 1.0? They may have different error checking strategies when reading descriptors. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 4, 2013, at 5:38 PM, Matus UHLAR - fantomas wrote: libusb-1.0 - 1.0.9-1 libusb-compat - 0.1.4-1 On 04.04.13 22:14, Charles Lepple wrote: Does libusb-compat have an equivalent to the USB_DEBUG that was present in libusb-0.1? Also, the drivers drop privileges when run as root. Try -u root to see if it is a permissions problem. there seems to be LIBUSB_DEBUG symbol in libusb-1.0. libusb-compat apparently uses libusb, so I got this: root@gw:~# export LIBUSB_DEBUG=9 root@gw:~# /lib/nut/usbhid-ups -a eaton -u root -D -D -D Network UPS Tools - Generic HID driver 0.38 (2.6.5) USB communication driver 0.31 0.00 debug level is '3' 0.002127 upsdrv_initups... libusb: 0.00 error [get_config_descriptor] short output read 0/8 0.008228 Checking device (1D6B/0002) (001/001) 0.009258 - VendorID: 1d6b 0.009537 - ProductID: 0002 0.009749 - Manufacturer: Linux 3.8.3 ehci_hcd 0.009961 - Product: EHCI Host Controller 0.010173 - Serial Number: ehci-platform 0.010370 - Bus: 001 0.010562 Trying to match device 0.010817 Device does not match - skipping 0.011103 No appropriate HID device found now this got somewhere... open(/dev/bus/usb/001/003, O_RDONLY) = 7 read(7, \t\2\\0\1\1\0\240, 8)= 8 open(/dev/bus/usb/001/003, O_RDONLY) = 7 read(7, \t\2\\0\1\1\0\240\n\t\4\0\0\1\3\0\0\0\t!\20\20!\1\M\2\7\5\201\3\10..., 34) = 34 open(/dev/bus/usb/001/003, O_RDONLY) = 7 read(7, \t\2\\0\1\1, 6) = 6 read(7, , 8) = 0 write(2, libusb: , 8) = 8 write(2, 0, 1)= 1 write(2, ., 1)= 1 write(2, 0, 1)= 1 write(2, 0, 1)= 1 write(2, 0, 1)= 1 write(2, 0, 1)= 1 write(2, 0, 1)= 1 write(2, 0, 1)= 1 write(2, , 1)= 1 write(2, error, 5)= 5 write(2, [, 2) = 2 write(2, get_config_descriptor, 21) = 21 write(2, ] , 2) = 2 write(2, short output read , 18) = 18 write(2, 0, 1)= 1 write(2, /, 1)= 1 write(2, 8, 1)= 1 write(2, \n, 1) = 1 -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Windows 2000: 640 MB ought to be enough for anybody ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote: libusb: 0.00 error [get_config_descriptor] short output read 0/8 Reading the config descriptor is a pretty basic operation. What does lsusb -vvv -d 0463: return? -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] can't find UPS on openwrt/arm
On Apr 4, 2013, at 5:38 PM, Matus UHLAR - fantomas wrote: libusb-1.0 - 1.0.9-1 libusb-compat - 0.1.4-1 Does libusb-compat have an equivalent to the USB_DEBUG that was present in libusb-0.1? Also, the drivers drop privileges when run as root. Try -u root to see if it is a permissions problem. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
