Displaying 4 results from an estimated 4 matches for "dp55kg".
2010 Nov 01
2
Best supported motherboard
Which among these three motherboard is the best supported in Linux
(Centos/Ubuntu) ?
Intel? Desktop Board DH55HC [ http://ark.intel.com/Product.aspx?id=42409 ]
Intel? Desktop Board DP55WG [ http://ark.intel.com/Product.aspx?id=40078 ]
Intel? Desktop Board DP55KG [
http://www.intel.com/products/desktop/motherboards/DP55KG/DP55KG-overview.htm]
Also which will be a good processor , for using in a desktop PC to run 4 or
5 Virtual machines concurrently on VirtualBox or VMWare ESX server ?
Intel? Xeon? Processor X3460 [ http://ark.intel.com/Product.aspx?i...
2009 Oct 13
6
USB/UPS connectivity issue on Intel DP55KG Motherboard
Hello,
I use the following in my ups.conf:
# USB:
[apc]
driver = usbhid-ups
port = auto
desc = "APC 1500VA"
pollfreq = 5
On my new motherboard (an Intel DP55KG), every once and awhile I get this:
Broadcast Message from nut at box.com
(somewhere) at 17:48 ...
Communications with UPS apc at localhost lost
Broadcast Message from nut at box.com
(somewhere) at 17:48 ...
Communications with UPS apc at localhost established
On my previous...
2009 Oct 29
1
2.6.31.4: Any other suggestions regarding a UPS/USB (APC1500VA) on (Intel P55KG) stale issue?
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...
2011 Apr 21
0
2.6.38.3 w/nut: libusb_get_string: error sending control message: Broken pipe
...r 21 09:44:20 p34 usbhid-ups[3737]: libusb_get_string: error sending control
message: Broken pipe
Error from 2009 (still a problem)
http://lists.alioth.debian.org/pipermail/nut-upsuser/2009-October/005530.html
This occurred on my last Intel motherboard (Intel 965WH) and current
motherboard, Intel DP55KG.
Is there something that can be 'fixed' or an workaround implemented, or
should I just send these messages to /dev/null?
As the nut software does work OK, I keep getting these errors in the logs.
Thanks,
Justin.