If you want to try UEFI the most secure way is to have got a backup of your firmware chip. Sometimes you can do that with the integrated flash utility. When you have it you could order in case of problems a correct replacement or the mac adress of your integrated nic will be a default one. If you manage to "kill" a laptop with uefi tests you should probably get a spi flashing device when it is not in warrenty. I needed a chip replacement already last year after some simple tests, so update firmware to latest version and hope that most bugs are already fixed (board used was Asus P8Z68-V with buggy firmware 3203). All Asus boards suffer from another cleanup UEFI entry error but there is a trick to avoid it when you use differnet upper/lowercase for the loader (efibootmgr -l) in case you really want to use different optionsets with one kernel as direct boot entry.
I've put together systems where all of the components individually were right off the RHEL supported list but when assembled together, no go. There are obscure interactions between kernel versions, motherboard chipsets and drive firmwares. Sometimes firmware upgrades fix problems and sometimes they break things. I've spent far too much time debugging these things trying to make a stable system. There is no rhyme or reason, only empirical results.
You actually have to plug all of those things together, install the OS and run some torture tests before you can call it "working".
The marketing department doesn't always adhere to grammar (or logic). The name is 'Blu-Ray', so trying to convince everyone that it's 'Blue-Ray' is like screaming, "I'm a moron!" and then trying to convince everyone that it's a good thing to be a moron because you use a different definition than the rest of the world uses..Blue-ray (yes, I did mean to type it like that, the colour has an 'e')
It was meant to be amusing, I should have added a smiley to it :-)
After all I think this is a very good choice. The hardware should all be working with Linux if you install the NVIDIA proprietary driver for the graphics.
Last edited by AlbertP; 01-24-2013 at 10:03 AM.