After installing nut 2.6.5-r1, applying the fix as described in bug #486640 and configuring /etc/nut/ups.conf, running the command upsdrvctl start causes kernel log lines such as Aug 8 23:09:21 scotty kernel: [14901.955066] ehci-pci 0000:00:1d.0: reused qh ffff88030bd7b500 schedule Aug 8 23:09:21 scotty kernel: [14901.955072] usb 2-1.3: link qh16-0601/ffff88030bd7b500 start 5 [1/2 us] Aug 8 23:09:21 scotty kernel: [14902.204922] usb 2-1.3: unlink qh16-0601/ffff88030bd7b500 start 5 [1/2 us] to be repeated until upsdrvctl stop is run. Reproducible: Always Steps to Reproduce: 1. Run upsdrvctl start Actual Results: Syslog flooded with usb link/unlink notices. About one tripplet of lines every second. Expected Results: No syslog flood. emerge --info: Portage 2.2.8-r1 (default/linux/amd64/13.0/desktop, gcc-4.7.3, glibc-2.17, 3.12.21-gentoo-r1-nvidia x86_64) ================================================================= System uname: Linux-3.12.21-gentoo-r1-nvidia-x86_64-Intel-R-_Core-TM-_i3-2100_CPU_@_3.10GHz-with-gentoo-2.2 KiB Mem: 12275136 total, 9562080 free KiB Swap: 4194300 total, 4194300 free Timestamp of tree: Sun, 20 Jul 2014 11:30:01 +0000 ld GNU ld (GNU Binutils) 2.23.2 ccache version 3.1.9 [enabled] app-shells/bash: 4.2_p45 dev-lang/python: 2.7.6, 3.2.5-r3, 3.3.3 dev-util/ccache: 3.1.9-r3 dev-util/cmake: 2.8.12.2-r1 dev-util/pkgconfig: 0.28-r1 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.12.4 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.11.6, 1.12.6, 1.14.1 sys-devel/binutils: 2.23.2 sys-devel/gcc: 4.7.3-r1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4.2-r1 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.12 (virtual/os-headers) sys-libs/glibc: 2.17 Repositories: gentoo crossdev local ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA ut2003" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -msse4.1 -msse4.2 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.4/ext-active/ /etc/php/cgi-php5.4/ext-active/ /etc/php/cli-php5.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo" CXXFLAGS="-march=native -msse4.1 -msse4.2 -O2 -pipe" DISTDIR="/portage/distfiles" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs ccache config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://distfiles.gentoo.org" LANG="fr_BE.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j5" PKGDIR="/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/portage/tmp" PORTDIR="/portage/portage.d" PORTDIR_OVERLAY="/portage/overlay.d/crossdev /portage/overlay.d/local" USE="X a52 aac acl acpi alsa amd64 avahi berkdb bindist branding bzip2 cairo cdda cddb cdr cli consolekit cracklib crypt cups cxx dbus dirac dri dts dvd dvdr emboss encode exif fam firefox flac fontconfig fortran g3dvl gdbm gif gnome-keyring gnutls gpm gstreamer gtk iconv id3tag ipv6 jpeg lcms libnotify lzma lzo mad mmx mmxext mng modules mp3 mp4 mpeg multilib musepack ncurses nls nntp nptl offensive ogg opengl openmp pam pango pcre pdf png policykit ppds qt3support readline schroedinger sdl session slang spell sse sse2 ssl ssse3 startup-notification svg tcpd theora threads tiff truetype udev udisks unicode upower usb v4l vaapi vdpau vorbis wavpack x264 xcb xml xv xvid zeroconf zlib" ABI_X86="64" ALSA_CARDS="hda-intel" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="mustek" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="linuxinput keyboard mouse evdev wacom" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="fr en_GB en" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-3 php5-4" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" QEMU_SOFTMMU_TARGETS="arm aarch64 i386 x86_64" QEMU_USER_TARGETS="arm aarch64 i386 x86_64" RUBY_TARGETS="ruby19 ruby20" SANE_BACKENDS="gt68xx artec artec_eplus48k mustek mustek_pp mustek_usb plustek plustek_pp" USERLAND="GNU" VIDEO_CARDS="nvidia nouveau intel fbdev vesa" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, SYNC, USE_PYTHON Other usb packages are: - dev-libs/libusb-compat-0.1.5-r3 - dev-libs/libusb-1.0.18[udev] (because of pcscd IIRC) UPS is a Eaton Ellipse Pro (idVendor=0463, idProduct=ffff) Note that after a while, there seems to be like a new USB detection of the UPS, as if it had been plugged in again after a couple of minutes. I don't think it's expected either. Changing the USB port dies no change.
Here's /etc/nut/ups.conf as suggested by nut-scanner -U (after symlinking /lib/libusb.so): [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "0463" productid = "FFFF" product = "Ellipse PRO" serial = "G354E21053" vendor = "EATON" bus = "002"
Could be bad hardware (including USB hubs, controllers and cables).
(In reply to Jeroen Roovers from comment #2) > Could be bad hardware (including USB hubs, controllers and cables). I have other USB peripherals and disks and none of them exhibit that problem. It's also a brand new UPS, just bought it yesterday :( .
I have changed the cable, plugged it into all available ports, same thing. It's only when the command is run that the problem occurs. Honestly I doubt it's a hardware problem but it's more of a hope and I'd like to have a clue. All of my devices do work properly on all USB ports. I've also checked BeID module (which, besides, is pretty sensible to software changes) again and it works like a charm. Tested all my USB disks, none of them fail and syslog remains stable, no log flood. Guess I can exclude my PC hardware... Thing is every five minutes usbhid seems to re-detect the UPS: Aug 9 11:12:28 scotty kernel: [ 3454.225953] usb 2-1.5: unlink qh16-0601/ffff88030c149080 start 14 [1/2 us] Aug 9 11:12:28 scotty kernel: [ 3454.238375] ehci-pci 0000:00:1d.0: reused qh ffff88030c149080 schedule Aug 9 11:12:28 scotty kernel: [ 3454.238382] usb 2-1.5: link qh16-0601/ffff88030c149080 start 14 [1/2 us] Aug 9 11:12:28 scotty kernel: [ 3454.260637] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0020 Aug 9 11:12:28 scotty kernel: [ 3454.260876] hub 2-1:1.0: port 5, status 0100, change 0001, 12 Mb/s Aug 9 11:12:28 scotty kernel: [ 3454.260880] usb 2-1.5: USB disconnect, device number 15 Aug 9 11:12:28 scotty kernel: [ 3454.260882] usb 2-1.5: unregistering device Aug 9 11:12:28 scotty kernel: [ 3454.260884] usb 2-1.5: unregistering interface 2-1.5:1.0 Aug 9 11:12:28 scotty kernel: [ 3454.260918] usb 2-1.5: unlink qh16-0601/ffff88030c149080 start 14 [1/2 us] Aug 9 11:12:28 scotty kernel: [ 3454.260921] ehci-pci 0000:00:1d.0: shutdown urb ffff8802f821e540 ep1in-intr Aug 9 11:12:28 scotty kernel: [ 3454.262375] usbhid 2-1.5:1.0: removing 97 minor Aug 9 11:12:28 scotty kernel: [ 3454.262558] usb 2-1.5: usb_disable_device nuking all URBs Aug 9 11:12:28 scotty kernel: [ 3454.366415] hub 2-1:1.0: debounce: port 5: total 100ms stable 100ms status 0x100 Aug 9 11:12:29 scotty kernel: [ 3455.028205] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0020 Aug 9 11:12:29 scotty kernel: [ 3455.028513] hub 2-1:1.0: port 5, status 0101, change 0001, 12 Mb/s Aug 9 11:12:29 scotty kernel: [ 3455.131967] hub 2-1:1.0: debounce: port 5: total 100ms stable 100ms status 0x101 Aug 9 11:12:29 scotty kernel: [ 3455.142916] hub 2-1:1.0: port 5 not reset yet, waiting 10ms Aug 9 11:12:29 scotty kernel: [ 3455.204914] usb 2-1.5: new low-speed USB device number 16 using ehci-pci Aug 9 11:12:29 scotty kernel: [ 3455.306859] hub 2-1:1.0: port 5 not reset yet, waiting 10ms Aug 9 11:12:29 scotty kernel: [ 3455.678229] usb 2-1.5: skipped 1 descriptor after interface Aug 9 11:12:29 scotty kernel: [ 3455.722961] usb 2-1.5: default language 0x0409 Aug 9 11:12:30 scotty kernel: [ 3455.997696] usb 2-1.5: udev 16, busnum 2, minor = 143 Aug 9 11:12:30 scotty kernel: [ 3455.997710] usb 2-1.5: New USB device found, idVendor=0463, idProduct=ffff Aug 9 11:12:30 scotty kernel: [ 3455.997713] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=4 Aug 9 11:12:30 scotty kernel: [ 3455.997715] usb 2-1.5: Product: Ellipse PRO Aug 9 11:12:30 scotty kernel: [ 3455.997718] usb 2-1.5: Manufacturer: EATON Aug 9 11:12:30 scotty kernel: [ 3455.997720] usb 2-1.5: SerialNumber: G354E21053 Aug 9 11:12:30 scotty kernel: [ 3455.997916] usb 2-1.5: usb_probe_device Aug 9 11:12:30 scotty kernel: [ 3455.997923] usb 2-1.5: configuration #1 chosen from 1 choice Aug 9 11:12:30 scotty kernel: [ 3455.998242] usb 2-1.5: adding 2-1.5:1.0 (config #1, interface 0) Aug 9 11:12:30 scotty kernel: [ 3455.998286] usbhid 2-1.5:1.0: usb_probe_interface Aug 9 11:12:30 scotty kernel: [ 3455.998289] usbhid 2-1.5:1.0: usb_probe_interface - got id Aug 9 11:12:34 scotty kernel: [ 3459.764271] usbhid 2-1.5:1.0: looking for a minor, starting at 96 Aug 9 11:12:34 scotty kernel: [ 3459.764481] hid-generic 0003:0463:FFFF.000E: hiddev0,hidraw2: USB HID v1.10 Device [EATON Ellipse PRO] on usb-0000:00:1d.0-1.5/input0 Aug 9 11:12:34 scotty kernel: [ 3459.769720] usb 2-1.5: link qh16-0601/ffff88030be49f80 start 15 [1/2 us] I'm rebooting right now to check the UPS under Windows.
Ok, it is most definitely not a hardware problem: the thing works under Windows XP (yeah, like to live dangerously). I installed the management software and the latter did fetch its update (for the software stack, not the UPS firmware) and Eaton Companion installation was successful. The Companion window showed me the power consumption, remaining time and so on. So, no, it's not a hardware issue. I tend to believe it since reading https://bugs.gentoo.org/show_bug.cgi?id=486640#c6 .
Further investigation led me to plug the UPS to another Linux machine, a Linux Mint 16 (Petra) system. I just plugged the device in, I did not run the UPS daemon for nut is not installed on that system — fact I don't know what to install because the power manager applet seems to detect the Eaton Ellipse PRO and show an icon in the notification area. But as expected under Linux, current charge and remaining time are all zero. Now with the device plugged in, every exact 5 minutes the system log shows a USB disconnect event and one second later a USB reconnect. Just like this: Aug 10 17:54:55 Latitude-D420 kernel: [ 301.736219] usb 5-1: USB disconnect, device number 2 Aug 10 17:54:56 Latitude-D420 kernel: [ 302.692177] usb 5-1: new low-speed USB device number 3 using uhci_hcd Aug 10 17:54:57 Latitude-D420 kernel: [ 303.561261] usb 5-1: New USB device found, idVendor=0463, idProduct=ffff Aug 10 17:54:57 Latitude-D420 kernel: [ 303.561272] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4 Aug 10 17:54:57 Latitude-D420 kernel: [ 303.561278] usb 5-1: Product: Ellipse PRO Aug 10 17:54:57 Latitude-D420 kernel: [ 303.561283] usb 5-1: Manufacturer: EATON Aug 10 17:54:57 Latitude-D420 kernel: [ 303.561288] usb 5-1: SerialNumber: G354E21053 Aug 10 17:55:01 Latitude-D420 kernel: [ 307.374164] hid-generic 0003:0463:FFFF.0002: hiddev0,hidraw0: USB HID v1.10 Device [EATON Ellipse PRO] on usb-0000:00:1d.3-1/input0 Aug 10 17:55:01 Latitude-D420 mtp-probe: checking bus 5, device 3: "/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1" Aug 10 17:55:01 Latitude-D420 mtp-probe: bus: 5, device: 3 was not an MTP device Aug 10 17:59:55 Latitude-D420 kernel: [ 601.816213] usb 5-1: USB disconnect, device number 3 Aug 10 17:59:56 Latitude-D420 kernel: [ 602.932185] usb 5-1: new low-speed USB device number 4 using uhci_hcd Aug 10 17:59:57 Latitude-D420 kernel: [ 604.002366] usb 5-1: New USB device found, idVendor=0463, idProduct=ffff Aug 10 17:59:57 Latitude-D420 kernel: [ 604.002377] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4 Aug 10 17:59:57 Latitude-D420 kernel: [ 604.002383] usb 5-1: Product: Ellipse PRO Aug 10 17:59:57 Latitude-D420 kernel: [ 604.002388] usb 5-1: Manufacturer: EATON Aug 10 17:59:57 Latitude-D420 kernel: [ 604.002393] usb 5-1: SerialNumber: G354E21053 If that's a hardware issue, it's very strange because the pattern repeats exactly every five minutes.
Since you can reproduce it without NUT and on a totally different system, I would posit that it's maybe a bug or specific behavior you've found in the UPS's USB, possibly as an interaction with the kernel's hid-generic driver. I have seen some devices that deliberately reset every few minutes unless they explicitly get opened and get some magic confirmation, and similarly spammed dmesg. Do any interesting HID nodes show up in sysfs, or that you can query with input-utils (as root, lsinputs to find the device, then input-events to watch what comes from it)?
(In reply to Robin Johnson from comment #7) Thanks a lot for your lights Robin. I was considering taking back the device to the shop... > Do any interesting HID nodes show up in sysfs, or that you can query with > input-utils (as root, lsinputs to find the device, then input-events to > watch what comes from it)? I didn't know that I could take a look there. All I knew of so far was lsusb, which indeed shows me the UPS device: Bus 002 Device 022: ID 0463:ffff MGE UPS Systems UPS Five minutes later: Bus 002 Device 023: ID 0463:ffff MGE UPS Systems UPS Nothing in lsinput results shows a trace from the UPS however. Can you give me a hint on how I shall fetch it from sysfs?
# find /sys |grep 0463 Should show you something in /sys/bus/hid/drivers/hid-generic/ Looking under there, you might find sensors, but I won't guarantee it. There aren't any under my APC. As an alternative, find somebody else with the same UPS and see if they have the issue too, on similar kernels? I wouldn't rule out the UPS being buggy yet, just that I don't think it's likely.
(In reply to Robin Johnson from comment #9) > # find /sys |grep 0463 Here you go: /sys/bus/hid/devices/0003:0463:FFFF.00D4 /sys/bus/hid/drivers/hid-generic/0003:0463:FFFF.00D4 /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4 /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/power /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/power/control /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/power/runtime_active_time /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/power/autosuspend_delay_ms /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/power/runtime_status /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/power/runtime_suspended_time /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/modalias /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/driver /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2 /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/dev /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/power /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/power/control /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/power/runtime_active_time /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/power/autosuspend_delay_ms /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/power/runtime_status /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/power/runtime_suspended_time /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/device /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/subsystem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/hidraw/hidraw2/uevent /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/subsystem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/uevent /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:0463:FFFF.00D4/report_descriptor /sys/kernel/debug/hid/0003:0463:FFFF.00D4 /sys/kernel/debug/hid/0003:0463:FFFF.00D4/events /sys/kernel/debug/hid/0003:0463:FFFF.00D4/rdesc I can see the ever increasing counter 00D4 here. Do you spot any sensor over there? > Should show you something in /sys/bus/hid/drivers/hid-generic/ > Looking under there, you might find sensors, but I won't guarantee it. > > There aren't any under my APC. > > As an alternative, find somebody else with the same UPS and see if they have > the issue too, on similar kernels? There ain't nobody nearby — living in a small town and I'm probably the only one using Linux here, apart from the people whose computer I configured :D . I'll try to find people on the internet. > I wouldn't rule out the UPS being buggy > yet, just that I don't think it's likely. I really don't wish so because the delay for returning the device to the shop after primary inspection has expired (7 days). Most of all the tests they will do will involve Windows, which have revealed a perfectly functional device on my own. So I'm pretty much stuck with this one and... well, hope... Since you talked about kernel version, I'm going to try the latest available kernel — good thing 3.16 was released not so long ago. Gonna check 3.14 branch and then 3.16 if tests are inconclusive.
Robin, I must thank you for giving me the right idea of upgrading the kernel! Know what? Upgrading to gentoo-sources-3.14.14 did it! I had e-synced my computer only a few weeks ago when 3.14 was not in the stable branch yet. Now I can fully profit from the UPS. Here are some readings: # upsc ellipse battery.charge: 100 battery.charge.low: 20 battery.runtime: 439 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 650 device.serial: G354E21053 device.type: ups driver.name: usbhid-ups driver.parameter.bus: 002 driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.product: Ellipse PRO driver.parameter.productid: FFFF driver.parameter.serial: G354E21053 driver.parameter.vendor: EATON driver.parameter.vendorid: 0463 driver.version: 2.6.5 driver.version.data: MGE HID 1.31 driver.version.internal: 0.37 input.frequency: 50.0 input.transfer.high: 285 input.transfer.low: 165 input.voltage: 233.0 input.voltage.extended: no outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 2 outlet.1.status: on outlet.1.switchable: no outlet.2.desc: PowerShare Outlet 2 outlet.2.id: 3 outlet.2.status: on outlet.2.switchable: no outlet.desc: Main Outlet outlet.id: 1 outlet.switchable: no output.frequency: 50.0 output.frequency.nominal: 50 output.voltage: 227.0 output.voltage.nominal: 230 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.firmware: 01.08.0016 ups.load: 43 ups.mfr: EATON ups.model: Ellipse PRO 650 ups.power: 196 ups.power.nominal: 650 ups.productid: ffff ups.realpower: 174 ups.serial: G354E21053 ups.status: OL CHRG ups.timer.shutdown: 0 ups.timer.start: 0 ups.vendorid: 0463 All I had to do was upgrade the kernel, that's it. Shall I close this bug with result INVALID? Thanks a lot for your help!
thanks, closing
I'd like to add that maybe it's a good idea to mention the recent libusb requires kernel >=3.14. Unless of course specified in the documentation but IMHO a hard dependency would probably help a little more running into this kind of issue.
