Problem upgrading kernel image with Update-Manager

[Gareth Mullan]

Similar to David Whyte's experience although not identical I had my Ubuntu
break with the Feisty upgrade with the common ata piix issue and I had to
fall back to the previous kernel after manually reconfigrung my xconf. The
kernal upgrage of a couple of weeks ago fixed it. Woohoo! The kernal upgrade
of a couple of nights ago broke it again. The same BusyBox TTY error. Very
disappointing quality control. c'est la vie...

-----Original Message-----
From: ubuntu-au-bounces at lists.ubuntu.com
[mailto:ubuntu-au-bounces at lists.ubuntu.com]On Behalf Of David Whyte
Sent: Sunday, 10 June 2007 8:28 PM
To: Ubuntu
Subject: Problem upgrading kernel image with Update-Manager


Last week, upgrade manager pushed out a new version of the kernel
image, which I accepted but didn't seem to install correctly.  Upon a
reboot I got a kernel panic and had to drop back to the older version
from the grub menu.

Today, another new kernel image was pushed out which I accepted hoping
it would fix the issue, but it doesn't seem to have made any
difference.  I get the following errors applying the package:

E:
/var/cache/apt/archives/linux-image-2.6.20-16-generic_2.6.20-16.29_i386.deb:
failed in buffer_write(fd) (9, ret=-1)
E: /var/cache/apt/archives/linux-image-2.6.20-16-386_2.6.20-16.29_i386.deb:
failed in buffer_write(fd) (9, ret=-1)

I use the generic kernel, but the 386 one is there for historical
reasons.  The following is my recent upgrade history:

- Commit Log for Sun Jun 10 12:28:45 2007

Upgraded the following packages:
libxvidcore4 (2:1.1.2-0.1ubuntu1) to 2:1.1.2-0.1ubuntu1.1
libxvidcore4-dev (2:1.1.2-0.1ubuntu1) to 2:1.1.2-0.1ubuntu1.1
linux-headers-2.6.20-16 (2.6.20-16.28) to 2.6.20-16.29
linux-headers-2.6.20-16-generic (2.6.20-16.28) to 2.6.20-16.29
linux-image-2.6.20-16-386 (2.6.20-16.28) to 2.6.20-16.29
linux-image-2.6.20-16-generic (2.6.20-16.28) to 2.6.20-16.29
linux-libc-dev (2.6.20-16.28) to 2.6.20-16.29

- Commit Log for Tue Jun  5 11:11:34 2007

Upgraded the following packages:
firefox (2.0.0.3+1-0ubuntu2) to 2.0.0.4+1-0ubuntu1
firefox-gnome-support (2.0.0.3+1-0ubuntu2) to 2.0.0.4+1-0ubuntu1
gimp (2.2.13-1ubuntu4) to 2.2.13-1ubuntu4.1
gimp-data (2.2.13-1ubuntu4) to 2.2.13-1ubuntu4.1
gimp-python (2.2.13-1ubuntu4) to 2.2.13-1ubuntu4.1
libfreetype6 (2.2.1-5ubuntu1) to 2.2.1-5ubuntu1.1
libfreetype6-dev (2.2.1-5ubuntu1) to 2.2.1-5ubuntu1.1
libgimp2.0 (2.2.13-1ubuntu4) to 2.2.13-1ubuntu4.1
libnspr4 (2:1.firefox2.0.0.3+1-0ubuntu2) to 2:1.firefox2.0.0.4+1-0ubuntu1
libnss3 (2:1.firefox2.0.0.3+1-0ubuntu2) to 2:1.firefox2.0.0.4+1-0ubuntu1
linux-386 (2.6.20.15.14) to 2.6.20.16.28.1
linux-headers-generic (2.6.20.15.14) to 2.6.20.16.28.1
linux-image-386 (2.6.20.15.14) to 2.6.20.16.28.1
linux-image-686 (2.6.20.15.14) to 2.6.20.16.28.1
linux-image-generic (2.6.20.15.14) to 2.6.20.16.28.1
linux-restricted-modules-386 (2.6.20.15.14) to 2.6.20.16.28.1
linux-restricted-modules-generic (2.6.20.15.14) to 2.6.20.16.28.1

Installed the following packages:
linux-headers-2.6.20-16 (2.6.20-16.28)
linux-headers-2.6.20-16-generic (2.6.20-16.28)
linux-image-2.6.20-16-386 (2.6.20-16.28)
linux-image-2.6.20-16-generic (2.6.20-16.28)
linux-restricted-modules-2.6.20-16-386 (2.6.20.5-16.28)
linux-restricted-modules-2.6.20-16-generic (2.6.20.5-16.28)

Is there anyway for me to easily fix this?  Is this going to require a
bug being filed?

Cheers,
Whytey

--
ubuntu-au mailing list
ubuntu-au at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-au