RE: Problem with linux-image-2.6.15-1-486
Ok. Now I'm very confused. Somehow running "aptitude install" by itself
fixed the problem. (Running "aptitude install linux-image-2.6.15-1-486"
didn't work.) In any case at this point it looks like the question falls
into the category of why didn't it work before, but obviously that isn't as
important.
jcc02003-1:/home/jeff# aptitude install linux-image-2.6.15-1-486
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following NEW packages will be automatically installed:
busybox-cvs-static initramfs-tools klibc-utils libklibc
The following packages have been kept back:
module-init-tools udev
The following NEW packages will be installed:
busybox-cvs-static initramfs-tools klibc-utils libklibc
The following packages will be upgraded:
linux-image-2.6.15-1-486
1 packages upgraded, 4 newly installed, 0 to remove and 2 not upgraded.
Need to get 0B/17.0MB of archives. After unpacking 2073kB will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Preconfiguring packages ...
Selecting previously deselected package busybox-cvs-static.
(Reading database ... 27124 files and directories currently installed.)
Unpacking busybox-cvs-static (from
.../busybox-cvs-static_20040623-1_i386.deb) ...
Selecting previously deselected package libklibc.
Unpacking libklibc (from .../libklibc_1.1.16-2bpo1_i386.deb) ...
Selecting previously deselected package klibc-utils.
Unpacking klibc-utils (from .../klibc-utils_1.1.16-2bpo1_i386.deb) ...
Selecting previously deselected package initramfs-tools.
Unpacking initramfs-tools (from .../initramfs-tools_0.50bpo1_all.deb) ...
Selecting previously deselected package linux-image-2.6.15-1-486.
Preparing to replace linux-image-2.6.15-1-486 2.6.15-2bpo1 (using
.../linux-image-2.6.15-1-486_2.6.15-5bpo1_i386.deb) ...
The directory /lib/modules/2.6.15-1-486 still exists. Continuing as
directed.
Done.
Unpacking replacement linux-image-2.6.15-1-486 ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub .
dpkg: warning - old post-removal script returned error exit status 128
dpkg - trying script from the new package instead ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub .
dpkg: error processing
/var/cache/apt/archives/linux-image-2.6.15-1-486_2.6.15-5bpo1_i386.deb
(--unpack):
subprocess new post-removal script returned error exit status 128
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub .
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-2.6.15-1-486_2.6.15-5bpo1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ack! Something bad happened while installing packages. Trying to recover:
Setting up busybox-cvs-static (20040623-1) ...
Setting up libklibc (1.1.16-2bpo1) ...
Setting up klibc-utils (1.1.16-2bpo1) ...
Setting up initramfs-tools (0.50bpo1) ...
sha1sum: /boot/initrd.img-2.6.15-1-486: No such file or directory
/boot/initrd.img-2.6.15-1-486 was been altered. Cannot update.
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
jcc02003-1:/home/jeff# aptitude install
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages have been kept back:
module-init-tools udev
The following packages will be REMOVED:
modconf
The following packages will be upgraded:
linux-image-2.6.15-1-486
1 packages upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
Need to get 0B/16.2MB of archives. After unpacking 3801kB will be freed.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Preconfiguring packages ...
(Reading database ... 27219 files and directories currently installed.)
Removing modconf ...
(Reading database ... 27177 files and directories currently installed.)
Preparing to replace linux-image-2.6.15-1-486 2.6.15-2bpo1 (using
.../linux-image-2.6.15-1-486_2.6.15-5bpo1_i386.deb) ...
The directory /lib/modules/2.6.15-1-486 still exists. Continuing as
directed.
Done.
Unpacking replacement linux-image-2.6.15-1-486 ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub .
Setting up linux-image-2.6.15-1-486 (2.6.15-5bpo1) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs to build the ramdisk.
Running postinst hook /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub .
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
----------------
Thanks
Jefferson Cowart
Jeff@cowart.net
> -----Original Message-----
> From: backports-users-bounces@lists.backports.org
> [mailto:backports-users-bounces@lists.backports.org] On
> Behalf Of Jefferson Cowart
> Sent: Monday, February 20, 2006 12:46
> To: 'Norbert Tretkowski'; backports-users@lists.backports.org
> Subject: RE: Problem with linux-image-2.6.15-1-486
>
> So does anyone have any ideas how to fix my kernel problem?
> As it is I can't
> really do anything with aptitude as it is always trying to
> configure the
> linux-image package. I have tried manually downgrading to
> -2bpo and simply
> removing/purge the package and both of those operations fail.
>
>
> ----------------
> Thanks
> Jefferson Cowart
> Jeff@cowart.net
>
> > -----Original Message-----
> > From: backports-users-bounces@lists.backports.org
> > [mailto:backports-users-bounces@lists.backports.org] On
> > Behalf Of Norbert Tretkowski
> > Sent: Monday, February 20, 2006 01:36
> > To: backports-users@lists.backports.org
> > Subject: Re: Problem with linux-image-2.6.15-1-486
> >
> > * Jason Lunz wrote:
> > [...]
> > > Is the backport doing anything to handle unstable's switch to
> > > debconf?
> >
> > That's handled inside kernel-package, and we're using an up-to-date
> > version of kernel-package to build the kernel backports.
> >
> > Norbert
> >
> >
>
>
Reply to: