On Mon, 2011-03-21 at 08:16 +0100, Cesare Leonardi wrote: > 2011/3/19 Cesare Leonardi <celeo...@gmail.com>: > > --------------- > > The boot loader configuration for this system was not recognized. These > > settings in the configuration may need to be updated: > > > > * The root device ID passed as a kernel parameter; > > * The boot device ID used to install and update the boot loader. > > > > You should generally identify these devices by UUID or > > label. However, on MIPS systems the root device must be > > identified by name. > > --------------- > > Same message on a Sid notebook i use at work and that i've updated this > morning. > If that helps here is the relevant (IMHO) upgrades that happened on this pc: > firmware-linux-free 2.6.37 -> 3 > grub 0.97-64 -> 0.97-65 > grub-common 1.99~rc1-3 -> 1.99~rc1-4 > grub-pc 1.99~rc1-3 -> 1.99~rc1-4 > linux-base 3~experimental -> 3 > linux-image-2.6-686 2.6.37-2 -> 2.6.38-1 [...]
If you upgraded all of these at the same time, maybe grub-common was in the unpacked state (rather than installed) when linux-base checked it, and that would explain this behaviour. There are some places where it matters whether a package is fully installed, but in other places it should treat a package in the unpacked state in the same way. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
