Heh hold on.

1) UEFI install of Fedora is of course possible (http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ch-Boot-x86.html). EFI has been supported on linux prior than Windows due to server market using it when Intel first introduced it:)

2) Regarding the OOBE. Fedora by default installation installs the nouveau driver for nvidia. This is perfectly functional as OOBE but is very slow on 3D. They default to this driver because it's open source. So this is how you install the native nvidia driver on Fefora:

1) First add the RPMFusion repository http://rpmfusion.org/ (You want this anyhow as it will offer you stuff that can not be bundled on the Fedora repositories due to license restrictions..such as certain video/audio codecs. Once you enable the repository it is searched automatically for stuff when you try to install something).

2) http://rpmfusion.org/Howto/nVidia#x86_64_.2864bit.29_users

Note install akmod-nvidia not the kmod that's in the "or" parenthesis. The difference is that with every kernel update akmod will made sure the driver is proper. With kmod, you need to manually install a new kmod when you update the kernel.

And you'll find that Fedora docs has answers to almost every question 😛


EDIT: And yes of course you can OC under Linux. But due to the faster kernel/kernel architecture you may find it's a little more sensitive to instability that Windows. You will find that Linux will freeze on boot on cases where Windows would actually boot and crash later.


EDIT2: By installing hte nvidia driver this way you never have to bother about updates to it again as well, as when Fedora will tell you there are updated packages to install it will include these as well (much like Windows Update but with the driver actually being proper and properly installed unlike installing Nvidia from WU :p)

EDIT3: (Scrap this it's only needed for F18-)I almost forgot. After installing the akmod as in the guide, you have to also do this in a terminal prior to rebooting:

su, enter (put root password) mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
dracut /boot/initramfs-$(uname -r).img $(uname -r)

This will backup and disable the nouveau driver in iniramfs (a ramdrive used to boot the kernel/drivers faster). After this you can forget about it.

Hmm I don't know...with Ubuntu and Fedora I tried selecting "UEFI sony removable disk" and none of the times it booted or installed....fedora gave me an error "problem loading in kernel x.509" and "couldn't get size 0x8000000e" or something like that

If I select non UEFI sony removable it loads etc.

Thanks for the tips and help though Nodens...I really want to get some of those grungy alternative chicks so I'll stick with it....

Do you have Secure Boot on?

EDIT: Fefora in itself supports Secure Boot but two issues may arise. None of them is Fedora's control at the moment but rather Microsoft's:

1:

Third-party UEFI boot loaders (such as the Fedora boot loader) are not guaranteed to work on Microsoft Secure Boot systems because the necessary certificates are not part of the Windows 8 Hardware Certification Requirements. If your hardware is in this category, you need to switch off UEFI Secure Boot, enroll the missing Microsoft certificate, or enroll the Fedora certificate.

2:

Currently, the Fedora shim was signed in a way that gives it an expiration date of October 2013, prior to the Fedora 18 end-of-life. We are not aware of any hardware that honors this expiration date, but it's not out of the question. This is the date Microsoft gave the signature, Fedora has no control over it. We are investigating this issue and expect to resolve it in the future.

The error you're getting points to the issue 2.

I admire you Arne :). This would be an adventure for real. If you have the time to spend, you will learn a lot of things. This OS needs your attention and tweaking all the time. I was willing to try also, but unfortunately, I have no time now, to go back to command line and -$ 😄