Bug#344867: kernel module missing?
Jonas Meurer wrote: does it work when you add sha256 to /etc/mkinitrd/modules before creating the initrd? sha256 alone did not work. aes_i586 alone did not work. sha256 and aes_i586 together did work. if this is the problem, the documentation should be updated. Yep. Change: > # Setup the initrd (change 386 to the correct value) > mkinitrd -o /boot/initrd.img-2.6.7-1-386 To: # Prepare to create the initrd # Edit /etc/mkinitrd/modules and add the following lines sha256 aes_i586 # Note: this is necessary to boot using the recommended (above) cipher # Make the initrd image (change X-X-X to the correct value) mkinitrd -o /boot/initrd.img-2.6.X-X-X Thanks, James. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344867: kernel module missing?
On 28/01/2006 James Clark wrote: > Closed bug #290017 indicates that mkinitrd does support crypto now, > found from here: /usr/share/doc/cryptsetup/changelog.Debian.gz > > Does this mean there's an error in the documentation? yes, you're correct. i don't know mkinitrd, but i can imagine, that it loads only aes, as this is the default cypher for cryptsetup. does it work when you add sha256 to /etc/mkinitrd/modules before creating the initrd? if this is the problem, the documentation should be updated. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344867: kernel module missing?
* James Clark <[EMAIL PROTECTED]> [2006-01-28 08:39]: > >so how did you create the initrd? mkinitrd doesn't have cryptsetup > >support so far, but as far as i know, yaird does. > From /usr/share/doc/cryptsetup/CryptoRoot.HowTo: > # Setup the initrd (change 386 to the correct value) > mkinitrd -o /boot/initrd.img-2.6.7-1-386 > Does this mean there's an error in the documentation? No, initrd-tools supports dm-crypt and cryptsetup. yaird doesn't. See #336599: please support dm-crypt devices -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344867: kernel module missing?
Jonas Meurer wrote: so how did you create the initrd? mkinitrd doesn't have cryptsetup support so far, but as far as i know, yaird does. From /usr/share/doc/cryptsetup/CryptoRoot.HowTo: "... # Setup the initrd (change 386 to the correct value) mkinitrd -o /boot/initrd.img-2.6.7-1-386 ..." Closed bug #290017 indicates that mkinitrd does support crypto now, found from here: /usr/share/doc/cryptsetup/changelog.Debian.gz Does this mean there's an error in the documentation? Cheers, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344867: kernel module missing?
On 23/01/2006 James Clark wrote: > Jonas Meurer wrote: > >your screenshot includes the following error: > >modprobe: FATAL: Could not open \ > > '/lib/modules/2.6.12-1-k7/kernel/crypto/sha256.ko': \ > > No such file or directory > > > >this means, that the kernel module sha256 is not available for > >linux-image 2.6.12-1-k7 on your machine. please check your kernel > >konfiguration. > > # ls -l /lib/modules/2.6.12-1-k7/kernel/crypto/sha256.ko > -rw-r--r-- 1 root root 12200 2005-09-27 17:04 > /lib/modules/2.6.12-1-k7/kernel/crypto/sha256.ko > # uname -ar > Linux dvda 2.6.12-1-k7 #1 Tue Sep 27 13:22:07 JST 2005 i686 GNU/Linux > > It's on the filesystem, this is what makes me think it's not in the > initrd that's being generated. so how did you create the initrd? mkinitrd doesn't have cryptsetup support so far, but as far as i know, yaird does. please try to create your initrd with yaird, and tell us whether that fixes the problem. best would be to write a short howto about how to create a useful initrd with yaird or initramfs. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344867: kernel module missing?
Jonas Meurer wrote: your screenshot includes the following error: modprobe: FATAL: Could not open \ '/lib/modules/2.6.12-1-k7/kernel/crypto/sha256.ko': \ No such file or directory this means, that the kernel module sha256 is not available for linux-image 2.6.12-1-k7 on your machine. please check your kernel konfiguration. # ls -l /lib/modules/2.6.12-1-k7/kernel/crypto/sha256.ko -rw-r--r-- 1 root root 12200 2005-09-27 17:04 /lib/modules/2.6.12-1-k7/kernel/crypto/sha256.ko # uname -ar Linux dvda 2.6.12-1-k7 #1 Tue Sep 27 13:22:07 JST 2005 i686 GNU/Linux It's on the filesystem, this is what makes me think it's not in the initrd that's being generated. Thanks, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344867: kernel module missing?
hello james, your screenshot includes the following error: modprobe: FATAL: Could not open \ '/lib/modules/2.6.12-1-k7/kernel/crypto/sha256.ko': \ No such file or directory this means, that the kernel module sha256 is not available for linux-image 2.6.12-1-k7 on your machine. please check your kernel konfiguration. or do you have additional information? ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
