I'm having trouble installing linux on a machine I recently built. So far I've tried installation Ubuntu 14.04 LTS, 15. 04, fedora 22 workstation, fedora 22 plasma kde, fedora 22 workstation net install, and openSUSE. Additionally I have used both USB install options and CD/DVD install options. I have also tried both separate hard drive installations as well and dual booting on my SSD with windows 8.1.

I'm getting extremely frustrated that I can't get a successful install. I thought this was 2015, the year of the linux?

My problem is that every distribution is constantly freezing at some point. Ubuntu never gets past it's initial start up screen in any scenario, fedora occasionally starts the installer but freezes during the installation. I got fedora 22 installed but froze many times once I bloated up and when trying to update it froze and broke the kernel. OpenSUSE can't recognize any installation media despite booting up into the installer.

I'm having so much trouble and get even get into most installers. I'm not even getting error messages I'm getting constant unpredictable hanging and freezing.

I'm using an x99 EVGA FTW motherboard, Intel 5820k cpu, corsaid 2666mhz ddr4 16gb ram, EVGA GTX 980 gpu, corair RM850 psu, corair 750D case and an Asus bluray burner optical drive.

Fedora 22 recognized all of my devices inside of the operating system on the one successful install before it broke. And now I have no access to my windows partition because the boot loader is destroyed.

Can anybody please she'd some light on why this is happening?

Also, when I very first tried to install ubuntu I got an error message that my sound card wasn't compatible. It was only one time I got the message and I can't replicate it to give more details. I had this issue Debian years ago.

Shameless bump. I currently have no working computer and am quite frustrated at the moment. My bootloader is wrecked so I can't even access my windows partition. I've done as much searching as I can but nobody is having this consistent issue.

How are you transferring the ISO images to the installation medium?

Are you sure that the installation medium is functional and undamaged?

If you can get through the installation process, there should be a working entry for Windows in the (GNU/Linux) bootloader even if the GNU/Linux distribution does not work.

Which version of windows did you have installed?
Was it installed in UEFI mode?
Did you also try to install the various Linux distributions UEFI?
Boot one of the Linux installation DVD/flash drive and go to the site below, download and run the bootinfoscript and post the output, a results.txt file here. That should give more details and someone might be able to point you in the right direction.

http://sourceforge.net/projects/bootinfoscript/

At face value, your report hits to hardware incompatibilities. If your Windows 8.1 worked "flawlessly", try to find out how you can reinstall the windows bootloader for it, using whatever facility is there now for Windows 8.x. Frankly, I stopped doing that since XP so I would not be much of a help guiding you there.

Yeah, that is what some people get for doing their own thinking. In my experience.

Not a lot of details in this thread. Like did you md5sum iso downloaded files?
Where freezes occur during the install process?

A live cd session accessing the internal install and posting /var/log messages pertaining to error messages would have helped your cause.

I guess you can try this one. Just be sure to md5sum the iso download before getting started is my advice.
Use the pae iso since you have 16 gig of ram

http://www.mepiscommunity.org/mx

or not. I have yet to bork a install on any of my many computers. So I don't have a problem accessing one.

Edit: Incase you just want just your Windows Back. I went through something like this already with another user on another forum. http://www.linuxforums.org/forum/ins...boot-fail.html

Is your motherboard's BIO's UEFI?

Is secure boot disabled?

It could be that you have to install Linux on your new build in UEFI Mode.

Is this your mobo?
http://www.evga.com/Products/Product...150-HE-E997-KR

UEFI
this is not bad

bad is what MS created from it " a Frankenstein's monster called "secure boot"

is that DISABLED

there is nothing "off" with the hardware



Now a long time ago i learned that the ONLY way to WIN THE WAR with Microsoft is to
" not play the game"


let windows have the FIRST drive and the FRIST partition on it ( the mbr)
-- dotnet framework and service packs NEED MS WINDOWS THERE !!!!!
-- let Redmond have that realestate


make a /boot partition
and install linux boot loader there

and boot from THAT /boot partition

grub2 can boot MS windows just fine

That is not the issue here -- the OP has tried Ubuntu & Fedora: both have native support for Secure Boot.

The randomness of your issue suggests cooling issues or bad RAM in my opinion. Or power issues.

Are you overclocking anything? Is the PSU of the proper W to run all those things at the same time?

Perhaps unplug stuff and see if the problem goes away? The video card can be a real power hog so if you have power issues, not enough watts from the PSU for example, taking that out of the picture should make your life less hell-ish.

CD/DVD's were burned through PowerISO and the usb was created with Pen Drive Linux installer. All ISO md5sum checked and matched. Ubuntu said there was 2 errors in the files for 14.04 each time I reinstalled it and checked the md5.

Shadow_7, my psu has more than enough power to handle everything plus more and overclocked. But yes, both CPU and RAM are overclocked in the BIOS (UEFI) and my gpu is overclocked using a windows program (ELEET?)

I don't think cooling is an issue, my Glacer 240l runs and pumps fine and all RAM posts properly and came up fine in that one luck shot with fedora. I wouldn't think that it could affect it but I'm definitely going to try to return all of my settings to default. Hopefully I can restore the bootloader to reset my graphics card firmware.

My computer and all of the parts seem to be in 100 functional condition and they're all less than 2 months old. Compatibility could be an issue here but faulty components are quite unlikely.

nomodeset until you can get the nVidia blob installed? It's been a few months since I played with Maxwell but I was never able to get one installed that had X and the OS driver by default.

Just an update.

I successfully installed and updated fedora 22 net install last night around 0900. I didn't have time to play with it much but I wrote a basic c++ programand compiled it to check if it properly downloaded the c developer package and to see if it would freeze under normal operation.

I haven't tried loading into windows yet but windows 8.1 showed in the grub loader. The successful install came immediately after resetting my bios to default settings. If that was the issue with the installs then Shadow_7 I thank you VERY much because I'm a much happier man than I was two days ago. I'm going to start by raising the clock speed on my cpu by a little to see how long before the installation becomes unstable.

The GTX 980 is not yet fully supported by the open source drivers. It might help, if you blacklist the nouveau driver. I'm not sure how to do that exactly. It must be done via kernel parameters, since you can't boot; or you have to boot a "recovery" image, if that is installed besides your main Linux image.
You might find an EFIShell useful for getting your Windows back https://wiki.archlinux.org/index.php...ace#UEFI_Shell (also useful for adding kernel parameters to the boot of Linux, if that is still installed, or for booting a recovery image).
And like the others mentioned: The installation medium must be booted in UEFI mode (not compatability mode), so it recognizes it must perform an UEFI installation. Otherwise you get an MBR installation... Which is within spec, but a gross chimera. If consequently your drive now boots up in compatibility mode, because the MBR has a bootloader, it might explain why Windows disappeared. You could try changing your boot options to alter the priority as to first try UEFI and then MBR compatibility.

Glad to hear the good news!