Quantcast
Channel: All Business PCs, Workstations and Point of Sale Systems posts
Viewing all articles
Browse latest Browse all 36019

Re: Part # for Xeon v2 enabled motherboards

$
0
0

SDH -

 

Thank you for the information. I had done a search on HP Parts Surfer and saw the 619562-001 part # for the motherboard, which is the one I found available (new) from a dealer - just wasn't sure if it had the 2013 Boot Block. (I  e-mailed the vendor to ask if that motherboard supprted the v2 processors but have not heard back as yet - not sure if they would even be able to provide that info.) So I assume any of the motherboards with that part # have the newer 2013 Boot Block date.

 

Most of the motherboards I saw on e-Bay and from other vendors (ITCreations) were for refurbished motherboards, which I don't really want to consider.

 

I'm also not sure if the new processor would need the 1125 Watt power supply (I did find a decent price for the liquid cooling module - most vendors - if they even have it - are selling for the list price of $299.00 but I found one that has them in stock, new - supposedly - for @ $150.00).

 

The Xeon I bought is a new in the sealed retail box product I bought from SuperBiz, so I'm covered there. The power rating for the E5 2680v2 processor is 115 watt whereas the E5 2630 that originally came with the PC is a 95 watt part -

 

     http://cpuboss.com/cpu/Intel-Xeon-E5-2680-v2

 

     http://cpuboss.com/cpu/Intel-Xeon-E5-2630

 

I could probably get through the motherboard switch, but now my concern is entering the info in the bios. From what I understand it's a one time chance - if you screw it up the first time you don't get a second chance.

 

For the Mac it was great as one of the Forum members had created a script that updated the bios to support the new Xeon processors - an incredibly simple process.

 

 

Live and learn, I guess.


Viewing all articles
Browse latest Browse all 36019

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>