On Saturday, 03 March 2012 10:43:52 +0100,
tv.debian@googlemail.com wrote:
> >> Are you using kernel-package "make-kpkg" or the "make deb-pkg"
> >> target to build your kernel packages ? The former requires a bit of
> >> manual configuration to work properly.
> > I'm using make-kpkg:
> >
> > # cp /boot/config-`uname -r` .config
> > # make menuconfig
> > # make-kpkg --initrd --append_to_version=-layer7-imq-amd64 linux-image
> What steps did you take to configure kernel-package ? Did you read
> /usr/share/doc/kernel-package/README.gz ? Just a short citation:
>
> "With the new kernel-package conventions, you also need the example
> scripts in /etc/kernel/postinst.d/ and /etc/kernel/postrm.d, to create
> and remove the initramfs. Make sure that these scripts pay attention
> to the INITRD env variable to determine whether or not to take any
> action.
>
>
> Let me repeat:
> Since nothing is created automatically. you need to provide a hook
> script for things to happen when you install the kernel image
> package. The user provides such scripts. For example, to invoke
> mkinitramfs, I did:
>
> --8<---------------cut here---------------start------------->8---
> cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \
> /etc/kernel/postinst.d/
> cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \
> /etc/kernel/postrm.d/
> --8<---------------cut here---------------end--------------->8---
> "
>
> Maybe that's part of the problem.
Here I am not physically in front of the host to be tested, however I
installed Debian GNU/Linux 5.0.9 Lenny in a KVM virtual machine in order
to replicate the problem.
I was reading the file /usr/share/doc/kernel-package/README.gz on the
KVM virtual machine, but I didn't found the quote you mentioned, nor the
two files. However I tried the kernel compiled with the above steps
(without additional steps) and I could not reproduce the problem on my
virtual machine. i.e. it boots without problems. One test failed with a
message that the initrd was too big, but then to expand the RAM of the
VM, it boots without problems.
So now the issue is finding the difference between these two scenarios.
1) Debian GNU/Linux Lenny 5.0.8:
* 2.6.32-bpo.5-amd64 boots without problems.
* 2.6.32-layer7-imq-amd64 fails to find the MD devices.
* The environment is the same, so there were no changes in settings
or metadata, which makes me think that the difference is something
on the compiled kernel. But...
2) Debian GNU/Linux Lenny 5.0.9 (KVM):
* 2.6.32-bpo.5-amd64 boots without problems.
* 2.6.32-layer7-imq-amd64 compiled using the same procedure as in (1)
boots without problems. This makes me think that then the problem
is not the procedure used to compile.
Then the problem is due to a difference between 5.0.8 and 5.0.9? But, if
so, why precompiled kernel does not produce problems and the manually
compiled kernel fails using a procedure that did not bring problems in
another scenario?
Thanks for your reply.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598
Attachment:
signature.asc
Description: Digital signature