On Fri, Jan 2, 2009 at 5:31 PM, Hai Zaar <[email protected]> wrote: > On Sun, Dec 28, 2008 at 6:05 PM, Charles Lepple <[email protected]> wrote: >> On Fri, Dec 26, 2008 at 2:41 PM, Hai Zaar <[email protected]> wrote: >>> Good day! >>> I'm struggling to connect by Advice Partner PRPC650 UPS to Nut. The >>> UPS uses USB for communication and the current problem is that serial >>> device (/dev/ttyUSB*) is not detected. OS is Debian Lenny (same >>> behavior on Ubuntu Hardy). >>> Did anyone have any success with this UPS? Here is what my dmesg and >>> udevmonitor say (on Debian): >> >> You might be able to find more information by searching the NUT or >> linux-usb mailing lists, but the last Advice Partner entry on the >> driver compatibility list in SVN mentions the powercom driver, which >> is not USB. > From my understanding it should register /dev/ttyUSB0 then it in turn > will be used by Nut's powercom driver. > I've failed to google anything about this UPS working with Linux. > >> >> What does 'lsusb -d 0d9f:0002' say for this device? > Bus 001 Device 002: ID 0d9f:0002 Powercom Co., Ltd
Sorry, I meant to include a '-v' on that command line. > The current progress is like this: > With help from linux-hotplug guys > (http://thread.gmane.org/gmane.linux.hotplug.devel/13551) I've managed There are at least two lists in drivers/hid/hid-core.c, an "ignore list" and a "blacklist". Not sure which one your device needs to be added to. > to /dev/ttyUSB0 to be registered, but: > # /sbin/upsdrvctl start > Network UPS Tools - UPS driver controller 2.2.2 > Network UPS Tools - PowerCom and similars protocol UPS driver $ > Revision: 0.5 $ (2.2.2) > > writing error > # cat /etc/nut/ups.conf > [PRPC650] > driver = powercom > port = /dev/ttyUSB0 > desc = "Test" > > Trying with strace shows the following: > 12369 open("/dev/ttyUSB0", O_RDWR|O_EXCL|O_NOCTTY|O_NONBLOCK) = 4 > 12369 flock(4, LOCK_EX|LOCK_NB) = 0 > 12369 ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, {B1200 -opost -isig > -icanon -echo ...}) = 0 > 12369 ioctl(4, TCFLSH, 0) = 0 > 12369 ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, {B1200 -opost -isig > -icanon -echo ...}) = 0 > 12369 ioctl(4, SNDCTL_TMR_START or TCSETS, {B1200 -opost -isig -icanon > -echo ...}) = 0 > 12369 ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, {B1200 -opost -isig > -icanon -echo ...}) = 0 > 12369 ioctl(4, TIOCMBIC, [TIOCM_DTR]) = 0 > 12369 ioctl(4, TIOCMBIS, [TIOCM_RTS]) = 0 > 12369 write(4, "\1"..., 1) = -1 EAGAIN (Resource > temporarily unavailable) > 12369 write(2, "writing error\n"..., 14) = 14 Not sure - you will probably have to wait to hear from the powercom driver author, or someone else experienced in hacking that driver. -- - Charles Lepple _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
