Bug #11698 “kernel-image-2.4.27-1-386: apt-get upgrade fails to ...” : Bugs : module-init-tools package : Ubuntu

Revision history for this message

In Debian Bug tracker #287085, Simon Horman (horms) wrote on 2004-12-28: 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

#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

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

Revision history for this message

In Debian Bug tracker #287085, Dan Leitner (dleit) wrote on 2004-12-28: 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

#2

Download full text (5.1 KiB)

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

I aggree AMD64 is a key point.

New information.

The problem effects every kernel image I try to install, and the common failure is, a failure with building the initrd image post install configure.

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

...

> -----Original Message-----
> From: Horms [mailto:horms@debian.org]
> Sent: Tuesday, December 28, 2004 03:39 AM
> To: 'Dan Leitner', 287085@bugs.debian.org
> Cc: 'dann frazier'
> 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
> 
> 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.

I aggree AMD64 is a key point.

New information.

The problem effects every kernel image I try to install, and the common failure is, a failure with building the initrd image post install configure.

An update is now available for my only good 'kernel-image-2.6.8-9-amd64-smp' , 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=$?
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-generic 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-generic.
(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 code 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=100

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 suspect as the cause of the problem, and this bug should be re assigned to that.

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

Revision history for this message

In Debian Bug tracker #287085, Dan Leitner (dleit) wrote on 2004-12-29: 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)

#3

New info.

another example of failed attempt to install a kernel.

dan@technonerd:~$ sudo apt-get install kernel-image-2.6.8-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
lilo
The following NEW packages will be installed:
kernel-image-2.6.8-1-386
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 14.1MB of archives.
After unpacking 40.4MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-1-386 2.6.8-10 [ 14.1MB]
Fetched 14.1MB in 3m37s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-1-386.
(Reading database ... 100550 files and directories currently installed.)
Unpacking kernel-image-2.6.8-1-386 (from .../kernel-image-2.6.8-1-386_2.6.8-10_i386.deb) ...
Setting up kernel-image-2.6.8-1-386 (2.6.8-10) ...
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 code 1
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-1-386 (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
kernel-image-2.6.8-1-386
E: Sub-process /usr/bin/dpkg returned an error code (1)
dan@technonerd:~$

A google search for.
cp: cannot stat `(0x00000000)': No such file or directory

found this.

http://lists.debian.org/debian-user/2004/12/msg00260.html

Now, I hope I have a 32bit bootable kernel on diskette, since the only one on the hard drive vanished.

Would the sarge install disk serve this function as well?

DL

Revision history for this message

In Debian Bug tracker #287085, Dan Leitner (dleit) wrote on 2004-12-29: 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

#4

Download full text (3.2 KiB)

New info.

Booting an OLD woody 2.2.20-pci-ide kernel on a floppy, and following suggestion here http://lists.debian.org/debian-user/2004/12/msg00260.html allowed me to conplete the install of 'kernel-image-2.6.8-1-386'.

Next I booted the kernel-image-2.6.8-1-386, and then successfully installed kernel-image-2.4.27-1-386.

dan@technonerd:~$ sudo apt-get install kernel-image-2.4.27-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
lilo kernel-doc-2.4.27 kernel-source-2.4.27 kernel-pcmcia-modules-2.4.27-1-386
The following NEW packages will be installed:
kernel-image-2.4.27-1-386
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 0B/11.0MB of archives.
After unpacking 29.7MB of additional disk space will be used.
Selecting previously deselected package kernel-image-2.4.27-1-386.
(Reading database ... 102269 files and directories currently installed.)
Unpacking kernel-image-2.4.27-1-386 (from .../kernel-image-2.4.27-1-386_2.4.27-6_i386.deb) ...
Setting up kernel-image-2.4.27-1-386 (2.4.27-6) ...
Not touching initrd symlinks since we are being reinstalled (2.4.27-2)
Not updating image symbolic links since we are being updated (2.4.27-2)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.4.27-1-386
Updating /boot/grub/menu.lst ... done

dan@technonerd:~$

So then I tried this and was supprised to see it work.

dan@technonerd:~$ sudo apt-get install kernel-image-2.6.8-9-amd64-k8
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-k8
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 13.2MB of archives.
After unpacking 46.5MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-9-amd64-k8 2.6.8-8 [13.2MB]
Fetched 13.2MB in 3m24s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-9-amd64-k8.
(Reading database ... 103543 files and directories currently installed.)
Unpacking kernel-image-2.6.8-9-amd64-k8 (from .../kernel-image-2.6.8-9-amd64-k8_2.6.8-8_i386.deb) ...
Setting up kernel-image-2.6.8-9-amd64-k8 (2.6.8-8) ...
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8
Found kernel: /boot/vmlinuz-2.4.27-1-386
Updating /boot/grub/menu.lst ... done

dan@technonerd:~$

It seems I can not install kernel images (ie makinitrd) while running and amd64 kernel. What a pain in the butt.

The pending update of kernel-image-2.6.8-9-amd64-k8-smp might just upgrade now, if I do it running an i386 kernel. I'm holding off for now though.

Perhaps the amd64 kerne...

New info.

Booting an OLD woody 2.2.20-pci-ide kernel on a floppy, and following suggestion here http://lists.debian.org/debian-user/2004/12/msg00260.html allowed me to conplete the install of 'kernel-image-2.6.8-1-386'.

Next I booted the kernel-image-2.6.8-1-386, and then successfully installed kernel-image-2.4.27-1-386.

dan@technonerd:~$ sudo apt-get install kernel-image-2.4.27-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  lilo kernel-doc-2.4.27 kernel-source-2.4.27 kernel-pcmcia-modules-2.4.27-1-386
The following NEW packages will be installed:
  kernel-image-2.4.27-1-386
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 0B/11.0MB of archives.
After unpacking 29.7MB of additional disk space will be used.
Selecting previously deselected package kernel-image-2.4.27-1-386.
(Reading database ... 102269 files and directories currently installed.)
Unpacking kernel-image-2.4.27-1-386 (from .../kernel-image-2.4.27-1-386_2.4.27-6_i386.deb) ...
Setting up kernel-image-2.4.27-1-386 (2.4.27-6) ...
Not touching initrd symlinks since we are being reinstalled (2.4.27-2)
Not updating image symbolic links since we are being updated (2.4.27-2)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.4.27-1-386
Updating /boot/grub/menu.lst ... done

dan@technonerd:~$

So then I tried this and was supprised to see it work.

dan@technonerd:~$ sudo apt-get install kernel-image-2.6.8-9-amd64-k8
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-k8
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 13.2MB of archives.
After unpacking 46.5MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-9-amd64-k8 2.6.8-8 [13.2MB]
Fetched 13.2MB in 3m24s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-9-amd64-k8.
(Reading database ... 103543 files and directories currently installed.)
Unpacking kernel-image-2.6.8-9-amd64-k8 (from .../kernel-image-2.6.8-9-amd64-k8_2.6.8-8_i386.deb) ...
Setting up kernel-image-2.6.8-9-amd64-k8 (2.6.8-8) ...
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8
Found kernel: /boot/vmlinuz-2.4.27-1-386
Updating /boot/grub/menu.lst ... done

dan@technonerd:~$

It seems I can not install kernel images (ie makinitrd) while running and amd64 kernel. What a pain in the butt.

The pending update of kernel-image-2.6.8-9-amd64-k8-smp might just upgrade now, if I do it running an i386 kernel. I'm holding off for now though.

Perhaps the amd64 kernels don't work well on sarge, and should be removed

Revision history for this message

In Debian Bug tracker #287085, dann frazier (dannf) wrote on 2004-12-29: 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

#5

On Tue, Dec 28, 2004 at 12:39:32PM +0900, Horms wrote:
> 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 don't know much about amd64, sorry (I'm the ia64 guy....)

Revision history for this message

In Debian Bug tracker #287085, Thomas Hood (jdthood-aglu) wrote on 2005-01-05: retitle

#6

retitle 287085 kernel-image-2.4.27-1-386: apt-get upgrade fails to configure on amd64 - depmod exited with return value 1
thanks
--
Thomas Hood <email address hidden>

Revision history for this message

In Debian Bug tracker #287085, Simon Horman (horms) wrote on 2005-01-07: 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

#7

On Tue, Dec 28, 2004 at 10:10:33PM -0700, dann frazier wrote:
> On Tue, Dec 28, 2004 at 12:39:32PM +0900, Horms wrote:
> > 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 don't know much about amd64, sorry (I'm the ia64 guy....)

My mistake, sorry.

--
Horms

Revision history for this message

In Debian Bug tracker #287085, Simon Horman (horms) wrote on 2005-01-07:

#8

Download full text (5.7 KiB)

reassign 287085 module-init-tools
thanks

On Tue, Dec 28, 2004 at 04:33:56PM +0000, Dan Leitner wrote:
>
> > -----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 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.
>
> I aggree AMD64 is a key point.
>
> New information.
>
> The problem effects every kernel image I try to install, and the common failure is, a failure with b...

reassign 287085 module-init-tools
thanks

On Tue, Dec 28, 2004 at 04:33:56PM +0000, Dan Leitner wrote:
> 
> > -----Original Message-----
> > From: Horms [mailto:horms@debian.org]
> > Sent: Tuesday, December 28, 2004 03:39 AM
> > To: 'Dan Leitner', 287085@bugs.debian.org
> > Cc: 'dann frazier'
> > 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
> > 
> > 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.
> 
> I aggree AMD64 is a key point.
> 
> New information.
> 
> The problem effects every kernel image I try to install, and the common failure is, a failure with building the initrd image post install configure.
> 
> An update is now available for my only good 'kernel-image-2.6.8-9-amd64-smp' , 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=$?
> 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-generic 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-generic.
> (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 code 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=100
> 
> 
> 
> 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 suspect as the cause of the problem, and this bug should be re assigned to that. 
> 
> 
> > 
> > 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 for the additional info, I agree it seems to be some
sort of user-space problem not a kernel issue. I am going to reasign it
to module-init-tools, the package that owns depmod, but it is
probably actually a library problem. Hopefully the module-init-tools
maintainer has some ideas.

-- 
Horms

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#9

Automatically imported from Debian bug report #287085 http://bugs.debian.org/287085

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#10

Message-Id: <email address hidden>
Date: Thu, 23 Dec 2004 23:02:54 -0800
From: Dan Leitner <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: 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

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:~$

-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.8-9-amd64-k8-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kernel-image-2.4.27-1-386 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii initrd-tools 0.1.74 tools to create initrd image for p
ii modutils 2.4.26-1.2 Linux module utilities

-- no debconf information

Message-Id: <E1Chja8-0000AV-00@spohr.debian.org>
Date: Thu, 23 Dec 2004 23:02:54 -0800
From: Dan Leitner <dleit@speakeasy.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: 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

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:~$

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.8-9-amd64-k8-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kernel-image-2.4.27-1-386 depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  initrd-tools                  0.1.74     tools to create initrd image for p
ii  modutils                      2.4.26-1.2 Linux module utilities

-- no debconf information

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#11

Message-ID: <email address hidden>
Date: Tue, 28 Dec 2004 12:39:32 +0900
From: Horms <email address hidden>
To: 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

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

Message-ID: <20041228033932.GC10448@verge.net.au>
Date: Tue, 28 Dec 2004 12:39:32 +0900
From: Horms <horms@debian.org>
To: Dan Leitner <dleit@speakeasy.net>, 287085@bugs.debian.org
Cc: dann frazier <dannf@debian.org>
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

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

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#12

Download full text (5.6 KiB)

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

Message-ID: <W506269163125121104251636@webmail2>
Date: Tue, 28 Dec 2004 16:33:56 +0000
From: "Dan Leitner" <dleit@speakeasy.net>
To: "Horms" <horms@debian.org>, "Dan Leitner" <dleit@speakeasy.net>, 
    287085@bugs.debian.org
Cc: "dann frazier" <dannf@debian.org>
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:horms@debian.org]
> Sent: Tuesday, December 28, 2004 03:39 AM
> To: 'Dan Leitner', 287085@bugs.debian.org
> 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

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#13

Message-ID: <W803732185814281104281396@webmail1>
Date: Wed, 29 Dec 2004 00:49:56 +0000
From: "Dan Leitner" <email address hidden>
To: <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)

New info.

another example of failed attempt to install a kernel.

dan@technonerd:~$ sudo apt-get install kernel-image-2.6.8-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
lilo
The following NEW packages will be installed:
kernel-image-2.6.8-1-386
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 14.1MB of archives.
After unpacking 40.4MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-1-386 2.6.8-10 [ 14.1MB]
Fetched 14.1MB in 3m37s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-1-386.
(Reading database ... 100550 files and directories currently installed.)
Unpacking kernel-image-2.6.8-1-386 (from .../kernel-image-2.6.8-1-386_2.6.8-10_i386.deb) ...
Setting up kernel-image-2.6.8-1-386 (2.6.8-10) ...
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 code 1
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-1-386 (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
kernel-image-2.6.8-1-386
E: Sub-process /usr/bin/dpkg returned an error code (1)
dan@technonerd:~$

A google search for.
cp: cannot stat `(0x00000000)': No such file or directory

found this.

http://lists.debian.org/debian-user/2004/12/msg00260.html

Now, I hope I have a 32bit bootable kernel on diskette, since the only one on the hard drive vanished.

Would the sarge install disk serve this function as well?

DL

Message-ID: <W803732185814281104281396@webmail1>
Date: Wed, 29 Dec 2004 00:49:56 +0000
From: "Dan Leitner" <dleit@speakeasy.net>
To: 287085@bugs.debian.org
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)

New info.

another example of failed attempt to install a kernel.

dan@technonerd:~$ sudo apt-get install kernel-image-2.6.8-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  lilo
The following NEW packages will be installed:
  kernel-image-2.6.8-1-386
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 14.1MB of archives.
After unpacking 40.4MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-1-386 2.6.8-10 [                 14.1MB]
Fetched 14.1MB in 3m37s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-1-386.
(Reading database ... 100550 files and directories currently installed.)
Unpacking kernel-image-2.6.8-1-386 (from .../kernel-image-2.6.8-1-386_2.6.8-10_i386.deb) ...
Setting up kernel-image-2.6.8-1-386 (2.6.8-10) ...
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 code 1
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-1-386 (--configure):
 subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
 kernel-image-2.6.8-1-386
E: Sub-process /usr/bin/dpkg returned an error code (1)
dan@technonerd:~$

A google search for.
cp: cannot stat `(0x00000000)': No such file or directory

found this.

http://lists.debian.org/debian-user/2004/12/msg00260.html

Now, I hope I have a 32bit bootable kernel on diskette, since the only one on the hard drive vanished.

Would the sarge install disk serve this function as well?

DL

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#14

Download full text (3.6 KiB)

Message-ID: <W856362757061191104287729@webmail2>
Date: Wed, 29 Dec 2004 02:35:29 +0000
From: "Dan Leitner" <email address hidden>
To: <email address hidden>
Cc: "DuBoff, Alan 'Ferrari Luvn bitch'" <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

New info.

Booting an OLD woody 2.2.20-pci-ide kernel on a floppy, and following sug=
gestion here http://lists.debian.org/debian-user/2004/12/msg00260.html al=
lowed me to conplete the install of 'kernel-image-2.6.8-1-386'.

Next I booted the kernel-image-2.6.8-1-386, and then successfully install=
ed kernel-image-2.4.27-1-386.

dan@technonerd:~$ sudo apt-get install kernel-image-2.4.27-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
lilo kernel-doc-2.4.27 kernel-source-2.4.27 kernel-pcmcia-modules-2.4.2=
7-1-386
The following NEW packages will be installed:
kernel-image-2.4.27-1-386
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 0B/11.0MB of archives.
After unpacking 29.7MB of additional disk space will be used.
Selecting previously deselected package kernel-image-2.4.27-1-386.
(Reading database ... 102269 files and directories currently installed.)
Unpacking kernel-image-2.4.27-1-386 (from .../kernel-image-2.4.27-1-386_2=
.4.27-6_i386.deb) ...
Setting up kernel-image-2.4.27-1-386 (2.4.27-6) ...
Not touching initrd symlinks since we are being reinstalled (2.4.27-2)
Not updating image symbolic links since we are being updated (2.4.27-2)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst=
.
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.4.27-1-386
Updating /boot/grub/menu.lst ... done

dan@technonerd:~$

So then I tried this and was supprised to see it work.

dan@technonerd:~$ sudo apt-get install kernel-image-2.6.8-9-amd64-k8
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-k8
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 13.2MB of archives.
After unpacking 46.5MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-9-amd64-k=
8 2.6.8-8 [13.2MB]
Fetched 13.2MB in 3m24s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-9-amd64-k8.
(Reading database ... 103543 files and directories currently installed.)
Unpacking kernel-image-2.6.8-9-amd64-k8 (from .../kernel-image-2.6.8-9-am=
d64-k8_2.6.8-8_i386.deb) ...
Setting up kernel-image-2.6.8-9-amd64-k8 (2.6.8-8) ...
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst=
.
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k...

Message-ID: <W856362757061191104287729@webmail2>
Date: Wed, 29 Dec 2004 02:35:29 +0000
From: "Dan Leitner" <dleit@speakeasy.net>
To: 287085@bugs.debian.org
Cc: "DuBoff, Alan 'Ferrari Luvn bitch'" <aland@softorchestra.com>
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

New info.

Booting an OLD woody 2.2.20-pci-ide kernel on a floppy, and following sug=
gestion here http://lists.debian.org/debian-user/2004/12/msg00260.html al=
lowed me to conplete the install of 'kernel-image-2.6.8-1-386'.

Next I booted the kernel-image-2.6.8-1-386, and then successfully install=
ed kernel-image-2.4.27-1-386.

dan@technonerd:~$ sudo apt-get install kernel-image-2.4.27-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  lilo kernel-doc-2.4.27 kernel-source-2.4.27 kernel-pcmcia-modules-2.4.2=
7-1-386
The following NEW packages will be installed:
  kernel-image-2.4.27-1-386
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 0B/11.0MB of archives.
After unpacking 29.7MB of additional disk space will be used.
Selecting previously deselected package kernel-image-2.4.27-1-386.
(Reading database ... 102269 files and directories currently installed.)
Unpacking kernel-image-2.4.27-1-386 (from .../kernel-image-2.4.27-1-386_2=
.4.27-6_i386.deb) ...
Setting up kernel-image-2.4.27-1-386 (2.4.27-6) ...
Not touching initrd symlinks since we are being reinstalled (2.4.27-2)
Not updating image symbolic links since we are being updated (2.4.27-2)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst=
 .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.4.27-1-386
Updating /boot/grub/menu.lst ... done

dan@technonerd:~$

So then I tried this and was supprised to see it work.

dan@technonerd:~$ sudo apt-get install kernel-image-2.6.8-9-amd64-k8
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-k8
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 13.2MB of archives.
After unpacking 46.5MB of additional disk space will be used.
Get:1 http://mirrors.kernel.org testing/main kernel-image-2.6.8-9-amd64-k=
8 2.6.8-8 [13.2MB]
Fetched 13.2MB in 3m24s (64.8kB/s)
Selecting previously deselected package kernel-image-2.6.8-9-amd64-k8.
(Reading database ... 103543 files and directories currently installed.)
Unpacking kernel-image-2.6.8-9-amd64-k8 (from .../kernel-image-2.6.8-9-am=
d64-k8_2.6.8-8_i386.deb) ...
Setting up kernel-image-2.6.8-9-amd64-k8 (2.6.8-8) ...
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst=
 .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.8-1-386
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8-smp
Found kernel: /boot/vmlinuz-2.6.8-9-amd64-k8
Found kernel: /boot/vmlinuz-2.4.27-1-386
Updating /boot/grub/menu.lst ... done

dan@technonerd:~$

It seems I can not install kernel images (ie makinitrd) while running and=
 amd64 kernel. What a pain in the butt.

The pending update of kernel-image-2.6.8-9-amd64-k8-smp might just upgrad=
e now, if I do it running an i386 kernel. I'm holding off for now though.=

Perhaps the amd64 kernels don't work well on sarge, and should be removed=

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#15

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#16

Message-ID: <20041229051033.GA5558@jale>
Date: Tue, 28 Dec 2004 22:10:33 -0700
From: dann frazier <email address hidden>
To: Horms <email address hidden>
Cc: Dan Leitner <email address hidden>, <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

On Tue, Dec 28, 2004 at 12:39:32PM +0900, Horms wrote:
> 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 don't know much about amd64, sorry (I'm the ia64 guy....)

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#17

Message-Id: <1104950388.10099.113.camel@thanatos>
Date: Wed, 05 Jan 2005 19:39:48 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: retitle

retitle 287085 kernel-image-2.4.27-1-386: apt-get upgrade fails to configure on amd64 - depmod exited with return value 1
thanks
--
Thomas Hood <email address hidden>

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#18

Message-ID: <email address hidden>
Date: Fri, 7 Jan 2005 15:29:56 +0900
From: Horms <email address hidden>
To: dann frazier <email address hidden>
Cc: Dan Leitner <email address hidden>, <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

On Tue, Dec 28, 2004 at 10:10:33PM -0700, dann frazier wrote:
> On Tue, Dec 28, 2004 at 12:39:32PM +0900, Horms wrote:
> > 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 don't know much about amd64, sorry (I'm the ia64 guy....)

My mistake, sorry.

--
Horms

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#19

Download full text (6.1 KiB)

Message-ID: <email address hidden>
Date: Fri, 7 Jan 2005 15:34:30 +0900
From: Horms <email address hidden>
To: Dan Leitner <email address hidden>
Cc: <email address hidden>, <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

reassign 287085 module-init-tools
thanks

On Tue, Dec 28, 2004 at 04:33:56PM +0000, Dan Leitner wrote:
>
> > -----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 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 st...

Message-ID: <20050107063428.GE8795@verge.net.au>
Date: Fri, 7 Jan 2005 15:34:30 +0900
From: Horms <horms@debian.org>
To: Dan Leitner <dleit@speakeasy.net>
Cc: 287085@bugs.debian.org, control@bugs.debian.org
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

reassign 287085 module-init-tools
thanks

On Tue, Dec 28, 2004 at 04:33:56PM +0000, Dan Leitner wrote:
> 
> > -----Original Message-----
> > From: Horms [mailto:horms@debian.org]
> > Sent: Tuesday, December 28, 2004 03:39 AM
> > To: 'Dan Leitner', 287085@bugs.debian.org
> > Cc: 'dann frazier'
> > 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
> > 
> > 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.
> 
> I aggree AMD64 is a key point.
> 
> New information.
> 
> The problem effects every kernel image I try to install, and the common failure is, a failure with building the initrd image post install configure.
> 
> An update is now available for my only good 'kernel-image-2.6.8-9-amd64-smp' , 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=$?
> 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-generic 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-generic.
> (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 code 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=100
> 
> 
> 
> 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 suspect as the cause of the problem, and this bug should be re assigned to that. 
> 
> 
> > 
> > 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 for the additional info, I agree it seems to be some
sort of user-space problem not a kernel issue. I am going to reasign it
to module-init-tools, the package that owns depmod, but it is
probably actually a library problem. Hopefully the module-init-tools
maintainer has some ideas.

-- 
Horms

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#20

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

In Debian Bug tracker #287085, Marco d'Itri (md) wrote on 2005-01-07: severity of 287085 is important, reassign 287085 to rusty@rustcorp.com.au, tagging 287085

#30

# Automatically generated email from bts, devscripts version 2.8.6
severity 287085 important
reassign 287085 <email address hidden>
tags 287085 upstream

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#31

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

In Debian Bug tracker #287085, Marco d'Itri (md) wrote on 2005-01-07: reassign 287085 to rusty@rustcorp.com.au, bug 287085 is forwarded to rusty@rustcorp.com.au

#32

# Automatically generated email from bts, devscripts version 2.8.6
reassign 287085 <email address hidden>
forwarded 287085 <email address hidden>

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#33

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

In Debian Bug tracker #287085, Marco d'Itri (md) wrote on 2005-01-07: reassign 287085 to module-init-tools

#34

# Automatically generated email from bts, devscripts version 2.8.6
reassign 287085 module-init-tools

Revision history for this message

In Debian Bug tracker #287085, Simon Horman (horms) wrote on 2005-01-07: Re: Processed: 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

#35

On Fri, Jan 07, 2005 at 10:44:41AM +0100, Marco d'Itri wrote:
> bts severity 287085 important
> bts reassign 287085 <email address hidden>
> bts tag 287085 upstream
> thanks
>
> On Jan 07, Debian Bug Tracking System <email address hidden> wrote:
>
> > > reassign 287085 module-init-tools
> > Bug#287085: kernel-image-2.4.27-1-386: apt-get upgrade fails to configure on amd64 - depmod exited with return value 1
> > Bug reassigned from package `kernel-image-2.4.27-1-386' to `module-init-tools'.
>
> I do not know how to fix this, but I forwarded it upstream.
> Anyway, I encourage the adm64 people to look at the problem if they want
> to see it fixed.

Agreed.

--
Horms

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#36

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#37

Message-Id: <email address hidden>
Date: Fri, 7 Jan 2005 10:49:23 +0100
From: Marco d'Itri <email address hidden>
To: <email address hidden>
Subject: severity of 287085 is important, reassign 287085 to <email address hidden>, tagging 287085

# Automatically generated email from bts, devscripts version 2.8.6
severity 287085 important
reassign 287085 <email address hidden>
tags 287085 upstream

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#38

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#39

Message-Id: <email address hidden>
Date: Fri, 7 Jan 2005 11:10:34 +0100
From: Marco d'Itri <email address hidden>
To: <email address hidden>
Subject: reassign 287085 to <email address hidden>, bug 287085 is forwarded to <email address hidden>

# Automatically generated email from bts, devscripts version 2.8.6
reassign 287085 <email address hidden>
forwarded 287085 <email address hidden>

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#40

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#41

Message-ID: <email address hidden>
Date: Fri, 7 Jan 2005 19:13:22 +0900
From: Horms <email address hidden>
To: <email address hidden>, <email address hidden>,
"<email address hidden>" <email address hidden>
Subject: Re: Processed: 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

On Fri, Jan 07, 2005 at 10:44:41AM +0100, Marco d'Itri wrote:
> bts severity 287085 important
> bts reassign 287085 <email address hidden>
> bts tag 287085 upstream
> thanks
>
> On Jan 07, Debian Bug Tracking System <email address hidden> wrote:
>
> > > reassign 287085 module-init-tools
> > Bug#287085: kernel-image-2.4.27-1-386: apt-get upgrade fails to configure on amd64 - depmod exited with return value 1
> > Bug reassigned from package `kernel-image-2.4.27-1-386' to `module-init-tools'.
>
> I do not know how to fix this, but I forwarded it upstream.
> Anyway, I encourage the adm64 people to look at the problem if they want
> to see it fixed.

Agreed.

--
Horms

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#42

Message-Id: <email address hidden>
Date: Fri, 7 Jan 2005 11:20:05 +0100
From: Marco d'Itri <email address hidden>
To: <email address hidden>
Subject: reassign 287085 to module-init-tools

# Automatically generated email from bts, devscripts version 2.8.6
reassign 287085 module-init-tools

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-07:

#43

I sure wish that pure64 was closer to ready.

DL

Revision history for this message

Matt Zimmerman (mdz) wrote on 2005-01-07:

#58

This bug triggered a bug in debzilla somewhere, and has been downgraded anyway,
so closing and de-associating from the Debian bug

Revision history for this message

Matt Zimmerman (mdz) wrote on 2005-01-07:

#59

Re-associating for testing

Revision history for this message

In Debian Bug tracker #287085, Dan Leitner (dleit) wrote on 2005-06-05: 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

#60

I believe this bug can be closed, as it seams to me the problem is gone.

My system no longer has any problems installing or upgrading kernel images.

I really do not think any reason for the problem would ever be found, and keeping the bug open is simply not needed.

DL

Revision history for this message

In Debian Bug tracker #287085, Marco d'Itri (md) wrote on 2005-06-05: closing 287085

#61

# Automatically generated email from bts, devscripts version 2.8.14
close 287085

Bug Watch Updater (bug-watch-updater) on 2006-09-27

Changed in module-init-tools:
status:	Unknown → Fix Released

Affects		Status	Importance	Assigned to	Milestone
	module-init-tools (Debian)	Fix Released	Unknown	debbugs #287085
	module-init-tools (Ubuntu)	Invalid	High	Unassigned

Ubuntu
module-init-tools package

kernel-image-2.4.27-1-386: apt-get upgrade fails to configure on amd64 - depmod exited with return value 1

Bug Description

Other bug subscribers

Remote bug watches

Ubuntumodule-init-tools package

kernel-image-2.4.27-1-386: apt-get upgrade fails to configure on amd64 - depmod exited with return value 1

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
module-init-tools package