Citeren Greg Terkanian <[email protected]>:

I've compiled the 2.4.3 source with the proper options (through trial and error). I get the same initial error.

I told you that before. The device is still not autodetected, but at least the productid override now works.

When I run the driver directly with the following command, I get the following output:

r...@ccc-nms:/usr/src/nut-2.4.3# /lib/nut/usbhid-ups -DDDDD -a test -u root -x productid=4005
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
   0.000000     send_to_all: SETINFO driver.parameter.vendorid "09ae"
   0.000069     send_to_all: SETINFO driver.parameter.port "auto"
   0.000128     send_to_all: SETINFO driver.parameter.productid "4005"
   0.000169     debug level is '5'
   0.000676     upsdrv_initups...
   0.000882     Checking device (09AE/4005) (001/014)
   0.013161     - VendorID: 09ae
   0.013208     - ProductID: 4005
   0.013242     - Manufacturer: unknown
   0.013275     - Product: unknown
   0.013308     - Serial Number: unknown
   0.013341     - Bus: 001
   0.013373     Trying to match device
   0.013456     Device matches
0.036159 Unable to get HID descriptor (error sending control message: Protocol error)

This is bad.

   0.036210     i=0, extra[i]=09, extra[i+1]=21
0.036248 HID descriptor, method 2: (9 bytes) => 09 21 10 01 00 01 22 d6 04
   0.036282     HID descriptor length 1238
   0.040204     Unable to get Report descriptor: Protocol error

This is really bad.

   0.040276     Checking device (1D6B/0002) (001/001)
   0.040339     - VendorID: 1d6b
   0.040378     - ProductID: 0002
   0.040412     - Manufacturer: Linux 2.6.28-18-server usb-vhci-driver
   0.040446     - Product: vhci
   0.040480     - Serial Number: usb-vhci-driver
   0.040513     - Bus: 001
   0.040546     Trying to match device
   0.040580     Device does not match - skipping
   0.040616     No appropriate HID device found
   0.040653     No matching HID UPS found

Could you post the output of

    lsusb -vvv

for this device? Either the libusb library fails to break up control messages in chunks the UPS can handle, or your UPS uses a different endpoint from what we expect. I'm not sure which one is worse...

Best regards, Arjen
--
Please keep list traffic on the list


_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Reply via email to