Nut upsuser - Feb 2010 - Fw: trouble setting up kebo-1000d ups (usb)

----- Forwarded Message ----
From: Terry Powling <terrypowling at yahoo.co.uk>
To: nut-upsuser at lists.alioth.debian.org
Sent: Sat, 27 February, 2010 22:30:05
Subject: trouble setting up kebo-1000d ups (usb)


Trying to setup Kebo ups-1000D with usb port.

lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0925:1234 Lakeview Research
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
Bus 004 Device 003: ID 10df:0500 In-Win Development, Inc. iAPP CR-e500 Card
reader
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ups.conf
[Kebo]

   driver = megatec_usb
   port = auto
   mfr = Kebo UPS-1000D
   vendorid = 0925
   productid = 1234
#   subdriver = krauler
#   subdriver = agiler
   bus = "00[1-5]"



 service upsd start
NUT Starting UPS model drivers: Network UPS Tools - UPS driver controller 2.4.1
Network UPS Tools - Megatec protocol driver 1.6 (2.4.1)
Serial-over-USB transport layer 0.10
libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/002/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/003/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/002: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/003: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/005/001: Permission denied.
libusb requires write access to USB device nodes.
No supported devices found. Please check your device availability with
'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'vendorid' and 'subdriver'
options
specified. Please refer to the man page for details about these options
(man 8 megatec_usb).
Please report your results to the NUT user's mailing list
<nut-upsuser at lists.alioth.debian.org>.

Driver failed to start (exit status=1)
                                                                            
[FAILED]
NUT Starting UPS daemon: Network UPS Tools upsd 2.4.1
not listening on 127.0.0.1 port 3493
                                                                            
[FAILED]
ups.conf
[Kebo]
#       driver = newhidups
#   driver = megatec_usb
        driver = richcomm_usb
   port = auto
#   mfr = Kebo UPS-1000D
#   vendorid = 0925
#   productid = 1234
#   subdriver = krauler
#   subdriver = agiler
#   bus = "00[1-5]"

 service upsd start
NUT Starting UPS model drivers: Network UPS Tools - UPS driver controller 2.4.1
Network UPS Tools - Richcomm dry-contact to USB driver 0.04 (2.4.1)
Warning: This is an experimental driver.
Some features may not function correctly.

libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied.
libusb requires write access to USB device nodes.

Communications with UPS lost: Query to UPS failed
                                                                             [ 
OK  ]
NUT Starting UPS daemon: Network UPS Tools upsd 2.4.1
not listening on 127.0.0.1 port 3493
                                                                            
[FAILED]
Here is o/p from using megatec_usb driver and richcomm_usb driver.
System is Mandriva linux 2010.0
Linux 2.6.31.12-desktop586-1mnb Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz

How do I resolve the libusb issue with write access, as chmod is reset on reboot
and after failure of driver.
Tried changing 'MODE' in rules from 664 to 666, but no joy. Cant
continue conf without getting ups to bind with driver.

Thanks. 
Terry.


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20100228/e9c842e4/attachment.htm>

Citeren Terry Powling <terrypowling op yahoo.co.uk>:
> How do I resolve the libusb issue with write access, as chmod is  
> reset on reboot and after failure of driver.
This is a permissions problem, the first thing to try is if running  
the driver in debug mode as root helps:

     /path/to/richcomm_usb -DDD -u root -a Kebo

According to the USB VendorID and ProductID, this should be the  
correct driver. If this works, the driver will start and produce an  
endless amount of debugging information until you stop it with Ctrl-C.

Best regards, Arjen
-- 
Please keep list traffic on the list