search for: usb_detach_kernel_driver_np

I doesn't fix any problems but I think it is nicer code. :-) I don't think we want to call usb_detach_kernel_driver_np unless we claimed the device. $ diff -uw libusb.c.bak libusb.c.new --- libusb.c.bak 2010-05-11 09:35:39.000000000 -0400 +++ libusb.c.new 2010-05-11 09:32:44.000000000 -0400 @@ -206,18 +206,21 @@ upsdebugx(2, "failed to claim USB device: %s&quo...

...g for libusb ldflags... -lusb-1.0 checking for libusb.h... yes checking for libusb_init... yes checking for libusb_strerror... yes checking for libusb_kernel_driver_active... yes checking for libusb_set_auto_detach_kernel_driver... yes checking for libusb_detach_kernel_driver... yes checking for libusb_detach_kernel_driver_np... no checking for usb_detach_kernel_driver_np... no checking for libusb_get_port_number... yes checking whether to build USB drivers... yes (libusb-1.0) checking whether to install hotplug rules... no checking whether to generate scripts/udev/nut-usbups.rules... yes * build USB drivers: yes (libus...

...nSUSE seems to be adopting the 0.1.1x numbering scheme for libusb-compat so that the package looks newer (0.1.13) than the real libusb-0.1.12: https://build.opensuse.org/package/view_file/openSUSE:13.2/libusb-compat/libusb-compat.spec?expand=1 Note the changes mentioned in the return codes for usb_detach_kernel_driver_np(): https://build.opensuse.org/package/view_file/openSUSE:13.2/libusb-compat/libusb-compat.changes?expand=1 Those are the sort of edge cases that haven't been fully tested with NUT. It seems like the path from NUT driver through libusb to the kernel is relatively unchanged with libusb-compa...

...gt; checking for libusb.h... yes > checking for libusb_init... yes > checking for libusb_strerror... yes > checking for libusb_kernel_driver_active... yes > checking for libusb_set_auto_detach_kernel_driver... yes > checking for libusb_detach_kernel_driver... yes > checking for libusb_detach_kernel_driver_np... no > checking for usb_detach_kernel_driver_np... no > checking for libusb_get_port_number... yes > checking whether to build USB drivers... yes (libusb-1.0) > checking whether to install hotplug rules... no > checking whether to generate scripts/udev/nut-usbups.rules... yes > *...

...nSUSE seems to be adopting the 0.1.1x numbering scheme for libusb-compat so that the package looks newer (0.1.13) than the real libusb-0.1.12: https://build.opensuse.org/package/view_file/openSUSE:13.2/libusb-compat/libusb-compat.spec?expand=1 Note the changes mentioned in the return codes for usb_detach_kernel_driver_np(): https://build.opensuse.org/package/view_file/openSUSE:13.2/libusb-compat/libusb-compat.changes?expand=1 Those are the sort of edge cases that haven't been fully tested with NUT. It seems like the path from NUT driver through libusb to the kernel is relatively unchanged with libusb-compa...

...nSUSE seems to be adopting the 0.1.1x numbering scheme for libusb-compat so that the package looks newer (0.1.13) than the real libusb-0.1.12: https://build.opensuse.org/package/view_file/openSUSE:13.2/libusb-compat/libusb-compat.spec?expand=1 Note the changes mentioned in the return codes for usb_detach_kernel_driver_np(): https://build.opensuse.org/package/view_file/openSUSE:13.2/libusb-compat/libusb-compat.changes?expand=1 Those are the sort of edge cases that haven't been fully tested with NUT. It seems like the path from NUT driver through libusb to the kernel is relatively unchanged with libusb-compa...

Hi, I am trying to get NUT 2.7.2 working on my Solaris 11.2 system with a PowerWalker 2000 VI PSW UPS. I have carefully configured the software such that it 'works' using custom values in the ups.conf file: driver = nutdrv_qx port = auto desc = "my UPS" protocol = voltronic-qs subdriver = cypress vendorid = 0665 productid = 5161 The problem I'm experiencing is that after a

...e ((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) < 0) { + upsdebugx(2, "failed to detach kernel driver from USB device..."); + } + + upsdebugx(2, "trying again to claim USB device..."); + } + + if (dev_claimed == 0) + dev_claimed = 1;...

...((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) < 0) { + upsdebugx(2, "failed to detach kernel driver from USB device..."); + } + + upsdebugx(2, "trying again to claim USB device..."); + } + + if (dev_claimed == 0) + dev_claimed = 1;...

...((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) < 0) { + upsdebugx(2, "failed to detach kernel driver from USB device..."); + } + + upsdebugx(2, "trying again to claim USB device..."); + } + + if (dev_claimed == 0) + dev_claimed = 1;...

...r gd include flags... using defaults checking for gd library flags... using defaults checking whether to build CGI programs... no checking for Net-SNMP cflags... not found checking for Net-SNMP libs... not found checking for libusb cflags... checking for libusb libs... -L/usr/lib -lusb checking for usb_detach_kernel_driver_np in -lusb... yes checking for Linux hiddev.h... using default: /usr/include/linux/hiddev.h checking state path... using default: /var/state/ups checking alt pid path... using default: /var/state/ups checking driver path... using default checking cgi path... using default checking html path... using...

...pkg-config: command not found not found checking for libhal ldflags via pkg-config... ./configure: line 1: pkg-config: command not found not found checking libhal.h usability... no checking libhal.h presence... no checking for libhal.h... no checking for libhal_ctx_init in -lhal... no checking for usb_detach_kernel_driver_np in -lusb... yes checking for Linux hiddev.h... /usr/include/linux/hiddev.h checking for SSL library availability... yes checking whether to enable SSL development code... yes checking for getaddrinfo... yes checking for freeaddrinfo... yes checking for struct addrinfo... yes checking for struct soc...

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 > +++

..., it looks like it built against v0.1.7 of libusb (yes i think that is derived from the one you mention), checking for libusb version via pkg-config... 0.1.7 found checking for libusb cflags... checking for libusb ldflags... -lusb checking for usb.h... yes checking for usb_init... yes checking for usb_detach_kernel_driver_np... no I will first investigate how to set the debug level. Regards, Richard On Sun, Apr 5, 2015 at 12:44 AM Charles Lepple <clepple at gmail.com> wrote: > On Apr 4, 2015, at 7:19 PM, Richard Flint <richard.flint at gmail.com> wrote: > > More extensive debugging by running t...

On Sep 9, 2015, at 9:40 AM, Rob Groner <rgroner at RTD.com> wrote: > > I'm not sure which USB lib it compiled against. What does this return? ldd /path/to/driver -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150909/ba08f4c0/attachment.html>

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

...0.1.7 of libusb (yes i think that is derived from the one you mention), > > checking for libusb version via pkg-config... 0.1.7 found > checking for libusb cflags... > checking for libusb ldflags... -lusb > checking for usb.h... yes > checking for usb_init... yes > checking for usb_detach_kernel_driver_np... no > > I will first investigate how to set the debug level. > > Regards, > Richard > > On Sun, Apr 5, 2015 at 12:44 AM Charles Lepple <clepple at gmail.com> wrote: > >> On Apr 4, 2015, at 7:19 PM, Richard Flint <richard.flint at gmail.com> >> wrote...

...checking for Net-SNMP libs... checking for net-snmp/net-snmp-config.h... no checking for init_snmp... no checking for libusb version via pkg-config... 0.1.12 found checking for libusb cflags... checking for libusb ldflags... -lusb checking for usb.h... yes checking for usb_init... yes checking for usb_detach_kernel_driver_np... yes checking for libneon version via pkg-config (0.25.0 minimum required)... none found checking for libneon cflags... checking for libneon ldflags... checking for ne_xmlreq.h... no checking for ne_xml_dispatch_request... no checking for libpowerman cflags... checking for libpowerman libs... che...

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:

Hi again, I've succeeded in compiling the svn trunk with the automake tools and wish to say thank you to Charles Lepple for his help. After fixing some parameters in the hotplug script I can now get access to the UPS on /dev/usb/hiddev0 (I added productid and vendorid of my ups to the usermap). I've decided to try the newhidups driver with -x generic parameter and got this response :