Hello,
Problem: When I migrated from a DG965WH -> DP55KG motherboard, there were
quite a bit of issues, host still does not reboot without special flags,
e.g. reboot=a, the NIC driver is broken with the in-kernel version (the
one on e1000.sourceforge) fixes that and finally my UPS USB has driver
stale problems, with two issues already relating to the HW/drivers
themselves it would not be unrealistic to speculate that there could be an
issue with the USB chipset/driver with this P55 motherboard.
Is anyone else out there running an APC1500VA UPS on a P55 motherboard?
If so, what have been your results?
Motherboard: Intel P55KG
Kernel: 2.6.31.4 x86_64
Details from nut/kernel usb trace:
http://home.comcast.net/~jpiszcz/20091014/nut-problem.txt
The last thread petered out:
http://www.gossamer-threads.com/lists/linux/kernel/1143579
# From ups -D
Got 2 HID objects...
Quick update...
upsdrv_updateinfo...
Got 2 HID objects...
Quick update...
Can't retrieve Report 22: Broken pipe
upsdrv_updateinfo...
Got to reconnect!
upsdrv_updateinfo...
Got to reconnect!
Can't retrieve Report 19: Broken pipe
upsdrv_updateinfo...
Got to reconnect!
Can't retrieve Report 15: Broken pipe
upsdrv_updateinfo...
Got to reconnect!
upsdrv_updateinfo...
# From the system logs:
Broadcast Message from [email protected]
(somewhere) at 6:01 ...
Communications with UPS a...@localhost lost
Broadcast Message from [email protected]
(somewhere) at 6:02 ...
Communications with UPS a...@localhost established
Broadcast Message from [email protected]
(somewhere) at 6:03 ...
# From ups.conf:
[apc]
driver = usbhid-ups
port = auto
desc = "APC 1500VA"
All other USB devices work properly, USB CD/DVD writer, keyboard, mouse,
etc. The same UPS (APC 1500VA) worked fine on the last board, same cable,
etc. I have tried power cycling the UPS and using a different port on the
motherboard, to no avail.
Aside from purchasing a different UPS (if I wanted to use nut)- is it
possible there is a bug in the chipset on these P55 boards in the way the
driver communicates with it?
Since this problem is 100% reproducible every time, is there anyway to
look into this issue any further?
Justin.
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
