Brian Mearns <bmearns <at> ieee.org> writes: > > echo Creating block device nodes. > > mkblkdevs > > echo Creating character device nodes. > > mkchardevs > > echo "Loading dm-crypt module" > > modprobe -q dm-crypt > > echo "Loading aes module" > > modprobe -q aes > > echo "Loading cbc module" > > modprobe -q cbc > > echo "Loading sha256 module" > > modprobe -q sha256 > > echo "Loading pata_acpi module" > > modprobe -q pata_acpi > > echo "Loading ata_generic module" > > modprobe -q ata_generic > > echo Making device-mapper control node > > mkdmnod > > modprobe scsi_wait_scan > > rmmod scsi_wait_scan > > mkblkdevs > [clipped] > > I'm back home and can get some additional information about this. > Attempting to boot using the "crypto-initrd.img", which I generated > with "mkinitrd --with=aes --with=sha256" and specifying the > LUKS/cryptsetup encrypted drive for the kernel's "root" parameter, the > boot process gets to the point of asking me for a password, then > mentions a few things about an EXT4-fs (not sure which one, but no > error's reported here), then gives the following messages before > hanging: What AES mode are you using? If I remember correctly cbc is the default, but maybe your are using ecb. In any case, I think you should add the correct module to your initrd. (Try to add both, just to find out if the error is there) Other point, I spent one whole evening looking for a solution about a failing boot, I installed a clear fedora in a partition on the same disk to try to recover my system and then I gave up. The morning after the epiphany, the keyboard was set with the american layout, and I'm using an italian one. I dont think it's your case, coz you have different errors, but ... ;-) -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
