search for: usb_claim_interfac

Hello, I'm currently try to get newhidups running with the newhidups driver from nut 2.0.2. After some USB issues (usb_claim_interface() works only as root so far) newhidups is recognizing the device. Though it doesn't detect any state changes, meaning when I run the battery test mode it's not recognized. I wanted to try the CVS version but it seems anonymous CVS is broken. The error messages looks like this: https://al...

...DETACH_KRNL_DRV + /* this method requires at least libusb 0.1.8: + * it force device claiming by unbinding + * attached driver... From libhid */ + retry = 3; + while (usb_set_configuration(dev_h, 1) != 0 && retry-- > 0) { +// while ((dev_claimed = usb_claim_interface(dev_h, 0)) != 0 && retry-- > 0) { + + upsdebugx(2, "failed to claim USB device, trying %d more time(s)...", retry); + + upsdebugx(2, "detaching kernel driver from USB device..."); + if (usb_detach_kernel_driver_np(dev_h, 0...

...TACH_KRNL_DRV + /* this method requires at least libusb 0.1.8: + * it force device claiming by unbinding + * attached driver... From libhid */ + retry = 3; + while (usb_set_configuration(dev_h, 1) != 0 && retry-- > 0) { +// while ((dev_claimed = usb_claim_interface(dev_h, 0)) != 0 && retry-- > 0) { + + upsdebugx(2, "failed to claim USB device, trying %d more time(s)...", retry); + + upsdebugx(2, "detaching kernel driver from USB device..."); + if (usb_detach_kernel_driver_np(dev_h,...

...TACH_KRNL_DRV + /* this method requires at least libusb 0.1.8: + * it force device claiming by unbinding + * attached driver... From libhid */ + retry = 3; + while (usb_set_configuration(dev_h, 1) != 0 && retry-- > 0) { +// while ((dev_claimed = usb_claim_interface(dev_h, 0)) != 0 && retry-- > 0) { + + upsdebugx(2, "failed to claim USB device, trying %d more time(s)...", retry); + + upsdebugx(2, "detaching kernel driver from USB device..."); + if (usb_detach_kernel_driver_np(dev_h,...

...open source fashion, I hacked at it till it worked. Couple things in this pull request: 1. Scale values for some of the SMART1500LCD parameters. 2. With my hardware and kernel, usbhid-ups wouldn't run more than 10 minutes before exiting with a fatal error. This seems to be related to holding usb_claim_interface() the entire life of the program. I've refactored claim_interface/release_interface calls to be around only when work is being done. Now usbhid-ups has run for 24+ hours without issue. 3. The very nature of USB in a home means that sometimes the driver will lose communications with the UPS (a...

...hacked at it till it worked. Couple things in this pull request: > > 1. Scale values for some of the SMART1500LCD parameters. Thanks! > 2. With my hardware and kernel, usbhid-ups wouldn't run more than 10 minutes before exiting with a fatal error. This seems to be related to holding usb_claim_interface() the entire life of the program. I've refactored claim_interface/release_interface calls to be around only when work is being done. Now usbhid-ups has run for 24+ hours without issue. Given how long we have been running with code that claims the interface at driver startup, I am a wary about...

Good Day all I am currently trying to get nut to work on a mac mini running OSX leopard . I have a usb ups and I am trying to use the megatec_usb driver. Can't claim USB device [0001:0000]: usb_claim_interface: couldn't claim interface Driver failed to start (exit status=1) Its seems as though OSX has "taken control" of the ups and nut cannot take ownership of the device. Has anybody else come across this problem before? Is there any way to tell osx to release the device? Any...

...continue; } - fatalx(EXIT_FAILURE, "Can't claim USB device [%04x:%04x]: %s", curDevice->VendorID, curDevice->ProductID, usb_strerror()); - } #else if (usb_claim_interface(udev, 0) < 0) { fatalx(EXIT_FAILURE, "Can't claim USB device [%04x:%04x]: %s", curDevice->VendorID, curDevice->ProductID, usb_strerror());

Joel Peshkin wrote: > > I hacked in the following additonal changes... > > Index: newhidups.c > =================================================================== > RCS file: /cvsroot/nut/nut/drivers/newhidups.c,v > retrieving revision 1.1.1.1.8.6.2.21 > diff -u -r1.1.1.1.8.6.2.21 newhidups.c > --- newhidups.c 7 Nov 2005 22:14:20 -0000 1.1.1.1.8.6.2.21 > +++

Since the issue of USB permissions keeps coming up on the lists, I am wondering if there is something we can do to improve the messages printed at the default debug level when starting a USB driver. For instance, it shouldn't be too hard to mention which user was configured for non-privileged operations. A lot of people tend to assume that unless indicated otherwise, starting a program as

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

...to `usb_busses' libusb.o(.text+0x75): In function `libusb_open': : undefined reference to `usb_open' libusb.o(.text+0x14a): In function `libusb_open': : undefined reference to `usb_set_altinterface' libusb.o(.text+0x15a): In function `libusb_open': : undefined reference to `usb_claim_interface' libusb.o(.text+0x17e): In function `libusb_open': : undefined reference to `usb_control_msg' libusb.o(.text+0x192): In function `libusb_open': : undefined reference to `usb_strerror' libusb.o(.text+0x203): In function `libusb_open': : undefined reference to `usb_get_string...

...pointer to incomplete type amload.c:823: warning: implicit declaration of function `usb_open` amload.c:830: warning: implicit declaration of function `usb_set_configuration` amload.c:832: warning: format argument is not a pointer (arg 2) amload.c:836: warning: implicit declaration of function `usb_claim_interface` amload.c:838: warning: format argument is not a pointer (arg 2) amload.c:843: warning: format argument is not a pointer (arg 2) amload.c:848: warning: format argument is not a pointer (arg 2) amload.c:857: warning: implicit declaration of function `usb_release_interface` amload.c:859: warnin...

Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker: