On Wed, 2006-09-20 at 02:55 +0000, Richard Kleeman wrote:
> I am booting from a Dapper /boot/grub/menu.lst and am updating
> the system using chroot and aptitude on the mounted Edgy partition (/test). Could this be the problem?
Well, I can't support an install/upgrade with this method. I have no
idea what affect it will have.
> BTW the Edgy knot 2 livecd also failed to boot apparently for the same
> reason.
Try the Knot3 CD.
> I looked in the /boot/grub/menu.lst and found that
> kopt_2_6
>
> was always commented out (i.e. there was always a # at the beginning of
> the line). Does this mean it is really commented or do I need to remove
> all lines with it and run grub-update?
>
> BTW this was the case in the /test/boot/grub/menu.lst file as well...
Remove it, it gets used by update-grub if it exists (commented out just
means it gets ignored by the grub program itself). It's used to create
the main menu entries.
On Wed, 2006-09-20 at 02:55 +0000, Richard Kleeman wrote:
> I am booting from a Dapper /boot/grub/menu.lst and am updating
> the system using chroot and aptitude on the mounted Edgy partition (/test). Could this be the problem?
Well, I can't support an install/upgrade with this method. I have no
idea what affect it will have.
> BTW the Edgy knot 2 livecd also failed to boot apparently for the same
> reason.
Try the Knot3 CD.
> I looked in the /boot/grub/menu.lst and found that grub/menu. lst file as well...
> kopt_2_6
>
> was always commented out (i.e. there was always a # at the beginning of
> the line). Does this mean it is really commented or do I need to remove
> all lines with it and run grub-update?
>
> BTW this was the case in the /test/boot/
Remove it, it gets used by update-grub if it exists (commented out just
means it gets ignored by the grub program itself). It's used to create
the main menu entries.