I doubt it's a UEFI or SecureBoot problem... the Fedora Live USB I made boots just fine. The UEFI setting is EFI-only (no legacy boot). I also tried with and without SecureBoot, and had the same behavior. (Interestingly, even with SecureBoot turned on, I did not have any issues installing and booting Fedora if I removed all the existing partitions. I didn't actually expect that to work and still not sure why it did.)

To be clear, the problem doesn't occur at boot time. Rather, Anaconda appears to lock up before it begins creating the partitions I specified and installing packages.

So, I'm willing to bet it's more of an Anaconda problem. I'm just not sure how to even begin tracking it down. I had thought it may have something to do with the extra recovery partitions, but the partitioning screen in Anaconda seemed to detect the existing partitions just fine.


--
Christopher L Tubbs II
http://gravatar.com/ctubbsii

On Sun, Nov 30, 2014 at 12:43 PM, Alexander Ploumistos <alex.ploumistos@gmail.com> wrote:
Unless there is a bug in anaconda, that smells a lot like UEFI.

Did you boot in BIOS/Legacy mode or UEFI when windows 8 were installed?
What were your BIOS settings with regard to that and SecureBoot?

There are some issues with recent Lenovo laptops, UEFI and linux.

2014-11-30 19:09 GMT+02:00 Christopher <ctubbsii-fedora@apache.org>:
Hi all,

I was testing installing Fedora 21 Final RC1 in the free space on a GPT drive with Windows 8.1 (Lenovo Z40). I'm installing from a USB stick made from the ISO.

Every time I click "Begin Installation" in Anaconda, it locks up at the screen where I'm supposed to be able to enter the root password and create a user account. The message at the bottom is something like "Initializing setup configuration" (sorry, I can't recall the exact words). I can't click on anything in Anaconda, but I can switch to a terminal and "kill -9 <pid of anaconda>" to drop me back to the Live desktop.

I do not get the same problem if I delete all the existing partitions on the drive and install only Fedora. That proceeds fine. The problem only seems to exist if I try to install alongside Windows.

My question is: how might I go about troubleshooting this?

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct