search for: wrenn

...: USBDEVFS_CONTROL failed cmd bcmxcp_usb rqt 66 rq 13 len 4 ret -110 I believe that these indicate that the USB driver is timing out USB messages to the UPS. The identical setup running on a Westmere + Tylersburg + ICH10R works fine but on that platform the USB connection is USB 1.1. Thanks, Rich Wrenn -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120624/85192d6a/attachment.html>

...es and if so, how can I help get them into the stock driver? Attached is my patch file. Note that the comments are a little verbose but that is only to make sure we comply with the GPL so I expect that those would be removed if the patch is incorporated into the stock bcmxcp.c. Thanks, Rich Wrenn System Architect, DataDirect Networks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110910/feb93dfe/attachment.html> -------------- next part -------------- A non-text attachment was scrubb...

Greetings, The way that bcmxcp_usb reacts to and recovers from a USB cable unplug-plug appears to have changed significantly between 2.4.1 and 2.6.0. While I can see some improvements, bcmxcp_usb 2.6.0 does not appear to handle a USB cable unplug-plug correctly. Does anyone know if this has been fixed in subsequent releases? Here are the details. When the USB cable between my server and my

Hello all. I am trying to get my second x100p card set up and am having some troubles. My zaptel.conf reads: fxsks=1-2 fxoks=3-4 defaultzone=us loadzone=us before adding this card my zaptel.conf read: fxsks=1 fxoks=2-3 defaultzone=us loadzone=us But now that I've made the change I am getting the following error when running modprobe wcfxo and of course the same

Nut-names.txt states that 1. ups.start.auto controls whether the UPS starts when mains is (re)applied. 2. shutdown.stayoff causes "turn off the load possibly after a delay and remain even if power returns". 3. shutdown.return causes "turn off the load possibly after a delay and return when power is back". 1 seems to conflict with 2 and 3. That is, 2

Has anyone out there successfully set up their * box to terminate their VONAGE calls? I (and I am sure lots of others) would love to hear how you did it. I'd like to be able to get rid of the extra hardware I have hanging around here and use the ASTERISK machine to handle the SIP termination instead of needing to have a Linksys modem (w/phone) and an additional X100P card. Thanks.

I have two x100p cards and a TDM20b set up such that the home phone is one exten, the home office is another, on one of the incoming lines (the same copper line that has the main home phone number) There is a distinctive ringing number set up as well. Here's the crazy part. any calls coming in on that line I want to ring both extensions. But I want the distinctive ringing to pass through only

During the last month, I've been integrating a Powerware 5115 into an embedded system by writing a custom NUT daemon. This work has gone quite well and NUT has been very helpful, but it sure would be nice to have some additional instcmds for the 5115. The bcmxcp driver comments mention "manuals for the BCM/XCP". I'm wondering if I could get a copy of those so that I might

Specs: Fedora Core 3. Dual P3 600 (Dell PEdge 1300) SCSI Disks 1x X100P (channel 1) 1x TDM20 (channels 2+3) 1x Knockoff X100P (channel 4) I am looking to have all local and all toll free calls go outbound through the Copper line, and all long-distance and international to go out through the Vonage line. This way I can eliminate LD on my home line, and pay minimal LD charges through

Hi, I'm trying to get a Powerware 5115 to communicate with the NUT via USB under Debian Linux and need help. Here is the output that I see. co-nh5:/tmp/mnt/projects/pwusb/nut-2.4.1# /usr/local/ups/bin/upsdrvctl -u root start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Communications with UPS lost: