Well, I don't understand how this went wrong and it's probably fixed
now.
Next time you update the kernel (for a security update or point
release), please check after rebooting that the new version is actually
running (use 'cat /proc/version'). If the same thing happened, then
open a new bug
On Fri, 2013-05-24 at 06:06 +0200, nobswolf wrote:
Am 21.05.2013 02:54, schrieb Ben Hutchings:
A kernel installation should run update-grub anyway, so running
that only 'solves the problem' until the next security update that
doesn't get properly installed.
For some reason in file
Am 24.05.2013 14:02, schrieb Ben Hutchings:
Do you remember which release you originally installed?
No idea by myself, but:
root@okami:~# cat /var/log/installer/lsb-release
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build
Am 21.05.2013 02:54, schrieb Ben Hutchings:
A kernel installation should run update-grub anyway, so running
that only 'solves the problem' until the next security update that
doesn't get properly installed.
For some reason in file /etc/kernel-img.conf the entry do_bootloader
was set to no.
Although this problem is not kernel related I leave the solution here
for completeness:
For some reason a manual update of GRUB was needed, so ...
update-grub
grub-install ...
... solved the problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
On Mon, 2013-05-20 at 09:12 +0200, nobswolf wrote:
Although this problem is not kernel related I leave the solution here
for completeness:
For some reason a manual update of GRUB was needed, so ...
update-grub
grub-install ...
... solved the problem.
A kernel installation should run
6 matches
Mail list logo
