similar to: usb stopped working

I'm experiencing a rather serious issue with the usbhid-ups driver on two different Linux systems. The symptoms on both systems are the same: After anything from a few hours to a day or two, upsd is no longer able to communicate with the UPS. upsd initially starts complaining about "data from UPS <such-and-such> is stale - check driver", then upsmon reports a loss of

I'm going to bugz this if no one tells me I made another brain-damaged error here. Also, if I can get one confirmation, it'll let me breath easier. I ran a version searching for ".cmd" and ".c" just trying to convince myself I'm not *that* brain-damaged. You'd think after all these years that regex compilation would be pretty darn stable... Oh! Forgot it was

Hi there, I''m using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on X86-64 and I''m experiencing a problem with the network. I boot into the Xen kernel and everything works just fine. I can browse the net etc. However after a while the network stops responding completely. I am not sure what causes this to happen or what triggers it. After a few hours, the network just stops

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

Greetings; Nut pull & build from about two weeks ago, 2.4.3 I believe. Belkin UPS. I have everything working but a proper shutdown of upsd when I reboot, it hangs there and needs the hdwe reset button to reset it. That may be related to my finding more than 1 K##upsd and more than one K##upsmon, in /etc/rc5.d and which I have now nuked. However, while its working well enough to monitor,

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hello Ben, commit (mini) [~/work/linux-2.6] git bisect bad 8777c5c11764d8336d8270f96778158c34c92108 is the first bad commit commit 8777c5c11764d8336d8270f96778158c34c92108 Author: Ben Skeggs <bskeggs at redhat.com> Date: Fri Jun 6 18:09:55 2014 +1000 drm/nouveau/dp: probe dpcd to determine connectedness Signed-off-by: Ben Skeggs <bskeggs at redhat.com> introduces a

Hi Konrad, Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361). It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0." With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between. dmesg and xm dmesg attached -- Sander Dom0 shows: total

dmesg output: --------------------------------------------------------------------------------------------------------- [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.0-38-generic (buildd at allspice) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #52~14.04.1-Ubuntu

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

Hi, I have just started to setup and configure my asterisk box and am having trouble with it. I have a dlink nic in the box as well as the digium card. When the nic is in there by itself it works, but when I put the tdm400p in, there seems to be some sort of conflict with the network card. The tdm appears as another type of network card, which I don't think it should, should it? It shows

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

On 10 August 2014 09:05, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 7:57 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > > Error -32 is EPIPE, which means that the PC didn't see a reply from the device during the descriptor read. I don't know that we have ever successfully run one of these issues to ground. > Considering Eaton do

Dears, I'm trying to connect this new version of the AVR700U to nut - 2.7.4-27 running over OpenWrt 22.03.5, installed from the stable release repositories, for an ath79 USB2.0 gigabit WiFi router. According to the supported list, I thought this UPS was supposed to use the USB 2010 protocol, but I guess that was an old version because now uses the 3024 protocol (perhaps it would be good to

> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one > computer using megatec_usb driver. But megatec_usb completly ignores port > directive in ups.conf, I even try port = /dev/null and megatec_usb founds > ups and it works. The 'port' is not used for USB connected devices, it's only needed for compatibility reasons. > Problem is that

I think 3024 was added after NUT 2.7.4 release. On Thu, May 4, 2023, 18:20 Feliciano Chavez via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Dears, > > I'm trying to connect this new version of the AVR700U to nut - 2.7.4-27 > running over OpenWrt 22.03.5, installed from the stable release > repositories, for an ath79 USB2.0 gigabit WiFi router. >

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting: