Bug#442252: linux-image-2.6.18-5-k7: loop-aes does not work because CONFIG_BLK_DEV_LOOP=m
Eero Vuojolahti
Version: 2.6.18.dfsg.1-13etch2
Severity: important
When trying to mount a device crypted with loop-aes I get this error:
ioctl: LOOP_MULTI_KEY_SETUP_V3: Invalid argument
The loop-aes documentation says that CONFIG_BLK_DEV_LOOP must be set to "n", but in Debian Etch it is set to "m". Could this be changed to "n"?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-5-k7 depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii initramfs-tools [linux-initra 0.85h tools for generating an initramfs
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-5-k7 recommends:
ii libc6-i686 2.3.6.ds1-13etch2 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.18-5-k7/postinst/kimage-is-a-directory:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-5-k7/prerm/would-invalidate-boot-loader-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/postinst/old-initrd-link-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/preinst/abort-install-2.6.18-5-k7:
linux-image-2.6.18-5-k7/postinst/bootloader-error-2.6.18-5-k7:
linux-image-2.6.18-5-k7/preinst/failed-to-move-modules-2.6.18-5-k7:
linux-image-2.6.18-5-k7/preinst/overwriting-modules-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/postinst/bootloader-test-error-2.6.18-5-k7:
linux-image-2.6.18-5-k7/postinst/old-system-map-link-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/preinst/lilo-has-ramdisk:
* linux-image-2.6.18-5-k7/preinst/already-running-this-2.6.18-5-k7:
linux-image-2.6.18-5-k7/postinst/create-kimage-link-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/preinst/initrd-2.6.18-5-k7:
linux-image-2.6.18-5-k7/postinst/depmod-error-2.6.18-5-k7: false
linux-image-2.6.18-5-k7/prerm/removing-running-kernel-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/postinst/old-dir-initrd-link-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/preinst/elilo-initrd-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/preinst/bootloader-initrd-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/preinst/lilo-initrd-2.6.18-5-k7: true
linux-image-2.6.18-5-k7/preinst/abort-overwrite-2.6.18-5-k7:
linux-image-2.6.18-5-k7/postinst/depmod-error-initrd-2.6.18-5-k7: false
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Debian Bug Tracking System
with message-id <20070914120...@baikonur.stro.at>
and subject line Bug#442252: linux-image-2.6.18-5-k7: loop-aes does not work because CONFIG_BLK_DEV_LOOP=m
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)