[Nut-upsuser] Liebert GXT3 ID 10af:0000 Not working
clepple at gmail.com
Tue Aug 20 11:22:44 UTC 2013
[please keep the list CC'd.]
On Aug 20, 2013, at 12:50 AM, Korviakov Andrey wrote:
> Yes, it's my mistake: UPS used USB cable for communication, but i think that it's simple usb-com cable because nut work with liebert driver on ttyS0 port.
If that is the case, I doubt that usbhid-ups will be able to retrieve any additional information.
> In ups.conf i tried:
> driver = usbhid-ups
> port = auto
> vendorid = 10af
> but got error:
> Can't claim USB device [10af:0000]: could not detach kernel driver from interface 0: Operation not permitted
> Driver failed to start (exit status=1)
Usually the simpler reason is that the driver does not have permission to detach the kernel driver. If an UPS is not listed as supported by NUT, then the udev rules have not been applied to that device.
> This problem described at this page: http://belgorod.lug.ru/wiki/index.php/%D0%9D%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0_UPS
> "if you got this error check kernel config…
> # CONFIG_USB_DEVICE_CLASS is not set
> They suggested disable CONFIG_USB_DEVICE_CLASS option and rebuild kernel.
> Now i rebuilding kernel, and try again.
> 20.08.2013, в 6:21, Charles Lepple <clepple at gmail.com> написал(а):
>> On Aug 19, 2013, at 9:10 PM, Charles Lepple wrote:
>>> On Aug 19, 2013, at 12:58 PM, Korviakov Andrey wrote:
>>>> I have Liebert GXT3 UPS connected to CentOS Linux with kernel 2.6.32-131.0.15.el6.x86_64 and nut version 2.6.5-2.
>>>> lsusb: Bus 002 Device 003: ID 10af:0000 Liebert Corp. UPS
>>>> And this UPS detected only with this section in ups.conf:
>>>> driver = liebert
>>>> port = /dev/ttyS0
>>> I am confused. Are you using a serial cable with the liebert driver, or a USB cable with the usbhid-ups driver?
>> Actually, for the serial 'liebert' driver, it will only detect OL/OB/LB.
>> We haven't had much luck with the USB firmware on other Liebert units, but if it's anything like some of the other UPSes out there, you may need to power the UPS completely off (unplug from the wall, no LEDs on, etc.) before switching between USB and serial.
>> Also, running the usbhid-ups driver with debugging enabled may shed some light on the problem.
clepple at gmail
More information about the Nut-upsuser