Re: [Nut-upsuser] 2.6.31.4: USB/UPS connectivity issue on Intel DP55KG Motherboard [DEBUG logs included upsd/upsmon/usbhid-ups]

2009-11-01 Thread Arjen de Korte
Citeren Justin Piszcz : Is it possible that a different USB Chip may act differently causing this problem? As I noted CD/DVD (USB) and all other USB devices function properly. This may be due to the fact that we reconnect, instead of retry on many signs of problems in the usbhid-ups driv

Re: [Nut-upsuser] 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']

2009-11-01 Thread Matthew Dharm
On Sun, Nov 01, 2009 at 04:18:40PM -0500, Justin Piszcz wrote: > > I do not use any hubs in this environment, everything is directly > attached to the motheboard. Per Matthew (noted below) when I > mention hub I am talking about your typical USB hub one would > attach to a USB port on the board,

Re: [Nut-upsuser] 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']

2009-11-01 Thread Matthew Dharm
On Sun, Nov 01, 2009 at 12:11:44PM -0500, Alan Stern wrote: > On Sat, 31 Oct 2009, Justin Piszcz wrote: > > > 1. 5 minutes of usbmon output on via chipset [working] > > 2. 5 minutes of usbmon output on intel p55 usb chipset [ehci/not working] > > To summarize the differences between the logs, the

Re: [Nut-upsuser] 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']

2009-11-01 Thread Arjan van de Ven
On Sat, 31 Oct 2009 19:43:38 -0400 (EDT) Justin Piszcz wrote: > >> Problem appears to be the Intel P55KG / USB Chipset in the way > >> that it handles usbhid-raw devices as CD/USB sticks/kbd/mouse/etc > >> do not appear to be affected. > >> > >> So far all other USB devices work fine, with the exc

Re: [Nut-upsuser] Powercom support and sponsorship

2009-11-01 Thread Morozov Alexey
Dear Alexander, Thank you for your quick reply. We've updated communication protocol for Powercom UPS to be compatible with HID for power device and would like to add it in NUT. Russian Powercom team can provide communication protocol and demo units for testing. Can i send communication protoc

Re: [Nut-upsuser] 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']

2009-11-01 Thread Justin Piszcz
re the same. Specifically, ports 1 and 9 have special properties (related to USB-based debugging). You should try other ports (note that I count ports starting at 0). I have tested every port on the motherboard (the 8 on the back and 4 off of the USB headers on the motherboard): http://home.comc

Re: [Nut-upsuser] 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']

2009-11-01 Thread Justin Piszcz
have special properties (related to USB-based debugging). You should try other ports (note that I count ports starting at 0). I have tested every port on the motherboard (the 8 on the back and 4 off of the USB headers on the motherboard): http://home.comcast.net/~jpiszcz/20091101/ports.txt The prob

Re: [Nut-upsuser] 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']

2009-11-01 Thread Alan Stern
On Sat, 31 Oct 2009, Justin Piszcz wrote: > >> SUMMARY: P55 Chipset/USB has issues with UPS' (broken pipe on 3 diff UPS') > >> WORKAROUND: Buy/use PCI USB card if you want to use nut/connect a UPS. > >> NOTES: All other USB (non-UPS) devices seem to function without any > >> problems. > >>

Re: [Nut-upsuser] nut files empty

2009-11-01 Thread Arnaud Quette
2009/10/31 mystified : > I just installed nut in Debian and all of my files are missing.   I'm not > even sure what all files are required.  I hope someone can give me the list > of the files and I can create them.  Also if there is any pertinent info I > need. the files are located in /etc/nut/ b

Re: [Nut-upsuser] 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']

2009-11-01 Thread Justin Piszcz
no more errors: just as a wild guess; does it go away if you disable CONFIG_USB_SUSPEND ? also, google suggests that your bios may not have c-states enabled; if so, enabling those in the bios might also be a good idea Hi Arjan, Thanks for the reply, http://home.comcast.net/~jpiszcz/20091101/co