Something strange was with permissions/device files. I deleted /dev/bus/usb, then - re-inserted hid-generic, and usbhid-ups starts. libusb debug says nothing useful. I pushed changes into git, with hack in hotplug.sh (libusb detached usbhid driver and re-attached dummy driver so /dev/bus/usb/xxx/yyy node is re-created with root:root owner:group).
In future it'll be good to add /etc/hotplug.d with scripts that'll be called (for specific device driver or vid/pid or some else conditions). 21.11.2014 20:10, kp kirchdoerfer пишет: > Hi Andrew; > > Am Freitag, 21. November 2014, 19:16:50 schrieb Andrew: >> 21.11.2014 19:05, kp kirchdoerfer пишет: >>> Hi Andrew; >>> >>> Am Freitag, 21. November 2014, 18:34:18 schrieb Andrew: >>>> Hi all. >>>> >>>> It seems like NUT doesn't work with libusb-compat correctly. When it's >>>> runned as nut user - it fails with permissions error; when it runs at >>>> root - it can't detach hid driver so fails with i/o error. >>>> >>>> Anybody tested libusb-related software? >>> To my own surprise there currently only two packages that seems to require >>> libusb*, I haven't tested neither of these. >>> >>> usbmodeswitch requires libusb, a package which may be used by David AFAIK, >>> and nut, which does not work with libusb, but should with libusb-compat. >>> >>> Seems we do have a problem... >>> >>> kp >> usb-modeswitch should work ok with legacy libusb-0.xxx (at least old >> versions). maybe we just need to place fresh rules to old usb-modeswitch >> if it becomes incompatible with old libusb. >> >> nut is linked against libusb and libusb-compat, and after system upgrade >> from 4.x-trunk to pre-5.2.1 trunk, I have broken ups montoring. I asked >> in nut maillist, and got answer that nut wasn't even checked with >> libusb-compat, it should work with legacy libusb. > I looked into request on nut-user and it's apparently a few days old and I > assume you've invested the issue a bit further, so you may have already > investigated, if our move to the 3.10 kernel could cause the issue? > > Have you been able to get more output with LIBSUB_DEBUG? I remember I had to > solve an issue with nut and an UPS almost with debugging the output and the > help of the nut-maintainers - they have been providing outstanding support, > and it seems they still do so. > > I've looked into various mailing-lists and bug-reports when moving to libusb1 > and nut failed - AFAIR they all recommended libusb-compat as a solution.... > >> I'll try to build nut with old libusb, if it'll work - I'll look on >> usb-modeswitch. >> > Ok; I was about to prepare a 5.1.2 release, but will wait for your verdict > about libusb.... > > kp > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > > _______________________________________________ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
