kernel-package concept question
Dear group, I am not sure about the concept of the kernel-package
system. From the documentation I have learned that if I compile my
custom kernel, I also need to rebuild my pcmcia modules to match the
kernel. I use a laptop with pcmcia cards. I have managed to do so,
creating both:
kernel-image-2.2.17_dell.0.1+i386.deb
pcmcia-modules-2.2.17_3.1.8-16+dell.0.1_i386.deb
Also, I have assumed that if I make modifications to the kernel
configuration, I should use the revision scheme to make a next kernel.
This is the point where I assumed that again the pcmcia modules should
be rebuild to accompany the new kernel module. So I went ahead and made:
kernel-image-2.2.17_dell.0.2+i386.deb
pcmcia-modules-2.2.17_3.1.8-16+dell.0.2_i386.deb
It has been suggested in a previous post that the pcmcia should have
been left alone. Now my question is, when is it required to rebuild that?
Only if I compile a kernel from a different source?
At this point, I am left in a situation where I am unable to install the
0.2 kernel.deb because (as it seems to me) I also did the pcmcia. The
message reads:
eme_lap:/usr/src# dpkg -i kernel-image-2.2.17_dell.0.2_i386.deb
dpkg: regarding kernel-image-2.2.17_dell.0.2_i386.deb containing
kernel-image-2.2.17:
pcmcia-modules-2.2.17 conflicts with kernel-image-2.2.17 (>> dell.0.1)
kernel-image-2.2.17 (version dell.0.2) is to be installed.
dpkg: error processing kernel-image-2.2.17_dell.0.2_i386.deb
(--install):
conflicting packages - not installing kernel-image-2.2.17
Errors were encountered while processing:
kernel-image-2.2.17_dell.0.2_i386.deb
Does anyone have an idea how to get around this? I have considered to go
back and install the first kernel.deb, but am a bit worried to mess up
the system at all...
Any suggestions most welcome!
--
Erik van der Meulen <e.van.der.meulen@avondel.nl>
Reply to: