[Bug 463401] Re: package linux-image-generic 2.6.24.25.27 failed to install/upgrade: dependency problems - leaving unconfigured

Stefan Bader stefan.bader at canonical.com
Mon Nov 2 22:32:35 UTC 2009


martinba wrote:
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/sda6             289G   13G  262G   5% /
> /dev/sda3             193M  192M     0 100% /boot

/ is ok, in your case /boot is completely full. The reason is very likely,
that you have gathered quite a lot of older kernels. if you do a

#> ls -la /boot/vmlinuz-*

you should see a list of kernels. chose the oldest number (be aware the sort
order is lexically not numerically, so 2.6.24-2 would show up after 2.6.24-10,
but 2.6.24-10 is newer).
Say you want to delete 2.6.24-2 (I just picked a random number), then you would
type this command to see which packages related to this kernel are installed:

#> dpkg -l | grep -- -2.6.24-2-

Likely there will be a linux-image, a linux-ubuntu-modules and a
linux-restricted-modules (maybe linux-headers and linux-backports-modules).

Now you would remove those with:

#> sudo dpkg --purge <put here the package names from above seperated
with space>

Be careful not to delete the currently running kernel version (likely 2.6.24-24).
If you post the output of the "ls -la" shown above, I can help you on the selection.
But if you start with the oldest one and check the "df" output for /boot you could
see when you again have 20-30M free, which should be enough.

-- 
package linux-image-generic 2.6.24.25.27 failed to install/upgrade: dependency problems - leaving unconfigured
https://bugs.launchpad.net/bugs/463401
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.




More information about the kernel-bugs mailing list