Hi Thomas,

[EMAIL PROTECTED] wrote:
> seems that I'm the only user of loop-aes ;)

Dunno, but you have a good touch for shaking out the corner
cases :-)

> When I now install the kernel-image (before I have purged the same
> version) I get the following message:
> [...]
> Setting up kernel-image-2.6.10-nb (01) ...
> /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
> FATAL: Module loop.ko_orig not found.
> WARNING: This failure MAY indicate that your kernel will not boot!
> but it can also be triggered by needed modules being compiled into
> the kernel.
> [...]

What happens here is that mkinitrd does not ignore non-.o/.ko/.gz
modules as it probably should. The warning is "just" annoying though,
it makes no difference for the initrd build in any way. 

> These seems to be the consequence of the last bugfix.
> Going to $MODULDIR/block/drivers and issuing
> laptop:/lib/modules/2.6.10-nb/kernel/drivers/block# ls -l loop*
> -rw-r--r--  1 root root 20597 Mar 29 20:25 loop.ko-orig

This one is confusing me. 

Just so I understand, when you purged the kernel image, was 
loop-aes installed? Did you purge loop-aes as well? Was loop-aes
installed at the time you did "ls" above?

Do you remember which version of loop-aes was installed before?
I'm thinking this could be a side effect from changing the diversion
during upgrade from a version < 2.2d-3, if kernel-image was removed
before upgrade of the loop-aes package.

Another thing, could you send output of 
 
 dpkg-divert --list | grep /lib/modules/2.6.10-nb
 dpkg -S /lib/modules/2.6.10-nb/kernel/drivers/block/loop.ko{,-orig}

Thanks.

> When is this diversion thing issued ?
> When I install loop-aes or the korresponding kernel-image ?

It's added in preinst of the loop-aes module package, so when you
install that one.

> I don't know if this bug would be better directed to initrd-tools ...

The spurious warning from mkinitrd can be fixed in initrd-tools.
I think I'll prepare a patch and later clone/submit the bug there.

cheers,
Max


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to