Comment 12 for bug 11698

Message-ID: <W506269163125121104251636@webmail2>
Date: Tue, 28 Dec 2004 16:33:56 +0000
From: "Dan Leitner" <email address hidden>
To: "Horms" <email address hidden>, "Dan Leitner" <email address hidden>,
    <email address hidden>
Cc: "dann frazier" <email address hidden>
Subject: Re: 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

> -----Original Message-----
> From: Horms [mailto:<email address hidden>]
> Sent: Tuesday, December 28, 2004 03:39 AM
> To: 'Dan Leitner', <email address hidden>
> Cc: 'dann frazier'
> Subject: Re: Bug#287085: kernel-image-2.4.27-1-386: apt-get upgrade fai=
ls 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 amd=
64
> > system has both kernel-image-2.6.8-9-amd64-k8-smp and this 2.4 i386 k=
ernel installed. I suspect the problem is in either modutils or module-in=
it-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 FAST=
ER. 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 kern=
el 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 f=
or
> > 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 th=
is
> > 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
> > =09Since this image uses initrd, I am not deleting the file
> > =09/lib/modules/2.4.27-1-386/modules.dep. However, there is no
> > =09guarantee that the file is valid. I would strongly advice
> > =09you to either abort and fix the errors in depmod, or
> > =09regenerate the initrd image with a known good modules.dep
> > =09file. I repeat, an initrd kernel image with a bad modules.dep
> > =09shall fail to boot.
> > =09Would you like to abort now? [No] yes
> > =09dpkg: error processing kernel-image-2.4.27-1-386 (--configure):
> > =09 subprocess post-installation script returned error exit status
> > =09 1
> > =09 Errors were encountered while processing:
> > =09 kernel-image-2.4.27-1-386
> > =09 E: Sub-process /usr/bin/dpkg returned an error code (1)
> > =09 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.

I aggree AMD64 is a key point.

New information.

The problem effects every kernel image I try to install, and the common f=
ailure is, a failure with building the initrd image post install configur=
e.

An update is now available for my only good 'kernel-image-2.6.8-9-amd64-s=
mp' , and so to prevent that from being damaged I used kpackage to atempt=
 a few kernel installs.

Below is the kpackage virtual terminal output from one of those kernels I=
 tried to install.

<pt-get install --yes 'kernel-image-2.6.8-9-amd64-generic' ;echo RESULT=3D=
$?
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  lilo
The following NEW packages will be installed:
  kernel-image-2.6.8-9-amd64-generic
0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 12.5MB of archives.
After unpacking 44.5MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-9-amd64-g=
eneric 2.6.8-8 [12.5MB]
Fetched 12.5MB in 3m13s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-9-amd64-generi=
c.
(Reading database ... 96124 files and directories currently installed.)
Unpacking kernel-image-2.6.8-9-amd64-generic (from .../kernel-image-2.6.8=
-9-amd64-generic_2.6.8-8_i386.deb) ...
Setting up kernel-image-2.6.8-9-amd64-generic (2.6.8-8) ...
cpio: (0x00000000): No such file or directory
cp: cannot stat `(0x00000000)': No such file or directory
run-parts: /usr/share/initrd-tools/scripts/e2fsprogs exited with return c=
ode 1
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-9-amd64-generic (--configure):
 subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
 kernel-image-2.6.8-9-amd64-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
RESULT=3D100

With help from a good friend, we tried to build our own 2.6.10 amd64 smp =
kernel last night and that fails. In that case we didn't get to the point=
 of building an initrd image. It was getting late and had to stop trying.=

I believe what ever utils are needed to create the initrd image are suspe=
ct as the cause of the problem, and this bug should be re assigned to tha=
t.

>
> 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/
>

I really don't think the kernel package is the problem.

Thanks.

DL