Re: Problem with pcmcia-modules and kernel-image
Raphael Hertzog <rhertzog@hrnet.fr> wrote:
> i'm running unstable and i can't get pcmcia-modules-2.2.18 to work
> with kernel-image-2.2.18. I always get unresolved symbols (script log
> attached). And I had the same problem with 2.2.18pre21 but 2.2.17 is
> ok. I didn't report it for 2.2.18pre21 because I thought that this was
> a temporary problem but since it's still here i'm wondering what's
> going on ... am i the only one having unresolved symbol ?
No. There is already an open bug report for this problem (see
Bug#80301).
> ... After looking at the BTS, I learned about a possible
> incompatibility because one was compiled with gcc 2.95 and the other
> one with gcc272 ... is that still the problem ?
Hmm ... I don't know. I have gcc 2.95 installed on my system, which was
used to build the pcmcia-modules-2.2.18 package. I don't know what
Herbert Xu has used to build the kernel-image-2.2.18 package. He has
not responded to my email regarding this problem.
One thing is clear. I'm doing something different to build the PCMCIA
modules than was done to build the kernel image. For example, I think
that you can get Debian's PCMCIA modules to work if you rebuild the
kernel-image package yourself. At least, I've had no trouble building
PCMCIA modules against kernel images that I have built myself, only
against the official Debian kernel.
> PS: BTW, each time when I boot a new kernel there's a loop because
> modules.dep doesn't exist ... I don't know who is responsible to
> generate this file but pcmcia-modules should call it for sure ... and
> actually the postint does call depmod -a only if the current kernel is
> the one for which the modules have been compiled, shouldn't it call
> depmod -a <kernel-version> instead ?
Well, that only works if the appropriate kernel version has already
been installed, something that the pcmcia-modules package cannot
ensure. Certainly, I can guarantee that the currently running kernel
is installed; therefore, I call "depmod -a" if the modules match this
kernel.
If the modules accompany another kernel, then the system will need to
be rebooted to use the kernel in question. Therefore, I think that
it should be the kernel package's responsibility to ensure that the
dependencies have been created.
If you have any creative ideas to better handle this problem, please
share them.
- Brian
Reply to: