Gidday all - I've got a 1700VA dynamix UPS which is USB.
The previous model (with a serial port) worked wonderfully with megatec,
but this new one with USB is not working.
It feels like the kernel is not handing the USB device properly.
The web has not yeilded any useful info.
What can I do from here?
==========================================[root at hera ups]# lsusb
Bus 006 Device 002: ID 0001:0000 Fry's Electronics
[root at hera ups]# megatec_usb -DD -a ups
Network UPS Tools - Megatec protocol driver 1.6 (2.4.1)
Serial-over-USB transport layer 0.10
debug level is '2'
Checking device (0001/0000) (006/002)
- VendorID: 0001
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 006
Trying to match device
Device matches
failed to claim USB device: could not claim interface 0: Operation not
permitted
failed to detach kernel driver from USB device: could not detach kernel
driver from interface 0: Operation not permitted
failed to claim USB device: could not claim interface 0: Operation not
permitted
failed to detach kernel driver from USB device: could not detach kernel
driver from interface 0: Operation not permitted
failed to claim USB device: could not claim interface 0: Operation not
permitted
failed to detach kernel driver from USB device: could not detach kernel
driver from interface 0: Operation not permitted
failed to claim USB device: could not claim interface 0: Operation not
permitted
failed to detach kernel driver from USB device: could not detach kernel
driver from interface 0: Operation not permitted
Can't claim USB device [0001:0000]: could not detach kernel driver from
interface 0: Operation not permitted
----------- ups.conf
[ups]
driver = megatec_usb
# vendor="Fry's Electronics"
# vendorid = 1
# productid = 0
desc = "UPS"
port = auto
------------- dmesg snippets
grep -i usb /var/log/messages
Sep 15 15:00:35 hera kernel: usbcore: registered new driver usbfs
Sep 15 15:00:35 hera kernel: usbcore: registered new driver hub
Sep 15 15:00:35 hera kernel: usbcore: registered new driver hiddev
Sep 15 15:00:35 hera kernel: usbcore: registered new driver usbhid
Sep 15 15:00:35 hera kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
core driver
Sep 15 15:00:35 hera kernel: ehci_hcd 0000:00:1a.7: new USB bus
registered, assigned bus number 1
Sep 15 15:00:35 hera kernel: ehci_hcd 0000:00:1a.7: USB 2.0 started,
EHCI 1.00, driver 10 Dec 2004
Sep 15 15:00:35 hera kernel: usb usb1: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 1-0:1.0: USB hub found
Sep 15 15:00:35 hera kernel: ehci_hcd 0000:00:1d.7: new USB bus
registered, assigned bus number 2
Sep 15 15:00:35 hera kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started,
EHCI 1.00, driver 10 Dec 2004
Sep 15 15:00:35 hera kernel: usb usb2: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 2-0:1.0: USB hub found
Sep 15 15:00:35 hera kernel: USB Universal Host Controller Interface
driver v3.0
Sep 15 15:00:35 hera kernel: uhci_hcd 0000:00:1a.0: new USB bus
registered, assigned bus number 3
Sep 15 15:00:35 hera kernel: usb usb3: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 3-0:1.0: USB hub found
Sep 15 15:00:35 hera kernel: uhci_hcd 0000:00:1a.1: new USB bus
registered, assigned bus number 4
Sep 15 15:00:35 hera kernel: usb usb4: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 4-0:1.0: USB hub found
Sep 15 15:00:35 hera kernel: uhci_hcd 0000:00:1a.2: new USB bus
registered, assigned bus number 5
Sep 15 15:00:35 hera kernel: usb usb5: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 5-0:1.0: USB hub found
Sep 15 15:00:35 hera kernel: uhci_hcd 0000:00:1d.0: new USB bus
registered, assigned bus number 6
Sep 15 15:00:35 hera kernel: usb usb6: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 6-0:1.0: USB hub found
Sep 15 15:00:35 hera kernel: uhci_hcd 0000:00:1d.1: new USB bus
registered, assigned bus number 7
Sep 15 15:00:35 hera kernel: usb usb7: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 7-0:1.0: USB hub found
Sep 15 15:00:35 hera kernel: uhci_hcd 0000:00:1d.2: new USB bus
registered, assigned bus number 8
Sep 15 15:00:35 hera kernel: usb usb8: configuration #1 chosen from 1 choice
Sep 15 15:00:35 hera kernel: hub 8-0:1.0: USB hub found
Sep 15 15:00:36 hera kernel: Initializing USB Mass Storage driver...
Sep 15 15:00:36 hera kernel: usbcore: registered new driver usb-storage
Sep 15 15:00:36 hera kernel: USB Mass Storage support registered.
Sep 15 15:01:48 hera kernel: usb 2-1: new high speed USB device using
ehci_hcd and address 2
Sep 15 15:01:48 hera kernel: usb 2-1: configuration #1 chosen from 1 choice
Sep 15 15:01:48 hera kernel: hub 2-1:1.0: USB hub found
Sep 15 15:01:48 hera kernel: usb 2-1.2: new low speed USB device using
ehci_hcd and address 3
Sep 15 15:01:48 hera kernel: usb 2-1.2: configuration #1 chosen from 1
choice
Sep 15 15:11:06 hera kernel: usb 6-1: new low speed USB device using
uhci_hcd and address 2
Sep 15 15:11:07 hera kernel: usb 6-1: string descriptor 0 read error: -32
Sep 15 15:11:07 hera kernel: usb 6-1: string descriptor 0 read error: -32
Sep 15 15:11:07 hera kernel: usb 6-1: configuration #1 chosen from 1 choice
Sep 15 15:11:07 hera kernel: hiddev96: USB HID v1.00 Device [HID
0001:0000] on usb-0000:00:1d.0-1
The server is an IBM x3200 tower server running centos 5.3
Linux hera 2.6.18-92.1.22.el5.centos.plus #1 SMP Wed Dec 17 10:50:49 EST
2008 i686 i686 i386 GNU/Linux
--
Craig Falconer
The Total Team - Managed Systems
Office: 0800 888 326 / +643 974 9128
Email: workorder at totalteam.co.nz
Web: http://www.totalteam.co.nz/
2009/10/20 Craig Falconer <suppliers at totalteam.co.nz>:> Gidday all - I've got a 1700VA dynamix UPS which is USB.Hi Craig,> The previous model (with a serial port) worked wonderfully with megatec, > but this new one with USB is not working. > > It feels like the kernel is not handing the USB device properly. > The web has not yeilded any useful info. > > What can I do from here? > > ==========================================> [root at hera ups]# lsusb > Bus 006 Device 002: ID 0001:0000 Fry's Electronicsouch, not that clean: these kind of VendorID (and productID) is completly not complying to USB standards! anyway, this (0001:0000) is already supported by megatec_usb (krauler subdriver)...> [root at hera ups]# megatec_usb -DD -a ups > Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) > Serial-over-USB transport layer 0.10 > debug level is '2' > Checking device (0001/0000) (006/002) > - VendorID: 0001 > - ProductID: 0000 > - Manufacturer: unknown > - Product: unknown > - Serial Number: unknown > - Bus: 006 > Trying to match device > Device matches > failed to claim USB device: could not claim interface 0: Operation not > permitted > ...this is a typical permission issue (as Charles already told). but you should already have the udev suppport. as per your lsusb output, you should have an entry with privileges of 664 / root:nut ie: "ls -l /dev/bus/usb/006/002" should give something like crw-rw-r-- 1 root nut 189, 769 2009-10-21 11:04 /dev/bus/usb/006/002 otherwise, try to unplug / replug your USB cable to force udev rules application.> Sep 15 15:11:06 hera kernel: usb 6-1: new low speed USB device using > uhci_hcd and address 2 > Sep 15 15:11:07 hera kernel: usb 6-1: string descriptor 0 read error: -32 > Sep 15 15:11:07 hera kernel: usb 6-1: string descriptor 0 read error: -32 > Sep 15 15:11:07 hera kernel: usb 6-1: configuration #1 chosen from 1 choice > Sep 15 15:11:07 hera kernel: hiddev96: USB HID v1.00 Device [HID > 0001:0000] on usb-0000:00:1d.0-1 > > > The server is an IBM x3200 tower server running centos 5.3 > Linux hera 2.6.18-92.1.22.el5.centos.plus #1 SMP Wed Dec 17 10:50:49 EST > 2008 i686 i686 i386 GNU/Linuxah, 2.6.18 on Centos. iirc, there were some USB issue with 2.6.18, and some have recently surfaced on the nut user list... something is puzzling me though: this device seems to be a HID one. So usbhid-ups would be the way to go, *if* it's a real HID compliant device (unlike some Tripplite units supported by tripplite_usb iirc). so, depending on your results with megatec_usb, an usbhid-ups debug output would be needed... cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/