similar to: NUT 2.x causes uhci-usb error messages in syslog.

Hi Arnaud, hi all I wish you all the best for 2006. Enjoying of some less stressed time, I follow your advice, Arnaud, to switch our UPS management on the newhidups driver. ( Enfin ! ;) Our goal is to support (soon) the new MGE ASR ELLIPSE ( and of course also the old ELLIPSE and EXTREME models ). I rebuild the libusb-0.1.10a packages to conform to our installation process. I perform the same

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

Hi all, I've tried installing NUT from both the Debian packages and the 2.0.4-pre1 source but I'm unable to sort out the USB permissions when using the newhidups driver and an APC XS series UPS. In each case, I'm able to run newhidups as user root but running it as user nut fails: --- as 'nut' # /lib/nut/newhidups -u nut -a apc1 Network UPS Tools: New USB/HID UPS driver 0.28

Hi, I have installed in suse 9.3 and ellipse premium 500 usb a psp 3.0 with yast2 and versions: nut-2.0.2-4 mgeups-psp-3.0.0-3 the first time that I launch psp it seems to contact the UPS and you can make changes to the parameters and all seems ok. If you make a reboot the psp hangs up and if you try /etc/init.d/ups it fails: Starting service NUT: -> Starting UPS driver: Network UPS Tools -

Hello everybody, After succeeded in "tuning" nut-2.0.0's hidups and 2.0.3's newhidups on customized Linux kernels, we are now facing a new challenge : trying to install nut-2.0.5 on a RedHat ES4 which is based on a 2.6.9 kernel. I picked up the 2.0.5 source package and follow the INSTALL doc until step 6. So far so good. RH ES4 is managed by udev, therefore I presume we

Hi, I recently got a new UPS, the model is TriPro Power Plus UPS 1000VA and it comes with a USB cable, anyone knows what model/driver i need to use ? When i connect the UPS to my linux system (CentOS 3.3, Kernel 2.4.21) the following information is written to the logs: kernel: hub.c: new USB device 00:11.2-2, assigned address 2 kernel: usb-uhci.c: interrupt, status 3, frame# 235 kernel:

Hi I try since a week to run my MGE Protection Center under Suse Linux 9.3. At the MGE site i found an HowTo. I have installed NUT an create the=20 configs but at boot the newhidups driver say=B4s "no USB/HID UPS found".=20= Anyone an Idea? Johannes Schatz=

I can start the driver successfully manually, after the machine is up and running, but at boot time, it can't find my UPS. My init script makes sure that the usbfs is up (by checking for the existence of /proc/bus/usb/devices), and I can't think of what else could be different with the boot-time failure versus the manual startup after logging in. I'll include my configuration at the

I have gone ahead and merged the regex_branch with the main Development branch. Reason: recent renaming of files and moving around of code leads to conflicts between the branches that will be increasingly difficult to resolve. It is easier to merge now while the two branches are still relatively similar and most edits non-overlapping. The merge is between tags before_PSE_6 and after_PSE_6 on

Ok, I installed the ups, and installed nut, and /proc/bus/usb/devices says this T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06da ProdID=0002 Rev= 0.01 S: Manufacturer=POWERWARE S: Product=Powerware UPS C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 20mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00

Hi! I've installed NUT 2.0.2 to work with my MGE Protection Center and it works but for one thing. When I reboot the computer, at startup upsdrvctl/newhidups can't find the UPS so I have to manually unplug, replug and start upsdrvctl/upsd every time. I've installed from sourcecode onto a Gentoo machine. Where should I look for the problem (USB/hotplug/newhidups/somewhere else)?

I observed that following could cause machine lockup since at least 8-CURRENT. Now I'm on 9-STABLE No usb in kernel, attached mouse pointer. # kldload usb ums ehci # kldload uhci or # kldload uhci usb ums ehci uhci is required for working mouse. Can anyone confirm? Please test few different iterations, as it's probably not easily reproducible. Most times nothing happens, if

managedsave/start appears to work, but VM is unusable due to non-stop repeating uhci_hcd errors. I can't remove the USB controller from QEMU, but I CAN remove it through virsh edit. Doing so eliminates the USB controller in the guest, preventing non-stop repeating uhci_hcd errors. (QEMU only lets you remove the USB redirection entries, which didn't help.) Using libvirt 1.2.18 (-1 Arch)

I have a Belkin F6H500ukUNV ups that I am attempting to get working under nut, however it does not appear to be detected by nut, I'm assuming that I need to feed some information back to you guys to get it included in the database somwhere. I've included (what I can think might be) the relivant outputs. Please let me know if you require anything else. dmesg output /sbin/newhidsups

I have CentOS 5 installed on a Compaq Evo. I don't know the exact Evo model. When I first installed it, booted up fine. Now, when it boots, it freezes when it loads the UHCI kernel module. Here's what I see: input: AT Translated set 2 keyboard as /class/input/input0 Creating block device nodes. Loading uhci-hcd.ko module. USB Universal Host Controller Interface driver 3.0 And that's

I ran in to an almost impossible ability to run MeetMe on our poweredge. Our PE is a 4 proc with OHCI and we had no need to buy any PCI cards other than for running MeetMe. If you know how to recompile your kernel, recompile it and make RTC a module (its compiled in by default). Then you can use zaprtc as your timing source. Be sure to `rmmod rtc` before you `insmod zaprtc` because zaprtc is a

Hello everyone! If this message was posted twice, my apologies. I'm having issues with my webmail today... I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to