Hello
I also encountered this bug after upgrading the kernel today.
A quick workaround was to
* boot using a grml64 CD
* mount the /, /usr and /var partions
* chroot to the partions
* execute "lilo -v"
* reboot
I now wonder if the system is permanently "fixed" or if it might randomly
hang
reopen 505609
reassign 505609 lilo
thanks
Le vendredi 14 novembre 2008 12:42:06 Debian Bug Tracking System, vous avez
écrit :
> De : Bastian Blank <[EMAIL PROTECTED]>
> On Thu, Nov 13, 2008 at 08:54:32PM +0100, Xavier Brochard wrote:
> > When reboting I obtain this message from Lilo:
> > "Loading
Le jeudi 13 novembre 2008 22:48:10, vous avez écrit :
> On Thu, 2008-11-13 at 20:54 +0100, Xavier Brochard wrote:
> > Package: linux-image-2.6.26-1-amd64
> > Version: 2.6.26-10
> > Severity: critical
> >
> > I've did an upgrade on 2008-11-09, on a new installed system, upgrading
> > kernel 2.6.26-0
On Thu, 2008-11-13 at 20:54 +0100, Xavier Brochard wrote:
> Package: linux-image-2.6.26-1-amd64
> Version: 2.6.26-10
> Severity: critical
>
> I've did an upgrade on 2008-11-09, on a new installed system, upgrading
> kernel
> 2.6.26-09 to 2.6.26.10. Apt was also upgraded.
> I've seen nothing stra
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-10
Severity: critical
I've did an upgrade on 2008-11-09, on a new installed system, upgrading kernel
2.6.26-09 to 2.6.26.10. Apt was also upgraded.
I've seen nothing strange during upgrade and in the apt and dpkg logs. The
system is entirely on
5 matches
Mail list logo