On 10 January 2011 20:28, Mick <[email protected]> wrote: > On Monday 10 January 2011 12:19:34 you wrote: >> Hi Mick >> >> 2011/1/9 Mick <[email protected]> > >> > -rwxr-xr-x 1 root root 17840 Jul 25 11:45 /usr/libexec/hald-addon-hid-ups > [snip ...] > >> > Could any of the above be causing the clash? >> >> indeed, /usr/libexec/hald-addon-hid-ups which is part of UPower (integrated >> power management), which is automatically launched when a new USB/HID UPS >> is plugged. >> since UPower is running as root, it will prevent usbhid-ups from claiming >> back your UPS after software disconnection. >> you may try to run nut as root to check if you still see the claim >> interface failure. >> >> I'll have to check UPower, since iirc, it wasn't previously running as root >> (or I'm maybe confusing with HAL...) > > So assuming that the new driver can now deal with my UPS, is this something > that I'll have wait for to settle, as hal is deprecated and on a path to be > replaced with upower?
Some more testing tonight and after a reboot I get this. :-) # upsc iDowell battery.capacity: 0.03 battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 device.mfr: iDowell device.model: iBox device.serial: 00000001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0300 driver.parameter.vendorid: 075d driver.version: 2.6.0-pre1 driver.version.data: iDowell HID 0.1 driver.version.internal: 0.35 ups.delay.shutdown: 20 ups.delay.start: 30 ups.mfr: iDowell ups.model: iBox ups.productid: 0300 ups.serial: 00000001 ups.status: OL CHRG ups.timer.start: 0 ups.vendorid: 075d While nut is running, my logs fill up with: Jan 10 22:50:06 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:08 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:10 compaq usbhid-ups[5083]: libusb_get_report: No error Jan 10 22:50:12 compaq usbhid-ups[5083]: libusb_get_report: No error regularly at 2 second intervals. Is there a way to tell it to not log such messages (or log them only once?) If I add "pollonly" in ups.conf I get these messages: Jan 10 23:15:57 compaq upsd[5995]: listening on 127.0.0.1 port 3493 Jan 10 23:15:57 compaq upsd[5995]: Connected to UPS [iDowell]: usbhid-ups-iDowell Jan 10 23:15:57 compaq upsd[5995]: allowfrom in upsd.users is no longer used Jan 10 23:15:57 compaq upsd[5996]: Startup successful Jan 10 23:15:57 compaq usbhid-ups[5945]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 10 23:15:57 compaq usbhid-ups[5945]: Got disconnected by another driver: Device or resource busy Jan 10 23:15:59 compaq usbhid-ups[5945]: libusb_get_report: could not claim interface 0: Device or resource busy Jan 10 23:15:59 compaq usbhid-ups[5945]: Got disconnected by another driver: Device or resource busy ... and so on. Not sure if this is how it should be - but within a few minutes I get: # upsc iDowell Error: Data stale PS. What is the meaning of: battery.capacity: 0.03 ? -- Regards, Mick _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
