Max Vozeler schrieb:
> Hi Thomas,
Hi Max,
> 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.
Not really:
inspecting the initrd (installation without error) gives me:
thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# ls
cciss.ko cpqarray.ko cryptoloop.ko DAC960.ko floppy.ko loop.ko
pktcdvd.ko sx8.ko umem.ko xd.ko
thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# ls -l
insgesamt 372
-rw-r--r-- 1 root root 52420 1970-01-01 01:00 cciss.ko
-rw-r--r-- 1 root root 29880 1970-01-01 01:00 cpqarray.ko
-rw-r--r-- 1 root root 5340 1970-01-01 01:00 cryptoloop.ko
-rw-r--r-- 1 root root 84937 1970-01-01 01:00 DAC960.ko
-rw-r--r-- 1 root root 79175 1970-01-01 01:00 floppy.ko
-rw-r--r-- 1 root root 20745 1970-01-01 01:00 loop.ko
-rw-r--r-- 1 root root 39039 1970-01-01 01:00 pktcdvd.ko
-rw-r--r-- 1 root root 22584 1970-01-01 01:00 sx8.ko
-rw-r--r-- 1 root root 20230 1970-01-01 01:00 umem.ko
-rw-r--r-- 1 root root 23989 1970-01-01 01:00 xd.ko
thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# modinfo
loop.ko
filename: loop.ko
license: GPL
alias: block-major-7-*
vermagic: 2.6.10-knoelk preempt K7 gcc-3.3
depends:
parm: max_loop:Maximum number of loop devices (1-256)
thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block#
So I have the original kernel loop modul. (how sould mkinitrd know that one
adds the loop-aes-modul package afterwards)
Installation with error:
thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# ls -l
total 440
-rw-r--r-- 1 root root 84937 Jan 1 1970 DAC960.ko
-rw-r--r-- 1 root root 52420 Jan 1 1970 cciss.ko
-rw-r--r-- 1 root root 29880 Jan 1 1970 cpqarray.ko
-rw-r--r-- 1 root root 5340 Jan 1 1970 cryptoloop.ko
-rw-r--r-- 1 root root 79175 Jan 1 1970 floppy.ko
-rw-r--r-- 1 root root 69611 Jan 1 1970 loop.ko
-rw-r--r-- 1 root root 20745 Jan 1 1970 loop.ko-orig
-rw-r--r-- 1 root root 39039 Jan 1 1970 pktcdvd.ko
-rw-r--r-- 1 root root 22584 Jan 1 1970 sx8.ko
-rw-r--r-- 1 root root 20230 Jan 1 1970 umem.ko
-rw-r--r-- 1 root root 23989 Jan 1 1970 xd.ko
thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# modinfo
loop.ko
filename: loop.ko
license: GPL
alias: block-major-7-*
vermagic: 2.6.10-knoelk preempt K7 gcc-3.3
depends:
parm: lo_nice:Loop thread scheduler nice (0 ... -20)
parm: lo_prealloc:Number of pre-allocated pages [,index,pages]...
parm: max_loop:Maximum number of loop devices (1-256)
thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# modinfo
loop.ko-orig
filename: loop.ko-orig
license: GPL
alias: block-major-7-*
vermagic: 2.6.10-knoelk preempt K7 gcc-3.3
depends:
parm: max_loop:Maximum number of loop devices (1-256)
thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block#
So I have a different initrd. The latter one has the loop-aes loop modul.
Perhaps one should document this "feature".
> > 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?
Now I got a method to show the error.
- Installed latest loop-aes-source 2.2d-5
- Clean /lib/modules
thomas:/lib/modules# ls -l
insgesamt 20
drwxr-xr-x 4 root root 4096 2005-04-03 18:46 2.4.27-grsec
drwxr-xr-x 5 root root 4096 2005-02-03 18:16 2.6.10-1-k7
drwxr-xr-x 5 root root 4096 2005-04-04 15:14 2.6.10-sc
drwxr-xr-x 4 root root 4096 2005-04-03 18:45 2.6.8-1-k7
drwxr-xr-x 4 root root 4096 2005-04-03 18:45 2.6.8-sc
The desired kernel will have version 2.6.10-knoelk.
- Installing the compiled kernel ( make-kpkg kernel_image --append-to-version
\-knoelk modules_image --initrd ) and loop-aes-modules.
( I have these packages completly purged from the system before )
thomas:/usr/src# dpkg -i kernel-image-2.6.10-knoelk_10.00.Custom_i386.deb
loop-aes-2.6.10-knoelk_2.2d-5+10.00.Custom_i386.deb
Selecting previously deselected package kernel-image-2.6.10-knoelk.
(Reading database ... 158381 files and directories currently installed.)
Unpacking kernel-image-2.6.10-knoelk (from
kernel-image-2.6.10-knoelk_10.00.Custom_i386.deb) ...
Selecting previously deselected package loop-aes-2.6.10-knoelk.
Unpacking loop-aes-2.6.10-knoelk (from
loop-aes-2.6.10-knoelk_2.2d-5+10.00.Custom_i386.deb) ...
Adding `diversion of /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko
to /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko-orig by
loop-aes-2.6.10-knoelk'
Setting up kernel-image-2.6.10-knoelk (10.00.Custom) ...
/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.
/initrd.img does not exist. Installing from scratch, eh?
Or maybe you don't want a symbolic link here. Hmm? Lets See.
/vmlinuz does not exist. Installing from scratch, eh?
Or maybe you don't want a symbolic link here. Hmm? Lets See.
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.10-1-k7
Found kernel: /boot/vmlinuz-2.6.10-sc
Found kernel: /boot/vmlinuz-2.6.10-knoelk
Updating /boot/grub/menu.lst ... done
Setting up loop-aes-2.6.10-knoelk (2.2d-5+10.00.Custom) ...
The "FATAL" error message occurs also when I first install loop-aes and then
the kernel. Only first kernel and afterwards loop-aes doesn't show the
problem.
> Do you remember which version of loop-aes was installed before?
Unfortunately I don't remember.
> 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}
Yeep after the above dpkg invocation:
thomas:/usr/src# dpkg-divert --list | grep /lib/modules/2.6.10-knoelk/
diversion of /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko
to /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko-orig by
loop-aes-2.6.10-knoelk
thomas:/usr/src# dpkg
-S /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko{,-orig}
diversion by loop-aes-2.6.10-knoelk
from: /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko
diversion by loop-aes-2.6.10-knoelk
to: /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko-orig
loop-aes-2.6.10-knoelk,
kernel-image-2.6.10-knoelk:
/lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko
diversion by loop-aes-2.6.10-knoelk
from: /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko
diversion by loop-aes-2.6.10-knoelk
to: /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko-orig
Greetings
Thomas
PS: Excuse the wired explanation. I always explore the bug during writing ;)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
