On Sun, Aug 8, 2010 at 1:53 PM, Adam Huffman <adam.huffman@xxxxxxxxx> wrote: > On Tue, Aug 3, 2010 at 6:54 PM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: >> On Sun, 2010-08-01 at 15:48 +0100, pbrobinson@xxxxxxxxx wrote: >>> On Sun, Aug 1, 2010 at 3:29 PM, Adam Huffman <adam.huffman@xxxxxxxxx> wrote: >>> > I've entered bug https://bugzilla.redhat.com/show_bug.cgi?id=620202 as >>> > I can no longer boot Fedora on my laptop, after finding a LUKS error >>> > with the F14 kernel. >>> > >>> > Not a big problem for me as there's nothing significant stored on the >>> > laptop but this would be pretty serious for a normal upgrade. >>> >>> Yes but a big problem if you have a requirement to encrypt your root >>> partition or the entire install. Sounds like an alpha blocker to me. >> >> Being able to install with encryption is indeed an Alpha criterion: >> >> "The installer must be able to complete an installation using the entire >> disk, existing free space, or existing Linux partitions methods, with or >> without encryption enabled " >> >> So if this is broken it does block Alpha. But see Bruno's reply. > > I tried adding init=/sbin/upstart and it got further but still wasn't > able to boot successfully. I've since wiped what was on there, > re-installed F13 and then used an F14 Alpha TC2 netinst disc to > upgrade to F14 Alpha. This time the encrypted partitions are > seemingly dealt with. However, boot never completes. I have a photo > of the latter - is it best to make a new bugzilla entry for this, or > put it on your Trac, or? > Adding init=/sbin/upstart allows the boot process to complete, so there does seem to be a problem with the upgrade from F13 to F14 Alpha using this TC2 image. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
