The Sandy Bridge Review: Intel Core i7-2600K, i5-2500K and Core i3-2100 Tested
by Anand Lal Shimpi on January 3, 2011 12:01 AM ESTUEFI Support: 3TB Drives & Mouse Support Pre-Boot
Remember the mountain of issues I had trying to get Seagate’s 3TB HDD to work as a boot drive in my X58 system? A couple of weeks ago Intel released version 10.1 of its storage drivers, which added software support for drives larger than 2.2TB. That’s one piece of the puzzle. With Sandy Bridge, many motherboard manufacturers are moving to UEFI instead of traditional 32-bit PC BIOSes. Combine that with a GPT partition and your new Sandy Bridge system should have no problems booting to and accessing 3TB drives made of a single partition.
ASUS' entire SNB lineup is UEFI enabled
ASUS sent over a couple of its 6-series motherboards which boast a custom skinned UEFI implementation. You get all of the functionality of a traditional BIOS but with a GUI, and yes, there’s full mouse support.
You’re either going to love or hate the new UEFI GUIs. They do take a little time to get used to but pretty much everything is where you’d expect it to be. Navigating with the mouse can be quicker than the keyboardin some situations and slower in others. Thankfully the interface, at least ASUS’, is pretty quick. There’s scroll wheel support although no draggable scroll bars, which makes quickly scrolling a little frustrating.
Unlike P55, you can set your SATA controller to compatible/legacy IDE mode. This is something you could do on X58 but not on P55. It’s useful for running HDDERASE to secure erase your SSD for example. If you do want to use HDDERASE on a 6-series motherboard you’ll need to first run HDDERASE4 to disable the UEFI initiated security on your drive and then run HDDERASE3 to secure erase it.
The biggest improvement to me honestly is POST time. Below is a quick comparison of time from power on to the Starting Windows screen. I’m using the exact same hardware in all three cases, just varying motherboard/CPU:
| Intel P67 | Intel P55 | Intel X58 | |
| Time from Power on to Boot Loader | 22.4 seconds | 29.4 seconds | 29.3 seconds |
Facebook
Twitter
RSS
283 Comments
View All Comments
omelet - Monday, January 3, 2011 - link
> The Sandy Bridge Review: Intel Core i5 2600K, i5 2500K and Core i3 2100 TestedDoesn't look fixed over here.
Zoomer - Monday, January 3, 2011 - link
Score one for intel marketing!Oh wait...
Beenthere - Monday, January 3, 2011 - link
I'll stick with my AMD 965 BE as it delivers a lot of performance for the price and I don't get fleeced on mobo and CPU prices like with Intel stuff.geek4life!! - Monday, January 3, 2011 - link
Exactly what I have been waiting on, time to build my RIG again. Been without a PC for 1 year now and itching to build a new one.Game on baby!!!!!!!!!!!!!!
Doormat - Monday, January 3, 2011 - link
If QuickSync is only available to those using the integrated GPU, does that mean you cant use QS with a P67 board, since they don't support integrated graphics? If so, I'll end up having to buy a dedicated QS box (a micro-ATX board, a S or T series CPU seem to be up to that challenge). Also what if the box is headless (e.g. Windows Home Server)?Does the performance of QS have to do with the number of EUs? The QS testing was on a 12-EU CPU, does performance get cut in half on a 6-EU CPU (again, S or T series CPUs would be affected).
No mention of Intel AVX functions. I suppose thats more of an architecture thing (which was covered separately), but no benchmarks (synthetic or otherwise) to demo the new feature.
MeSh1 - Monday, January 3, 2011 - link
Yeah I think this is the case or according the the blurb below you can connect a monitor to the IGP in order to use QS. Is this a design flaw? Seems like a messy workaround :(" you either have to use the integrated GPU alone or run a multimonitor setup with one monitor connected to Intel’s GPU in order to use Quick Sync."
SandmanWN - Monday, January 3, 2011 - link
The sad part is for all the great encoding you get, the playback sucks. Jacked up.Doormat - Monday, January 3, 2011 - link
I'm not that interested in playback on that device - its going to be streamed to my PS3, DLNA-enabled TVs, iPad/iPhone, etc. Considering this wont be supported as a hackintosh for a while, I might as well build a combo transcoding station and WHS box.JarredWalton - Monday, January 3, 2011 - link
How do you figure "playback sucks"? If you're using MPC-HC, it's currently broken, but that's an application issue not a problem with SNB in general.Absolution75 - Monday, January 3, 2011 - link
Thank you so much for the VS benchmarks!! Programmers rejoice!