Bug#478268: [Pkg-cryptsetup-devel] Bug#478268: Bug#478268: cryptsetup: LUKS device no more recognized at boot

2008-05-14 Thread David Härdeman
On Wed, May 14, 2008 16:13, Luca Capello wrote: > Yesterday I remembered that since a while [1] I've MODULES=dep in > /etc/initramfs-tools/initramfs.conf. Indeed, this is the source of my > bug: changing it to MODULES=most generates an initrd which recognizes my > cryptoroot partition. Ok, that e

Bug#478268: [Pkg-cryptsetup-devel] Bug#478268: Bug#478268: cryptsetup: LUKS device no more recognized at boot

2008-05-14 Thread David Härdeman
On Wed, May 14, 2008 16:05, Luca Capello wrote: > Indeed, my kernel cmdline has "panic=10" by default, removing it allows > "break" to work. Good, then allow the "Waiting for root file system..." prompt to timeout (takes about 3 minutes, can be lowered by setting rootwait=), then run "cat /proc/mo

Bug#478268: [Pkg-cryptsetup-devel] Bug#478268: Bug#478268: cryptsetup: LUKS device no more recognized at boot

2008-05-14 Thread Luca Capello
Hi David! On Wed, 14 May 2008 11:23:00 +0200, David Härdeman wrote: > initramfs will behave differently if the "panic" kernel option is set > (initramfs will not spawn any shells in that case but reboot instead). > > Which options do you use to boot? Indeed, my kernel cmdline has "panic=10" by de

Bug#478268: [Pkg-cryptsetup-devel] Bug#478268: Bug#478268: cryptsetup: LUKS device no more recognized at boot

2008-05-14 Thread David Härdeman
On Wed, May 14, 2008 10:58, Jonas Meurer wrote: > On 28/04/2008 Luca Capello wrote: >> Booting with the "break" kernel option (as suggested at bug #466573 [1]) >> causes the machine to reboot before prompting for the cryptsetup >> password, at least with kernel 2.6.25-trunk-amd64. >> > > That's ind