Bug#287085: kernel-image-2.4.27-1-386: apt-get upgrade fails to configure kernel-image-2.4.27-1 - depmod exited with return value 1
On Thu, Dec 23, 2004 at 11:02:54PM -0800, Dan Leitner wrote:
> Package: kernel-image-2.4.27-1-386
> Version: 2.4.27-6
> Severity: grave
> Justification: renders package unusable
>
> During post install configure depmod output hundreds of 'not for this
> architecture' errors. Actually it did for every module. This dual amd64
> system has both kernel-image-2.6.8-9-amd64-k8-smp and this 2.4 i386 kernel installed. I suspect the problem is in either modutils or module-init-tools as they both claim the '/sbin/depmod' is a part of their package. The system runs usually on the 2.6 k8 smp kernel since it runs WAY FASTER. The 2.4 kernel is a backup, just in case, but now I have no backup.
>
> In case you're interested... I would be using a 2.4 amd64-k8-smp kernel if one was offered as the 2.6 version is just a bad choice for CDRW'S. I still can't get that to work.. But that's a different bug. ;-)
>
> The post install configure ends like this, but several hundreds other 'not for this archtecture' errors.
>
> depmod: ELF file /lib/modules/2.4.27-1-386/kernel/net/x25/x25.o not for
> this architecture
> depmod: ELF file /lib/modules/2.4.27-1-386/kernel/net/xfrm/xfrm_user.o
> not for this architecture
> depmod: ELF file /lib/modules/2.4.27-1-386/initrd/vesafb.o not for this
> architecture
> There was a problem running depmod. This may be benign,
> (You may have versioned symbol names, for instance).
> Or this could be an error.
> depmod exited with return value 1
> Since this image uses initrd, I am not deleting the file
> /lib/modules/2.4.27-1-386/modules.dep. However, there is no
> guarantee that the file is valid. I would strongly advice
> you to either abort and fix the errors in depmod, or
> regenerate the initrd image with a known good modules.dep
> file. I repeat, an initrd kernel image with a bad modules.dep
> shall fail to boot.
> Would you like to abort now? [No] yes
> dpkg: error processing kernel-image-2.4.27-1-386 (--configure):
> subprocess post-installation script returned error exit status
> 1
> Errors were encountered while processing:
> kernel-image-2.4.27-1-386
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> dan@technonerd:~$
That is quite strange,
there was an ABI change in this release, but I am not sure
that is the problem that you are seeing. It seems to be
AMD64 specific. Dannf, perhaps you have some ideas.
In the mean time, you may want to test the proposed replacement
for 2.4.27-6
http://debian.vergenet.net/pending/kernel-image-2.4.27-i386-2.4.27/
--
Horms
Reply to: