> Precisely, uInitrd is old. And that is no good.
As stated, i've installed some package (mdadm, lvm2) that trigger an initrd rebuild, but i've not put / (root) filesystem on software raid or LVM, so i've not re mkimage-ed it.
> And furthermore, even you did not see newer
> mainline kernel files afer apt-get dist-upgrade
> this time, it does not mean that you want to do
> that in the future.
> I'm speaking in general to other users who are
> reading this, too.
This is true. Generally speaking doing a dist upgrade can be dangerous, without some caution...
As stated, i've installed some package (mdadm, lvm2) that trigger an initrd rebuild, but i've not put / (root) filesystem on software raid or LVM, so i've not re mkimage-ed it.
> And furthermore, even you did not see newer
> mainline kernel files afer apt-get dist-upgrade
> this time, it does not mean that you want to do
> that in the future.
> I'm speaking in general to other users who are
> reading this, too.
This is true. Generally speaking doing a dist upgrade can be dangerous, without some caution...