On 22/02/2008 Didier Raboud wrote:
> I tried your proposal : _it works!_. The boot then hangs on "Configuring
> network interfaces", but at least the crypto is no problem anymore !
great news!
> P.S. I guess I should let this bug open until it is resolved upstream or such?
agreed. it should be
Le vendredi, 22 février 2008 00.53:33 Jonas Meurer, vous avez écrit :
> On 21/02/2008 Didier Raboud wrote:
> > I can't ! chainiv isn't in the initrd... I think I could be able to
> > rebuild an initramfs with correct modules inserted by `man`ing cpio and
> > such, I just don't know how and when I w
On 21/02/2008 Didier Raboud wrote:
> Le jeudi, 21 février 2008 16.04:55 Jonas Meurer, vous avez écrit :
> > On 21/02/2008 Didier Raboud wrote:
> > > As far as I understand them, the solution is either to wait for the merge
> > > of chainiv into blkcipher or adding chainiv.ko into the initramfs. I j
Le jeudi, 21 février 2008 16.04:55 Jonas Meurer, vous avez écrit :
> On 21/02/2008 Didier Raboud wrote:
> > As far as I understand them, the solution is either to wait for the merge
> > of chainiv into blkcipher or adding chainiv.ko into the initramfs. I just
> > don't know how I can test it myself
On 21/02/2008 Didier Raboud wrote:
> One more thing : the thread that Jonas pointed has had new answers with
> somebody reaching something like a solution :
>
> http://marc.info/?l=linux-kernel&m=120353967024559&w=2
> > I just tested one affected configuration and problem was in missing
> > "chai
Hi,
One more thing : the thread that Jonas pointed has had new answers with
somebody reaching something like a solution :
http://marc.info/?l=linux-kernel&m=120353967024559&w=2
> I just tested one affected configuration and problem was in missing
> "chainiv.ko" module on ramdisk.
As far as I u
Le jeudi, 21 février 2008 00.08:15 David Härdeman, vous avez écrit :
> Didier, as a test, could you try booting with the "break" parameter,
> that should at least drop you into a shell even if cryptsetup refused
> to.
>
> Then you can do a "modprobe crypto_blkcipher", followed by "exit" which
> wil
On 21/02/2008 Jan Niehusmann wrote:
> The missing module seems to be chainiv.ko, as discovered by Milan Broz:
>
> http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/2553
Yes, but Herbert Xu already promised to merge chainiv.ko into blkcipher
module, so I suggest to wait until 2.6.
Le mercredi, 20 février 2008 09.33:55 David Härdeman, vous avez écrit :
> If cryptsetup fails three times, the boot should continue, initramfs-tools
> should panic cause there is no root device setup, and you should be
> dropped into a shell. Could you please do that and then check which
> modules
On Tue, February 19, 2008 23:38, Didier Raboud wrote:
...
> $ ls -la /tmp/init-2.6.25/lib/modules/2.6.25-rc2-amd64/kernel/crypto/
> total 93
> drwxr-xr-x 2 didier didier 1024 2008-02-19 23:31 .
> drwxr-xr-x 8 didier didier 1024 2008-02-19 23:31 ..
> -rw-r--r-- 1 didier didier 33060 2008-02-19 23:
Le mardi, 19 février 2008 22.10:10 David Härdeman, vous avez écrit :
> On Tue, Feb 19, 2008 at 06:38:49PM +0100, Didier Raboud wrote:
> >
> >Command failed: No key available with this passphrase.
>
> This probably means that the necessary crypto modules are not present in
> the initramfs image or t
On Tue, Feb 19, 2008 at 06:38:49PM +0100, Didier Raboud wrote:
Package: cryptsetup
Version: 2:1.0.6~pre1+svn45-1
Severity: normal
Hi,
using kernel 2.6.25-rc2-amd64 from Debian-Kernel, I can't boot on my system because it is
not possible to open my LUKS root (/).
The encountered error is the
12 matches
Mail list logo
